Quick SNITCH

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

Times Quick Cryptic Crossword 2436

Date 11 July 2023
Number 2436
Day of week Tuesday
NITCH 93
Count of ref solvers 69
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2436

* 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:08 97 104
Paul Gilbert 02:28 02:26 98 105
Jason 02:32 02:39 104 111
verlaine 02:36 02:01 77 82
mistigris 02:40 02:09 80 86
hilarym 02:43 02:20 85 91
cmjhutton 02:44 02:46 101 108
aphis99 aphis99 02:49 02:23 84 90
Flimmy flammy 03:04 02:42 88 94
Topical Tim Topical Tim 03:38 03:20 91 97
richard 03:39 03:44 102 109
markdobell 03:50 02:44 71 76
Heyesey 03:52 02:54 75 80
Kinghedger 03:52 02:44 70 75
glheard 04:02 03:29 86 92
Strober 04:04 03:42 90 96
lickert 04:11 03:23 80 86
chindit 04:13 04:49 114 122
MikeOsborne 04:21 05:28 125 134
tilbee 04:21 03:52 88 94
Roscoe 04:26 04:06 92 98
lucyg43484 04:30 04:12 93 100
patrickcates 04:33 03:23 74 79
Tom Stubbs Tom Stubbs 04:36 05:54 128 137
d.middleton 04:39 05:06 109 117
andrewlake 04:44 03:14 68 73
canismiser 04:45 05:09 108 116
andy 04:46 04:42 98 105
March 04:46 04:24 92 98
LouWeed LouWeed 04:46 04:10 87 93
alexh 04:47 03:53 81 87
denislaw 04:47 04:18 89 95
pitcaithlie Pitcaithlie 04:48 04:40 97 104
Ed freshpot 04:50 04:01 83 89
MK76 04:53 04:06 83 89
Umpire 04:54 04:13 86 92
Honggui 04:54 04:50 98 105
michaelbell53 04:58 03:54 78 83
7dPenguin 7dPenguin 05:05 05:05 100 107
Liari 05:09 04:22 84 90
Squallaby 05:09 05:00 97 104
neilr neilr 05:10 04:19 83 89
annbrew 05:11 05:36 108 116
Tibthorpe 05:12 03:57 75 80
footballblue 05:17 06:01 113 121
Penfold_61 05:18 04:32 85 91
Aly Duncan 05:21 04:09 77 82
fshephe 05:25 05:12 96 103
daulbs 05:26 05:37 103 110
george.plumbly 05:28 06:24 117 125
KET 05:29 06:05 110 118
mw7000 05:29 06:01 109 117
jdrubin 05:29 06:25 117 125
Dekkers 05:31 05:39 102 109
admin 05:31 05:54 106 113
stguest2 05:32 05:56 107 115
AndyR 05:36 05:56 105 112
Finzi 05:39 06:07 108 116
Julian Forbes 05:45 06:26 111 119
Shabbo 05:46 05:27 94 101
Looch 05:48 05:45 99 106
cheryllayne cheryllayne 05:50 06:15 107 115
SlumdogEngineer 05:54 05:10 87 93
Dzhigit 05:54 04:37 78 83
SimonB 05:56 05:03 85 91
Carol 05:56 04:55 82 88
GeorgeTz 05:56 05:52 98 105
McBeak McBeak 06:00 04:53 81 87
nigel 06:00 05:02 83 89
Crossiant 06:01 04:44 78 83
DunPangolin 06:03 06:12 102 109
PGooden 06:03 05:26 89 95
Jeremy Weissmann plusjeremy 06:05 05:13 85 91
Tudds 06:05 06:18 103 110
GMcD 06:08 06:26 104 111
martinphillips 06:09 04:01 65 69
jimwetzler 06:16 06:33 104 111
James P 06:18 05:06 80 86
IreneC 06:19 05:06 80 86
JMbrow29 06:19 06:38 105 112
Wyn Lewis Wyn Lewis 06:28 06:25 99 106
william.horner 06:44 06:23 94 101
DianeRS 06:46 05:57 87 93
1234 06:48 05:10 75 80
endafk 06:48 06:12 91 97
Edprof 06:49 05:23 78 83
Hodge21 06:49 06:31 95 102
Viscomte 06:51 05:58 87 93
jjspomeroy 06:54 05:05 73 78
benedick 07:04 06:11 87 93
Templar Redux Templar 07:37 05:59 78 83
crosswordian 07:46 06:01 77 82

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.