hkjc_barrier_trials

PREMIUM 8,674 rows

Hong Kong barrier trial results, times and running comments

No-code

Download a file

CSV · Excel · Parquet · JSON. Filtered exports.

See pricing
For engineers

Query with SQL

DBeaver, DuckDB, MotherDuck, or HTTPS. Sub-second latency.

Open connection details
Agent builders

Connect to AI

MCP for Claude Desktop, Cursor, ChatGPT, Goose. 1-line install.

See setup

Hong Kong barrier trial (practice race) results — every horse's run in each morning trial batch at Sha Tin, Conghua and Happy Valley. Includes jockey, trainer, draw, gear, finishing order, time, lengths behind winner (LBW), running positions and the stewards' note on each horse's run. Barrier trials are how unraced and returning horses qualify and show form before the racecard, so this is early-signal data for spotting fitness and intent that the main results don't yet reveal.

Premium dataset

Evaluate it in full below: the evidence and a working sample are open to everyone. Buy or subscribe to unlock the complete dataset — your account is created automatically at checkout.

See access options

The evidence

Data coverage
May 2025 – present
Pass access: Most recent 24 months, rolling
Volume
8,674 rows
Last updated
7 July, 2026 (1 week ago)

Rows over time

month
2025-05-01 2026-07-01
Schema & column quality (23 columns)
Column Type Description Populated Distinct
trial_date Nullable(Date) Date the barrier trial was run (YYYY-MM-DD) — —
venue Nullable(String) Trial venue — SHA TIN, CONGHUA or HAPPY VALLEY — —
track Nullable(String) Track surface used for the trial — TURF or ALL WEATHER TRACK — —
distance_m Nullable(Int64) Trial distance in metres (e.g. 1000, 1200, 1600) — —
batch_no Nullable(Int64) Batch (trial) number within the venue's session for that date — —
going Nullable(String) Going (track condition), e.g. GOOD, WET SLOW — —
batch_winning_time Nullable(String) Winning time for the batch as a whole, i.e. the time of the batch's fastest horse (M.SS.hh). The same for every runner in the batch — for this horse's own time, use horse_time. — —
batch_sectional_time Nullable(String) Section split times for the batch as a whole, in seconds, space-separated (e.g. '24.1 22.3 24.0'). The same for every runner in the batch. — —
finishing_position Nullable(Int64) The order HKJC lists this horse in for the trial (1 = first across the line). Barrier trials are not officially placed, so this is the running order as published: horses that dead-heat appear as consecutive positions rather than sharing one. — —
horse Nullable(String) Horse's name in English — —
brand_code Nullable(String) Horse's HKJC brand number (e.g. H294) — —
horse_id Nullable(String) Canonical horse identifier (HK_YYYY_XXXX format) — —
jockey Nullable(String) Jockey who rode the horse in the trial — —
trainer Nullable(String) Horse's trainer — —
draw Nullable(Int64) Barrier (gate) draw number for the trial — —
gear Nullable(String) Equipment carried (HKJC gear codes, e.g. B = Blinkers, TT = Tongue Tie) — —
lbw Nullable(String) Lengths behind winner (LBW) — distance behind the first-place finisher — —
running_position Nullable(String) Running positions through the trial, space-separated by section — —
horse_time Nullable(String) This horse's individual finishing time (M.SS.hh) — —
result Nullable(String) Trial result note (e.g. Passed for a qualifying trial), blank if none — —
comment Nullable(String) Stewards'/HKJC comment describing how the horse ran in the trial — —
updated_at Nullable(DateTime64(3)) Timestamp this row was last (re)parsed into the warehouse — —
id String Stable unique identifier for this row — the last column of every export. Use it to deduplicate, to key an incremental load, or to reference one specific row. It is additive: the entity and join keys you already use (race_id, horse_id, and the like) are unchanged. — —

Sample data

CSV Excel

Last 6 months of barrier trials — the same horses you will meet on the racecard, trialling before they run.

SELECT * FROM renavon_exports.hkjc_barrier_trials LIMIT 50 0.02s
Loading data… | Click a header to sort; drag headers to reorder.

Choose your access

A Pass gives you freshness within a rolling window. The Full Archive gives you the full history we hold for the dataset, frozen at purchase. They solve different problems, and they work together.

Satisfaction guarantee: 14-day money-back. Details →

Pass subscription

Racing Pass Pro

Continuously updated, with API access.

View full package →
Access window
Most recent 24 months, rolling
Updates
Continuous, within hours of the source
Delivery
API, SQL and downloads
Exports
1,000,000 rows/month included
Included Datasets
HKJC Barrier Trials this dataset
HKJC Dividends
HKJC Horses Database
HKJC Jackpots
HKJC Jockey Rankings
HKJC Pool Investments
HKJC Race Results
HKJC Race Results (Core)
HKJC Race Catalog
HKJC Racing Changes
HKJC Sectional Times
HKJC Track Conditions
HKJC Trainer Rankings
US$149
per month
SAVE 17%
US$1490
per year
(US$124.17/month)

Pass subscription

Racing Pass Enterprise

Continuously updated, with API access.

View full package →
Access window
Most recent 24 months, rolling
Updates
Continuous, within hours of the source
Delivery
API, SQL and downloads
Exports
Uncapped
Included Datasets
HKJC Barrier Trials this dataset
HKJC Dividends
HKJC Horses Database
HKJC Jackpots
HKJC Jockey Rankings
HKJC Odds Movements (tick-level)
HKJC Closing Odds
HKJC Pool Investments
HKJC Race Results
HKJC Race Results (Core)
HKJC Race Catalog
HKJC Racing Changes
HKJC Sectional Times
HKJC Track Conditions
HKJC Trainer Rankings
US$499
per month
SAVE 17%
US$4990
per year
(US$415.83/month)

Get notified when this dataset is updated.

Questions about this data?

Our data experts are ready to help clarify any aspects of this dataset.

Contact Our Team