Quick SNITCH

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

Times Quick Cryptic Crossword 3061

Date 07 August 2025
Number 3061
Setter Jet
Day of week Thursday
NITCH 111
Count of ref solvers 76
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 3061

* 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 02:04 97 87
Paul Gilbert 02:14 02:04 92 82
cmjhutton 02:18 02:33 110 99
Jason 02:35 02:26 94 84
verlaine 02:38 02:51 108 97
Magoo 02:46 02:35 93 83
aphis99 aphis99 02:51 04:01 140 126
Flimmy flammy 03:11 03:37 113 101
richard 03:37 03:48 105 94
Ciolf 03:37 03:08 86 77
markdobell 03:39 05:53 161 145
Heyesey 03:41 04:02 109 98
Sheapey Sheapey 03:43 03:29 93 83
Amoeba89 03:55 03:50 97 87
AlanS 03:55 05:12 132 118
Kinghedger 04:01 05:38 140 126
SimonAnthony 04:04 03:38 89 80
glheard 04:06 04:23 106 95
Topical Tim Topical Tim 04:11 05:51 139 125
Deane Short 04:13 03:51 91 81
MikeOsborne 04:17 06:25 149 134
Roscoe 04:32 04:14 93 83
MK76 04:35 08:23 182 163
chindit 04:37 03:49 82 73
EricK 04:38 05:32 119 107
Bluejacket 04:39 04:02 86 77
tilbee 04:40 05:30 117 105
lucyg43484 04:41 05:35 119 107
Freemers 04:44 07:29 158 142
Tom Stubbs Tom Stubbs 04:46 04:46 100 90
philjordan1147 BUSMAN 04:46 04:59 104 93
alexh 04:47 06:06 127 114
LuckOfLucien 04:48 05:53 122 109
Jon Delfin 04:52 04:56 101 90
andrewlake 04:53 06:31 133 119
LouWeed LouWeed 04:53 06:39 136 122
andy 04:55 05:01 102 91
fshephe 04:56 05:33 112 100
cdb_100 05:00 04:30 90 81
JayEm 05:01 04:37 92 82
neilr neilr 05:02 04:06 81 72
March 05:03 05:00 99 89
nina s 05:10 06:32 126 113
Squallaby 05:15 06:43 127 114
7dPenguin 7dPenguin 05:16 05:48 110 99
Tibthorpe 05:19 05:22 100 90
babka 05:21 04:56 92 82
Vannyx 05:30 08:30 154 138
rrricharrrd 05:32 06:35 118 106
whichcraft 05:36 07:37 136 122
esmeralda 05:38 05:45 102 91
Paul Hammond Paul Hammond 05:38 05:57 105 94
Finzi 05:39 05:32 97 87
Crossiant 05:42 05:51 102 91
mw7000 05:48 06:13 107 96
Rabbitoh galspray 05:49 06:49 117 105
SBQuick 05:54 07:05 120 108
RobR RobR 05:55 06:16 105 94
KarenR 05:57 07:07 119 107
Looch 05:58 06:23 106 95
Mike C 06:04 05:49 95 85
hopkinb hopkinb 06:07 08:26 137 123
Anomalospiza 06:10 05:48 94 84
cath23 06:13 06:06 98 88
PGooden 06:15 07:42 123 110
Rosron 06:18 06:40 105 94
andrewfeist96 06:22 05:09 80 72
thewanderingeditor 06:27 08:30 131 118
Dzhigit 06:34 07:46 118 106
Adrian Cobb 06:34 08:34 130 117
julian_w 06:35 05:46 87 78
Curarist 06:42 07:46 115 103
ilan 06:52 06:47 98 88
tds 06:57 08:02 115 103
janesa 07:03 08:09 115 103
Jamie Fox 07:15 06:38 91 81
robinh 07:18 08:28 115 103
Aldus 07:23 08:28 114 102
TomHerbert 07:44 08:38 111 100
Dvynys Dvynys 07:45 07:52 101 90
Doyler 07:49 07:37 97 87
smalley552 08:08 06:59 85 76
Templar Redux Templar 08:30 08:11 96 86
Peloton 08:59 07:56 88 79
f4rch 09:09 07:44 84 75
Chrisa9 13:20 08:41 65 58

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.