Quick SNITCH

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

Times Quick Cryptic Crossword 2401

Date 23 May 2023
Number 2401
Setter Mara
Day of week Tuesday
NITCH 81
Count of ref solvers 68
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2401

* 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:19 106 130
Paul Gilbert 02:28 02:11 88 108
Jason 02:32 01:46 69 85
verlaine 02:36 02:06 80 98
mistigris 02:40 02:13 83 102
hilarym 02:43 02:32 93 114
cmjhutton 02:44 01:44 63 77
aphis99 aphis99 02:49 02:03 72 88
Flimmy flammy 03:04 02:34 83 102
Topical Tim Topical Tim 03:38 02:26 66 81
richard 03:39 02:27 67 82
markdobell 03:50 03:56 102 125
Heyesey 03:52 03:46 97 119
Kinghedger 03:52 03:32 91 112
glheard 04:02 03:40 90 111
Strober 04:04 03:57 97 119
xyster 04:04 03:14 79 97
lickert 04:11 02:59 71 87
chindit 04:13 03:05 73 90
philjordan1147 BUSMAN 04:14 04:27 105 129
AlanS 04:19 03:49 88 108
MikeOsborne 04:21 03:32 81 100
tilbee 04:21 04:20 99 122
Roscoe 04:26 04:20 97 119
trux 04:29 03:33 79 97
lucyg43484 04:30 02:56 65 80
jfisher60 04:33 02:33 56 69
Tom Stubbs Tom Stubbs 04:36 03:39 79 97
John Walsh 04:37 04:22 94 116
Jim Willis 04:38 03:13 69 85
d.middleton 04:39 05:17 113 139
scrabbler 04:39 03:51 82 101
andrewlake 04:44 03:11 67 82
andy 04:46 03:38 76 93
March 04:46 03:30 73 90
LouWeed LouWeed 04:46 03:32 74 91
pitcaithlie Pitcaithlie 04:48 03:20 69 85
Ed freshpot 04:50 03:43 76 93
MK76 04:53 03:26 70 86
Umpire 04:54 04:29 91 112
7dPenguin 7dPenguin 05:05 03:42 72 88
Squallaby 05:09 04:23 85 104
Paul Bacon 05:09 05:11 100 123
neilr neilr 05:10 04:30 87 107
annbrew 05:11 04:47 92 113
Tibthorpe 05:12 04:17 82 101
fishernick79 05:19 04:58 93 114
Aly Duncan 05:21 03:11 59 72
esmeralda 05:23 04:03 75 92
fshephe 05:25 05:18 97 119
daulbs 05:26 04:00 73 90
ChuckB 05:26 04:41 86 106
jimpen 05:26 03:24 62 76
george.plumbly 05:28 04:05 74 91
KET 05:29 05:01 91 112
mw7000 05:29 03:49 69 85
Rabbitoh 05:32 05:23 97 119
john.marshall 05:33 04:45 85 104
Finzi 05:39 04:28 79 97
Paul Hammond Paul Hammond 05:41 04:41 82 101
Kevin Gregg Kevin Gregg 05:51 04:59 85 104
SlumdogEngineer 05:54 05:33 94 116
Dzhigit 05:54 05:16 89 109
Carol 05:56 05:27 91 112
cmcnsmith 05:56 05:48 97 119
McBeak McBeak 06:00 03:54 65 80
nigel 06:00 05:17 88 108
Crossiant 06:01 04:45 78 96
Tudds 06:05 05:21 87 107
Rosron 06:07 04:32 74 91
GMcD 06:08 05:13 85 104
robinh 06:19 04:45 75 92
Michael Dove 06:23 03:49 59 72
paul.whitehouse69 06:25 05:05 79 97
Mike Harper Mike Harper 06:32 05:02 77 95
Gussie 06:35 05:43 86 106
KenD51 06:42 05:33 82 101
jon 06:42 04:43 70 86
John Arnold 06:44 05:22 79 97
maisiemae 06:45 05:54 87 107
endafk 06:48 05:51 86 106
Hodge21 06:49 05:49 85 104
Cookincats 06:57 05:13 75 92
m5harp 07:15 05:09 71 87
gsriordan52 07:20 05:22 73 90
mattindoha 07:57 05:44 72 88
nigelmzzz 08:44 05:41 65 80

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.