Quick SNITCH

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

Times Quick Cryptic Crossword 2460

Date 14 August 2023
Number 2460
Setter Mara
Day of week Monday
NITCH 79
Count of ref solvers 66
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2460

* 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
Jason 02:32 02:19 91 115
verlaine 02:36 02:30 96 121
mistigris 02:40 02:09 80 101
hilarym 02:43 02:24 88 111
cmjhutton 02:44 01:48 65 82
aphis99 aphis99 02:49 02:23 84 106
Flimmy flammy 03:04 02:16 73 92
Topical Tim Topical Tim 03:38 04:08 113 143
richard 03:39 03:45 102 129
markdobell 03:50 02:25 63 79
Kinghedger 03:52 03:24 87 110
glheard 04:02 02:47 69 87
Strober 04:04 03:53 95 120
lickert 04:11 02:55 69 87
chindit 04:13 03:44 88 111
chriswords 04:14 03:58 93 117
nina s 04:19 03:22 77 97
joelhames 04:21 03:12 73 92
MikeOsborne 04:21 03:28 79 100
Roscoe 04:26 04:00 90 113
lucyg43484 04:30 03:35 79 100
Tom Stubbs Tom Stubbs 04:36 03:31 76 96
d.middleton 04:39 02:11 46 58
andrewlake 04:44 04:06 86 108
wwalker50 04:45 04:24 92 116
LouWeed LouWeed 04:46 03:21 70 88
andy 04:46 03:57 82 103
March 04:46 04:03 84 106
alexh 04:47 03:42 77 97
Dofray 04:48 02:47 57 72
pitcaithlie Pitcaithlie 04:48 04:05 85 107
Ed freshpot 04:50 04:06 84 106
MK76 04:53 03:09 64 81
Umpire 04:54 02:19 47 59
Honggui 04:54 03:16 66 83
michaelbell53 04:58 05:26 109 137
Zander 05:02 04:07 81 102
7dPenguin 7dPenguin 05:05 03:25 67 84
The Dabbler 05:05 04:17 84 106
Liari 05:09 02:45 53 67
Squallaby 05:09 04:03 78 98
Paul Bacon 05:09 04:41 90 113
neilr neilr 05:10 05:11 100 126
annbrew 05:11 05:08 99 125
Tibthorpe 05:12 03:56 75 94
andy_knott 05:13 04:18 82 103
DaveH 05:15 05:15 100 126
footballblue 05:17 05:25 102 129
esmeralda 05:23 04:03 75 94
fshephe 05:25 03:59 73 92
daulbs 05:26 02:46 50 63
mw7000 05:29 03:35 65 82
Dekkers 05:31 04:36 83 105
Rabbitoh 05:32 02:53 52 65
Finzi 05:39 04:45 84 106
Paul Hammond Paul Hammond 05:41 03:43 65 82
Looch 05:48 05:01 86 108
Kevin Gregg Kevin Gregg 05:51 04:35 78 98
cath23 05:52 04:36 78 98
Dzhigit 05:54 05:21 90 113
Carol 05:56 04:38 78 98
GeorgeTz 05:56 05:05 85 107
Mark Three 05:58 04:56 82 103
McBeak McBeak 06:00 04:47 79 100
Crossiant 06:01 04:35 76 96
DunPangolin 06:03 04:59 82 103
Tudds 06:05 05:14 86 108
Rosron 06:07 04:40 76 96
GMcD 06:08 05:19 86 108
hopkinb hopkinb 06:08 04:44 77 97
Blackbeard 06:11 04:29 72 91
ilan 06:17 04:00 63 79
robinh 06:19 05:22 84 106
andrejpanjkov 06:19 05:17 83 105
paul.whitehouse69 06:25 05:19 82 103
Wyn Lewis Wyn Lewis 06:28 02:42 41 51
Mike Harper Mike Harper 06:32 04:35 70 88
julian_w 06:34 05:08 78 98
Nangle 06:41 03:46 56 70
KenD51 06:42 02:47 41 51
Kalakuta72 06:45 05:06 75 94
DianeRS 06:46 05:19 78 98
Corymbia Corymbia 06:57 05:27 78 98
hookyt 07:13 05:04 70 88
Doyler 07:15 03:09 43 54
martinede 07:15 05:05 70 88
TomHerbert 07:52 04:50 61 77
BletchleyReject 08:27 02:00 23 29

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.