Quick SNITCH

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

Times Quick Cryptic Crossword 2340

Date 27 February 2023
Number 2340
Setter Mara
Day of week Monday
NITCH 83
Count of ref solvers 66
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2340

* 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 01:59 90 108
Paul Gilbert 02:28 01:43 69 83
Jason 02:32 01:56 76 91
verlaine 02:36 02:59 114 137
mistigris 02:40 02:16 85 102
hilarym 02:43 02:14 82 98
cmjhutton 02:44 02:34 93 112
aphis99 aphis99 02:49 02:07 75 90
Flimmy flammy 03:04 02:21 76 91
Topical Tim Topical Tim 03:38 02:43 74 89
markdobell 03:50 03:39 95 114
Heyesey 03:52 03:41 95 114
glheard 04:02 03:32 87 104
Strober 04:04 03:17 80 96
lickert 04:11 02:47 66 79
chindit 04:13 03:41 87 104
philjordan1147 BUSMAN 04:14 03:01 71 85
AlanS 04:19 03:23 78 93
MikeOsborne 04:21 03:02 69 83
tilbee 04:21 02:52 65 78
Roscoe 04:26 04:18 96 115
tiggis 04:29 04:13 94 113
lucyg43484 04:30 04:33 101 121
Tom Stubbs Tom Stubbs 04:36 04:01 87 104
scrabbler 04:39 03:19 71 85
d.middleton 04:39 04:32 97 116
andrewlake 04:44 03:56 83 100
canismiser 04:45 04:00 84 101
andy 04:46 04:29 94 113
March 04:46 04:14 88 106
LouWeed LouWeed 04:46 03:55 82 98
alexh 04:47 04:37 96 115
Dofray 04:48 04:15 88 106
pitcaithlie Pitcaithlie 04:48 03:08 65 78
Ease This Jam 04:50 03:17 67 80
Umpire 04:54 05:07 104 125
michaelbell53 04:58 04:58 100 120
Zander 05:02 04:41 93 112
Squallaby 05:09 04:53 94 113
Liari 05:09 04:39 90 108
Paul Bacon 05:09 05:04 98 118
neilr neilr 05:10 05:14 101 121
annbrew 05:11 04:37 89 107
Tibthorpe 05:12 03:44 71 85
andy_knott 05:13 04:10 79 95
footballblue 05:17 05:33 105 126
Aly Duncan 05:21 05:43 106 127
esmeralda 05:23 04:00 74 89
fshephe 05:25 04:07 76 91
daulbs 05:26 04:53 89 107
ChuckB 05:26 04:33 83 100
jimpen 05:26 03:44 68 81
pammar 05:26 05:31 101 121
mw7000 05:29 03:48 69 83
KET 05:29 05:44 104 125
stguest2 05:32 05:18 95 114
Eddddddd 05:34 05:25 97 116
Finzi 05:39 03:49 67 80
Looch 05:48 03:36 62 74
Kevin Gregg Kevin Gregg 05:51 05:34 95 114
MrChumley MrChumley 05:52 05:07 87 104
Tommo87 05:53 04:50 82 98
SlumdogEngineer 05:54 05:31 93 112
nigel 06:00 04:10 69 83
Colin2355 06:02 05:06 84 101
Xebeq 06:02 06:02 100 120
DunPangolin 06:03 04:16 70 84
Tudds 06:05 04:51 79 95
GMcD 06:08 04:23 71 85
earlylight 06:09 05:43 92 110
Curarist 06:12 05:19 85 102
James P 06:18 04:24 69 83
Michael Dove 06:23 05:17 82 98
paul.whitehouse69 06:25 04:54 76 91
Aloysius 06:28 03:54 60 72
pfalloon 06:30 04:56 75 90
julian_w 06:34 05:33 84 101
KenD51 06:42 02:20 34 40
jjspomeroy 06:54 05:50 84 101
ChrisBrea 06:57 05:02 72 86
ratterz 07:00 05:47 82 98
benedick 07:04 06:04 85 102
m5harp 07:15 05:30 75 90
Sheen 07:21 06:03 82 98
dec 07:26 05:45 77 92
Dan W 07:27 05:14 70 84
TomHerbert 07:52 05:48 73 87
john.brassey 08:08 06:00 73 87

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.