Quick SNITCH

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

Times Quick Cryptic Crossword 2454

Date 04 August 2023
Number 2454
Setter Beck
Day of week Friday
NITCH 98
Count of ref solvers 69
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2454

* 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 02:46 112 114
verlaine 02:36 02:21 90 91
mistigris 02:40 02:45 103 105
hilarym 02:43 02:20 85 86
cmjhutton 02:44 02:29 90 91
aphis99 aphis99 02:49 03:04 108 110
Flimmy flammy 03:04 03:44 121 123
Topical Tim Topical Tim 03:38 04:16 117 119
richard 03:39 04:26 121 123
markdobell 03:50 03:28 90 91
Heyesey 03:52 04:12 108 110
Kinghedger 03:52 04:25 114 116
chriss 04:01 04:22 108 110
glheard 04:02 04:11 103 105
Strober 04:04 04:29 110 112
lickert 04:11 03:36 86 87
chindit 04:13 03:46 89 90
chriswords 04:14 04:17 101 103
nina s 04:19 04:55 113 115
AlanS 04:19 05:25 125 127
joelhames 04:21 05:11 119 121
tilbee 04:21 05:01 115 117
Roscoe 04:26 03:33 80 81
tiggis 04:29 04:37 102 104
lucyg43484 04:30 04:17 95 96
patrickcates 04:33 04:03 89 90
Tom Stubbs Tom Stubbs 04:36 04:12 91 92
Jim Willis 04:38 03:30 75 76
andrewlake 04:44 04:21 91 92
canismiser 04:45 04:34 96 97
wwalker50 04:45 04:02 84 85
LouWeed LouWeed 04:46 04:46 100 102
andy 04:46 06:38 139 141
March 04:46 05:41 119 121
alexh 04:47 04:03 84 85
Dofray 04:48 06:20 131 133
Ease This Jam 04:50 04:04 84 85
Ed freshpot 04:50 05:11 107 109
MK76 04:53 04:30 92 93
Umpire 04:54 02:51 58 59
Honggui 04:54 05:11 105 107
Zander 05:02 06:27 128 130
7dPenguin 7dPenguin 05:05 05:52 115 117
Squallaby 05:09 04:50 93 94
Liari 05:09 03:41 71 72
neilr neilr 05:10 05:32 107 109
Tibthorpe 05:12 05:55 113 115
andy_knott 05:13 04:49 92 93
Penfold_61 05:18 06:24 120 122
Aly Duncan 05:21 05:38 105 107
esmeralda 05:23 04:35 85 86
fshephe 05:25 04:57 91 92
daulbs 05:26 06:13 114 116
george.plumbly 05:28 05:31 100 102
jdrubin 05:29 05:59 109 111
Dekkers 05:31 05:07 92 93
admin 05:31 05:26 98 100
Rabbitoh 05:32 06:03 109 111
Finzi 05:39 05:29 97 98
Paul Hammond Paul Hammond 05:41 06:20 111 113
Shabbo 05:46 07:05 122 124
Looch 05:48 05:44 98 100
Dzhigit 05:54 04:50 81 82
Carol 05:56 04:14 71 72
GeorgeTz 05:56 05:57 100 102
McBeak McBeak 06:00 04:09 69 70
Crossiant 06:01 05:03 83 84
Jeremy Weissmann plusjeremy 06:05 03:57 64 65
Rosron 06:07 06:07 100 102
earlylight 06:09 05:51 95 96
cerds 06:14 06:49 109 111
jimwetzler 06:16 05:57 94 95
ilan 06:17 06:00 95 96
James P 06:18 04:43 74 75
JMbrow29 06:19 03:39 57 58
Michael Dove 06:23 06:05 95 96
Gussie 06:35 06:29 98 100
valerian1967 06:35 05:09 78 79
Rubeculaw Rubeculaw 06:39 06:42 100 102
DrBill 06:42 06:03 90 91
alastair52 06:43 06:47 100 102
Riche Riche 06:43 05:51 87 88
maisiemae 06:45 06:56 102 104
ChrisBrea 06:57 06:47 97 98
ratterz 07:00 07:02 100 102
benedick 07:04 06:49 96 97
gsriordan52 07:20 06:56 94 95
Sheen 07:21 06:25 87 88
Cuppa378 07:32 06:06 80 81
pauliwan 08:00 06:29 81 82
nigelmzzz 08:44 06:27 73 74

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.