Quick SNITCH

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

Times Quick Cryptic Crossword 2450

Date 31 July 2023
Number 2450
Setter Jalna
Day of week Monday
NITCH 93
Count of ref solvers 71
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2450

* 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:41 122 131
Paul Gilbert 02:28 02:44 110 118
Jason 02:32 02:12 86 92
verlaine 02:36 02:17 87 93
mistigris 02:40 02:29 93 100
hilarym 02:43 02:55 107 115
cmjhutton 02:44 02:04 75 80
aphis99 aphis99 02:49 02:28 87 93
Flimmy flammy 03:04 03:43 121 130
Topical Tim Topical Tim 03:38 04:00 110 118
richard 03:39 03:42 101 108
markdobell 03:50 03:15 84 90
Heyesey 03:52 03:11 82 88
Kinghedger 03:52 02:56 75 80
chriss 04:01 04:18 107 115
glheard 04:02 04:31 111 119
Strober 04:04 03:31 86 92
lickert 04:11 04:20 103 110
chindit 04:13 03:57 93 100
philjordan1147 BUSMAN 04:14 03:15 76 81
AlanS 04:19 05:08 118 126
joelhames 04:21 05:25 124 133
tilbee 04:21 04:13 96 103
Roscoe 04:26 04:48 108 116
trux 04:29 03:41 82 88
lucyg43484 04:30 05:42 126 135
patrickcates 04:33 04:06 90 96
Tom Stubbs Tom Stubbs 04:36 04:46 103 110
John Walsh 04:37 04:33 98 105
d.middleton 04:39 05:01 107 115
andrewlake 04:44 04:49 101 108
edschrono 04:44 04:24 92 98
canismiser 04:45 04:21 91 97
andy 04:46 05:43 119 127
LouWeed LouWeed 04:46 04:10 87 93
alexh 04:47 04:00 83 89
MK76 04:53 05:29 112 120
Umpire 04:54 03:53 79 84
Honggui 04:54 04:39 94 101
Zander 05:02 04:33 90 96
7dPenguin 7dPenguin 05:05 05:22 105 112
The Dabbler 05:05 04:35 90 96
Squallaby 05:09 03:51 74 79
Liari 05:09 03:40 71 76
neilr neilr 05:10 04:00 77 82
Tibthorpe 05:12 05:38 108 116
andy_knott 05:13 04:35 87 93
Penfold_61 05:18 04:45 89 95
Aly Duncan 05:21 04:48 89 95
esmeralda 05:23 03:49 70 75
fshephe 05:25 05:20 98 105
daulbs 05:26 03:58 73 78
ChuckB 05:26 05:46 106 113
george.plumbly 05:28 04:46 87 93
KET 05:29 04:25 80 86
mw7000 05:29 05:01 91 97
Rabbitoh 05:32 04:38 83 89
AndyR 05:36 05:42 101 108
Finzi 05:39 05:42 100 107
Paul Hammond Paul Hammond 05:41 04:23 77 82
Shabbo 05:46 05:26 94 101
Looch 05:48 05:56 102 109
cheryllayne cheryllayne 05:50 02:48 48 51
squark 05:50 05:18 90 96
cath23 05:52 05:36 95 102
SlumdogEngineer 05:54 05:48 98 105
McBeak McBeak 06:00 04:18 71 76
nigel 06:00 04:58 82 88
Crossiant 06:01 05:27 90 96
DunPangolin 06:03 05:25 89 95
PGooden 06:03 05:22 88 94
Tudds 06:05 04:57 81 87
Jeremy Weissmann plusjeremy 06:05 05:49 95 102
Rosron 06:07 06:01 98 105
GMcD 06:08 05:58 97 104
martinphillips 06:09 05:11 84 90
Curarist 06:12 05:41 91 97
ilan 06:17 05:27 86 92
Aloysius 06:28 05:48 89 95
hipponym 06:31 05:39 86 92
Dvynys Dvynys 06:37 06:03 91 97
Nangle 06:41 05:30 82 88
Riche Riche 06:43 05:42 84 90
alastair52 06:43 06:03 90 96
Kalakuta72 06:45 04:59 73 78
Puzzleplease 06:46 05:24 79 84
endafk 06:48 06:11 90 96
FraserH 06:56 04:47 68 73
Corymbia Corymbia 06:57 05:24 77 82
ratterz 07:00 05:51 83 89
suethepotterer 09:07 04:09 45 48

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.