Quick SNITCH

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

Times Quick Cryptic Crossword 2310

Date 16 January 2023
Number 2310
Setter Mara
Day of week Monday
NITCH 86
Count of ref solvers 60
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2310

* 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 01:46 83 96
Paul Gilbert 02:14 02:35 115 133
cmjhutton 02:18 01:53 81 94
Jason 02:35 01:52 72 83
verlaine 02:38 02:29 94 109
mistigris 02:39 02:31 94 109
hilarym 02:50 02:26 85 98
aphis99 aphis99 02:51 02:34 90 104
Flimmy flammy 03:11 02:27 76 88
richard 03:37 03:18 91 105
markdobell 03:39 03:34 97 112
Heyesey 03:41 02:51 77 89
AlanS 03:55 04:33 116 134
glheard 04:06 03:31 85 98
lickert 04:15 03:35 84 97
MikeOsborne 04:17 03:04 71 82
John Walsh 04:27 03:57 88 102
Roscoe 04:32 03:44 82 95
chindit 04:37 05:05 110 127
tilbee 04:40 04:02 86 100
lucyg43484 04:41 03:47 80 93
Tom Stubbs Tom Stubbs 04:46 04:10 87 101
philjordan1147 BUSMAN 04:46 03:59 83 96
alexh 04:47 03:33 74 86
scrabbler 04:51 04:54 101 117
canismiser 04:52 03:12 65 75
andrewlake 04:53 02:51 58 67
LouWeed LouWeed 04:53 04:22 89 103
Paul Bacon 04:54 03:40 74 86
andy 04:55 04:19 87 101
fshephe 04:56 04:15 86 100
footballblue 04:56 04:30 91 105
d.middleton 04:57 04:35 92 106
neilr neilr 05:02 05:12 103 119
March 05:03 03:45 74 86
Ed freshpot 05:04 04:17 84 97
Honggui 05:06 03:41 72 83
Zander 05:14 03:46 71 82
Squallaby 05:15 04:08 78 90
7dPenguin 7dPenguin 05:16 04:57 93 108
ChuckB 05:18 05:15 99 115
Tibthorpe 05:19 04:47 89 103
cmcnsmith 05:25 05:21 98 113
esmeralda 05:38 03:32 62 72
Finzi 05:39 04:48 84 97
Crossiant 05:42 05:38 98 113
mcrossib1 05:45 03:57 68 79
Rabbitoh galspray 05:49 04:57 85 98
MrChumley MrChumley 05:52 05:39 96 111
Looch 05:58 05:20 89 103
KET 06:02 04:36 76 88
hopkinb hopkinb 06:07 04:10 68 79
cath23 06:13 04:02 64 74
PGooden 06:15 05:17 84 97
paul.whitehouse69 06:34 05:03 76 88
Tudds 06:38 05:14 78 90
Michael Dove 06:39 05:10 77 89
endafk 06:42 05:05 75 87
Curarist 06:42 05:09 76 88
jon 06:47 05:30 81 94
Manveru 06:50 05:19 77 89
uvofiz 07:01 05:08 73 84
Kevin Gregg Kevin Gregg 07:13 06:20 87 101
Puzzleplease 07:27 05:03 67 77
Desdeeloeste Desdeeloeste 07:31 06:41 88 102
TomHerbert 07:44 05:20 68 79
nigel 07:54 05:34 70 81
plett11 Plett11 08:14 07:55 96 111
Templar Redux Templar 08:30 06:55 81 94
johndun John Dunleavy 08:40 05:29 63 73
vinyl12345 vinyl1 08:40 07:59 92 106
annbrew 09:28 04:49 50 58
Nuck_the_king 11:07 05:36 50 58
Cedric Statherby 11:34 11:00 95 110
WordPlodder BletchleyReject 11:52 09:07 76 88
chabuduo chabuduo 12:22 08:25 68 79
Mendes Mendesest 14:04 09:00 63 73
Merlin_55 Merlin 14:50 16:00 107 124
Doofenschmirtz Doofenschmirtz 15:25 09:12 59 68
bangsar DearHector 21:12 20:46 97 112
Dofray 22:17 03:38 16 18
mozbadel mozbadel 24:24 14:10 58 67

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.