Quick SNITCH

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

Times Quick Cryptic Crossword 2425

Date 26 June 2023
Number 2425
Setter Teazel
Day of week Monday
NITCH 113
Count of ref solvers 68
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2425

* 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:21 107 94
Paul Gilbert 02:28 03:57 160 141
Jason 02:32 02:36 102 90
verlaine 02:36 02:00 76 67
mistigris 02:40 02:47 104 92
hilarym 02:43 03:03 112 99
cmjhutton 02:44 03:28 126 111
aphis99 aphis99 02:49 03:14 114 100
Flimmy flammy 03:04 03:29 113 100
Topical Tim Topical Tim 03:38 03:30 96 84
richard 03:39 03:19 90 79
Heyesey 03:52 04:04 105 92
Kinghedger 03:52 04:38 119 105
andybannister 03:59 02:26 61 53
glheard 04:02 04:34 113 100
Strober 04:04 03:59 97 85
lickert 04:11 05:35 133 117
chindit 04:13 03:19 78 69
philjordan1147 BUSMAN 04:14 04:10 98 86
nina s 04:19 08:05 187 165
tilbee 04:21 04:08 95 84
MikeOsborne 04:21 05:03 116 102
Roscoe 04:26 05:31 124 109
Tom Stubbs Tom Stubbs 04:36 04:41 101 89
Jim Willis 04:38 04:22 94 83
andrewlake 04:44 05:08 108 95
March 04:46 05:23 112 99
LouWeed LouWeed 04:46 04:43 98 86
alexh 04:47 05:10 108 95
pitcaithlie Pitcaithlie 04:48 05:05 105 92
Ed freshpot 04:50 05:10 106 93
MK76 04:53 05:26 111 98
Umpire 04:54 05:31 112 99
Honggui 04:54 06:12 126 111
Zander 05:02 04:38 92 81
7dPenguin 7dPenguin 05:05 05:17 103 91
Squallaby 05:09 07:31 145 128
Tibthorpe 05:12 06:10 118 104
footballblue 05:17 02:26 46 40
Aly Duncan 05:21 05:40 105 92
esmeralda 05:23 07:16 134 118
fshephe 05:25 05:07 94 83
george.plumbly 05:28 07:17 133 117
KET 05:29 06:30 118 104
Dekkers 05:31 07:37 138 122
Rabbitoh 05:32 05:58 107 94
AndyR 05:36 06:58 124 109
Finzi 05:39 06:14 110 97
Shabbo 05:46 06:09 106 93
Looch 05:48 07:27 128 113
Kevin Gregg Kevin Gregg 05:51 07:54 135 119
cath23 05:52 08:45 149 131
Dzhigit 05:54 05:51 99 87
SimonB 05:56 07:24 124 109
Carol 05:56 04:24 74 65
McBeak McBeak 06:00 05:57 99 87
Crossiant 06:01 08:26 140 123
Tudds 06:05 06:40 109 96
GMcD 06:08 05:47 94 83
Curarist 06:12 07:28 120 106
James P 06:18 09:00 142 125
IreneC 06:19 08:59 142 125
Aloysius 06:28 09:09 141 124
uvofiz 06:30 08:30 130 115
Mike Harper Mike Harper 06:32 06:47 103 91
robertbridge 06:38 08:12 123 108
alastair52 06:43 09:17 138 122
John Arnold 06:44 08:58 133 117
maisiemae 06:45 06:31 96 84
Puzzleplease 06:46 06:26 95 84
DianeRS 06:46 07:09 105 92
endafk 06:48 05:27 80 70
Edprof 06:49 09:17 136 120
Viscomte 06:51 07:47 113 100
Corymbia Corymbia 06:57 07:24 106 93
ulaca ulaca 06:57 07:37 109 96
ratterz 07:00 07:00 100 88
drginacoco 07:01 10:06 143 126
barracuda barracuda 07:08 06:44 94 83
m5harp 07:15 09:46 134 118
gsriordan52 07:20 06:36 90 79
Sheen 07:21 09:44 132 116
Dr_Bob 07:24 08:48 118 104
vefatica vefatica 07:46 08:16 106 93
mattindoha 07:57 09:02 113 100
TonyN6 07:59 09:05 113 100
branch branch 08:11 10:04 123 108
goblin 08:21 09:49 117 103
Pauline Minter 08:42 10:12 117 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.