Quick SNITCH

A quantitative guide to the degree of difficulty of the Times Quick Cryptic Crossword

Times Quick Cryptic Crossword 2312

Date 18 January 2023
Number 2312
Setter Pedro
Day of week Wednesday
NITCH 120
Count of ref solvers 64
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2312

* Requires access to the Times Crossword Club

Detailed solving results

 

If you would like to help cover the costs of running the SNITCH site, please "buy me a coffee".

Reference, Tracked and Blog solvers with error-free solutions to this puzzle are shown below.

We also show the solver's Personal NITCH, which is their result on this puzzle compared to their average time, and the Wavelength Index of Times Cryptic Hardness, the WITCH, which is the Personal NITCH compared to the SNITCH.

Name TfTT Name Average time This time Personal NITCH WITCH
mohn 02:07 02:05 98 81
cmjhutton 02:18 02:53 125 104
Jason 02:35 03:16 126 105
verlaine 02:38 03:23 128 106
mistigris 02:39 03:18 124 103
hilarym 02:50 02:42 95 79
aphis99 aphis99 02:51 03:39 128 106
Flimmy flammy 03:11 04:14 132 110
richard 03:37 04:11 115 95
markdobell 03:39 05:13 142 118
Heyesey 03:41 07:13 195 162
AlanS 03:55 05:37 143 119
glheard 04:06 04:30 109 90
Topical Tim Topical Tim 04:11 03:52 92 76
lickert 04:15 05:33 130 108
MikeOsborne 04:17 04:39 108 90
Roscoe 04:32 06:33 144 120
tilbee 04:40 05:27 116 96
philjordan1147 BUSMAN 04:46 04:12 88 73
Tom Stubbs Tom Stubbs 04:46 06:08 128 106
alexh 04:47 04:37 96 80
scrabbler 04:51 05:42 117 97
canismiser 04:52 08:55 183 152
andrewlake 04:53 05:58 122 101
LouWeed LouWeed 04:53 04:20 88 73
andy 04:55 05:20 108 90
fshephe 04:56 07:35 153 127
d.middleton 04:57 05:37 113 94
Johninterred 05:00 07:12 144 120
neilr neilr 05:02 06:06 121 100
March 05:03 07:08 141 117
Ed freshpot 05:04 04:00 78 65
Honggui 05:06 05:17 103 85
Zander 05:14 06:58 133 110
7dPenguin 7dPenguin 05:16 06:41 126 105
Tibthorpe 05:19 05:50 109 90
esmeralda 05:38 07:38 135 112
Finzi 05:39 06:47 120 100
Crossiant 05:42 07:16 127 105
mcrossib1 05:45 05:52 102 85
Penfold_61 05:48 07:21 126 105
Rabbitoh galspray 05:49 06:15 107 89
Looch 05:58 06:19 105 87
hopkinb hopkinb 06:07 07:40 125 104
Carol 06:20 07:06 112 93
Shabbo 06:32 05:44 87 72
Tudds 06:38 06:05 91 75
GMcD 06:38 06:09 92 76
Michael Dove 06:39 07:58 119 99
Curarist 06:42 06:11 92 76
endafk 06:42 07:48 116 96
jon 06:47 09:22 138 115
uvofiz 07:01 07:49 111 92
James P 07:05 08:38 121 100
Gussie 07:08 07:55 110 91
Aloysius 07:11 06:00 83 69
earlylight 07:24 07:12 97 80
Puzzleplease 07:27 07:26 99 82
Desdeeloeste Desdeeloeste 07:31 07:42 102 85
Mike Harper Mike Harper 07:35 11:28 151 125
TomHerbert 07:44 06:42 86 71
Dvynys Dvynys 07:45 11:09 143 119
Corymbia Corymbia 07:47 06:33 84 70
ChrisBrea 07:51 06:54 87 72
John Arnold 08:12 07:56 96 80
Sheen 08:15 08:33 103 85
johndun John Dunleavy 08:40 08:52 102 85
m5harp 08:46 08:53 101 84
alastair52 08:50 08:01 90 75
RPY 08:52 08:55 100 83
luxtonj61 08:55 09:01 101 84
kath 09:02 09:07 100 83
timbo 09:11 08:29 92 76
annbrew 09:28 05:44 60 50
barracuda barracuda 09:28 08:16 87 72
Cedric Statherby 11:34 13:00 112 93
WordPlodder BletchleyReject 11:52 11:56 100 83
chabuduo chabuduo 12:22 19:05 154 128
Doofenschmirtz Doofenschmirtz 15:25 18:52 122 101
bangsar DearHector 21:12 23:41 111 92
mozbadel mozbadel 24:24 26:35 108 90

A guide to the solver status

Legend
 Reference solver used for SNITCH
 Other Reference solver
 Tracked solver
 Blog solver

Blog Solvers

Blog Solvers are those who have allowed their times to be taken from the Times for the Times blog.

Notes for Blog Solvers:

  • the most reliable format for reporting times is with format "mm:ss" or as "x minutes" in the title or at the start of the entry
  • only the first main comment for each blogger is used; responses to other comments or a second comment is ignored
  • to report errors, include "n errors" just after the time
  • If you just have a time it is assumed you have no errors unless you mention DNF or pink squares or giving up, etc, in the text
  • Examples of good time notifications are "38:30, 0 errors" and "39 minutes, 0 errors" in the comment title or as the first part of your comment

Notes

The definition of Reference and Tracked solvers is described on the Neutrinos page.

The results for Reference solvers are normally used to calcuate the SNITCH. When this happens they are shown in the list with a solid blue line to the left. In the previous SNITCH results listing for each crossword, these were the only entries shown.

The most common causes for Reference solver results not to be used are: (a) that they did not meet the criteria this month to be used as a reference (e.g. they may not have completed enough puzzles on each day of the week) or (b) they have been pushed out of the top 100 on the leader board. In these cases, the results are now shown, but their data is not used for the SNITCH calculation.

Where there is data for Tracked solvers, I show them also in this table. The solving data is not always available, as the Crossword Club site only shows the top 100 solvers to everyone. Logged-in users get their own leaderboard position and those around them, but this is not available to everyone. So the SNITCH site only gets data for those who have made the top 100 in the leaderboard at some point during the day.

As a result there are a few geographically advantaged solvers; those of us who solve early in the day (e.g. we in the Antipodes, those in Asia and those staying up late in North America) are more likely to hit the leaderboard even with slower times. Solvers who are just as capable but solve later in the UK day might not make the top 100 and I have no way to capture their results.

You may wonder why there are Tracked solvers (in red) with low average solving times, mixed in with the Reference solvers (in blue). These are usually those that, while they don't seem to be Neutrinos, are not well aligned to the SNITCH. So I don't use them as Reference solvers in the SNITCH calculation, but still show their overall results.

You might also notice that there's some inconsistency at the tail end of the Reference solver list. My cutoff point is an average solving time of 45 minutes. But if someone around this mark is chosen as a Reference solver, their next month's results might end up being over 45 minutes and they will still be used. Alternatively, a Tracked solver might creep in under 45 minutes on the next calculation, but didn't make the cut for the prior Reference list. It's on the to-do list to see if I can make this a bit more predictable.