Quick SNITCH

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

Times Quick Cryptic Crossword 2456

Date 08 August 2023
Number 2456
Setter Trelawney
Day of week Tuesday
NITCH 76
Count of ref solvers 68
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2456

* 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:54 77 101
Jason 02:32 01:49 71 93
verlaine 02:36 01:59 76 100
mistigris 02:40 01:52 70 92
hilarym 02:43 02:26 89 117
cmjhutton 02:44 02:15 82 107
aphis99 aphis99 02:49 02:15 79 103
Flimmy flammy 03:04 02:05 67 88
Topical Tim Topical Tim 03:38 03:21 92 121
richard 03:39 02:45 75 98
boulemiche 03:45 03:37 96 126
markdobell 03:50 02:20 60 78
Heyesey 03:52 02:56 75 98
Kinghedger 03:52 02:44 70 92
chriss 04:01 03:11 79 103
xyster 04:04 02:58 72 94
lickert 04:11 03:08 74 97
chindit 04:13 03:10 75 98
chriswords 04:14 03:48 89 117
tilbee 04:21 03:15 74 97
MikeOsborne 04:21 04:20 99 130
Roscoe 04:26 03:38 81 106
tiggis 04:29 03:44 83 109
trux 04:29 03:49 85 111
lucyg43484 04:30 03:01 67 88
patrickcates 04:33 04:31 99 130
Tom Stubbs Tom Stubbs 04:36 03:10 68 89
John Walsh 04:37 04:11 90 118
Jim Willis 04:38 03:12 69 90
andrewlake 04:44 03:19 70 92
canismiser 04:45 04:36 96 126
andy 04:46 03:23 70 92
March 04:46 03:27 72 94
LouWeed LouWeed 04:46 05:04 106 139
alexh 04:47 04:42 98 128
pitcaithlie Pitcaithlie 04:48 05:02 104 136
Ed freshpot 04:50 04:18 88 115
Honggui 04:54 03:26 70 92
Umpire 04:54 02:25 49 64
Zander 05:02 03:58 78 102
7dPenguin 7dPenguin 05:05 04:23 86 113
Squallaby 05:09 04:34 88 115
Paul Bacon 05:09 04:45 92 121
neilr neilr 05:10 03:37 70 92
annbrew 05:11 04:36 88 115
Tibthorpe 05:12 04:58 95 125
andy_knott 05:13 03:53 74 97
Penfold_61 05:18 03:56 74 97
fishernick79 05:19 03:12 60 78
Aly Duncan 05:21 03:40 68 89
esmeralda 05:23 03:18 61 80
fshephe 05:25 03:37 66 86
daulbs 05:26 02:52 52 68
ChuckB 05:26 04:56 90 118
george.plumbly 05:28 03:08 57 75
MossDef 05:30 03:56 71 93
Dekkers 05:31 04:33 82 107
Rabbitoh galspray 05:32 04:59 90 118
AndyR 05:36 04:08 73 96
Paul Hammond Paul Hammond 05:41 04:40 82 107
Shabbo 05:46 05:04 87 114
Looch 05:48 04:38 79 103
cheryllayne cheryllayne 05:50 03:37 62 81
Kevin Gregg Kevin Gregg 05:51 03:43 63 82
cath23 05:52 03:40 62 81
Dzhigit 05:54 05:02 85 111
cmcnsmith 05:56 04:23 73 96
Carol 05:56 04:32 76 100
GeorgeTz 05:56 04:40 78 102
McBeak McBeak 06:00 03:45 62 81
Crossiant 06:01 04:29 74 97
PGooden 06:03 05:00 82 107
Tudds 06:05 04:50 79 103
GMcD 06:08 04:05 66 86
hopkinb hopkinb 06:08 04:49 78 102
earlylight 06:09 03:48 61 80
martinphillips 06:09 05:00 81 106
cerds 06:14 04:57 79 103
Michael Dove 06:23 04:16 66 86
paul.whitehouse69 06:25 05:04 78 102
uvofiz 06:30 04:33 70 92
jon 06:42 04:53 72 94
alastair52 06:43 04:17 63 82
Puzzleplease 06:46 05:08 75 98
endafk 06:48 04:26 65 85
plett11 Plett11 06:48 05:05 74 97
ratterz 07:00 04:27 63 82
Cryptique 07:17 05:05 69 90
Cuppa378 07:32 04:36 61 80
Jcal 08:01 05:02 62 81

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.