Quick SNITCH

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

Times Quick Cryptic Crossword 2343

Date 02 March 2023
Number 2343
Setter Breadman
Day of week Thursday
NITCH 109
Count of ref solvers 65
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2343

* 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:38 120 110
Paul Gilbert 02:28 02:03 83 76
Jason 02:32 04:06 161 147
verlaine 02:36 04:00 153 140
mistigris 02:40 03:15 121 111
hilarym 02:43 02:58 109 100
cmjhutton 02:44 02:14 81 74
aphis99 aphis99 02:49 03:30 124 113
Flimmy flammy 03:04 02:47 90 82
Topical Tim Topical Tim 03:38 04:13 116 106
richard 03:39 03:50 105 96
markdobell 03:50 05:15 136 124
Heyesey 03:52 04:43 121 111
glheard 04:02 04:35 113 103
Strober 04:04 03:43 91 83
lickert 04:11 03:52 92 84
philjordan1147 BUSMAN 04:14 05:07 120 110
AlanS 04:19 04:36 106 97
tilbee 04:21 04:12 96 88
tiggis 04:29 05:42 127 116
lucyg43484 04:30 05:01 111 101
Tom Stubbs Tom Stubbs 04:36 04:40 101 92
scrabbler 04:39 04:46 102 93
andrewlake 04:44 05:47 122 111
canismiser 04:45 05:16 110 100
andy 04:46 06:06 127 116
LouWeed LouWeed 04:46 05:09 108 99
March 04:46 04:18 90 82
alexh 04:47 04:49 100 91
pitcaithlie Pitcaithlie 04:48 05:17 110 100
Ed freshpot 04:50 04:51 100 91
Ease This Jam 04:50 03:35 74 67
MK76 04:53 05:13 106 97
Umpire 04:54 05:11 105 96
Honggui 04:54 06:28 131 120
Zander 05:02 04:54 97 88
7dPenguin 7dPenguin 05:05 05:59 117 107
Liari 05:09 05:17 102 93
Squallaby 05:09 06:29 125 114
neilr neilr 05:10 05:16 101 92
annbrew 05:11 05:43 110 100
Tibthorpe 05:12 05:53 113 103
fshephe 05:25 06:43 124 113
jimpen 05:26 05:41 104 95
george.plumbly 05:28 06:15 114 104
Dekkers 05:31 05:26 98 89
Rabbitoh 05:32 05:38 101 92
Eddddddd 05:34 06:54 123 112
Finzi 05:39 06:43 118 108
Julian Forbes 05:45 05:40 98 89
Shabbo 05:46 05:52 101 92
Kevin Gregg Kevin Gregg 05:51 06:55 118 108
cath23 05:52 05:20 90 82
Tommo87 05:53 05:22 91 83
SlumdogEngineer 05:54 06:12 105 96
Carol 05:56 05:35 94 86
McBeak McBeak 06:00 06:16 104 95
Crossiant 06:01 04:31 75 68
Colin2355 06:02 06:41 110 100
DunPangolin 06:03 06:16 103 94
GMcD 06:08 07:01 114 104
rhi.andrew 06:10 06:21 102 93
Curarist 06:12 06:17 101 92
cerds 06:14 06:43 107 98
jimwetzler 06:16 07:08 113 103
robinh 06:19 06:09 97 88
mandyroberts2007 06:20 06:27 101 92
Michael Dove 06:23 06:11 96 88
Mike Mansbridge 06:24 06:22 99 90
paul.whitehouse69 06:25 06:08 95 87
uvofiz 06:30 07:04 108 99
Gussie 06:35 06:18 95 87
Rubeculaw Rubeculaw 06:39 06:05 91 83
jon 06:42 07:13 107 98
John Arnold 06:44 06:55 102 93
maisiemae 06:45 06:27 95 87
1234 06:48 06:13 91 83
Deezzaa Deezzaa 06:56 05:23 77 70
Corymbia Corymbia 06:57 06:54 99 90
goldenpie 07:06 07:19 103 94
martinede 07:15 07:16 100 91
Cuppa378 07:32 07:19 97 88
AndyLast 07:35 06:53 90 82
frost 07:51 07:17 92 84
TomHerbert 07:52 07:21 93 85
Laputan 08:18 07:17 87 79
BletchleyReject 08:27 07:29 88 80
nigelmzzz 08:44 03:15 37 33
Merlin_55 Merlin 14:45 07:19 49 44
Doofenschmirtz Doofenschmirtz 16:37 13:57 83 76

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.