Quick SNITCH

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

Times Quick Cryptic Crossword 2361

Date 28 March 2023
Number 2361
Setter Breadman
Day of week Tuesday
NITCH 103
Count of ref solvers 60
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2361

* 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:13 101 98
Paul Gilbert 02:28 02:31 102 99
Jason 02:32 02:49 111 107
verlaine 02:36 02:38 101 98
hilarym 02:43 03:12 117 113
aphis99 aphis99 02:49 02:47 98 95
Flimmy flammy 03:04 02:45 89 86
Sheapey Sheapey 03:31 03:54 110 106
richard 03:39 04:29 122 118
markdobell 03:50 03:12 83 80
Heyesey 03:52 04:05 105 101
xyster 04:04 03:50 94 91
lickert 04:11 03:41 88 85
chindit 04:13 03:56 93 90
AlanS 04:19 04:35 106 102
MikeOsborne 04:21 03:47 86 83
tilbee 04:21 04:18 98 95
lucyg43484 04:30 04:13 93 90
Tom Stubbs Tom Stubbs 04:36 05:59 130 126
scrabbler 04:39 05:41 122 118
d.middleton 04:39 06:11 132 128
andrewlake 04:44 04:41 98 95
canismiser 04:45 04:24 92 89
wwalker50 04:45 04:22 91 88
andy 04:46 04:56 103 100
March 04:46 03:55 82 79
LouWeed LouWeed 04:46 05:48 121 117
alexh 04:47 05:12 108 104
Ed freshpot 04:50 04:53 101 98
Ease This Jam 04:50 04:38 95 92
Honggui 04:54 04:39 94 91
Zander 05:02 04:43 93 90
7dPenguin 7dPenguin 05:05 05:38 110 106
Liari 05:09 05:55 114 110
neilr neilr 05:10 07:48 150 145
Tibthorpe 05:12 06:19 121 117
footballblue 05:17 07:42 145 140
esmeralda 05:23 05:36 104 100
fshephe 05:25 04:20 80 77
pammar 05:26 03:46 69 66
daulbs 05:26 08:14 151 146
ChuckB 05:26 05:28 100 97
jimpen 05:26 06:46 124 120
george.plumbly 05:28 05:39 103 100
MossDef 05:30 07:11 130 126
Rabbitoh 05:32 05:51 105 101
Finzi 05:39 06:11 109 105
Shabbo 05:46 04:26 76 73
Looch 05:48 06:12 106 102
Tommo87 05:53 06:54 117 113
SlumdogEngineer 05:54 04:44 80 77
cmcnsmith 05:56 06:11 104 100
Carol 05:56 05:26 91 88
McBeak McBeak 06:00 04:30 75 72
Colin2355 06:02 05:58 98 95
DunPangolin 06:03 06:48 112 108
GMcD 06:08 05:15 85 82
earlylight 06:09 05:03 82 79
rhi.andrew 06:10 06:12 100 97
Curarist 06:12 06:46 109 105
npweston 06:14 06:28 103 100
James P 06:18 06:31 103 100
robinh 06:19 07:22 116 112
IreneC 06:19 06:06 96 93
Michael Dove 06:23 07:04 110 106
paul.whitehouse69 06:25 05:42 88 85
uvofiz 06:30 07:24 113 109
Mike Harper Mike Harper 06:32 07:12 110 106
Dvynys Dvynys 06:37 05:34 84 81
jon 06:42 06:51 102 99
smalley552 06:42 06:53 102 99
endafk 06:48 06:58 102 99
raincloud 06:49 06:09 90 87
Edprof 06:49 06:45 99 96
timbo 06:51 04:36 67 65
ChrisBrea 06:57 08:04 116 112
ulaca ulaca 06:57 07:28 107 103
barracuda barracuda 07:08 07:22 103 100
docg 07:15 07:51 108 104
gsriordan52 07:20 08:14 112 108
luxtonj61 07:21 05:54 80 77
Sheen 07:21 08:16 112 108
Dan W 07:27 07:27 100 97
AndyLast 07:35 08:13 108 104
RPY 07:35 05:49 76 73
sue.cresswell 07:46 07:15 93 90
john.brassey 08:08 08:04 99 96

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.