There are races where the stopwatch shouts at you, and others where it whispers.
The 2.20 at Chepstow falls firmly into the second category.
Washington Royale won the 6f restricted maiden comfortably by 4¾ lengths, stopping the clock at 1m 14.58sec (74.58sec). On the bare numbers, that isn't a particularly exciting time. Racing Post recorded it as 6.58sec outside its standard, while Irish Racing calculated it at 2.17sec slower than the course average for today's going. �
racingpost.com +1
But our HRB Standard Time Calculator gives us a more interesting way of looking at it.
What does the HRB clock say?
We've built our Chepstow 6f standards from historical races rather than simply accepting one universal course standard.
For today's Good to Soft conditions, some of the important numbers are:
HRB category
Standard
All Chepstow 6f races
71.96 sec
Good to Soft
72.70 sec
Class 4
71.91 sec
Class 4 / Good to Soft
72.21 sec
Washington Royale today
74.58 sec
Against our most relevant Class 4/Good to Soft standard of 72.21, Washington Royale was approximately:
2.37 seconds slow.
Over six furlongs that's nearly 0.40 seconds per furlong outside standard.
If we stopped the analysis there, we'd call it an ordinary performance.
That would be a mistake.
The ground is talking to us
The official description was Good to Soft, Soft in places. �
sportinglife.com
And this is precisely why clock watching can't simply be:
Winning Time − Standard Time = Ability.
A standard time tells us what horses have historically been capable of running under comparable conditions. It doesn't tell us exactly how fast today's particular strip of turf was.
That's what we need to establish from the rest of the card.
If subsequent Chepstow races consistently come home two or three seconds outside our standards, Washington Royale's 74.58 suddenly looks perfectly respectable.
If later winners start beating or getting close to standard, then we have to downgrade it.
One race gives us a time.
A whole card gives us the going allowance.
That's the key distinction.
The way he won matters
This is where Washington Royale becomes interesting.
He didn't blast from the gates, establish an aggressive gallop and grind the opposition into submission.
Quite the opposite.
He was keen but held up towards the rear, was ridden after the two-furlong marker, took over more than a furlong from home and then pulled clear towards the finish, winning comfortably. �
irishracing.com
That is important.
The overall time might have been 74.58 seconds, but Washington Royale wasn't necessarily operating at maximum efficiency throughout those 74.58 seconds.
Without sectional times we cannot quantify his finishing speed accurately, so we shouldn't pretend that we can.
But visually, the decisive part of his performance occurred late.
The stopwatch therefore poses a question rather than providing the answer:
How much faster could Washington Royale have run if required to produce an evenly distributed effort from the start?
That's what makes him worth following.
The market got this one wrong
There's another fascinating aspect.
Washington Royale returned 2/1, while Ischgl was sent off the 8/13 favourite. Texas Crown, meanwhile, drifted dramatically to 28/1 before finishing second. �
racingpost.com +1
Yet Washington Royale had already been showing ability in stronger company.
His previous start had been a fifth in a Class 2 Goodwood maiden, and pre-race analysis specifically highlighted both the stronger races he'd contested and the significance of today's drop in grade. �
sportinglife.com
The market became increasingly convinced that Ischgl was the superior horse.
The race told a very different story.
Washington Royale didn't just beat him.
He finished 8½ lengths ahead of the favourite.
Don't rate the winner through Ischgl
There is a temptation after a result like this to say:
Ischgl was rated 80, Washington Royale thrashed him, therefore Washington Royale must have run to 80-plus.
That's dangerous handicapping.
Ischgl raced prominently but weakened rapidly and clearly didn't reproduce his best. He cannot sensibly be used as the anchor for Washington Royale's performance.
The clock is actually protecting us from getting carried away.
Washington Royale may well prove better than his pre-race OR of 75, but the raw time doesn't justify throwing an enormous figure at him yet.
What it does justify is putting a large “WATCH” beside his name.
And don't ignore Texas Crown
There might be another horse for the notebook.
Texas Crown came into the race rated 68 and was allowed to drift all the way to 28/1, having been available around 5/1–6/1 earlier. Despite that extraordinary lack of market confidence, he finished second. �
irishracing.com
His previous form figures were 022, so this wasn't entirely out of nowhere; he'd been progressing race by race. �
sportinglife.com
He couldn't live with Washington Royale once the winner accelerated, but he beat Beechwood Glory and was well clear of the remainder.
He's another worth remembering when returned to similar company.
Clock Watcher's verdict
Washington Royale — ↑↑
The raw time is nothing special:
74.58 sec versus our 72.21 sec Class 4/Good-to-Soft standard = +2.37 sec.
But that figure cannot yet be judged in isolation.
The ground appears genuinely testing, the winner wasn't asked to race flat-out throughout, and his strongest work came late as he put daylight between himself and the field.
So rather than declaring this either a fast or slow performance, I'm putting it into the notebook as:
PROVISIONAL — AWAITING GOING ALLOWANCE.
That's actually the fun of today's Chepstow card.
We've now got our first marker:
Chepstow Clock Watch
2.20 — 6f 16yds
Washington Royale — 74.58 sec
HRB C4/GTS Standard — 72.21 sec
Difference: +2.37 sec
Now we watch the next race.
Then the next.
By the end of the meeting, we'll have something much more valuable than an opinion about Washington Royale.
We'll have an evidence-based estimate of how fast Chepstow was actually riding today.
And once we know that, we can come back to 74.58 and find out what Washington Royale's performance was really worth.
No comments:
Post a Comment