Quick SNITCH

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

Times Quick Cryptic Crossword 2709

Date 22 June 2024
Number 2709
Setter Trelawney
Day of week Saturday
NITCH 74
Count of ref solvers 70
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 2709

* Requires access to the Times Crossword Club

Detailed solving results

 

If you would like to help cover the costs of running the SNITCH site, please "buy me a coffee".

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:07 01:30 70 94
Paul Gilbert 02:14 01:35 70 94
cmjhutton 02:18 02:08 92 124
Jason 02:35 02:02 78 105
verlaine 02:38 02:56 111 150
mistigris 02:39 02:12 83 112
hilarym 02:50 02:22 83 112
aphis99 aphis99 02:51 02:56 102 137
Flimmy flammy 03:11 02:40 83 112
richard 03:37 03:33 98 132
markdobell 03:39 02:53 78 105
Heyesey 03:41 02:21 63 85
SimonAnthony 04:04 03:26 84 113
glheard 04:06 03:47 92 124
Topical Tim Topical Tim 04:11 02:46 66 89
lickert 04:15 04:05 96 129
MikeOsborne 04:17 03:27 80 108
Umpire 04:21 02:20 53 71
Morphosis 04:28 03:10 70 94
MK76 04:35 03:14 70 94
chindit 04:37 03:57 85 114
tilbee 04:40 04:32 97 131
lucyg43484 04:41 03:00 64 86
Freemers 04:44 03:11 67 90
Tom Stubbs Tom Stubbs 04:46 03:40 76 102
philjordan1147 BUSMAN 04:46 03:18 69 93
alexh 04:47 02:30 52 70
scrabbler 04:51 04:14 87 117
canismiser 04:52 03:26 70 94
andrewlake 04:53 03:17 67 90
LouWeed LouWeed 04:53 04:15 87 117
Paul Bacon 04:54 05:24 110 148
andy 04:55 04:15 86 116
fshephe 04:56 03:18 66 89
footballblue 04:56 04:11 84 113
d.middleton 04:57 03:26 69 93
Liari 04:57 04:37 93 125
March 05:03 04:56 97 131
McBeakLives 05:04 03:38 71 95
nina s 05:10 04:49 93 125
Squallaby 05:15 04:01 76 102
7dPenguin 7dPenguin 05:16 03:22 63 85
Tibthorpe 05:19 04:44 89 120
esmeralda 05:38 04:25 78 105
Finzi 05:39 04:59 88 118
mcrossib1 05:45 03:01 52 70
Encota 05:47 04:04 70 94
chriswestontour 05:47 05:08 88 118
Rabbitoh galspray 05:49 03:53 66 89
Gaius 05:53 03:35 60 81
SBQuick 05:54 04:34 77 104
Looch 05:58 03:31 58 78
KET 06:02 04:27 73 98
Mike C 06:04 03:53 64 86
cath23 06:13 04:42 75 101
andrewfeist96 06:22 04:46 74 100
Tudds 06:38 05:25 81 109
endafk 06:42 04:10 62 83
hazyfantazee 06:43 04:35 68 91
ilan 06:52 04:33 66 89
KenD51 06:57 04:55 70 94
uvofiz 07:01 04:04 57 77
FraserH 07:01 05:28 77 104
janesa 07:03 03:57 56 75
James P 07:05 04:42 66 89
Kevin Gregg Kevin Gregg 07:13 05:41 78 105
earlylight 07:24 05:06 68 91
DamienKnapma 07:29 04:15 56 75
Mike Harper Mike Harper 07:35 05:32 72 97
Dvynys Dvynys 07:45 04:27 57 77
Corymbia Corymbia 07:47 05:11 66 89
1234 07:51 05:01 63 85
ChrisBrea 07:51 05:20 67 90
martinede 08:01 04:52 60 81
smalley552 08:08 03:49 46 62
plett11 Plett11 08:14 04:59 60 81
Sheen 08:15 04:50 58 78
Templar Redux Templar 08:30 05:32 65 87
johndun John Dunleavy 08:40 05:30 63 85
Mike Mansbridge 09:53 03:20 33 44
phatman 10:02 05:16 52 70
simjt simjt 11:21 06:36 58 78
Cedric Statherby 11:34 07:00 60 81
chabuduo chabuduo 12:22 06:25 51 68
flashman flashman 13:23 11:14 83 112
Doofenschmirtz Doofenschmirtz 15:25 06:00 38 51

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.