Quick SNITCH

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

Times Quick Cryptic Crossword 2377

Date 19 April 2023
Number 2377
Setter Oink
Day of week Wednesday
NITCH 104
Count of ref solvers 75
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2377

* 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:12 100 96
Paul Gilbert 02:28 02:16 91 87
Jason 02:32 02:59 117 112
mauefw 02:34 02:45 107 102
verlaine 02:36 02:19 89 85
mistigris 02:40 02:30 93 89
hilarym 02:43 02:54 106 101
cmjhutton 02:44 02:27 89 85
aphis99 aphis99 02:49 02:48 99 95
Flimmy flammy 03:04 02:35 84 80
Topical Tim Topical Tim 03:38 02:50 77 74
Kinghedger 03:52 03:50 99 95
lickert 04:11 05:04 121 116
chindit 04:13 04:40 110 105
philjordan1147 BUSMAN 04:14 04:16 100 96
MikeOsborne 04:21 04:12 96 92
tilbee 04:21 03:20 76 73
Roscoe 04:26 05:30 124 119
tiggis 04:29 05:11 115 110
lucyg43484 04:30 05:44 127 122
Tom Stubbs Tom Stubbs 04:36 05:30 119 114
Jim Willis 04:38 05:09 111 106
scrabbler 04:39 05:16 113 108
andrewlake 04:44 06:15 132 126
canismiser 04:45 05:19 111 106
wwalker50 04:45 05:07 107 102
March 04:46 04:28 93 89
LouWeed LouWeed 04:46 03:52 81 77
andy 04:46 06:31 136 130
alexh 04:47 04:54 102 98
denislaw 04:47 03:43 77 74
pitcaithlie Pitcaithlie 04:48 04:20 90 86
Ed freshpot 04:50 05:28 113 108
Ease This Jam 04:50 05:03 104 100
MK76 04:53 05:11 106 101
Umpire 04:54 05:22 109 104
Honggui 04:54 04:18 87 83
michaelbell53 04:58 05:41 114 109
Zander 05:02 05:05 100 96
7dPenguin 7dPenguin 05:05 04:45 93 89
Squallaby 05:09 04:43 91 87
Liari 05:09 04:09 80 76
neilr neilr 05:10 06:33 126 121
Tibthorpe 05:12 05:26 104 100
andy_knott 05:13 05:07 98 94
Aly Duncan 05:21 06:00 112 107
fshephe 05:25 05:15 96 92
daulbs 05:26 05:59 110 105
jimpen 05:26 04:56 90 86
Spanna 05:27 06:11 113 108
george.plumbly 05:28 07:22 134 128
MossDef 05:30 05:41 103 99
Rabbitoh 05:32 05:18 95 91
AndyR 05:36 06:29 115 110
Finzi 05:39 06:06 107 102
Paul Hammond Paul Hammond 05:41 05:45 101 97
Shabbo 05:46 07:36 131 125
Looch 05:48 05:30 94 90
cath23 05:52 06:09 104 100
Carol 05:56 07:07 119 114
Crossiant 06:01 07:11 119 114
DunPangolin 06:03 06:10 101 97
Tudds 06:05 07:58 130 125
Jeremy Weissmann plusjeremy 06:05 07:34 124 119
Rosron 06:07 07:55 129 124
GMcD 06:08 05:24 88 84
earlylight 06:09 04:56 80 76
jimwetzler 06:16 06:28 103 99
ilan 06:17 06:16 99 95
James P 06:18 04:56 78 75
IreneC 06:19 06:03 95 91
JMbrow29 06:19 06:24 101 97
paul.whitehouse69 06:25 06:35 102 98
uvofiz 06:30 07:28 114 109
alastair52 06:43 07:14 107 102
william.horner 06:44 07:04 104 100
maisiemae 06:45 07:04 104 100
endafk 06:48 07:22 108 103
plett11 Plett11 06:48 06:43 98 94
timbo 06:51 07:32 109 104
Claverton74 06:56 07:20 105 100
Corymbia Corymbia 06:57 07:34 108 103
ChrisBrea 06:57 07:14 104 100
Andrew Whiffin 07:25 06:58 93 89
Templar Redux Templar 07:37 07:07 93 89
frost 07:51 07:37 97 93
jaraab 07:54 06:52 86 82
goblin 08:21 07:58 95 91
iholloway 08:28 08:02 94 90

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.