Quick SNITCH

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

Times Quick Cryptic Crossword 2387

Date 03 May 2023
Number 2387
Setter Hurley
Day of week Wednesday
NITCH 105
Count of ref solvers 72
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2387

* 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:42 123 117
Paul Gilbert 02:28 02:12 89 84
Jason 02:32 02:33 100 95
verlaine 02:36 01:52 71 67
mistigris 02:40 02:58 111 105
hilarym 02:43 02:45 101 96
cmjhutton 02:44 03:19 121 115
aphis99 aphis99 02:49 03:00 106 100
Flimmy flammy 03:04 03:53 126 120
Topical Tim Topical Tim 03:38 03:40 100 95
markdobell 03:50 03:20 86 81
Strober 04:04 04:00 98 93
lickert 04:11 06:39 158 150
chindit 04:13 03:49 90 85
philjordan1147 BUSMAN 04:14 04:59 117 111
AlanS 04:19 04:18 99 94
PaulCooke 04:19 03:30 81 77
MikeOsborne 04:21 03:48 87 82
tilbee 04:21 05:14 120 114
Roscoe 04:26 05:25 122 116
tiggis 04:29 04:14 94 89
lucyg43484 04:30 07:06 157 149
Tom Stubbs Tom Stubbs 04:36 04:16 92 87
Jim Willis 04:38 04:58 107 101
scrabbler 04:39 04:37 99 94
andrewlake 04:44 04:26 93 88
canismiser 04:45 04:58 104 99
wwalker50 04:45 05:09 108 102
andy 04:46 05:25 113 107
March 04:46 05:34 116 110
alexh 04:47 03:25 71 67
Ease This Jam 04:50 05:08 106 100
Umpire 04:54 05:32 112 106
Zander 05:02 05:11 102 97
7dPenguin 7dPenguin 05:05 05:08 100 95
Squallaby 05:09 05:03 98 93
neilr neilr 05:10 05:36 108 102
annbrew 05:11 05:31 106 100
Tibthorpe 05:12 05:57 114 108
Aly Duncan 05:21 05:25 101 96
esmeralda 05:23 05:04 94 89
fshephe 05:25 05:50 107 101
daulbs 05:26 05:52 107 101
ChuckB 05:26 05:58 109 103
jimpen 05:26 06:07 112 106
Spanna 05:27 05:50 107 101
george.plumbly 05:28 05:44 104 99
KET 05:29 06:14 113 107
mw7000 05:29 05:29 100 95
Rabbitoh galspray 05:32 06:08 110 104
john.marshall 05:33 04:59 89 84
Finzi 05:39 06:07 108 102
Julian Forbes 05:45 05:51 101 96
Shabbo 05:46 04:57 85 80
Looch 05:48 05:12 89 84
squark 05:50 05:34 95 90
Kevin Gregg Kevin Gregg 05:51 06:35 112 106
Tommo87 05:53 06:06 103 98
SlumdogEngineer 05:54 06:00 101 96
Carol 05:56 07:07 119 113
nigel 06:00 07:14 120 114
Crossiant 06:01 06:34 109 103
DunPangolin 06:03 05:33 91 86
PGooden 06:03 07:08 117 111
Tudds 06:05 06:48 111 105
Rosron 06:07 03:53 63 60
Curarist 06:12 06:33 105 100
cerds 06:14 06:37 106 100
ilan 06:17 06:49 108 102
James P 06:18 06:40 105 100
robinh 06:19 06:46 107 101
JMbrow29 06:19 05:16 83 79
paul.whitehouse69 06:25 06:59 108 102
uvofiz 06:30 07:26 114 108
Mike Harper Mike Harper 06:32 07:25 113 107
DrBill 06:42 04:56 73 69
alastair52 06:43 06:53 102 97
maisiemae 06:45 06:49 100 95
Puzzleplease 06:46 06:57 102 97
endafk 06:48 06:33 96 91
plett11 Plett11 06:48 07:27 109 103
FraserH 06:56 07:04 101 96
ChrisBrea 06:57 06:25 92 87
ulaca ulaca 06:57 07:06 102 97
barracuda barracuda 07:08 06:56 97 92
Sheen 07:21 06:33 89 84
Pendrov 07:24 07:02 95 90
Cuppa378 07:32 07:20 97 92
RPY 07:35 06:59 92 87
TonyN6 07:59 07:25 92 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.