Quick SNITCH

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

Times Quick Cryptic Crossword 2394

Date 12 May 2023
Number 2394
Setter Felix
Day of week Friday
NITCH 108
Count of ref solvers 70
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2394

* 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:09 98 90
Paul Gilbert 02:28 02:44 110 101
Jason 02:32 02:27 96 88
verlaine 02:36 02:50 108 100
mistigris 02:40 03:05 115 106
hilarym 02:43 02:47 102 94
cmjhutton 02:44 02:46 101 93
aphis99 aphis99 02:49 02:26 86 79
Flimmy flammy 03:04 03:09 102 94
Topical Tim Topical Tim 03:38 04:33 125 115
richard 03:39 03:35 98 90
markdobell 03:50 03:34 93 86
Strober 04:04 03:48 93 86
lickert 04:11 05:37 134 124
chindit 04:13 05:25 128 118
philjordan1147 BUSMAN 04:14 04:29 105 97
nina s 04:19 05:34 128 118
MikeOsborne 04:21 05:16 121 112
tilbee 04:21 04:34 104 96
Roscoe 04:26 04:04 91 84
trux 04:29 04:51 108 100
lucyg43484 04:30 05:31 122 112
Tom Stubbs Tom Stubbs 04:36 05:12 113 104
Jim Willis 04:38 05:55 127 117
scrabbler 04:39 05:01 107 99
andrewlake 04:44 06:26 135 125
andy 04:46 06:25 134 124
March 04:46 04:38 97 89
LouWeed LouWeed 04:46 04:39 97 89
alexh 04:47 04:36 96 88
pitcaithlie Pitcaithlie 04:48 05:29 114 105
Ease This Jam 04:50 03:29 72 66
Ed freshpot 04:50 04:36 95 87
Umpire 04:54 03:28 70 64
Honggui 04:54 05:29 111 102
Zander 05:02 06:26 127 117
Squallaby 05:09 05:01 97 89
Liari 05:09 04:40 90 83
neilr neilr 05:10 06:21 122 112
annbrew 05:11 05:45 110 101
andy_knott 05:13 06:18 120 111
Penfold_61 05:18 06:28 122 112
ChuckB 05:26 04:58 91 84
jimpen 05:26 05:25 99 91
george.plumbly 05:28 05:15 96 88
KET 05:29 07:20 133 123
admin 05:31 05:15 95 87
Rabbitoh galspray 05:32 05:29 99 91
Finzi 05:39 07:10 126 116
Paul Hammond Paul Hammond 05:41 05:19 93 86
Shabbo 05:46 07:09 123 113
Looch 05:48 06:37 114 105
squark 05:50 04:45 81 75
Kevin Gregg Kevin Gregg 05:51 07:48 133 123
cath23 05:52 06:04 103 95
Dzhigit 05:54 05:50 98 90
Carol 05:56 07:49 131 121
GeorgeTz 05:56 06:24 107 99
Crossiant 06:01 05:25 90 83
DunPangolin 06:03 06:47 112 103
Tudds 06:05 06:11 101 93
Rosron 06:07 06:25 104 96
GMcD 06:08 05:05 82 75
earlylight 06:09 07:26 120 111
martinphillips 06:09 06:05 98 90
jimwetzler 06:16 07:31 119 110
ilan 06:17 06:26 102 94
James P 06:18 06:36 104 96
JMbrow29 06:19 05:39 89 82
paul.whitehouse69 06:25 07:15 112 103
chrismarch 06:27 07:47 120 111
uvofiz 06:30 06:27 99 91
jon 06:42 07:01 104 96
DrBill 06:42 07:44 115 106
alastair52 06:43 07:06 105 97
Riche Riche 06:43 07:05 105 97
maisiemae 06:45 06:45 100 92
1234 06:48 06:42 98 90
plett11 Plett11 06:48 07:44 113 104
ChrisBrea 06:57 07:43 111 102
Doyler 07:15 07:29 103 95
luxtonj61 07:21 07:28 101 93
Andrew Whiffin 07:25 06:21 85 78
RPY 07:35 07:29 98 90
Templar Redux Templar 07:37 07:53 103 95
TomHerbert 07:52 06:48 86 79
OldSolver 07:52 07:25 94 87
goblin 08:21 07:14 86 79

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.