Quick SNITCH

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

Times Quick Cryptic Crossword 2400

Date 22 May 2023
Number 2400
Setter Oink
Day of week Monday
NITCH 95
Count of ref solvers 74
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2400

* Requires access to the Times Crossword Club

Detailed solving results

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:11 02:06 96 101
Paul Gilbert 02:28 02:30 101 106
Jason 02:32 02:08 84 88
verlaine 02:36 02:17 87 91
mistigris 02:40 02:35 96 101
cmjhutton 02:44 03:01 110 115
aphis99 aphis99 02:49 02:42 95 100
Flimmy flammy 03:04 02:38 85 89
Topical Tim Topical Tim 03:38 03:13 88 92
richard 03:39 03:31 96 101
markdobell 03:50 03:51 100 105
Heyesey 03:52 03:42 95 100
glheard 04:02 06:07 151 158
lickert 04:11 04:16 101 106
chindit 04:13 04:32 107 112
philjordan1147 BUSMAN 04:14 04:02 95 100
AlanS 04:19 03:43 86 90
MikeOsborne 04:21 04:06 94 98
tilbee 04:21 03:04 70 73
Roscoe 04:26 04:49 108 113
David Crooks 04:27 04:14 95 100
tiggis 04:29 05:17 117 123
lucyg43484 04:30 04:44 105 110
Tom Stubbs Tom Stubbs 04:36 03:40 79 83
Jim Willis 04:38 06:00 129 135
andrewlake 04:44 03:38 76 80
canismiser 04:45 04:54 103 108
March 04:46 04:17 89 93
LouWeed LouWeed 04:46 03:57 82 86
alexh 04:47 04:58 103 108
denislaw 04:47 03:44 78 82
pitcaithlie Pitcaithlie 04:48 05:04 105 110
Ed freshpot 04:50 04:20 89 93
Ease This Jam 04:50 03:31 72 75
MK76 04:53 04:44 96 101
michaelbell53 04:58 03:50 77 81
Zander 05:02 05:51 116 122
Squallaby 05:09 06:16 121 127
Tibthorpe 05:12 05:16 101 106
andy_knott 05:13 05:28 104 109
footballblue 05:17 05:12 98 103
Penfold_61 05:18 04:50 91 95
Aly Duncan 05:21 04:57 92 96
fshephe 05:25 05:39 104 109
daulbs 05:26 03:17 60 63
jimpen 05:26 04:46 87 91
george.plumbly 05:28 04:55 89 93
KET 05:29 04:40 85 89
mw7000 05:29 05:36 102 107
Rabbitoh 05:32 05:15 94 98
Finzi 05:39 06:50 120 126
Paul Hammond Paul Hammond 05:41 05:25 95 100
Shabbo 05:46 05:50 101 106
Looch 05:48 05:47 99 104
squark 05:50 05:42 97 102
Kevin Gregg Kevin Gregg 05:51 05:29 93 97
cath23 05:52 05:10 88 92
Tommo87 05:53 06:11 105 110
Carol 05:56 06:18 106 111
nigel 06:00 04:23 73 76
Crossiant 06:01 05:28 90 94
DunPangolin 06:03 04:27 73 76
PGooden 06:03 04:30 74 77
Tudds 06:05 05:25 89 93
Jeremy Weissmann plusjeremy 06:05 06:06 100 105
GMcD 06:08 06:25 104 109
earlylight 06:09 06:10 100 105
Masha 06:09 06:09 100 105
Curarist 06:12 04:25 71 74
jimwetzler 06:16 06:28 103 108
James P 06:18 05:01 79 83
JMbrow29 06:19 06:13 98 103
Mike Mansbridge 06:24 06:37 103 108
Aloysius 06:28 05:44 88 92
Gussie 06:35 06:22 96 101
jon 06:42 05:42 85 89
Riche Riche 06:43 06:50 101 106
Puzzleplease 06:46 06:48 100 105
DianeRS 06:46 06:15 92 96
endafk 06:48 05:30 80 84
timbo 06:51 05:58 87 91
Deezzaa Deezzaa 06:56 06:50 98 103
Corymbia Corymbia 06:57 05:34 80 84
ChrisBrea 06:57 06:39 95 100
Yatton50 07:02 05:19 75 78
benedick 07:04 06:56 98 103
m5harp 07:15 06:49 94 98
AndyLast 07:35 05:47 76 80
Templar Redux Templar 07:37 05:39 74 77
frost 07:51 06:01 76 80
Laputan 08:18 06:30 78 82

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.