Quick SNITCH

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

Times Quick Cryptic Crossword 2338

Date 23 February 2023
Number 2338
Setter Joker
Day of week Thursday
NITCH 117
Count of ref solvers 63
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2338

* 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:56 91 77
Paul Gilbert 02:14 02:31 112 95
cmjhutton 02:18 04:01 174 148
Jason 02:35 02:07 81 69
verlaine 02:38 04:08 156 133
mistigris 02:39 03:12 120 102
hilarym 02:50 03:35 126 107
aphis99 aphis99 02:51 03:24 119 101
Flimmy flammy 03:11 03:01 94 80
richard 03:37 04:16 117 100
markdobell 03:39 04:43 129 110
Heyesey 03:41 06:28 175 149
AlanS 03:55 04:05 104 88
Topical Tim Topical Tim 04:11 03:25 81 69
lickert 04:15 04:51 114 97
MikeOsborne 04:17 03:45 87 74
chindit 04:37 05:45 124 105
lucyg43484 04:41 05:10 110 94
Tom Stubbs Tom Stubbs 04:46 04:26 93 79
philjordan1147 BUSMAN 04:46 05:55 124 105
scrabbler 04:51 04:19 89 76
canismiser 04:52 04:52 100 85
andrewlake 04:53 04:22 89 76
fshephe 04:56 05:42 115 98
tiggis 04:57 05:05 102 87
Johninterred 05:00 05:33 111 94
neilr neilr 05:02 04:35 91 77
March 05:03 05:17 104 88
Ed freshpot 05:04 05:34 109 93
Honggui 05:06 04:33 89 76
Aly Duncan 05:07 04:40 91 77
Zander 05:14 08:49 168 143
DunPangolin 05:14 09:50 187 159
Squallaby 05:15 06:50 130 111
Tibthorpe 05:19 05:49 109 93
pitcaithlie Pitcaithlie 05:24 06:25 118 100
esmeralda 05:38 05:51 103 88
Finzi 05:39 06:34 116 99
Crossiant 05:42 07:20 128 109
mcrossib1 05:45 06:25 111 94
Encota 05:47 05:11 89 76
Rabbitoh galspray 05:49 09:19 160 136
Looch 05:58 05:17 88 75
hopkinb hopkinb 06:07 05:06 83 70
cath23 06:13 04:22 70 59
Carol 06:20 05:23 85 72
paul.whitehouse69 06:34 08:14 125 106
GMcD 06:38 06:01 90 76
Tudds 06:38 06:24 96 82
jimwetzler 06:39 08:07 122 104
endafk 06:42 07:30 111 94
Curarist 06:42 08:14 122 104
KenD51 06:57 06:37 95 81
uvofiz 07:01 07:55 112 95
James P 07:05 08:09 115 98
Gussie 07:08 08:03 112 95
Kevin Gregg Kevin Gregg 07:13 10:03 139 118
robinh 07:18 06:36 90 76
earlylight 07:24 08:21 112 95
Mike Harper Mike Harper 07:35 14:28 190 162
ChrisBrea 07:51 08:07 103 88
docg 07:56 09:58 125 106
John Arnold 08:12 09:21 114 97
plett11 Plett11 08:14 08:54 108 92
Sheen 08:15 09:18 112 95
Templar Redux Templar 08:30 10:36 124 105
johndun John Dunleavy 08:40 09:17 107 91
vinyl12345 vinyl1 08:40 10:11 117 100
goblin 08:43 09:42 111 94
m5harp 08:46 07:38 87 74
alastair52 08:50 08:13 93 79
vefatica vefatica 08:56 08:40 97 82
Edprof 09:38 07:36 78 66
Cedric Statherby 11:34 12:00 103 88
chabuduo chabuduo 12:22 19:24 156 133
Merlin_55 Merlin 14:50 19:47 133 113
Doofenschmirtz Doofenschmirtz 15:25 21:47 141 120
Dofray 22:17 08:46 39 33
mozbadel mozbadel 24:24 20:51 85 72

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.