Quick SNITCH

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

Times Quick Cryptic Crossword 2373

Date 13 April 2023
Number 2373
Setter Teazel
Day of week Thursday
NITCH 103
Count of ref solvers 73
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2373

* 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:14 102 99
verlaine 02:36 02:20 89 86
mistigris 02:40 02:33 95 92
hilarym 02:43 02:48 103 100
cmjhutton 02:44 02:52 104 100
aphis99 aphis99 02:49 02:04 73 70
Flimmy flammy 03:04 03:05 100 97
Topical Tim Topical Tim 03:38 04:06 112 108
richard 03:39 03:07 85 82
markdobell 03:50 03:39 95 92
Heyesey 03:52 03:26 88 85
glheard 04:02 05:02 124 120
Strober 04:04 03:46 92 89
lickert 04:11 03:11 76 73
chindit 04:13 04:26 105 101
philjordan1147 BUSMAN 04:14 04:27 105 101
AlanS 04:19 04:09 96 93
MikeOsborne 04:21 04:52 111 107
tilbee 04:21 04:51 111 107
tiggis 04:29 04:01 89 86
lucyg43484 04:30 04:13 93 90
jfisher60 04:33 04:34 100 97
Tom Stubbs Tom Stubbs 04:36 04:26 96 93
Jim Willis 04:38 05:24 116 112
scrabbler 04:39 05:02 108 104
andrewlake 04:44 06:15 132 128
wwalker50 04:45 04:58 104 100
andy 04:46 04:56 103 100
March 04:46 05:33 116 112
LouWeed LouWeed 04:46 04:48 100 97
denislaw 04:47 04:13 88 85
pitcaithlie Pitcaithlie 04:48 06:11 128 124
Ed freshpot 04:50 04:21 90 87
Ease This Jam 04:50 03:44 77 74
MK76 04:53 05:56 121 117
Umpire 04:54 06:27 131 127
Honggui 04:54 04:48 97 94
michaelbell53 04:58 05:29 110 106
Zander 05:02 04:23 87 84
7dPenguin 7dPenguin 05:05 04:24 86 83
Liari 05:09 05:11 100 97
Squallaby 05:09 06:56 134 130
neilr neilr 05:10 06:34 127 123
Tibthorpe 05:12 05:13 100 97
footballblue 05:17 05:03 95 92
Penfold_61 05:18 05:25 102 99
esmeralda 05:23 06:37 122 118
fshephe 05:25 06:46 124 120
ChuckB 05:26 03:58 73 70
george.plumbly 05:28 05:38 103 100
MossDef 05:30 05:37 102 99
Rabbitoh 05:32 04:50 87 84
john.marshall 05:33 05:32 99 96
AndyR 05:36 06:46 120 116
Finzi 05:39 06:34 116 112
Paul Hammond Paul Hammond 05:41 05:34 97 94
monkfish 05:44 05:05 88 85
Shabbo 05:46 05:32 95 92
Looch 05:48 06:44 116 112
Kevin Gregg Kevin Gregg 05:51 06:35 112 108
cath23 05:52 05:58 101 98
Crossiant 06:01 05:20 88 85
Tudds 06:05 06:29 106 102
Rosron 06:07 06:39 108 104
GMcD 06:08 04:17 69 66
ilan 06:17 07:39 121 117
James P 06:18 07:55 125 121
JMbrow29 06:19 03:28 54 52
IreneC 06:19 06:11 97 94
robinh 06:19 07:48 123 119
Mike Mansbridge 06:24 06:12 96 93
uvofiz 06:30 07:45 119 115
Mike Harper Mike Harper 06:32 07:52 120 116
julian_w 06:34 06:21 96 93
Nangle 06:41 07:54 118 114
jon 06:42 05:18 79 76
DrBill 06:42 07:00 104 100
Puzzleplease 06:46 07:38 112 108
endafk 06:48 06:30 95 92
Edprof 06:49 05:50 85 82
FraserH 06:56 06:36 95 92
Deezzaa Deezzaa 06:56 07:52 113 109
ChrisBrea 06:57 06:32 94 91
Corymbia Corymbia 06:57 06:51 98 95
barracuda barracuda 07:08 07:26 104 100
kath 07:10 06:21 88 85
m5harp 07:15 07:57 109 105
RPY 07:35 06:59 92 89
jaraab 07:54 06:27 81 78
jemcd33 08:05 07:24 91 88

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.