Quick SNITCH

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

Times Quick Cryptic Crossword 3043

Date 17 July 2025
Number 3043
Setter Mara
Day of week Thursday
NITCH 84
Count of ref solvers 76
Ref solvers excluded with errors 0
Link to crossword View Crossword*
Times for the Times Link 3043

* 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:54 137 163
Paul Gilbert 02:14 01:37 72 85
cmjhutton 02:18 01:58 85 101
Jason 02:35 02:46 107 127
verlaine 02:38 01:58 74 88
mistigris 02:39 02:44 103 122
Magoo 02:46 02:27 88 104
hilarym 02:50 03:11 112 133
aphis99 aphis99 02:51 02:29 87 103
Flimmy flammy 03:11 04:14 132 157
Ciolf 03:37 02:50 78 92
richard 03:37 03:54 107 127
markdobell 03:39 02:24 65 77
Heyesey 03:41 03:36 97 115
AlanS 03:55 02:53 73 86
Amoeba89 03:55 03:19 84 100
Kinghedger 04:01 04:26 110 130
SimonAnthony 04:04 03:48 93 110
glheard 04:06 03:30 85 101
Topical Tim Topical Tim 04:11 03:15 77 91
Deane Short 04:13 04:02 95 113
lickert 04:15 04:38 109 129
MikeOsborne 04:17 04:57 115 136
Umpire 04:21 03:41 84 100
MK76 04:35 03:48 82 97
Bluejacket 04:39 03:44 80 95
tilbee 04:40 03:48 81 96
lucyg43484 04:41 03:25 72 85
Freemers 04:44 03:47 79 94
Tom Stubbs Tom Stubbs 04:46 03:16 68 80
philjordan1147 BUSMAN 04:46 04:31 94 111
alexh 04:47 04:00 83 98
scrabbler 04:51 04:13 86 102
Jon Delfin 04:52 03:04 63 75
canismiser 04:52 04:11 85 101
andrewlake 04:53 04:38 94 111
LouWeed LouWeed 04:53 05:05 104 123
andy 04:55 05:49 118 140
fshephe 04:56 03:50 77 91
Liari 04:57 03:59 80 95
d.middleton 04:57 05:42 115 136
cdb_100 05:00 05:29 109 129
JayEm 05:01 04:16 85 101
neilr neilr 05:02 04:18 85 101
March 05:03 04:34 90 107
Ed freshpot 05:04 04:13 83 98
Adelaider 05:06 03:53 76 90
Honggui 05:06 04:50 94 111
Aybee 05:07 03:52 75 89
Zander 05:14 04:11 79 94
Squallaby 05:15 04:20 82 97
7dPenguin 7dPenguin 05:16 03:29 66 78
ChuckB 05:18 04:49 90 107
Tibthorpe 05:19 05:03 94 111
AndyKnott321 05:27 04:13 77 91
Riche Riche 05:32 03:54 70 83
rrricharrrd 05:32 03:55 70 83
Paul Hammond Paul Hammond 05:38 04:31 80 95
Finzi 05:39 04:43 83 98
Crossiant 05:42 04:13 73 86
mcrossib1 05:45 05:15 91 108
mw7000 05:48 03:36 62 73
Rabbitoh galspray 05:49 04:47 82 97
SBQuick 05:54 04:00 67 79
KET 06:02 04:56 81 96
Mike C 06:04 04:51 79 94
Anomalospiza 06:10 04:09 67 79
cath23 06:13 04:59 80 95
Rosron 06:18 05:20 84 100
dr.shred 06:26 05:11 80 95
Adrian Cobb 06:34 04:57 75 89
Dzhigit 06:34 05:17 80 95
julian_w 06:35 05:11 78 92
robertbridge 06:36 05:14 79 94
hazyfantazee 06:43 05:34 82 97
ilan 06:52 05:31 80 95
edwards.robert1 06:53 04:12 61 72
uvofiz 07:01 04:16 60 71
James P 07:05 04:28 63 75
robertL 07:13 05:31 76 90
Rembleforth 07:31 05:24 71 84
TomHerbert 07:44 04:16 55 65
ChrisBrea 07:51 05:05 64 76
kath 09:02 05:44 63 75

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.