Quick SNITCH

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

Times Quick Cryptic Crossword 2429

Date 30 June 2023
Number 2429
Setter Mara
Day of week Friday
NITCH 109
Count of ref solvers 74
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2429

* 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:21 107 98
Paul Gilbert 02:28 02:16 91 83
Jason 02:32 02:20 92 84
verlaine 02:36 02:20 89 81
mistigris 02:40 02:44 102 93
hilarym 02:43 03:15 119 109
cmjhutton 02:44 03:00 109 100
aphis99 aphis99 02:49 02:59 105 96
Flimmy flammy 03:04 02:34 83 76
Topical Tim Topical Tim 03:38 04:30 123 112
richard 03:39 03:44 102 93
markdobell 03:50 04:19 112 102
Heyesey 03:52 03:44 96 88
glheard 04:02 06:03 150 137
Strober 04:04 03:58 97 88
lickert 04:11 03:45 89 81
chindit 04:13 06:36 156 143
philjordan1147 BUSMAN 04:14 05:23 127 116
nina s 04:19 07:50 181 166
AlanS 04:19 04:26 102 93
MikeOsborne 04:21 05:37 129 118
tilbee 04:21 05:32 127 116
Roscoe 04:26 04:56 111 101
trux 04:29 04:49 107 98
lucyg43484 04:30 04:00 88 80
patrickcates 04:33 04:46 104 95
Tom Stubbs Tom Stubbs 04:36 05:49 126 115
Jim Willis 04:38 05:01 108 99
andrewlake 04:44 04:59 105 96
canismiser 04:45 05:04 106 97
March 04:46 03:57 82 75
LouWeed LouWeed 04:46 04:21 91 83
denislaw 04:47 04:22 91 83
alexh 04:47 04:10 87 79
Ed freshpot 04:50 05:30 113 103
Ease This Jam 04:50 06:45 139 127
MK76 04:53 05:47 118 108
Umpire 04:54 03:39 74 67
Squallaby 05:09 05:52 113 103
neilr neilr 05:10 05:02 97 88
Tibthorpe 05:12 05:16 101 92
Penfold_61 05:18 04:56 93 85
esmeralda 05:23 07:14 134 122
fshephe 05:25 06:18 116 106
ChuckB 05:26 06:03 111 101
jimpen 05:26 06:33 120 110
george.plumbly 05:28 05:23 98 89
KET 05:29 08:21 152 139
Rabbitoh 05:32 04:38 83 76
AndyR 05:36 05:48 103 94
Finzi 05:39 06:17 111 101
Shabbo 05:46 06:02 104 95
Looch 05:48 05:37 96 88
Kevin Gregg Kevin Gregg 05:51 05:52 100 91
SlumdogEngineer 05:54 06:31 110 100
Dzhigit 05:54 05:21 90 82
SimonB 05:56 06:36 111 101
Carol 05:56 07:04 119 109
McBeak McBeak 06:00 05:45 95 87
nigel 06:00 07:17 121 111
Crossiant 06:01 06:17 104 95
DunPangolin 06:03 06:05 100 91
PGooden 06:03 05:49 96 88
Tudds 06:05 06:45 110 100
GMcD 06:08 05:13 85 77
martinphillips 06:09 07:08 115 105
Curarist 06:12 07:06 114 104
jimwetzler 06:16 07:59 127 116
ilan 06:17 06:15 99 90
robinh 06:19 05:13 82 75
JMbrow29 06:19 07:48 123 112
paul.whitehouse69 06:25 07:01 109 100
uvofiz 06:30 07:20 112 102
Mike Harper Mike Harper 06:32 06:46 103 94
Gussie 06:35 06:48 103 94
Nangle 06:41 06:30 97 88
jon 06:42 07:05 105 96
alastair52 06:43 07:58 118 108
Puzzleplease 06:46 07:26 109 100
endafk 06:48 07:58 117 107
raincloud 06:49 07:47 114 104
Viscomte 06:51 07:01 102 93
Corymbia Corymbia 06:57 08:17 119 109
ratterz 07:00 07:14 103 94
barracuda barracuda 07:08 07:56 111 101
martinede 07:15 08:05 111 101
gsriordan52 07:20 07:28 101 92
vefatica vefatica 07:46 08:24 108 99
frost 07:51 07:41 97 88
Laputan 08:18 08:00 96 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.