Quick SNITCH

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

Times Quick Cryptic Crossword 3067

Date 14 August 2025
Number 3067
Setter Hurley
Day of week Thursday
NITCH 93
Count of ref solvers 72
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 3067

* 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
Paul Gilbert 02:14 02:11 97 104
cmjhutton 02:18 02:02 88 94
Jason 02:35 02:59 115 123
verlaine 02:38 02:29 94 101
mistigris 02:39 02:51 107 115
Magoo 02:46 02:07 76 81
hilarym 02:50 02:45 97 104
aphis99 aphis99 02:51 03:04 107 115
Flimmy flammy 03:11 02:36 81 87
Ciolf 03:37 03:05 85 91
Heyesey 03:41 03:03 82 88
Sheapey Sheapey 03:43 03:44 100 107
AlanS 03:55 03:28 88 94
Amoeba89 03:55 03:40 93 100
Kinghedger 04:01 04:29 111 119
SimonAnthony 04:04 03:36 88 94
glheard 04:06 03:59 97 104
Topical Tim Topical Tim 04:11 03:42 88 94
lickert 04:15 04:52 114 122
MikeOsborne 04:17 05:28 127 136
John Walsh 04:27 05:29 123 132
Roscoe 04:32 05:24 119 127
MK76 04:35 04:10 90 96
chindit 04:37 04:19 93 100
EricK 04:38 04:05 88 94
Bluejacket 04:39 03:13 69 74
tilbee 04:40 04:13 90 96
lucyg43484 04:41 05:00 106 113
Freemers 04:44 05:00 105 112
Tom Stubbs Tom Stubbs 04:46 04:29 94 101
philjordan1147 BUSMAN 04:46 04:59 104 111
alexh 04:47 04:14 88 94
scrabbler 04:51 04:40 96 103
Jon Delfin 04:52 03:52 79 84
LouWeed LouWeed 04:53 04:52 99 106
andrewlake 04:53 05:08 105 112
andy 04:55 05:35 113 121
fshephe 04:56 03:35 72 77
tiggis 04:57 04:39 93 100
d.middleton 04:57 04:52 98 105
cdb_100 05:00 05:44 114 122
JayEm 05:01 05:17 105 112
neilr neilr 05:02 04:41 93 100
March 05:03 04:14 83 89
Ed freshpot 05:04 04:53 96 103
Aybee 05:07 04:45 92 98
Zander 05:14 05:58 114 122
Squallaby 05:15 05:09 98 105
7dPenguin 7dPenguin 05:16 05:25 102 109
Tibthorpe 05:19 04:56 92 98
babka 05:21 04:34 85 91
AndyKnott321 05:27 06:08 112 120
rrricharrrd 05:32 04:46 86 92
Streaky Bacon 05:35 05:19 95 102
Finzi 05:39 06:31 115 123
Crossiant 05:42 05:40 99 106
Encota 05:47 05:47 100 107
chriswestontour 05:47 05:51 101 108
Rabbitoh galspray 05:49 03:36 61 65
MrChumley MrChumley 05:52 06:11 105 112
Gaius 05:53 06:05 103 110
Looch 05:58 05:58 100 107
Mike C 06:04 06:19 104 111
Anomalospiza 06:10 04:54 79 84
cath23 06:13 05:56 95 102
Carol 06:20 05:06 80 86
andrewfeist96 06:22 05:44 90 96
dr.shred dr.shred 06:26 04:58 77 82
Shabbo 06:32 05:40 86 92
Adrian Cobb 06:34 06:46 103 110
julian_w 06:35 05:52 89 95
Tudds 06:38 06:03 91 97
jimwetzler 06:39 05:34 83 89
Curarist 06:42 06:39 99 106
uvofiz 07:01 06:17 89 95
James P 07:05 06:00 84 90
Jamie Fox 07:15 04:40 64 68
Doyler 07:49 06:13 79 84
mjwiseman 07:53 05:05 64 68
smalley552 08:08 05:50 71 76
hemantyd 08:36 06:33 76 81
f4rch 09:09 06:29 70 75
Mike Mansbridge 09:53 04:05 41 44

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.