Quick SNITCH

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

Times Quick Cryptic Crossword 2461

Date 15 August 2023
Number 2461
Setter Izetti
Day of week Tuesday
NITCH 119
Count of ref solvers 48
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2461

* 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
Paul Gilbert 02:28 02:26 98 82
Jason 02:32 03:06 122 102
verlaine 02:36 03:00 115 96
mistigris 02:40 03:16 122 102
hilarym 02:43 02:54 106 89
cmjhutton 02:44 03:10 115 96
aphis99 aphis99 02:49 02:32 89 74
Topical Tim Topical Tim 03:38 03:27 94 78
richard 03:39 04:37 126 105
markdobell 03:50 03:23 88 73
Heyesey 03:52 04:47 123 103
lickert 04:11 03:54 93 78
chindit 04:13 03:52 91 76
philjordan1147 BUSMAN 04:14 04:49 113 94
nina s 04:19 02:20 54 45
AlanS 04:19 04:13 97 81
tilbee 04:21 04:42 108 90
Roscoe 04:26 03:38 81 68
Tom Stubbs Tom Stubbs 04:36 05:04 110 92
canismiser 04:45 05:38 118 99
andy 04:46 05:13 109 91
LouWeed LouWeed 04:46 05:51 122 102
alexh 04:47 05:20 111 93
pitcaithlie Pitcaithlie 04:48 05:40 118 99
Umpire 04:54 04:54 100 84
The Dabbler 05:05 06:28 127 106
7dPenguin 7dPenguin 05:05 06:03 119 100
Squallaby 05:09 11:21 220 184
Penfold_61 05:18 05:32 104 87
daulbs 05:26 08:10 150 126
ChuckB 05:26 05:24 99 83
Spanna 05:27 05:06 93 78
KET 05:29 07:45 141 118
Finzi 05:39 06:41 118 99
cheryllayne cheryllayne 05:50 18:42 320 268
Kevin Gregg Kevin Gregg 05:51 07:27 127 106
McBeak McBeak 06:00 09:10 152 127
Crossiant 06:01 06:31 108 90
DunPangolin 06:03 07:02 116 97
PGooden 06:03 07:41 126 105
Jeremy Weissmann plusjeremy 06:05 10:00 164 137
Blackbeard 06:11 13:50 223 187
Curarist 06:12 06:33 105 88
jimwetzler 06:16 06:52 109 91
James P 06:18 17:12 273 229
robinh 06:19 06:48 107 89
JMbrow29 06:19 24:32 388 326
Wyn Lewis Wyn Lewis 06:28 07:30 115 96
tds 06:29 08:21 128 107
uvofiz 06:30 09:45 150 126
julian_w 06:34 03:53 59 49
valerian1967 06:35 08:00 121 101
KenD51 06:42 08:28 126 105
jon 06:42 07:41 114 95
Riche Riche 06:43 10:11 151 126
John Arnold 06:44 07:23 109 91
Cookincats 06:57 08:37 123 103
ChrisBrea 06:57 10:13 147 123
ratterz 07:00 09:44 139 116
benedick 07:04 08:03 113 94
goldenpie 07:06 10:13 143 120
Doyler 07:15 14:15 196 164
gsriordan52 07:20 08:04 110 92
Sheen 07:21 10:13 139 116
dec 07:26 14:46 198 166
Dan W 07:27 23:10 310 260
crosswordian 07:46 07:45 99 83
TomHerbert 07:52 09:49 124 104
jaraab 07:54 10:13 129 108
Laputan 08:18 12:18 148 124
goblin 08:21 10:39 127 106
nigelmzzz 08:44 10:29 120 100
Mkgnao Mkgnao 08:53 09:53 111 93
Dr. Memory 08:56 10:30 117 98
Rhys 08:58 15:31 173 145
BertieVII 09:06 11:42 128 107
suethepotterer 09:07 18:51 206 173
Destime 09:18 10:13 109 91
edwards.robert1 09:41 11:51 122 102
Troothful 11:26 17:41 154 129
paulmcl 11:32 14:36 126 105
ifincham2 11:32 14:55 129 108
albrecht1959 11:45 15:17 130 109
Rozz 12:19 12:19 100 84

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.