Quick SNITCH

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

Times Quick Cryptic Crossword 2427

Date 28 June 2023
Number 2427
Setter Orpheus
Day of week Wednesday
NITCH 81
Count of ref solvers 62
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2427

* 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:53 86 106
Paul Gilbert 02:28 02:09 87 107
Jason 02:32 02:05 82 101
verlaine 02:36 02:07 81 100
mistigris 02:40 02:03 76 93
hilarym 02:43 02:31 92 113
cmjhutton 02:44 02:24 87 107
aphis99 aphis99 02:49 02:01 71 87
Topical Tim Topical Tim 03:38 02:49 77 95
markdobell 03:50 04:14 110 135
Heyesey 03:52 02:25 62 76
Kinghedger 03:52 03:06 80 98
glheard 04:02 02:56 72 88
lickert 04:11 03:18 78 96
chindit 04:13 02:54 68 83
philjordan1147 BUSMAN 04:14 02:52 67 82
chriswords 04:14 04:21 102 125
AlanS 04:19 03:27 79 97
MikeOsborne 04:21 03:34 81 100
tilbee 04:21 03:16 75 92
Roscoe 04:26 04:08 93 114
lucyg43484 04:30 03:50 85 104
jfisher60 04:33 03:25 75 92
John Walsh 04:37 04:47 103 127
d.middleton 04:39 04:36 98 120
andrewlake 04:44 02:44 57 70
LouWeed LouWeed 04:46 04:29 94 116
March 04:46 03:57 82 101
alexh 04:47 05:23 112 138
Dofray 04:48 02:42 56 69
Ed freshpot 04:50 04:07 85 104
Ease This Jam 04:50 03:21 69 85
Umpire 04:54 03:16 66 81
Honggui 04:54 03:35 73 90
michaelbell53 04:58 03:58 79 97
Zander 05:02 04:08 82 101
Squallaby 05:09 03:53 75 92
Paul Bacon 05:09 05:50 113 139
neilr neilr 05:10 03:45 72 88
annbrew 05:11 04:32 87 107
footballblue 05:17 06:47 128 158
Penfold_61 05:18 04:27 83 102
esmeralda 05:23 03:09 58 71
daulbs 05:26 03:54 71 87
ChuckB 05:26 04:15 78 96
jimpen 05:26 04:28 82 101
KET 05:29 02:21 42 51
Rabbitoh 05:32 04:51 87 107
AndyR 05:36 04:57 88 108
Shabbo 05:46 04:40 80 98
SlumdogEngineer 05:54 04:24 74 91
Dzhigit 05:54 04:18 72 88
Mark Three 05:58 05:45 96 118
McBeak McBeak 06:00 07:01 116 143
Crossiant 06:01 05:13 86 106
DunPangolin 06:03 05:51 96 118
PGooden 06:03 05:35 92 113
Tudds 06:05 05:15 86 106
Rosron 06:07 05:30 89 109
GMcD 06:08 05:14 85 104
Curarist 06:12 05:07 82 101
ilan 06:17 03:56 62 76
James P 06:18 04:10 66 81
robinh 06:19 05:08 81 100
uvofiz 06:30 04:12 64 79
Mike Harper Mike Harper 06:32 04:34 69 85
Dvynys Dvynys 06:37 04:39 70 86
alastair52 06:43 05:23 80 98
Riche Riche 06:43 06:56 103 127
John Arnold 06:44 05:03 75 92
plett11 Plett11 06:48 05:07 75 92
Edprof 06:49 05:40 83 102
Viscomte 06:51 07:04 103 127
jjspomeroy 06:54 05:45 83 102
Deezzaa Deezzaa 06:56 06:34 94 116
FraserH 06:56 06:26 92 113
Claverton74 06:56 06:22 91 112
ChrisBrea 06:57 06:47 97 119
Bobby D 06:58 06:00 86 106
hookyt 07:13 06:04 84 103
martinede 07:15 06:39 91 112
docg 07:15 06:01 82 101
gsriordan52 07:20 05:48 79 97
dec 07:26 06:18 84 103
crosswordian 07:46 06:07 78 96
jaraab 07:54 05:46 72 88
mattindoha 07:57 06:06 76 93
john.brassey 08:08 05:53 72 88
Laputan 08:18 07:01 84 103

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.