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:31 UTC (3.4h ago), catching up

The fastest Gigling in Gigaverse

2.47s#30338Giga

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

2#29044Legendaryhot1mo ago49.43s adj48.25s raw
3#22445Gigahot3mo ago49.53s adj48.35s raw
6#13667Gigahot3mo ago50.40s adj49.20s raw
7#29228Relichot1mo ago50.47s adj49.26s raw
8#3493Gigacold3mo ago50.54s adj49.43s raw
10#29041Gigahot1mo ago50.91s adj49.69s raw
12#30061Legendarycold22d ago50.95s adj49.83s raw
14#28261Legendaryhot2mo ago51.01s adj49.79s raw
15#28395Gigahot2mo ago51.01s adj49.79s raw
16#28252Gigahot1mo ago51.05s adj49.83s raw
17#28636Gigahot2mo ago51.07s adj49.85s raw
19#4565Gigacold2mo ago51.20s adj50.07s raw
20#28495Reliccold2mo ago51.22s adj50.09s raw
24#26236Relichot3mo ago51.40s adj50.17s 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.