Quick SNITCH

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

Times Quick Cryptic Crossword 2374

Date 14 April 2023
Number 2374
Setter Alfie
Day of week Friday
NITCH 96
Count of ref solvers 67
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2374

* 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 01:51 84 87
Paul Gilbert 02:28 01:56 78 81
verlaine 02:36 02:18 88 91
mistigris 02:40 02:48 105 109
hilarym 02:43 02:44 100 104
cmjhutton 02:44 02:36 95 98
aphis99 aphis99 02:49 03:18 117 121
Flimmy flammy 03:04 03:06 101 105
Topical Tim Topical Tim 03:38 03:33 97 101
richard 03:39 03:41 100 104
markdobell 03:50 03:18 86 89
Heyesey 03:52 03:03 78 81
Strober 04:04 04:28 109 113
lickert 04:11 04:20 103 107
chindit 04:13 03:56 93 96
philjordan1147 BUSMAN 04:14 04:19 101 105
AlanS 04:19 04:42 108 112
MikeOsborne 04:21 03:55 90 93
tilbee 04:21 05:29 126 131
tiggis 04:29 05:42 127 132
lucyg43484 04:30 04:33 101 105
Tom Stubbs Tom Stubbs 04:36 05:34 121 126
Jim Willis 04:38 04:01 86 89
scrabbler 04:39 03:44 80 83
andrewlake 04:44 04:02 85 88
canismiser 04:45 04:50 101 105
wwalker50 04:45 05:44 120 125
andy 04:46 05:40 118 122
March 04:46 04:37 96 100
pitcaithlie Pitcaithlie 04:48 04:36 95 98
Umpire 04:54 04:17 87 90
Honggui 04:54 03:46 76 79
Zander 05:02 04:34 90 93
7dPenguin 7dPenguin 05:05 04:33 89 92
Squallaby 05:09 05:32 107 111
Liari 05:09 04:42 91 94
Paul Bacon 05:09 06:08 119 123
neilr neilr 05:10 04:41 90 93
Tibthorpe 05:12 04:28 85 88
Penfold_61 05:18 05:23 101 105
Aly Duncan 05:21 04:58 92 95
esmeralda 05:23 04:00 74 77
daulbs 05:26 04:28 82 85
ChuckB 05:26 04:47 88 91
jimpen 05:26 05:20 98 102
Spanna 05:27 05:26 99 103
MossDef 05:30 05:54 107 111
Rabbitoh 05:32 05:09 93 96
john.marshall 05:33 06:02 108 112
AndyR 05:36 04:58 88 91
Finzi 05:39 05:57 105 109
Paul Hammond Paul Hammond 05:41 03:41 64 66
Julian Forbes 05:45 06:11 107 111
Looch 05:48 04:46 82 85
Kevin Gregg Kevin Gregg 05:51 06:28 110 114
cath23 05:52 06:23 108 112
Tommo87 05:53 06:47 115 119
cmcnsmith 05:56 06:09 103 107
McBeak McBeak 06:00 06:51 114 118
nigel 06:00 06:25 106 110
DunPangolin 06:03 04:47 79 82
Tudds 06:05 06:26 105 109
Rosron 06:07 06:49 111 115
GMcD 06:08 06:14 101 105
martinphillips 06:09 05:42 92 95
jimwetzler 06:16 07:01 111 115
James P 06:18 04:55 78 81
JMbrow29 06:19 04:37 73 76
robinh 06:19 06:33 103 107
Michael Dove 06:23 06:12 97 101
uvofiz 06:30 06:03 93 96
Mike Harper Mike Harper 06:32 05:32 84 87
julian_w 06:34 06:07 93 96
Gussie 06:35 06:23 96 100
KenD51 06:42 05:55 88 91
jon 06:42 05:29 81 84
Riche Riche 06:43 06:27 96 100
endafk 06:48 06:29 95 98
Corymbia Corymbia 06:57 06:16 90 93
benedick 07:04 06:53 97 101
barracuda barracuda 07:08 06:38 92 95
hookyt 07:13 05:38 78 81
Doyler 07:15 07:01 96 100
Crippens1 07:41 06:12 80 83
jaraab 07:54 06:21 80 83
john.brassey 08:08 06:27 79 82

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.