Quick SNITCH

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

Times Quick Cryptic Crossword 2410

Date 05 June 2023
Number 2410
Setter Myles
Day of week Monday
NITCH 77
Count of ref solvers 74
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2410

* 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 01:56 88 114
Paul Gilbert 02:28 01:39 66 85
Jason 02:32 01:51 73 94
hilarym 02:43 01:49 66 85
cmjhutton 02:44 02:02 74 96
aphis99 aphis99 02:49 02:03 72 93
Flimmy flammy 03:04 02:24 78 101
Topical Tim Topical Tim 03:38 02:46 76 98
richard 03:39 02:42 73 94
markdobell 03:50 02:46 72 93
Kinghedger 03:52 02:45 71 92
Heyesey 03:52 04:55 127 164
chriss 04:01 03:48 94 122
glheard 04:02 03:06 76 98
Strober 04:04 03:41 90 116
lickert 04:11 03:07 74 96
chindit 04:13 03:45 88 114
philjordan1147 BUSMAN 04:14 03:02 71 92
chriswords 04:14 04:29 105 136
PaulCooke 04:19 04:24 101 131
AlanS 04:19 03:24 78 101
MikeOsborne 04:21 03:39 83 107
tilbee 04:21 03:42 85 110
trux 04:29 03:40 81 105
lucyg43484 04:30 02:28 54 70
Tom Stubbs Tom Stubbs 04:36 04:45 103 133
John Walsh 04:37 04:49 104 135
d.middleton 04:39 04:42 101 131
andrewlake 04:44 03:33 75 97
canismiser 04:45 03:28 72 93
wwalker50 04:45 03:19 69 89
andy 04:46 02:52 60 77
March 04:46 04:11 87 112
LouWeed LouWeed 04:46 02:53 60 77
alexh 04:47 04:34 95 123
Dofray 04:48 04:33 94 122
pitcaithlie Pitcaithlie 04:48 03:42 77 100
Ed freshpot 04:50 03:38 75 97
Ease This Jam 04:50 02:01 41 53
MK76 04:53 03:17 67 87
Umpire 04:54 04:26 90 116
Honggui 04:54 05:02 102 132
michaelbell53 04:58 03:56 79 102
Zander 05:02 03:45 74 96
7dPenguin 7dPenguin 05:05 03:46 74 96
Squallaby 05:09 03:47 73 94
neilr neilr 05:10 04:44 91 118
Tibthorpe 05:12 03:57 75 97
Penfold_61 05:18 05:28 103 133
Aly Duncan 05:21 03:42 69 89
esmeralda 05:23 03:52 71 92
daulbs 05:26 03:37 66 85
jimpen 05:26 03:56 72 93
ChuckB 05:26 04:56 90 116
george.plumbly 05:28 04:30 82 106
jdrubin 05:29 04:34 83 107
KET 05:29 03:34 65 84
Rabbitoh 05:32 04:37 83 107
AndyR 05:36 04:44 84 109
Finzi 05:39 04:12 74 96
Paul Hammond Paul Hammond 05:41 04:03 71 92
Shabbo 05:46 05:09 89 115
Kevin Gregg Kevin Gregg 05:51 04:17 73 94
SlumdogEngineer 05:54 04:58 84 109
Dzhigit 05:54 04:43 79 102
Mark Three 05:58 05:24 90 116
McBeak McBeak 06:00 03:11 53 68
Crossiant 06:01 05:15 87 112
DunPangolin 06:03 05:03 83 107
Tudds 06:05 04:36 75 97
Jeremy Weissmann plusjeremy 06:05 05:20 87 112
Rosron 06:07 04:16 69 89
GMcD 06:08 05:16 85 110
earlylight 06:09 04:40 75 97
Curarist 06:12 05:02 81 105
ilan 06:17 04:32 72 93
Aloysius 06:28 04:18 66 85
uvofiz 06:30 05:19 81 105
Mike Harper Mike Harper 06:32 05:13 79 102
Gussie 06:35 04:55 74 96
Nangle 06:41 05:30 82 106
jon 06:42 05:17 78 101
alastair52 06:43 04:46 70 90
John Arnold 06:44 04:37 68 88
Puzzleplease 06:46 05:06 75 97
Edprof 06:49 04:42 68 88
jjspomeroy 06:54 05:18 76 98
OldSolver 07:52 05:29 69 89

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.