Quick SNITCH

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

Times Quick Cryptic Crossword 2465

Date 21 August 2023
Number 2465
Setter Oink
Day of week Monday
NITCH 83
Count of ref solvers 70
Ref solvers excluded with errors 2
Link to crossword View Crossword*
Times for the Times Link 2465

* 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
Paul Gilbert 02:28 01:41 68 81
Jason 02:32 02:03 80 96
verlaine 02:36 02:40 102 122
mistigris 02:40 02:14 83 100
hilarym 02:43 02:16 83 100
cmjhutton 02:44 02:09 78 93
aphis99 aphis99 02:49 02:24 85 102
Flimmy flammy 03:04 04:27 145 174
Topical Tim Topical Tim 03:38 03:01 83 100
richard 03:39 02:22 64 77
markdobell 03:50 03:12 83 100
Kinghedger 03:52 03:42 95 114
chriss 04:01 03:03 75 90
glheard 04:02 03:24 84 101
Strober 04:04 04:17 105 126
lickert 04:11 03:56 94 113
chindit 04:13 03:45 88 106
chriswords 04:14 04:14 100 120
AlanS 04:19 03:27 79 95
MikeOsborne 04:21 04:39 106 127
tilbee 04:21 04:07 94 113
Roscoe 04:26 04:10 93 112
lucyg43484 04:30 03:58 88 106
patrickcates 04:33 05:12 114 137
jfisher60 04:33 04:18 94 113
Tom Stubbs Tom Stubbs 04:36 03:48 82 98
John Walsh 04:37 04:53 105 126
andrewlake 04:44 04:12 88 106
canismiser 04:45 05:33 116 139
wwalker50 04:45 03:47 79 95
andy 04:46 03:44 78 93
March 04:46 04:07 86 103
LouWeed LouWeed 04:46 03:23 70 84
alexh 04:47 02:24 50 60
Dofray 04:48 05:27 113 136
pitcaithlie Pitcaithlie 04:48 03:25 71 85
Ed freshpot 04:50 04:32 93 112
MK76 04:53 03:22 68 81
Umpire 04:54 04:49 98 118
7dPenguin 7dPenguin 05:05 04:26 87 104
Squallaby 05:09 04:31 87 104
Liari 05:09 04:12 81 97
neilr neilr 05:10 04:58 96 115
Tibthorpe 05:12 04:29 86 103
footballblue 05:17 05:17 100 120
Aly Duncan 05:21 04:21 81 97
esmeralda 05:23 04:43 87 104
fshephe 05:25 04:13 77 92
daulbs 05:26 03:46 69 83
pammar 05:26 05:40 104 125
george.plumbly 05:28 04:57 90 108
KET 05:29 03:31 64 77
mw7000 05:29 03:48 69 83
Rabbitoh 05:32 05:18 95 114
Finzi 05:39 05:09 91 109
Paul Hammond Paul Hammond 05:41 05:17 92 110
Looch 05:48 04:10 71 85
cheryllayne cheryllayne 05:50 06:04 104 125
Kevin Gregg Kevin Gregg 05:51 04:01 68 81
MrChumley MrChumley 05:52 05:06 86 103
cath23 05:52 04:08 70 84
SlumdogEngineer 05:54 04:26 75 90
GeorgeTz 05:56 05:33 93 112
Crossiant 06:01 04:12 69 83
PGooden 06:03 05:25 89 107
Tudds 06:05 04:03 66 79
GMcD 06:08 03:42 60 72
earlylight 06:09 04:53 79 95
Blackbeard 06:11 03:37 58 69
Curarist 06:12 05:33 89 107
jimwetzler 06:16 04:05 65 78
ilan 06:17 04:09 66 79
James P 06:18 05:24 85 102
robinh 06:19 05:49 92 110
Mike Mansbridge 06:24 05:20 83 100
uvofiz 06:30 04:15 65 78
julian_w 06:34 05:40 86 103
Nangle 06:41 04:49 72 86
jon 06:42 05:34 83 100
DrBill 06:42 05:58 89 107
Puzzleplease 06:46 05:47 85 102
DianeRS 06:46 04:40 68 81
1234 06:48 05:31 81 97
plett11 Plett11 06:48 04:54 72 86
Viscomte 06:51 04:37 67 80
Corymbia Corymbia 06:57 06:02 86 103
ChrisBrea 06:57 05:53 84 101
benedick 07:04 05:50 82 98
dec 07:26 04:53 65 78
frost 07:51 05:56 75 90
Doofenschmirtz Doofenschmirtz 16:37 09:13 55 66

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.