Quick SNITCH

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

Times Quick Cryptic Crossword 2445

Date 24 July 2023
Number 2445
Setter Trelawney
Day of week Monday
NITCH 86
Count of ref solvers 64
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2445

* 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
mohn 02:11 01:43 78 90
Paul Gilbert 02:28 02:07 85 98
verlaine 02:36 02:21 90 104
mistigris 02:40 02:04 77 89
hilarym 02:43 02:18 84 97
cmjhutton 02:44 02:02 74 86
Flimmy flammy 03:04 02:43 88 102
Topical Tim Topical Tim 03:38 03:15 89 103
richard 03:39 03:27 94 109
markdobell 03:50 02:48 73 84
Heyesey 03:52 02:38 68 79
glheard 04:02 03:44 92 106
lickert 04:11 03:32 84 97
chindit 04:13 04:30 106 123
philjordan1147 BUSMAN 04:14 03:08 74 86
nina s 04:19 03:38 84 97
AlanS 04:19 04:34 105 122
MikeOsborne 04:21 02:48 64 74
tilbee 04:21 04:11 96 111
Roscoe 04:26 04:08 93 108
tiggis 04:29 04:27 99 115
trux 04:29 03:39 81 94
patrickcates 04:33 04:12 92 106
Tom Stubbs Tom Stubbs 04:36 04:39 101 117
Jim Willis 04:38 03:32 76 88
d.middleton 04:39 05:02 108 125
wwalker50 04:45 04:08 87 101
LouWeed LouWeed 04:46 04:51 101 117
March 04:46 05:05 106 123
andy 04:46 04:21 91 105
alexh 04:47 04:10 87 101
Ed freshpot 04:50 04:03 83 96
MK76 04:53 04:14 86 100
Umpire 04:54 03:26 70 81
Honggui 04:54 03:57 80 93
Zander 05:02 04:29 89 103
7dPenguin 7dPenguin 05:05 04:24 86 100
Squallaby 05:09 04:31 87 101
Liari 05:09 03:46 73 84
Paul Bacon 05:09 05:38 109 126
neilr neilr 05:10 05:01 97 112
Tibthorpe 05:12 05:58 114 132
footballblue 05:17 02:03 38 44
Penfold_61 05:18 05:08 96 111
esmeralda 05:23 05:28 101 117
fshephe 05:25 05:23 99 115
daulbs 05:26 03:49 70 81
george.plumbly 05:28 04:19 78 90
KET 05:29 04:04 74 86
Dekkers 05:31 05:02 91 105
AndyR 05:36 04:08 73 84
Finzi 05:39 05:18 93 108
Paul Hammond Paul Hammond 05:41 04:54 86 100
Looch 05:48 04:27 76 88
squark 05:50 05:28 93 108
cheryllayne cheryllayne 05:50 05:52 100 116
cath23 05:52 04:02 68 79
MrChumley MrChumley 05:52 05:53 100 116
Dzhigit 05:54 05:04 85 98
McBeak McBeak 06:00 05:37 93 108
Crossiant 06:01 06:06 101 117
DunPangolin 06:03 05:01 82 95
Tudds 06:05 05:46 94 109
Jeremy Weissmann plusjeremy 06:05 05:49 95 110
Rosron 06:07 04:59 81 94
Curarist 06:12 05:20 86 100
ilan 06:17 04:31 71 82
James P 06:18 05:44 91 105
Mike Mansbridge 06:24 04:45 74 86
paul.whitehouse69 06:25 04:50 75 87
Wyn Lewis Wyn Lewis 06:28 03:54 60 69
uvofiz 06:30 05:08 78 90
Nuck_the_king 06:34 01:45 26 30
Gussie 06:35 05:21 81 94
valerian1967 06:35 05:26 82 95
robertbridge 06:38 06:02 90 104
KenD51 06:42 04:05 60 69
JeffHobbs 06:42 05:27 81 94
Riche Riche 06:43 05:35 83 96
rburman 06:43 06:06 90 104
plett11 Plett11 06:48 05:53 86 100
raincloud 06:49 05:40 83 96
Corymbia Corymbia 06:57 06:04 87 101
ratterz 07:00 05:20 76 88
m5harp 07:15 05:52 80 93
Cuppa378 07:32 05:46 76 88

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.