The results I have earned—and the context they need.
These numbers mark real moments in my development. I keep official races, training tests, and retrospective estimates separate because they do not carry the same level of certainty.
100M · OFFICIAL COMPETITION · ATHLETE-REPORTED11.45s
I ran 11.45 with electronic timing at WSE in Shanghai in late August. My paper result is still in Shanghai, and I do not have a digital copy to link here. The wind reading and race year are not confirmed on this page.
WSE · Shanghai · Late August · year unconfirmed
FIRST OFFICIAL 100M12.30s
My first electronically timed 100m race · April 2026
FLYING 10M1.00s
Electronic training test · improved from 1.10 seconds
40-YARD DASH4.60s
Standing-start team assessment · September 2025
APPROACH VERTICAL95cm
Best five-step approach jump · fall 2025 case · measured after deload
OFFICIAL 100M CHANGE−0.85s
From the first official race to the current official PB: approximately 6.9% less elapsed time.
FLYING 10M CHANGE−0.10s
From 1.10 to 1.00 seconds: 9.1% less time, equivalent to a 10.0% increase in average segment speed.
HOW I READ ITA result is a checkpoint, not an explanation.
Training blocks, sprint technique, physical development, recovery, and testing conditions all changed over time. The improvement is real; the exact share caused by each factor is not something this dataset can isolate.
HOW I LABEL THE EVIDENCE
Honest categories make comparisons more useful.
OFFICIAL
I report 11.45 as my official electronically timed competition PB. I do not have a digital result available for independent checking. Electronic timing alone does not confirm fully automatic timing, and without the wind reading I cannot confirm whether the mark was wind-legal.
OBSERVED
The 40-yard dash and flying 10m were electronically measured training or team tests.
ESTIMATED
The earlier squat 1RM references in my fall 2025 case are estimates from working weight and RPE. The final 130 kg single and 95 cm approach jump were actual post-deload tests. The original paper training log is currently unavailable.