Quick SNITCH

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

Times Quick Cryptic Crossword 2435

Date 10 July 2023
Number 2435
Setter Teazel
Day of week Monday
NITCH 87
Count of ref solvers 73
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2435

* 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 02:01 92 105
Paul Gilbert 02:28 01:57 79 90
Jason 02:32 02:03 80 91
verlaine 02:36 02:41 103 118
mistigris 02:40 02:11 81 93
hilarym 02:43 02:10 79 90
cmjhutton 02:44 03:23 123 141
aphis99 aphis99 02:49 02:16 80 91
Flimmy flammy 03:04 02:49 91 104
Topical Tim Topical Tim 03:38 04:51 133 152
richard 03:39 02:55 79 90
markdobell 03:50 03:51 100 114
Heyesey 03:52 02:08 55 63
Kinghedger 03:52 03:08 81 93
glheard 04:02 03:47 93 106
Strober 04:04 03:45 92 105
xyster 04:04 04:09 102 117
lickert 04:11 02:46 66 75
chindit 04:13 03:40 86 98
philjordan1147 BUSMAN 04:14 03:25 80 91
nina s 04:19 04:21 100 114
MikeOsborne 04:21 03:17 75 86
tilbee 04:21 03:58 91 104
Roscoe 04:26 03:14 72 82
patrickcates 04:33 05:19 116 133
jfisher60 04:33 04:14 93 106
Tom Stubbs Tom Stubbs 04:36 03:18 71 81
John Walsh 04:37 05:06 110 126
Jim Willis 04:38 04:55 106 121
d.middleton 04:39 04:00 86 98
andrewlake 04:44 02:58 62 71
canismiser 04:45 05:37 118 135
andy 04:46 03:59 83 95
March 04:46 04:43 98 112
LouWeed LouWeed 04:46 03:00 62 71
alexh 04:47 04:02 84 96
denislaw 04:47 03:11 66 75
pitcaithlie Pitcaithlie 04:48 04:29 93 106
Ed freshpot 04:50 04:09 85 97
Ease This Jam 04:50 04:46 98 112
MK76 04:53 04:18 88 101
Umpire 04:54 03:38 74 85
Honggui 04:54 05:00 102 117
michaelbell53 04:58 05:25 109 125
7dPenguin 7dPenguin 05:05 04:19 84 96
Squallaby 05:09 04:20 84 96
Liari 05:09 03:54 75 86
neilr neilr 05:10 04:21 84 96
Tibthorpe 05:12 04:34 87 100
footballblue 05:17 04:04 76 87
Penfold_61 05:18 04:48 90 103
Aly Duncan 05:21 05:07 95 109
esmeralda 05:23 04:07 76 87
daulbs 05:26 05:44 105 120
jimpen 05:26 05:38 103 118
george.plumbly 05:28 05:04 92 105
KET 05:29 04:45 86 98
mw7000 05:29 03:41 67 77
Rabbitoh 05:32 05:11 93 106
john.marshall 05:33 04:10 75 86
Finzi 05:39 04:57 87 100
Shabbo 05:46 05:08 89 102
Looch 05:48 04:31 77 88
cheryllayne cheryllayne 05:50 04:40 80 91
Kevin Gregg Kevin Gregg 05:51 05:28 93 106
SlumdogEngineer 05:54 05:15 88 101
Carol 05:56 05:10 87 100
nigel 06:00 05:27 90 103
DunPangolin 06:03 04:53 80 91
PGooden 06:03 04:54 80 91
Jeremy Weissmann plusjeremy 06:05 04:32 74 85
GMcD 06:08 04:12 68 78
ilan 06:17 04:52 77 88
JMbrow29 06:19 05:04 80 91
IreneC 06:19 05:14 82 94
paul.whitehouse69 06:25 05:35 87 100
uvofiz 06:30 05:45 88 101
julian_w 06:34 05:33 84 96
jon 06:42 05:27 81 93
Puzzleplease 06:46 05:49 85 97
endafk 06:48 05:14 76 87
Edprof 06:49 05:41 83 95
Viscomte 06:51 05:51 85 97
Deezzaa Deezzaa 06:56 04:28 64 73
ulaca ulaca 06:57 04:58 71 81
ChrisBrea 06:57 05:45 82 94
barracuda barracuda 07:08 05:16 73 83
goblin 08:21 05:44 68 78

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.