Quick SNITCH

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

Times Quick Cryptic Crossword 2458

Date 10 August 2023
Number 2458
Setter Wurm
Day of week Thursday
NITCH 90
Count of ref solvers 60
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2458

* 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 85
Jason 02:32 02:17 90 100
verlaine 02:36 01:58 75 83
hilarym 02:43 03:15 119 132
cmjhutton 02:44 02:16 82 91
aphis99 aphis99 02:49 02:48 99 110
Flimmy flammy 03:04 02:36 84 93
Topical Tim Topical Tim 03:38 02:23 65 72
richard 03:39 03:33 97 107
markdobell 03:50 03:24 88 97
Heyesey 03:52 03:29 90 100
Kinghedger 03:52 03:15 84 93
chriss 04:01 03:19 82 91
Strober 04:04 03:53 95 105
lickert 04:11 03:47 90 100
AlanS 04:19 03:44 86 95
nina s 04:19 04:20 100 111
tilbee 04:21 03:56 90 100
MikeOsborne 04:21 04:33 104 115
Roscoe 04:26 03:49 86 95
lucyg43484 04:30 03:54 86 95
patrickcates 04:33 04:48 105 116
Tom Stubbs Tom Stubbs 04:36 04:06 89 98
John Walsh 04:37 04:43 102 113
Jim Willis 04:38 02:57 63 70
wwalker50 04:45 04:11 88 97
March 04:46 03:40 76 84
LouWeed LouWeed 04:46 04:03 84 93
andy 04:46 04:16 89 98
alexh 04:47 05:08 107 118
Ed freshpot 04:50 04:02 83 92
MK76 04:53 04:38 94 104
Honggui 04:54 03:36 73 81
Umpire 04:54 05:18 108 120
Zander 05:02 05:01 99 110
7dPenguin 7dPenguin 05:05 04:52 95 105
chilibombom 05:07 05:51 114 126
Squallaby 05:09 05:03 98 108
Paul Bacon 05:09 04:34 88 97
neilr neilr 05:10 04:56 95 105
Tibthorpe 05:12 05:09 99 110
esmeralda 05:23 04:32 84 93
daulbs 05:26 06:11 113 125
Spanna 05:27 05:22 98 108
george.plumbly 05:28 04:36 84 93
Dekkers 05:31 06:04 109 121
Eddddddd 05:34 06:02 108 120
AndyR 05:36 05:34 99 110
Finzi 05:39 04:39 82 91
Paul Hammond Paul Hammond 05:41 04:14 74 82
Shabbo 05:46 04:52 84 93
Looch 05:48 05:22 92 102
Kevin Gregg Kevin Gregg 05:51 04:53 83 92
Dzhigit 05:54 05:24 91 101
cmcnsmith 05:56 06:24 107 118
Carol 05:56 06:04 102 113
GeorgeTz 05:56 05:22 90 100
McBeak McBeak 06:00 05:34 92 102
DunPangolin 06:03 04:59 82 91
PGooden 06:03 05:57 98 108
Tudds 06:05 05:18 87 96
GMcD 06:08 06:22 103 114
earlylight 06:09 05:11 84 93
Blackbeard 06:11 05:13 84 93
Curarist 06:12 04:32 73 81
jimwetzler 06:16 04:58 79 87
James P 06:18 06:14 98 108
JMbrow29 06:19 04:46 75 83
Michael Dove 06:23 04:22 68 75
paul.whitehouse69 06:25 05:09 80 88
Wyn Lewis Wyn Lewis 06:28 05:24 83 92
uvofiz 06:30 05:37 86 95
julian_w 06:34 05:23 81 90
alex.scordellis 06:34 06:34 100 111
Gussie 06:35 05:28 83 92
jon 06:42 06:11 92 102
alastair52 06:43 06:30 96 106
Riche Riche 06:43 06:43 100 111
Kalakuta72 06:45 06:18 93 103
timbo 06:51 06:16 91 101
ulaca ulaca 06:57 06:18 90 100
Doyler 07:15 06:41 92 102
BinLinerBob 07:21 06:05 82 91
FelicityTT 07:42 06:33 85 94
frost 07:51 06:45 85 94
OldSolver 07:52 06:43 85 94
mattindoha 07:57 06:28 81 90

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.