Quick SNITCH

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

Times Quick Cryptic Crossword 2411

Date 06 June 2023
Number 2411
Setter Hawthorn
Day of week Tuesday
NITCH 106
Count of ref solvers 73
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2411

* 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:23 109 102
Jason 02:32 02:19 91 85
verlaine 02:36 02:28 94 88
mistigris 02:40 02:43 101 95
hilarym 02:43 03:34 131 123
cmjhutton 02:44 02:24 87 82
aphis99 aphis99 02:49 03:13 114 107
Flimmy flammy 03:04 03:13 104 98
Topical Tim Topical Tim 03:38 04:52 133 125
richard 03:39 03:35 98 92
markdobell 03:50 04:08 107 100
Heyesey 03:52 03:31 90 84
glheard 04:02 04:26 109 102
Strober 04:04 04:55 120 113
lickert 04:11 04:03 96 90
chindit 04:13 04:54 116 109
philjordan1147 BUSMAN 04:14 04:11 98 92
AlanS 04:19 05:22 124 116
MikeOsborne 04:21 04:19 99 93
tilbee 04:21 05:07 117 110
Roscoe 04:26 04:29 101 95
trux 04:29 05:33 123 116
lucyg43484 04:30 04:24 97 91
Tom Stubbs Tom Stubbs 04:36 05:56 128 120
Jim Willis 04:38 03:55 84 79
andrewlake 04:44 04:42 99 93
canismiser 04:45 04:35 96 90
March 04:46 04:33 95 89
LouWeed LouWeed 04:46 05:17 110 103
andy 04:46 07:04 148 139
alexh 04:47 04:39 97 91
pitcaithlie Pitcaithlie 04:48 04:13 87 82
Ed freshpot 04:50 05:43 118 111
MK76 04:53 04:53 100 94
Umpire 04:54 05:51 119 112
Honggui 04:54 04:49 98 92
michaelbell53 04:58 04:42 94 88
Zander 05:02 04:47 95 89
7dPenguin 7dPenguin 05:05 06:31 128 120
Squallaby 05:09 03:40 71 66
Liari 05:09 05:12 100 94
neilr neilr 05:10 04:39 90 84
Tibthorpe 05:12 06:43 129 121
footballblue 05:17 05:09 97 91
esmeralda 05:23 06:31 121 114
fshephe 05:25 05:40 104 98
jimpen 05:26 05:57 109 102
daulbs 05:26 06:18 115 108
ChuckB 05:26 06:47 124 116
george.plumbly 05:28 06:39 121 114
KET 05:29 05:24 98 92
Rabbitoh 05:32 04:28 80 75
AndyR 05:36 06:47 121 114
Finzi 05:39 06:05 107 100
Paul Hammond Paul Hammond 05:41 05:24 95 89
Looch 05:48 07:17 125 117
cheryllayne cheryllayne 05:50 05:09 88 83
squark 05:50 06:56 118 111
Kevin Gregg Kevin Gregg 05:51 07:13 123 116
cath23 05:52 06:21 108 101
Dzhigit 05:54 06:09 104 98
Carol 05:56 06:04 102 96
cmcnsmith 05:56 06:12 104 98
McBeak McBeak 06:00 06:13 103 97
DunPangolin 06:03 06:30 107 100
Jeremy Weissmann plusjeremy 06:05 06:35 108 101
Tudds 06:05 06:05 100 94
GMcD 06:08 06:47 110 103
earlylight 06:09 05:55 96 90
Curarist 06:12 05:31 88 83
ilan 06:17 06:18 100 94
Michael Dove 06:23 05:22 84 79
uvofiz 06:30 07:04 108 101
Mike Harper Mike Harper 06:32 07:05 108 101
Gussie 06:35 06:23 96 90
Nangle 06:41 06:43 100 94
jon 06:42 05:39 84 79
KenD51 06:42 06:09 91 85
Puzzleplease 06:46 07:29 110 103
1234 06:48 06:51 100 94
endafk 06:48 07:32 110 103
ChrisBrea 06:57 06:49 98 92
ratterz 07:00 07:15 103 97
barracuda barracuda 07:08 05:38 78 73
docg 07:15 06:03 83 78
luxtonj61 07:21 07:25 100 94
AndyLast 07:35 07:41 101 95
CoxBurglar 07:37 07:14 94 88
vinyl12345 vinyl1 07:53 06:09 78 73
branch branch 08:11 07:14 88 83

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.