Quick SNITCH

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

Times Quick Cryptic Crossword 2307

Date 11 January 2023
Number 2307
Setter Breadman
Day of week Wednesday
NITCH 92
Count of ref solvers 63
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2307

* Requires access to the Times Crossword Club

Detailed solving results

 

If you would like to help cover the costs of running the SNITCH site, please "buy me a coffee".

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:07 02:15 106 115
Paul Gilbert 02:14 01:48 80 86
cmjhutton 02:18 01:12 52 56
mauefw 02:19 02:05 89 96
Jason 02:35 02:52 110 119
mistigris 02:39 02:39 100 108
hilarym 02:50 02:47 98 106
Flimmy flammy 03:11 02:27 76 82
richard 03:37 03:10 87 94
markdobell 03:39 03:36 98 106
Heyesey 03:41 03:52 104 113
AlanS 03:55 05:20 136 147
Topical Tim Topical Tim 04:11 03:10 75 81
lickert 04:15 03:30 82 89
MikeOsborne 04:17 03:50 89 96
Roscoe 04:32 04:00 88 95
MK76 04:35 04:39 101 109
chindit 04:37 04:32 98 106
lucyg43484 04:41 04:39 99 107
Tom Stubbs Tom Stubbs 04:46 03:14 67 72
philjordan1147 BUSMAN 04:46 06:38 139 151
alexh 04:47 05:07 106 115
scrabbler 04:51 03:11 65 70
canismiser 04:52 03:44 76 82
andrewlake 04:53 02:03 41 44
LouWeed LouWeed 04:53 04:40 95 103
Paul Bacon 04:54 06:03 123 133
andy 04:55 04:08 84 91
footballblue 04:56 05:10 104 113
d.middleton 04:57 04:42 94 102
tiggis 04:57 05:14 105 114
neilr neilr 05:02 04:58 98 106
March 05:03 04:46 94 102
Ed freshpot 05:04 04:01 79 85
Zander 05:14 04:16 81 88
DunPangolin 05:14 06:02 115 125
Squallaby 05:15 04:05 77 83
7dPenguin 7dPenguin 05:16 03:46 71 77
ChuckB 05:18 05:33 104 113
Tibthorpe 05:19 06:19 118 128
pitcaithlie Pitcaithlie 05:24 04:03 75 81
esmeralda 05:38 05:38 100 108
Crossiant 05:42 05:37 98 106
mcrossib1 05:45 05:05 88 95
MrChumley MrChumley 05:52 06:18 107 116
Looch 05:58 04:33 76 82
hopkinb hopkinb 06:07 05:30 89 96
cath23 06:13 05:39 90 97
PGooden 06:15 06:50 109 118
paul.whitehouse69 06:34 05:13 79 85
julian_w 06:35 06:22 96 104
Kalakuta72 06:36 06:20 95 103
Tudds 06:38 05:31 83 90
jimwetzler 06:39 05:40 85 92
endafk 06:42 03:11 47 51
jon 06:47 06:33 96 104
uvofiz 07:01 05:41 80 86
FraserH 07:01 06:43 95 103
James P 07:05 06:26 90 97
Gussie 07:08 06:34 92 100
Aloysius 07:11 06:11 86 93
Kevin Gregg Kevin Gregg 07:13 06:04 84 91
robinh 07:18 05:25 74 80
earlylight 07:24 05:37 75 81
Puzzleplease 07:27 06:48 91 98
SlumdogEngineer 07:33 05:04 67 72
Mike Harper Mike Harper 07:35 06:14 82 89
plett11 Plett11 08:14 07:56 96 104
Templar Redux Templar 08:30 09:57 117 127
vinyl12345 vinyl1 08:40 03:04 35 38
johndun John Dunleavy 08:40 07:13 83 90
RPY 08:52 05:49 65 70
crosswordian 09:00 06:04 67 72
annbrew 09:28 04:33 48 52
Deezzaa Deezzaa 09:31 07:04 74 80
Edprof 09:38 04:25 45 48
Laputan 10:47 06:35 61 66
rlowin2 11:21 03:30 30 32
Cedric Statherby 11:34 13:00 112 121
WordPlodder BletchleyReject 11:52 11:05 93 101
flashman flashman 13:23 08:00 59 64
Mendes Mendesest 14:04 17:00 120 130
Merlin_55 Merlin 14:50 14:14 95 103

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.