On-chain finish times, resolved races

Racing records

Fastest finishes from every resolved race. Hot tracks run faster, so raw times are not directly comparable. Adjusted times correct for track temperature where we have enough data; this reduces, but does not fully remove, condition effects, which is why the condition is always shown.

Standings as of 17:29 UTC (3.5h ago), catching up

The fastest Gigling in Gigaverse

2.47s#30338Giga

adjusted, fastest finish at 100m, set in hot conditions, owned by afropengu.

2#22445Gigahot3mo ago40.88s adj39.62s raw
3#28180Reliccold2mo ago42.18s adj41.35s raw
4#18813Relichot3mo ago42.32s adj41.02s raw
5#22999Gigahot2mo ago42.49s adj41.18s raw
6#28573Reliccold1mo ago42.61s adj41.76s raw
7#30245Gigacold11d ago43.00s adj42.15s raw
8#1871Gigacold3mo ago43.03s adj42.18s raw
11#27596Gigahot2mo ago43.26s adj41.93s raw
13#28186Legendaryhot2mo ago43.50s adj42.16s raw
15#6000Gigahot3mo ago43.83s adj42.48s raw
21#523Legendarycold3mo ago44.24s adj43.37s raw
22#30247Gigacold12d ago44.27s adj43.39s raw
23#6158Relichot2mo ago44.27s adj42.91s raw
24#3493Gigacold3mo ago44.29s adj43.41s raw

adj = adjusted for track temperature, raw = on-chain time. Shown together only where they differ.

Showing 25 of 100 records.

On-chain finish times from resolved races, the condition each was set in always shown. Reference condition average, recomputed each run. The public /api/v1/records endpoint is the programmatic export of this data.