Quick SNITCH

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

Times Quick Cryptic Crossword 2386

Date 02 May 2023
Number 2386
Setter Breadman
Day of week Tuesday
NITCH 104
Count of ref solvers 70
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2386

* 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:06 96 92
Paul Gilbert 02:28 03:18 133 127
verlaine 02:36 03:05 118 113
mistigris 02:40 02:38 98 94
hilarym 02:43 03:16 120 115
cmjhutton 02:44 03:29 127 122
aphis99 aphis99 02:49 03:19 117 112
Flimmy flammy 03:04 02:41 87 83
Topical Tim Topical Tim 03:38 04:28 122 117
markdobell 03:50 03:02 79 75
lickert 04:11 06:20 151 145
chindit 04:13 04:08 98 94
philjordan1147 BUSMAN 04:14 04:34 107 102
AlanS 04:19 04:41 108 103
tilbee 04:21 04:39 106 101
MikeOsborne 04:21 05:17 121 116
Roscoe 04:26 04:43 106 101
lucyg43484 04:30 04:52 108 103
Tom Stubbs Tom Stubbs 04:36 05:00 108 103
Jim Willis 04:38 05:01 108 103
scrabbler 04:39 04:36 98 94
d.middleton 04:39 05:09 110 105
andrewlake 04:44 04:12 88 84
wwalker50 04:45 05:01 105 100
andy 04:46 03:38 76 73
March 04:46 04:11 87 83
alexh 04:47 03:45 78 75
grape 04:47 06:37 138 132
Ed freshpot 04:50 04:35 94 90
Ease This Jam 04:50 05:27 112 107
MK76 04:53 06:16 128 123
Umpire 04:54 03:56 80 76
Honggui 04:54 04:31 92 88
Zander 05:02 05:59 118 113
7dPenguin 7dPenguin 05:05 05:04 99 95
Squallaby 05:09 04:23 85 81
neilr neilr 05:10 05:00 96 92
annbrew 05:11 05:14 100 96
Tibthorpe 05:12 05:46 110 105
andy_knott 05:13 06:01 115 110
esmeralda 05:23 06:51 127 122
fshephe 05:25 05:43 105 100
daulbs 05:26 06:32 120 115
jimpen 05:26 05:13 96 92
george.plumbly 05:28 05:19 97 93
Rabbitoh 05:32 07:56 143 137
john.marshall 05:33 05:57 107 102
AndyR 05:36 05:30 98 94
Finzi 05:39 05:28 96 92
Paul Hammond Paul Hammond 05:41 04:44 83 79
Shabbo 05:46 05:47 100 96
Looch 05:48 05:16 90 86
squark 05:50 06:19 108 103
Kevin Gregg Kevin Gregg 05:51 06:35 112 107
cath23 05:52 06:19 107 102
cmcnsmith 05:56 06:32 110 105
Carol 05:56 05:34 93 89
nigel 06:00 08:01 133 127
Crossiant 06:01 06:27 107 102
Colin2355 06:02 05:36 92 88
DunPangolin 06:03 06:34 108 103
Rosron 06:07 05:48 94 90
GMcD 06:08 05:08 83 79
earlylight 06:09 06:39 108 103
Curarist 06:12 04:40 75 72
James P 06:18 06:54 109 104
robinh 06:19 07:57 125 120
mandyroberts2007 06:20 07:11 113 108
Mike Mansbridge 06:24 06:28 101 97
uvofiz 06:30 05:46 88 84
Mike Harper Mike Harper 06:32 05:34 85 81
julian_w 06:34 07:13 109 104
Dvynys Dvynys 06:37 07:32 113 108
Nangle 06:41 06:46 101 97
jon 06:42 06:25 95 91
DrBill 06:42 06:48 101 97
DianeRS 06:46 06:11 91 87
endafk 06:48 05:19 78 75
Edprof 06:49 07:41 112 107
timbo 06:51 07:59 116 111
Corymbia Corymbia 06:57 06:18 90 86
ratterz 07:00 08:04 115 110
benedick 07:04 07:09 101 97
martinede 07:15 07:38 105 100
Sheen 07:21 07:55 107 102
Andrew Whiffin 07:25 06:08 82 78
sue.cresswell 07:46 07:11 92 88
vinyl12345 vinyl1 07:53 07:27 94 90
WordPlodder BletchleyReject 09:39 07:29 77 74

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.