Quick SNITCH

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

Times Quick Cryptic Crossword 2446

Date 25 July 2023
Number 2446
Setter Wurm
Day of week Tuesday
NITCH 95
Count of ref solvers 70
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2446

* 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:24 109 114
Jason 02:32 02:26 96 101
mistigris 02:40 02:17 85 89
hilarym 02:43 02:05 76 80
cmjhutton 02:44 02:18 84 88
Flimmy flammy 03:04 04:34 148 155
richard 03:39 03:26 94 98
markdobell 03:50 04:05 106 111
Heyesey 03:52 04:03 104 109
Kinghedger 03:52 03:46 97 102
chriss 04:01 04:24 109 114
glheard 04:02 03:41 91 95
lickert 04:11 04:03 96 101
chindit 04:13 04:51 115 121
nina s 04:19 02:58 68 71
AlanS 04:19 04:51 112 117
MikeOsborne 04:21 03:17 75 78
joelhames 04:21 05:37 129 135
tilbee 04:21 04:59 114 120
Roscoe 04:26 05:23 121 127
tiggis 04:29 04:45 105 110
trux 04:29 03:52 86 90
lucyg43484 04:30 03:45 83 87
patrickcates 04:33 03:46 82 86
Tom Stubbs Tom Stubbs 04:36 03:44 81 85
Jim Willis 04:38 04:57 106 111
canismiser 04:45 04:24 92 96
LouWeed LouWeed 04:46 03:39 76 80
andy 04:46 07:05 148 155
March 04:46 05:53 123 129
alexh 04:47 05:16 110 115
Dofray 04:48 03:29 72 75
pitcaithlie Pitcaithlie 04:48 04:02 84 88
Ed freshpot 04:50 04:31 93 97
Ease This Jam 04:50 04:46 98 103
Umpire 04:54 03:29 71 74
Honggui 04:54 06:09 125 131
michaelbell53 04:58 06:41 134 141
Zander 05:02 04:03 80 84
7dPenguin 7dPenguin 05:05 04:00 78 82
Squallaby 05:09 03:39 70 73
Liari 05:09 03:55 76 80
Tibthorpe 05:12 03:51 74 77
andy_knott 05:13 05:16 100 105
Aly Duncan 05:21 04:37 86 90
esmeralda 05:23 04:33 84 88
fshephe 05:25 05:03 93 97
daulbs 05:26 05:25 99 104
ChuckB 05:26 04:46 87 91
george.plumbly 05:28 06:34 120 126
KET 05:29 04:22 79 83
Dekkers 05:31 06:42 121 127
AndyR 05:36 05:40 101 106
Finzi 05:39 05:51 103 108
Paul Hammond Paul Hammond 05:41 04:56 86 90
Looch 05:48 04:13 72 75
Kevin Gregg Kevin Gregg 05:51 05:22 91 95
SlumdogEngineer 05:54 05:11 87 91
Dzhigit 05:54 05:43 96 101
cmcnsmith 05:56 04:58 83 87
GeorgeTz 05:56 06:00 101 106
McBeak McBeak 06:00 05:55 98 103
Crossiant 06:01 06:07 101 106
DunPangolin 06:03 07:22 121 127
PGooden 06:03 05:54 97 102
Tudds 06:05 05:27 89 93
Rosron 06:07 06:04 99 104
earlylight 06:09 04:54 79 83
Curarist 06:12 06:53 111 116
ilan 06:17 06:04 96 101
James P 06:18 06:36 104 109
JMbrow29 06:19 05:48 91 95
paul.whitehouse69 06:25 04:21 67 70
Aloysius 06:28 04:37 71 74
tds 06:29 07:14 111 116
Dvynys Dvynys 06:37 06:48 102 107
robertbridge 06:38 06:20 95 100
jon 06:42 05:45 85 89
DrBill 06:42 06:29 96 101
Edprof 06:49 05:49 85 89
Hodge21 06:49 05:58 87 91
FraserH 06:56 06:03 87 91
Corymbia Corymbia 06:57 06:47 97 102
Cookincats 06:57 07:03 101 106
ratterz 07:00 06:27 92 96
Yatton50 07:02 07:22 104 109
barracuda barracuda 07:08 06:35 92 96
gsriordan52 07:20 06:22 86 90
Sheen 07:21 07:04 96 101
Templar Redux Templar 07:37 06:43 88 92
TonyN6 07:59 07:19 91 95

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.