Quick SNITCH

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

Times Quick Cryptic Crossword 2286

Date 13 December 2022
Number 2286
Setter Teazel
Day of week Tuesday
NITCH 112
Count of ref solvers 59
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2286

* 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 94
Paul Gilbert 02:14 03:08 140 125
Jason 02:35 02:24 92 82
verlaine 02:38 04:15 161 143
mistigris 02:39 03:19 125 111
hilarym 02:50 03:43 131 116
aphis99 aphis99 02:51 02:43 95 84
Flimmy flammy 03:11 03:59 125 111
richard 03:37 03:27 95 84
markdobell 03:39 04:23 120 107
Heyesey 03:41 04:38 125 111
AlanS 03:55 05:15 134 119
glheard 04:06 05:18 129 115
Topical Tim Topical Tim 04:11 04:05 97 86
lickert 04:15 04:17 100 89
MikeOsborne 04:17 04:55 114 101
MK76 04:35 05:14 114 101
chindit 04:37 03:55 84 75
tilbee 04:40 05:21 114 101
lucyg43484 04:41 04:13 90 80
Tom Stubbs Tom Stubbs 04:46 05:52 123 109
philjordan1147 BUSMAN 04:46 04:26 93 83
alexh 04:47 05:59 125 111
scrabbler 04:51 04:26 91 81
LouWeed LouWeed 04:53 05:09 105 93
andrewlake 04:53 03:25 69 61
andy 04:55 06:18 128 114
fshephe 04:56 06:36 133 118
Johninterred 05:00 05:56 118 105
neilr neilr 05:02 06:01 119 106
March 05:03 05:07 101 90
Honggui 05:06 04:51 95 84
DunPangolin 05:14 05:30 105 93
Squallaby 05:15 05:54 112 100
7dPenguin 7dPenguin 05:16 05:34 105 93
Tibthorpe 05:19 05:59 112 100
pitcaithlie Pitcaithlie 05:24 05:40 104 92
esmeralda 05:38 06:55 122 108
Finzi 05:39 05:05 89 79
Crossiant 05:42 07:50 137 122
mcrossib1 05:45 06:36 114 101
Penfold_61 05:48 06:12 106 94
Rabbitoh galspray 05:49 04:02 69 61
Looch 05:58 04:42 78 69
hopkinb hopkinb 06:07 12:22 202 180
cath23 06:13 06:43 108 96
Shabbo 06:32 05:27 83 74
paul.whitehouse69 06:34 05:36 85 75
julian_w 06:35 07:12 109 97
robertbridge 06:36 06:03 91 81
GMcD 06:38 07:38 115 102
Curarist 06:42 06:17 93 83
endafk 06:42 08:18 123 109
edwards.robert1 06:53 05:09 74 66
uvofiz 07:01 08:21 119 106
James P 07:05 07:01 99 88
Kevin Gregg Kevin Gregg 07:13 10:13 141 125
Desdeeloeste Desdeeloeste 07:31 15:16 203 181
TomHerbert 07:44 07:41 99 88
1234 07:51 08:25 107 95
nigel 07:54 06:25 81 72
John Arnold 08:12 06:53 83 74
plett11 Plett11 08:14 08:39 105 93
ulaca ulaca 08:25 08:18 98 87
OldSolver 08:27 08:23 99 88
Templar Redux Templar 08:30 06:55 81 72
johndun John Dunleavy 08:40 11:03 127 113
m5harp 08:46 08:27 96 85
crosswordian 09:00 08:07 90 80
annbrew 09:28 05:17 55 49
Deezzaa Deezzaa 09:31 07:44 81 72
Cedric Statherby 11:34 15:00 129 115
WordPlodder BletchleyReject 11:52 14:08 119 106
140 Mandak 262 Jamuna 16:41 04:59 29 25
bangsar DearHector 21:12 17:00 80 71
Dofray 22:17 06:43 30 26
mozbadel mozbadel 24:24 27:19 111 99
IanV IanV 31:11 37:29 120 107

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.