Quick SNITCH

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

Times Quick Cryptic Crossword 2353

Date 16 March 2023
Number 2353
Setter Joker
Day of week Thursday
NITCH 113
Count of ref solvers 49
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2353

* 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
Paul Gilbert 02:28 02:07 85 75
Jason 02:32 03:39 144 127
hilarym 02:43 02:18 84 74
aphis99 aphis99 02:49 03:08 111 98
Flimmy flammy 03:04 02:40 86 76
Topical Tim Topical Tim 03:38 03:31 96 84
markdobell 03:50 05:18 138 122
Heyesey 03:52 03:10 81 71
Strober 04:04 03:47 93 82
lickert 04:11 03:41 88 77
chindit 04:13 04:13 100 88
AlanS 04:19 04:08 95 84
tiggis 04:29 03:41 82 72
lucyg43484 04:30 03:58 88 77
andrewlake 04:44 03:37 76 67
pitcaithlie Pitcaithlie 04:48 04:30 93 82
Umpire 04:54 06:22 129 114
Honggui 04:54 05:40 115 101
Zander 05:02 05:30 109 96
7dPenguin 7dPenguin 05:05 04:28 87 76
Liari 05:09 06:14 121 107
Penfold_61 05:18 05:30 103 91
Aly Duncan 05:21 07:32 140 123
ChuckB 05:26 06:24 117 103
george.plumbly 05:28 04:46 87 76
mw7000 05:29 09:53 180 159
Finzi 05:39 06:19 111 98
Shabbo 05:46 04:42 81 71
Looch 05:48 04:59 85 75
cath23 05:52 06:57 118 104
SlumdogEngineer 05:54 06:06 103 91
McBeak McBeak 06:00 07:45 129 114
PGooden 06:03 06:30 107 94
RobR RobR 06:03 06:46 111 98
Rosron 06:07 07:49 127 112
GMcD 06:08 10:20 168 148
earlylight 06:09 06:15 101 89
Curarist 06:12 05:50 94 83
jimwetzler 06:16 07:32 120 106
ilan 06:17 06:43 106 93
James P 06:18 06:36 104 92
Wyn Lewis Wyn Lewis 06:28 11:47 182 161
Aloysius 06:28 08:02 124 109
uvofiz 06:30 05:57 91 80
Mike Harper Mike Harper 06:32 09:14 141 124
julian_w 06:34 09:56 151 133
Gussie 06:35 13:28 204 180
jon 06:42 07:48 116 102
John Arnold 06:44 06:31 96 84
DianeRS 06:46 09:22 138 122
endafk 06:48 06:23 93 82
1234 06:48 07:37 112 99
raincloud 06:49 12:54 189 167
Edprof 06:49 07:57 116 102
FraserH 06:56 09:20 134 118
Bobby D 06:58 09:05 130 115
ratterz 07:00 07:03 100 88
hookyt 07:13 14:30 200 176
Dr_Bob 07:24 10:11 137 121
Dan W 07:27 09:23 125 110
Cuppa378 07:32 08:22 111 98
Crippens1 07:41 09:08 118 104
FelicityTT 07:42 13:50 179 158
frost 07:51 09:31 121 107
OldSolver 07:52 11:57 151 133
vinyl12345 vinyl1 07:53 14:03 178 157
jaraab 07:54 11:55 150 132
pauliwan 08:00 13:59 174 153
jemcd33 08:05 07:55 97 85
john.brassey 08:08 08:59 110 97
Laputan 08:18 11:38 140 123
goblin 08:21 10:58 131 115
nigelmzzz 08:44 12:50 146 129
Mkgnao Mkgnao 08:53 10:12 114 100
paulwestside 09:37 14:25 149 131
edwards.robert1 09:41 10:10 104 92
CWM65 11:08 14:04 126 111
Jayarem 14:05 14:05 100 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.