Quick SNITCH

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

Times Quick Cryptic Crossword 2449

Date 28 July 2023
Number 2449
Setter Mara
Day of week Friday
NITCH 95
Count of ref solvers 71
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2449

* 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:27 66 69
Paul Gilbert 02:28 01:49 73 76
Jason 02:32 02:16 89 93
verlaine 02:36 02:57 113 118
mistigris 02:40 03:03 114 120
hilarym 02:43 02:44 100 105
cmjhutton 02:44 02:47 101 106
aphis99 aphis99 02:49 02:32 89 93
Flimmy flammy 03:04 02:14 72 75
richard 03:39 04:35 125 131
markdobell 03:50 03:26 89 93
Kinghedger 03:52 04:50 125 131
Heyesey 03:52 04:35 118 124
glheard 04:02 03:52 95 100
lickert 04:11 02:51 68 71
philjordan1147 BUSMAN 04:14 03:31 83 87
AlanS 04:19 03:39 84 88
MikeOsborne 04:21 04:23 100 105
tilbee 04:21 04:18 98 103
Roscoe 04:26 04:19 97 102
tiggis 04:29 04:13 94 98
lucyg43484 04:30 04:45 105 110
Tom Stubbs Tom Stubbs 04:36 04:21 94 98
John Walsh 04:37 03:58 85 89
Jim Willis 04:38 04:05 88 92
andrewlake 04:44 04:42 99 104
andy 04:46 05:28 114 120
March 04:46 05:32 116 122
LouWeed LouWeed 04:46 06:59 146 153
alexh 04:47 05:55 123 129
Ed freshpot 04:50 04:53 101 106
Ease This Jam 04:50 05:15 108 113
Umpire 04:54 04:55 100 105
Zander 05:02 05:02 100 105
Pompeydave 05:04 04:36 90 94
7dPenguin 7dPenguin 05:05 04:27 87 91
Liari 05:09 04:10 80 84
Squallaby 05:09 05:44 111 116
neilr neilr 05:10 05:45 111 116
Tibthorpe 05:12 03:59 76 80
andy_knott 05:13 06:14 119 125
Penfold_61 05:18 03:32 66 69
fshephe 05:25 04:26 81 85
ChuckB 05:26 05:07 94 98
george.plumbly 05:28 05:12 95 100
KET 05:29 04:34 83 87
Dekkers 05:31 05:49 105 110
Rabbitoh 05:32 04:56 89 93
AndyR 05:36 06:08 109 114
Finzi 05:39 06:03 107 112
Paul Hammond Paul Hammond 05:41 04:49 84 88
Shabbo 05:46 05:26 94 98
Looch 05:48 04:41 80 84
cath23 05:52 05:14 89 93
Dzhigit 05:54 06:36 111 116
GeorgeTz 05:56 06:28 108 113
Mark Three 05:58 05:59 100 105
McBeak McBeak 06:00 05:43 95 100
Crossiant 06:01 06:19 104 109
PGooden 06:03 05:25 89 93
Tudds 06:05 05:47 95 100
GMcD 06:08 06:45 110 115
earlylight 06:09 05:00 81 85
Curarist 06:12 05:31 88 92
ilan 06:17 03:58 63 66
James P 06:18 06:46 107 112
robinh 06:19 06:39 105 110
Mike Mansbridge 06:24 05:42 89 93
paul.whitehouse69 06:25 07:11 111 116
Aloysius 06:28 04:50 74 77
Wyn Lewis Wyn Lewis 06:28 06:18 97 102
tds 06:29 06:27 99 104
uvofiz 06:30 06:41 102 107
Mike Harper Mike Harper 06:32 05:33 84 88
valerian1967 06:35 06:37 100 105
jon 06:42 06:01 89 93
DrBill 06:42 07:00 104 109
alastair52 06:43 03:48 56 58
Kalakuta72 06:45 06:22 94 98
Puzzleplease 06:46 06:36 97 102
DianeRS 06:46 05:34 82 86
Edprof 06:49 06:25 94 98
Viscomte 06:51 04:25 64 67
timbo 06:51 06:21 92 96
Deezzaa Deezzaa 06:56 07:08 102 107
Corymbia Corymbia 06:57 06:18 90 94
ratterz 07:00 05:45 82 86
Yatton50 07:02 05:36 79 83
m5harp 07:15 06:27 88 92
gsriordan52 07:20 05:30 75 78
Cuppa378 07:32 06:00 79 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.