Quick SNITCH

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

Times Quick Cryptic Crossword 2342

Date 01 March 2023
Number 2342
Setter Joker
Day of week Wednesday
NITCH 111
Count of ref solvers 73
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2342

* 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:14 102 91
Paul Gilbert 02:28 02:02 82 73
Jason 02:32 02:34 101 90
verlaine 02:36 02:15 86 77
mistigris 02:40 04:37 173 155
cmjhutton 02:44 02:42 98 88
aphis99 aphis99 02:49 03:00 106 95
Flimmy flammy 03:04 03:03 99 89
Topical Tim Topical Tim 03:38 04:43 129 116
richard 03:39 04:11 114 102
markdobell 03:50 04:29 116 104
Heyesey 03:52 04:20 112 100
glheard 04:02 03:56 97 87
lickert 04:11 03:49 91 81
philjordan1147 BUSMAN 04:14 04:10 98 88
AlanS 04:19 05:28 126 113
MikeOsborne 04:21 04:42 108 97
tilbee 04:21 04:38 106 95
Roscoe 04:26 05:21 120 108
tiggis 04:29 05:48 129 116
Tom Stubbs Tom Stubbs 04:36 04:47 103 92
scrabbler 04:39 04:11 89 80
andrewlake 04:44 05:58 126 113
andy 04:46 04:33 95 85
March 04:46 05:46 120 108
LouWeed LouWeed 04:46 05:21 112 100
alexh 04:47 05:30 114 102
Dofray 04:48 06:09 128 115
pitcaithlie Pitcaithlie 04:48 05:19 110 99
Ed freshpot 04:50 05:48 120 108
Ease This Jam 04:50 06:10 127 114
MK76 04:53 06:52 140 126
Honggui 04:54 04:56 100 90
Umpire 04:54 07:37 155 139
Zander 05:02 05:35 110 99
7dPenguin 7dPenguin 05:05 05:34 109 98
Squallaby 05:09 03:49 74 66
neilr neilr 05:10 05:06 98 88
Tibthorpe 05:12 06:11 118 106
footballblue 05:17 05:46 109 98
Penfold_61 05:18 05:05 95 85
Aly Duncan 05:21 08:24 157 141
fshephe 05:25 05:29 101 90
ChuckB 05:26 07:38 140 126
george.plumbly 05:28 05:31 100 90
mw7000 05:29 06:22 116 104
KET 05:29 07:26 135 121
Finzi 05:39 04:48 84 75
Shabbo 05:46 04:58 86 77
Looch 05:48 06:11 106 95
Kevin Gregg Kevin Gregg 05:51 06:52 117 105
cath23 05:52 05:35 95 85
Carol 05:56 05:52 98 88
GeorgeTz 05:56 06:58 117 105
McBeak McBeak 06:00 08:11 136 122
Crossiant 06:01 06:01 100 90
DunPangolin 06:03 07:42 127 114
Tudds 06:05 07:52 129 116
Rosron 06:07 06:27 105 94
GMcD 06:08 05:12 84 75
earlylight 06:09 07:15 117 105
Curarist 06:12 08:03 129 116
James P 06:18 06:28 102 91
robinh 06:19 06:41 105 94
paul.whitehouse69 06:25 06:52 107 96
Aloysius 06:28 06:58 107 96
Mike Harper Mike Harper 06:32 07:16 111 100
julian_w 06:34 07:25 112 100
Dvynys Dvynys 06:37 07:52 118 106
jon 06:42 07:21 109 98
alastair52 06:43 07:10 106 95
maisiemae 06:45 07:20 108 97
DianeRS 06:46 08:04 119 107
Deezzaa Deezzaa 06:56 07:32 108 97
Corymbia Corymbia 06:57 07:57 114 102
ChrisBrea 06:57 08:02 115 103
ratterz 07:00 08:27 120 108
barracuda barracuda 07:08 07:15 101 90
m5harp 07:15 08:29 117 105
AndyLast 07:35 07:20 96 86
crosswordian 07:46 08:28 109 98
TomHerbert 07:52 07:18 92 82
TonyN6 07:59 08:36 107 96
Pauline Minter 08:42 07:49 89 80
suethepotterer 09:07 04:41 51 45
edwards.robert1 09:41 08:18 85 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.