Quick SNITCH

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

Times Quick Cryptic Crossword 2703

Date 15 June 2024
Number 2703
Setter Orpheus
Day of week Saturday
NITCH 86
Count of ref solvers 68
Ref solvers excluded with errors 2
Link to crossword View Crossword*
Times for the Times Link 2703

* 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:37 76 88
Paul Gilbert 02:14 03:08 140 162
cmjhutton 02:18 03:32 153 177
Jason 02:35 02:10 83 96
mistigris 02:39 02:12 83 96
hilarym 02:50 02:16 80 93
aphis99 aphis99 02:51 03:01 105 122
Flimmy flammy 03:11 03:24 106 123
richard 03:37 02:56 81 94
markdobell 03:39 03:06 84 97
Heyesey 03:41 03:45 101 117
AlanS 03:55 04:09 105 122
Kinghedger 04:01 04:32 112 130
SimonAnthony 04:04 02:41 65 75
Topical Tim Topical Tim 04:11 03:09 75 87
lickert 04:15 03:56 92 106
MikeOsborne 04:17 03:41 85 98
Morphosis 04:28 03:16 73 84
MK76 04:35 03:52 84 97
chindit 04:37 04:10 90 104
Freemers 04:44 05:07 108 125
Tom Stubbs Tom Stubbs 04:46 03:15 68 79
alexh 04:47 03:54 81 94
scrabbler 04:51 04:03 83 96
LouWeed LouWeed 04:53 04:13 86 100
andrewlake 04:53 04:19 88 102
andy 04:55 03:16 66 76
fshephe 04:56 03:20 67 77
d.middleton 04:57 04:46 96 111
Liari 04:57 05:00 101 117
cdb_100 05:00 03:29 69 80
JayEm 05:01 06:35 131 152
Ed freshpot 05:04 04:17 84 97
McBeakLives 05:04 04:50 95 110
nina s 05:10 05:24 104 120
Zander 05:14 06:43 128 148
Squallaby 05:15 04:49 91 105
7dPenguin 7dPenguin 05:16 05:45 109 126
Tibthorpe 05:19 04:40 87 101
esmeralda 05:38 03:38 64 74
Nigel1953 05:38 06:47 120 139
Finzi 05:39 05:48 102 118
mcrossib1 05:45 03:36 62 72
Encota 05:47 04:49 83 96
chriswestontour 05:47 06:27 111 129
mw7000 05:48 05:24 93 108
Rabbitoh galspray 05:49 05:51 100 116
RobR RobR 05:55 05:27 92 106
Looch 05:58 05:06 85 98
KET 06:02 04:51 80 93
Mike C 06:04 05:20 87 101
hopkinb hopkinb 06:07 06:43 109 126
cath23 06:13 04:02 64 74
PGooden 06:15 06:54 110 127
Carol 06:20 05:53 92 106
Dzhigit 06:34 04:27 67 77
Adrian Cobb 06:34 06:46 103 119
Tudds 06:38 05:26 81 94
GMcD 06:38 05:39 85 98
Michael Dove 06:39 05:13 78 90
endafk 06:42 05:39 84 97
hazyfantazee 06:43 05:44 85 98
ilan 06:52 05:09 75 87
CrystalPip 06:54 06:21 92 106
valerian1967 06:56 06:20 91 105
janesa 07:03 06:50 96 111
James P 07:05 05:03 71 82
DianeRS 07:06 06:09 86 100
Kevin Gregg Kevin Gregg 07:13 04:49 66 76
earlylight 07:24 06:14 84 97
Mike Harper Mike Harper 07:35 07:01 92 106
Dvynys Dvynys 07:45 04:30 58 67
Corymbia Corymbia 07:47 04:52 62 72
nigel 07:54 06:18 79 91
John Arnold 08:12 05:59 72 83
plett11 Plett11 08:14 07:24 89 103
ulaca ulaca 08:25 05:43 67 77
jemcd33 08:25 06:39 79 91
Templar Redux Templar 08:30 07:28 87 101
johndun John Dunleavy 08:40 07:12 83 96
m5harp 08:46 06:36 75 87
richardCV22 10:06 05:58 59 68
Cedric Statherby 11:34 11:38 100 116
Merlin_55 Merlin 14:50 22:00 148 172
Doofenschmirtz Doofenschmirtz 15:25 14:30 94 109
IanV IanV 31:11 40:00 128 148

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.