Quick SNITCH

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

Times Quick Cryptic Crossword 2443

Date 20 July 2023
Number 2443
Setter Orpheus
Day of week Thursday
NITCH 91
Count of ref solvers 71
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2443

* 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:40 76 83
Paul Gilbert 02:28 01:44 70 76
Jason 02:32 02:34 101 110
verlaine 02:36 02:53 110 120
mistigris 02:40 02:06 78 85
hilarym 02:43 02:40 98 107
cmjhutton 02:44 02:48 102 112
aphis99 aphis99 02:49 02:55 103 113
Flimmy flammy 03:04 03:47 123 135
Topical Tim Topical Tim 03:38 03:01 83 91
richard 03:39 02:59 81 89
markdobell 03:50 03:00 78 85
Heyesey 03:52 02:44 70 76
glheard 04:02 04:44 117 128
Strober 04:04 03:45 92 101
lickert 04:11 03:25 81 89
chindit 04:13 03:43 88 96
philjordan1147 BUSMAN 04:14 03:27 81 89
nina s 04:19 04:51 112 123
AlanS 04:19 04:56 114 125
MikeOsborne 04:21 03:10 72 79
joelhames 04:21 06:03 139 152
Roscoe 04:26 03:50 86 94
tiggis 04:29 05:05 113 124
trux 04:29 05:29 122 134
lucyg43484 04:30 03:54 86 94
patrickcates 04:33 06:07 134 147
Tom Stubbs Tom Stubbs 04:36 03:32 76 83
Jim Willis 04:38 04:55 106 116
andrewlake 04:44 04:21 91 100
andy 04:46 03:07 65 71
March 04:46 03:36 75 82
LouWeed LouWeed 04:46 04:48 100 109
alexh 04:47 04:19 90 98
denislaw 04:47 03:48 79 86
pitcaithlie Pitcaithlie 04:48 03:48 79 86
Dofray 04:48 05:31 114 125
Ed freshpot 04:50 05:22 111 121
MK76 04:53 04:15 87 95
Umpire 04:54 05:12 106 116
Honggui 04:54 04:16 87 95
michaelbell53 04:58 04:27 89 97
Zander 05:02 04:17 85 93
7dPenguin 7dPenguin 05:05 04:23 86 94
Squallaby 05:09 04:43 91 100
Liari 05:09 04:23 85 93
neilr neilr 05:10 04:19 83 91
Tibthorpe 05:12 04:19 83 91
andy_knott 05:13 04:59 95 104
footballblue 05:17 06:24 121 132
esmeralda 05:23 04:04 75 82
fshephe 05:25 04:46 88 96
daulbs 05:26 05:16 96 105
ChuckB 05:26 04:52 89 97
jimpen 05:26 04:37 84 92
george.plumbly 05:28 04:24 80 87
KET 05:29 03:17 59 64
mw7000 05:29 05:50 106 116
Rabbitoh 05:32 05:02 90 98
AndyR 05:36 06:06 108 118
Finzi 05:39 05:37 99 108
Paul Hammond Paul Hammond 05:41 06:33 115 126
Julian Forbes 05:45 05:04 88 96
Shabbo 05:46 04:15 73 80
Looch 05:48 05:41 97 106
cheryllayne cheryllayne 05:50 04:16 73 80
Carol 05:56 05:39 95 104
nigel 06:00 06:03 100 109
PGooden 06:03 05:20 88 96
Tudds 06:05 05:39 92 101
hopkinb hopkinb 06:08 05:24 88 96
GMcD 06:08 06:09 100 109
ilan 06:17 06:01 95 104
Wyn Lewis Wyn Lewis 06:28 04:59 77 84
chabuduo chabuduo 06:36 06:36 100 109
Nangle 06:41 06:46 101 110
jon 06:42 06:12 92 101
maisiemae 06:45 05:30 81 89
Kalakuta72 06:45 06:24 94 103
DianeRS 06:46 04:53 72 79
Puzzleplease 06:46 05:40 83 91
plett11 Plett11 06:48 06:30 95 104
Edprof 06:49 04:57 72 79
ChrisBrea 06:57 06:19 90 98
ratterz 07:00 06:36 94 103
gsriordan52 07:20 05:52 80 87
Sheen 07:21 05:15 71 78
luxtonj61 07:21 06:05 82 90
Andrew Whiffin 07:25 06:53 92 101
mattindoha 07:57 06:24 80 87
jackk.larg 08:27 06:29 76 83

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.