Quick SNITCH

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

Times Quick Cryptic Crossword 2432

Date 05 July 2023
Number 2432
Setter Jalna
Day of week Wednesday
NITCH 89
Count of ref solvers 73
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2432

* 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 122
Paul Gilbert 02:28 02:15 91 102
Jason 02:32 02:27 96 107
verlaine 02:36 02:25 92 103
mistigris 02:40 02:23 89 100
hilarym 02:43 02:57 108 121
cmjhutton 02:44 02:35 94 105
aphis99 aphis99 02:49 02:14 79 88
Topical Tim Topical Tim 03:38 02:22 65 73
richard 03:39 03:18 90 101
markdobell 03:50 03:25 89 100
Heyesey 03:52 03:02 78 87
glheard 04:02 03:11 78 87
chindit 04:13 04:02 95 106
philjordan1147 BUSMAN 04:14 04:00 94 105
AlanS 04:19 04:58 115 129
MikeOsborne 04:21 03:20 76 85
tilbee 04:21 04:39 106 119
Roscoe 04:26 03:33 80 89
tiggis 04:29 05:08 114 128
trux 04:29 03:38 81 91
lucyg43484 04:30 04:47 106 119
patrickcates 04:33 04:15 93 104
jfisher60 04:33 04:08 90 101
Tom Stubbs Tom Stubbs 04:36 03:23 73 82
John Walsh 04:37 04:14 91 102
d.middleton 04:39 04:36 98 110
canismiser 04:45 06:15 131 147
March 04:46 05:08 107 120
LouWeed LouWeed 04:46 02:54 60 67
denislaw 04:47 04:03 84 94
pitcaithlie Pitcaithlie 04:48 05:24 112 125
Ed freshpot 04:50 05:33 114 128
Honggui 04:54 03:49 77 86
Zander 05:02 03:33 70 78
7dPenguin 7dPenguin 05:05 04:36 90 101
Squallaby 05:09 04:12 81 91
neilr neilr 05:10 04:43 91 102
Tibthorpe 05:12 04:20 83 93
Aly Duncan 05:21 04:19 80 89
esmeralda 05:23 05:33 103 115
fshephe 05:25 04:38 85 95
daulbs 05:26 03:54 71 79
ChuckB 05:26 04:41 86 96
jimpen 05:26 04:39 85 95
Spanna 05:27 05:27 100 112
george.plumbly 05:28 04:49 88 98
KET 05:29 03:47 68 76
mw7000 05:29 05:18 96 107
Rabbitoh 05:32 06:05 109 122
john.marshall 05:33 05:52 105 117
Finzi 05:39 06:01 106 119
Shabbo 05:46 05:03 87 97
Looch 05:48 04:27 76 85
squark 05:50 06:24 109 122
cath23 05:52 05:52 100 112
SlumdogEngineer 05:54 05:10 87 97
Dzhigit 05:54 04:43 79 88
cmcnsmith 05:56 06:02 101 113
Carol 05:56 05:17 89 100
McBeak McBeak 06:00 05:00 83 93
Crossiant 06:01 05:26 90 101
DunPangolin 06:03 04:54 80 89
PGooden 06:03 06:03 100 112
Tudds 06:05 05:06 83 93
GMcD 06:08 05:59 97 108
earlylight 06:09 05:23 87 97
Curarist 06:12 05:36 90 101
jimwetzler 06:16 05:44 91 102
ilan 06:17 05:17 84 94
James P 06:18 05:24 85 95
robinh 06:19 06:16 99 111
JMbrow29 06:19 05:38 89 100
IreneC 06:19 06:28 102 114
paul.whitehouse69 06:25 06:08 95 106
Wyn Lewis Wyn Lewis 06:28 05:06 78 87
Aloysius 06:28 05:09 79 88
uvofiz 06:30 06:40 102 114
Mike Harper Mike Harper 06:32 04:57 75 84
julian_w 06:34 06:23 97 108
Dvynys Dvynys 06:37 05:32 83 93
DrBill 06:42 06:27 96 107
John Arnold 06:44 05:24 80 89
maisiemae 06:45 04:46 70 78
Puzzleplease 06:46 04:58 73 82
endafk 06:48 04:24 64 71
Edprof 06:49 05:15 77 86
jjspomeroy 06:54 06:17 91 102
ulaca ulaca 06:57 06:00 86 96
TomHerbert 07:52 06:06 77 86
goblin 08:21 06:35 78 87

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.