Quick SNITCH

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

Times Quick Cryptic Crossword 2362

Date 29 March 2023
Number 2362
Setter Izetti
Day of week Wednesday
NITCH 107
Count of ref solvers 67
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2362

* 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:20 106 99
Paul Gilbert 02:28 02:36 105 98
Jason 02:32 03:15 128 119
mistigris 02:40 02:43 101 94
hilarym 02:43 03:20 122 114
cmjhutton 02:44 02:40 97 90
aphis99 aphis99 02:49 02:33 90 84
Flimmy flammy 03:04 03:39 119 111
richard 03:39 03:10 86 80
markdobell 03:50 04:05 106 99
glheard 04:02 04:21 107 100
Strober 04:04 04:11 102 95
lickert 04:11 05:01 119 111
philjordan1147 BUSMAN 04:14 03:20 78 72
AlanS 04:19 04:45 110 102
MikeOsborne 04:21 04:00 91 85
tilbee 04:21 04:28 102 95
lucyg43484 04:30 04:14 94 87
Tom Stubbs Tom Stubbs 04:36 05:49 126 117
scrabbler 04:39 05:37 120 112
andrewlake 04:44 06:05 128 119
canismiser 04:45 05:52 123 114
andy 04:46 04:47 100 93
LouWeed LouWeed 04:46 05:45 120 112
March 04:46 04:33 95 88
alexh 04:47 06:18 131 122
denislaw 04:47 04:23 91 85
Ed freshpot 04:50 05:52 121 113
Ease This Jam 04:50 04:46 98 91
MK76 04:53 05:29 112 104
Umpire 04:54 05:37 114 106
Honggui 04:54 04:39 94 87
michaelbell53 04:58 05:59 120 112
Zander 05:02 06:29 128 119
7dPenguin 7dPenguin 05:05 04:21 85 79
Squallaby 05:09 04:52 94 87
Liari 05:09 06:11 120 112
neilr neilr 05:10 05:17 102 95
annbrew 05:11 05:16 101 94
Tibthorpe 05:12 05:16 101 94
Aly Duncan 05:21 08:18 155 144
fshephe 05:25 06:06 112 104
pammar 05:26 07:03 129 120
jimpen 05:26 05:26 100 93
george.plumbly 05:28 06:26 117 109
MossDef 05:30 06:07 111 103
AndyR 05:36 05:04 90 84
Finzi 05:39 06:06 107 100
Paul Hammond Paul Hammond 05:41 07:02 123 114
Shabbo 05:46 05:44 99 92
Looch 05:48 06:20 109 101
MrChumley MrChumley 05:52 06:43 114 106
cath23 05:52 07:49 133 124
Tommo87 05:53 05:52 99 92
Crossiant 06:01 07:46 129 120
Colin2355 06:02 07:35 125 116
DunPangolin 06:03 07:07 117 109
PGooden 06:03 06:40 110 102
Tudds 06:05 05:16 86 80
Rosron 06:07 05:15 85 79
GMcD 06:08 05:56 96 89
rhi.andrew 06:10 07:10 116 108
Curarist 06:12 06:58 112 104
npweston 06:14 06:06 97 90
jimwetzler 06:16 06:32 104 97
ilan 06:17 07:39 121 113
James P 06:18 06:47 107 100
robinh 06:19 05:25 85 79
IreneC 06:19 07:23 116 108
paul.whitehouse69 06:25 07:24 115 107
uvofiz 06:30 05:49 89 83
KenD51 06:42 07:55 118 110
John Arnold 06:44 07:59 118 110
Puzzleplease 06:46 05:09 76 71
1234 06:48 08:07 119 111
timbo 06:51 07:56 115 107
Deezzaa Deezzaa 06:56 07:33 108 100
Corymbia Corymbia 06:57 07:32 108 100
Bobby D 06:58 08:07 116 108
ratterz 07:00 07:21 105 98
benedick 07:04 07:42 108 100
kath 07:10 07:53 110 102
m5harp 07:15 07:41 105 98
johndun John Dunleavy 07:17 08:27 116 108
RPY 07:35 06:19 83 77
Templar Redux Templar 07:37 07:14 94 87
OldSolver 07:52 07:30 95 88
TonyN6 07:59 07:36 95 88
john.brassey 08:08 08:10 100 93
Laputan 08:18 08:18 100 93

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.