Quick SNITCH

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

Times Quick Cryptic Crossword 2350

Date 13 March 2023
Number 2350
Setter Trelawney
Day of week Monday
NITCH 95
Count of ref solvers 76
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2350

* 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:04 94 98
Paul Gilbert 02:28 02:29 100 105
Jason 02:32 02:30 98 103
verlaine 02:36 02:24 92 96
mistigris 02:40 02:19 86 90
hilarym 02:43 02:24 88 92
cmjhutton 02:44 01:57 71 74
aphis99 aphis99 02:49 03:09 111 116
Flimmy flammy 03:04 03:24 110 115
Topical Tim Topical Tim 03:38 03:27 94 98
richard 03:39 04:07 112 117
mcrossib1 03:49 01:58 51 53
markdobell 03:50 04:50 126 132
Heyesey 03:52 03:45 96 101
glheard 04:02 04:10 103 108
lickert 04:11 03:59 95 100
chindit 04:13 04:27 105 110
philjordan1147 BUSMAN 04:14 04:09 98 103
AlanS 04:19 04:45 110 115
MikeOsborne 04:21 03:35 82 86
tilbee 04:21 03:30 80 84
Roscoe 04:26 04:08 93 97
tiggis 04:29 03:35 79 83
lucyg43484 04:30 04:49 107 112
jfisher60 04:33 02:43 59 62
Tom Stubbs Tom Stubbs 04:36 04:40 101 106
scrabbler 04:39 04:17 92 96
andrewlake 04:44 03:12 67 70
canismiser 04:45 03:47 79 83
wwalker50 04:45 05:26 114 120
LouWeed LouWeed 04:46 04:28 93 97
andy 04:46 04:53 102 107
March 04:46 05:58 125 131
alexh 04:47 05:12 108 113
pitcaithlie Pitcaithlie 04:48 05:32 115 121
Ed freshpot 04:50 04:09 85 89
Ease This Jam 04:50 05:02 104 109
MK76 04:53 03:44 76 80
Umpire 04:54 04:36 93 97
Honggui 04:54 04:28 91 95
michaelbell53 04:58 04:45 95 100
7dPenguin 7dPenguin 05:05 04:58 97 102
Paul Bacon 05:09 03:35 69 72
Squallaby 05:09 05:11 100 105
neilr neilr 05:10 06:19 122 128
andy_knott 05:13 04:44 90 94
footballblue 05:17 04:25 83 87
Penfold_61 05:18 05:59 112 117
Aly Duncan 05:21 04:49 90 94
fshephe 05:25 05:05 93 97
ChuckB 05:26 04:28 82 86
jimpen 05:26 05:41 104 109
george.plumbly 05:28 04:45 86 90
AndyR 05:36 05:48 103 108
Finzi 05:39 06:01 106 111
Shabbo 05:46 05:27 94 98
Looch 05:48 03:00 51 53
Kevin Gregg Kevin Gregg 05:51 05:35 95 100
cath23 05:52 04:40 79 83
cmcnsmith 05:56 06:20 106 111
Carol 05:56 05:55 99 104
McBeak McBeak 06:00 05:00 83 87
DunPangolin 06:03 05:45 95 100
Jeremy Weissmann plusjeremy 06:05 06:27 106 111
Rosron 06:07 06:24 104 109
GMcD 06:08 05:24 88 92
earlylight 06:09 05:59 97 102
jimwetzler 06:16 06:32 104 109
ilan 06:17 06:28 102 107
robinh 06:19 05:03 79 83
Mike Mansbridge 06:24 04:42 73 76
paul.whitehouse69 06:25 05:50 90 94
uvofiz 06:30 06:12 95 100
Mike Harper Mike Harper 06:32 06:13 95 100
Gussie 06:35 05:26 82 86
DianeRS 06:46 05:43 84 88
endafk 06:48 05:07 75 78
Edprof 06:49 05:59 87 91
FraserH 06:56 04:51 69 72
Corymbia Corymbia 06:57 05:45 82 86
ChrisBrea 06:57 06:07 88 92
Bobby D 06:58 05:29 78 82
m5harp 07:15 06:25 88 92
Doyler 07:15 06:30 89 93
johndun John Dunleavy 07:17 05:44 78 82
luxtonj61 07:21 06:00 81 85
vefatica vefatica 07:46 05:54 75 78

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.