Quick SNITCH

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

Times Quick Cryptic Crossword 2448

Date 27 July 2023
Number 2448
Setter Hurley
Day of week Thursday
NITCH 82
Count of ref solvers 72
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2448

* 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:41 77 93
Paul Gilbert 02:28 01:55 77 93
Jason 02:32 01:40 65 79
verlaine 02:36 01:58 75 91
mistigris 02:40 02:10 81 98
hilarym 02:43 02:23 87 106
cmjhutton 02:44 02:01 73 89
Flimmy flammy 03:04 02:41 87 106
richard 03:39 03:16 89 108
markdobell 03:50 02:49 73 89
Heyesey 03:52 03:07 80 97
Kinghedger 03:52 03:15 84 102
glheard 04:02 03:50 95 115
Strober 04:04 03:51 94 114
lickert 04:11 03:32 84 102
chindit 04:13 03:41 87 106
philjordan1147 BUSMAN 04:14 03:44 88 107
chriswords 04:14 04:23 103 125
nina s 04:19 03:04 71 86
AlanS 04:19 03:52 89 108
MikeOsborne 04:21 03:21 77 93
tilbee 04:21 03:12 73 89
Roscoe 04:26 03:58 89 108
tiggis 04:29 03:12 71 86
trux 04:29 04:32 101 123
lucyg43484 04:30 04:18 95 115
patrickcates 04:33 03:37 79 96
jfisher60 04:33 03:34 78 95
Tom Stubbs Tom Stubbs 04:36 04:12 91 110
John Walsh 04:37 04:34 98 119
Jim Willis 04:38 05:34 120 146
canismiser 04:45 04:08 87 106
March 04:46 03:56 82 100
LouWeed LouWeed 04:46 03:17 68 82
alexh 04:47 04:15 88 107
Ease This Jam 04:50 03:51 79 96
Ed freshpot 04:50 04:29 92 112
Honggui 04:54 04:39 94 114
Umpire 04:54 05:10 105 128
Zander 05:02 04:58 98 119
7dPenguin 7dPenguin 05:05 04:06 80 97
Squallaby 05:09 03:55 76 92
Liari 05:09 04:59 96 117
neilr neilr 05:10 04:34 88 107
annbrew 05:11 04:45 91 110
Tibthorpe 05:12 05:08 98 119
andy_knott 05:13 05:22 102 124
Penfold_61 05:18 05:30 103 125
Aly Duncan 05:21 03:36 67 81
esmeralda 05:23 03:23 62 75
fshephe 05:25 04:20 80 97
daulbs 05:26 04:47 88 107
ChuckB 05:26 04:46 87 106
mw7000 05:29 04:18 78 95
Dekkers 05:31 04:43 85 103
Rabbitoh 05:32 04:16 77 93
john.marshall 05:33 04:17 77 93
AndyR 05:36 04:45 84 102
Finzi 05:39 04:48 84 102
Paul Hammond Paul Hammond 05:41 03:34 62 75
Shabbo 05:46 04:15 73 89
Looch 05:48 04:18 74 90
cheryllayne cheryllayne 05:50 05:07 87 106
cath23 05:52 04:24 75 91
Dzhigit 05:54 03:22 57 69
SlumdogEngineer 05:54 04:59 84 102
Carol 05:56 04:21 73 89
Crossiant 06:01 04:09 68 82
DunPangolin 06:03 04:36 76 92
PGooden 06:03 05:20 88 107
Tudds 06:05 04:38 76 92
Jeremy Weissmann plusjeremy 06:05 04:33 74 90
Rosron 06:07 04:57 80 97
GMcD 06:08 04:20 70 85
Curarist 06:12 04:36 74 90
jimwetzler 06:16 05:37 89 108
ilan 06:17 04:40 74 90
paul.whitehouse69 06:25 05:30 85 103
uvofiz 06:30 04:46 73 89
julian_w 06:34 04:54 74 90
alastair52 06:43 04:12 62 75
Riche Riche 06:43 04:10 62 75
1234 06:48 05:12 76 92
plett11 Plett11 06:48 05:00 73 89
raincloud 06:49 04:22 64 78
Hodge21 06:49 05:17 77 93
goldenpie 07:06 05:06 71 86
barracuda barracuda 07:08 05:27 76 92
johndun John Dunleavy 07:17 05:18 72 87
Dan W 07:27 04:06 55 67
vinyl12345 vinyl1 07:53 05:28 69 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.