Quick SNITCH

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

Times Quick Cryptic Crossword 2391

Date 09 May 2023
Number 2391
Setter Teazel
Day of week Tuesday
NITCH 97
Count of ref solvers 73
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2391

* 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:00 91 93
Paul Gilbert 02:28 02:55 118 121
Jason 02:32 03:00 118 121
verlaine 02:36 02:37 100 103
mistigris 02:40 02:11 81 83
hilarym 02:43 02:00 73 75
aphis99 aphis99 02:49 03:03 108 111
Flimmy flammy 03:04 03:45 122 125
Topical Tim Topical Tim 03:38 03:04 84 86
markdobell 03:50 03:03 79 81
Heyesey 03:52 03:05 79 81
lickert 04:11 05:24 129 132
chindit 04:13 03:29 82 84
chriswords 04:14 03:22 79 81
philjordan1147 BUSMAN 04:14 03:47 89 91
AlanS 04:19 03:32 81 83
nina s 04:19 05:20 123 126
MikeOsborne 04:21 02:44 62 63
tilbee 04:21 03:38 83 85
Roscoe 04:26 04:02 90 92
trux 04:29 04:33 101 104
lucyg43484 04:30 04:10 92 94
Tom Stubbs Tom Stubbs 04:36 03:52 84 86
Jim Willis 04:38 05:02 108 111
scrabbler 04:39 04:35 98 101
andrewlake 04:44 05:38 119 122
canismiser 04:45 04:22 91 93
andy 04:46 03:54 81 83
LouWeed LouWeed 04:46 04:54 102 105
alexh 04:47 04:39 97 100
grape 04:47 04:35 95 97
denislaw 04:47 03:55 81 83
Ed freshpot 04:50 04:27 92 94
MK76 04:53 05:36 114 117
Umpire 04:54 06:28 131 135
Honggui 04:54 03:39 74 76
michaelbell53 04:58 04:29 90 92
Zander 05:02 04:57 98 101
Squallaby 05:09 04:51 94 96
Liari 05:09 06:30 126 129
Paul Bacon 05:09 05:19 103 106
neilr neilr 05:10 03:44 72 74
annbrew 05:11 05:15 101 104
Tibthorpe 05:12 05:22 103 106
footballblue 05:17 05:48 109 112
esmeralda 05:23 03:48 70 72
daulbs 05:26 06:57 127 130
ChuckB 05:26 04:23 80 82
jimpen 05:26 04:23 80 82
george.plumbly 05:28 04:51 88 90
Rabbitoh 05:32 06:59 126 129
AndyR 05:36 05:27 97 100
Finzi 05:39 05:25 95 97
Paul Hammond Paul Hammond 05:41 07:10 126 129
Shabbo 05:46 07:10 124 127
Looch 05:48 05:59 103 106
Kevin Gregg Kevin Gregg 05:51 06:24 109 112
cath23 05:52 06:29 110 113
SlumdogEngineer 05:54 03:48 64 65
cmcnsmith 05:56 06:58 117 120
Carol 05:56 05:25 91 93
nigel 06:00 06:15 104 107
DunPangolin 06:03 03:59 65 67
PGooden 06:03 04:51 80 82
Tudds 06:05 06:49 112 115
GMcD 06:08 06:59 113 116
earlylight 06:09 05:29 89 91
Curarist 06:12 06:21 102 105
jimwetzler 06:16 05:49 92 94
James P 06:18 06:43 106 109
robinh 06:19 07:02 111 114
IreneC 06:19 05:03 79 81
Aloysius 06:28 05:54 91 93
uvofiz 06:30 07:06 109 112
Mike Harper Mike Harper 06:32 06:41 102 105
julian_w 06:34 05:13 79 81
DrBill 06:42 06:58 103 106
Riche Riche 06:43 07:13 107 110
DianeRS 06:46 07:17 107 110
1234 06:48 06:42 98 101
timbo 06:51 06:55 100 103
Viscomte 06:51 06:24 93 95
Corymbia Corymbia 06:57 06:51 98 101
ChrisBrea 06:57 07:02 101 104
ratterz 07:00 05:24 77 79
benedick 07:04 06:14 88 90
martinede 07:15 06:34 90 92

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.