Quick SNITCH

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

Times Quick Cryptic Crossword 2402

Date 24 May 2023
Number 2402
Setter Felix
Day of week Wednesday
NITCH 91
Count of ref solvers 68
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2402

* 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:04 94 103
Paul Gilbert 02:28 02:29 100 109
Jason 02:32 02:16 89 97
verlaine 02:36 01:45 67 73
mistigris 02:40 02:55 109 119
hilarym 02:43 02:11 80 87
cmjhutton 02:44 01:39 60 65
Flimmy flammy 03:04 01:43 55 60
Topical Tim Topical Tim 03:38 02:51 78 85
richard 03:39 02:58 81 89
markdobell 03:50 03:26 89 97
Kinghedger 03:52 03:31 90 98
Heyesey 03:52 03:41 95 104
lickert 04:11 03:43 88 96
chindit 04:13 03:41 87 95
philjordan1147 BUSMAN 04:14 03:55 92 101
AlanS 04:19 03:14 74 81
MikeOsborne 04:21 03:34 81 89
tilbee 04:21 04:03 93 102
Roscoe 04:26 04:48 108 118
David Crooks 04:27 04:58 111 121
lucyg43484 04:30 03:20 74 81
Tom Stubbs Tom Stubbs 04:36 03:21 72 79
Jim Willis 04:38 04:20 93 102
andrewlake 04:44 03:54 82 90
canismiser 04:45 04:24 92 101
andy 04:46 04:13 88 96
March 04:46 05:22 112 123
alexh 04:47 05:33 116 127
denislaw 04:47 03:49 79 86
Ed freshpot 04:50 05:35 115 126
Ease This Jam 04:50 04:29 92 101
Umpire 04:54 03:42 75 82
Honggui 04:54 05:45 117 128
Zander 05:02 04:54 97 106
7dPenguin 7dPenguin 05:05 04:46 93 102
Squallaby 05:09 03:45 72 79
neilr neilr 05:10 04:40 90 98
annbrew 05:11 04:35 88 96
Tibthorpe 05:12 05:43 109 119
fishernick79 05:19 05:55 111 121
Aly Duncan 05:21 04:22 81 89
esmeralda 05:23 05:09 95 104
daulbs 05:26 02:56 53 58
ChuckB 05:26 05:14 96 105
jimpen 05:26 05:05 93 102
mw7000 05:29 04:54 89 97
Rabbitoh 05:32 04:20 78 85
AndyR 05:36 05:16 94 103
Finzi 05:39 05:51 103 113
Shabbo 05:46 05:45 99 108
Looch 05:48 05:18 91 100
squark 05:50 06:10 105 115
Kevin Gregg Kevin Gregg 05:51 04:40 79 86
cath23 05:52 06:24 109 119
Dzhigit 05:54 06:23 108 118
Carol 05:56 05:27 91 100
McBeak McBeak 06:00 07:03 117 128
Crossiant 06:01 06:16 104 114
PGooden 06:03 06:54 114 125
Rosron 06:07 05:51 95 104
James P 06:18 06:43 106 116
robinh 06:19 05:09 81 89
andrejpanjkov 06:19 06:18 99 108
mandyroberts2007 06:20 06:38 104 114
paul.whitehouse69 06:25 05:25 84 92
Mike Harper Mike Harper 06:32 07:04 108 118
Gussie 06:35 06:06 92 101
smalley552 06:42 06:33 97 106
JeffHobbs 06:42 06:17 93 102
DrBill 06:42 06:54 102 112
alastair52 06:43 06:31 97 106
rburman 06:43 05:56 88 96
maisiemae 06:45 06:22 94 103
Puzzleplease 06:46 05:31 81 89
Hodge21 06:49 05:42 83 91
Corymbia Corymbia 06:57 05:04 72 79
ChrisBrea 06:57 07:01 100 109
Bobby D 06:58 06:00 86 94
barracuda barracuda 07:08 07:04 99 108
Sheen 07:21 06:37 90 98
vinyl12345 vinyl1 07:53 06:18 79 86
mattindoha 07:57 07:04 88 96

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.