Quick SNITCH

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

Times Quick Cryptic Crossword 2399

Date 19 May 2023
Number 2399
Setter Izetti
Day of week Friday
NITCH 94
Count of ref solvers 72
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2399

* 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:05 95 101
Paul Gilbert 02:28 02:17 92 97
Jason 02:32 01:49 71 75
verlaine 02:36 02:16 87 92
mistigris 02:40 02:43 101 107
hilarym 02:43 02:38 96 102
aphis99 aphis99 02:49 02:28 87 92
Topical Tim Topical Tim 03:38 03:03 83 88
richard 03:39 03:31 96 102
markdobell 03:50 02:54 75 79
Heyesey 03:52 02:27 63 67
lickert 04:11 03:15 77 81
chindit 04:13 03:27 81 86
philjordan1147 BUSMAN 04:14 03:19 78 82
nina s 04:19 04:40 108 114
PaulCooke 04:19 04:45 110 117
MikeOsborne 04:21 04:46 109 115
tilbee 04:21 03:45 86 91
Roscoe 04:26 03:43 83 88
trux 04:29 03:17 73 77
lucyg43484 04:30 05:03 112 119
Tom Stubbs Tom Stubbs 04:36 04:28 97 103
John Walsh 04:37 04:16 92 97
Jim Willis 04:38 04:15 91 96
scrabbler 04:39 04:51 104 110
andrewlake 04:44 05:05 107 113
canismiser 04:45 03:15 68 72
andy 04:46 04:56 103 109
March 04:46 03:57 82 87
LouWeed LouWeed 04:46 05:09 108 114
alexh 04:47 06:29 135 143
Ed freshpot 04:50 03:22 69 73
Ease This Jam 04:50 04:52 100 106
MK76 04:53 04:25 90 95
Umpire 04:54 05:03 103 109
Honggui 04:54 04:34 93 98
Zander 05:02 06:34 130 138
7dPenguin 7dPenguin 05:05 04:06 80 85
annbrew 05:11 04:07 79 84
Tibthorpe 05:12 05:06 98 104
andy_knott 05:13 04:09 79 84
footballblue 05:17 06:20 119 126
fishernick79 05:19 04:46 89 94
Aly Duncan 05:21 04:22 81 86
esmeralda 05:23 06:44 125 132
fshephe 05:25 05:35 103 109
daulbs 05:26 05:04 93 98
ChuckB 05:26 05:27 100 106
Spanna 05:27 06:02 110 117
george.plumbly 05:28 04:58 90 95
mw7000 05:29 04:57 90 95
Rabbitoh 05:32 04:05 73 77
john.marshall 05:33 06:09 110 117
Finzi 05:39 04:35 81 86
Paul Hammond Paul Hammond 05:41 05:28 96 102
lazydays 05:44 04:05 71 75
Shabbo 05:46 05:40 98 104
Looch 05:48 05:30 94 100
squark 05:50 06:19 108 114
Kevin Gregg Kevin Gregg 05:51 06:17 107 113
MrChumley MrChumley 05:52 06:17 107 113
cath23 05:52 04:30 76 80
Tommo87 05:53 05:33 94 100
SlumdogEngineer 05:54 05:24 91 96
Dzhigit 05:54 04:51 82 87
Carol 05:56 05:15 88 93
nigel 06:00 04:45 79 84
Crossiant 06:01 06:48 113 120
DunPangolin 06:03 05:30 90 95
Tudds 06:05 06:54 113 120
Rosron 06:07 06:30 106 112
GMcD 06:08 06:24 104 110
Curarist 06:12 04:15 68 72
ilan 06:17 06:22 101 107
James P 06:18 06:13 98 104
robinh 06:19 06:06 96 102
paul.whitehouse69 06:25 06:04 94 100
Aloysius 06:28 06:12 95 101
uvofiz 06:30 06:45 103 109
Mike Harper Mike Harper 06:32 04:35 70 74
Nangle 06:41 06:35 98 104
jon 06:42 05:14 78 82
DrBill 06:42 06:02 90 95
Viscomte 06:51 05:47 84 89
FraserH 06:56 05:43 82 87
ulaca ulaca 06:57 06:57 100 106
ratterz 07:00 06:51 97 103
benedick 07:04 06:50 96 102
kath 07:10 06:14 86 91
martinede 07:15 06:09 84 89
jaraab 07:54 06:44 85 90

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.