Super Hang-On has a bug in the In-Game timer, present in both Rev 00 and Rev 01, in both console and emulator.

The first part of the video shows a playthrough of identical runs at 265 km/h (Left) and 263 km/h (Right). Notice the sector times look alright at first, but then start to make no sense, as the slower run gets faster splits and a faster IGT overall.

When a checkpoint is passed, the clock is zeroed and that time is written to memory. But then the timer starts counting from whatever fraction of a second was left over. For example, sectors in the first 265km/h run start from 00.80 each time, accounting for the mess.

I have now edited all runs current and obsolete on the leaderboard to show the true times. Only a couple of minor places have changed hands and all times are now totally accurate. One item of note is that Mc166's Expert run was never actually the WR, but since it spurred Dev to pull out a bonkers fast time, I don't think he will mind ;) Also let me just congratulate Seymour whose Beginner run was 3.5 seconds faster than it appeared, giving him a corrected and well-deserved 8th place!

So, how do you work out your actual time from a race? It's not so hard.

Write down the fractions of a second that show when you passed each sector, except the last sector of a race which doesn't show anyways. Add these up, and subtract them from the IGT. Then you have your True Time. I will always double check these. You may in future wish to complete any run which is close to your PB or a WR: typically an IGT is off by 2-3 seconds in Africa, increasing to 7-8 seconds in Europe.

Here's an example of how to do this from a race in Africa:

S1 35.93 S2 33.1 S3 34.8 S4 31.93 S5 35.8 (S6 time not shown on screen)

IGT showed 3'29"59. 0.93 + 0.1 + 0.8 +0.93 +0.8 = 3.56 3:29.59 - 3.56 = 3:26.03

Thanks for reading!

I noticed a few errors in my past submissions regarding subseconds: apologies for those inaccuracies. Whenever you make a submission please be sure to use Three digits for your subsecond time. For example, a time of of 3'26"03 should be submitted as "3m 26s 030ss" with 030 all written. I inadvertently misrepresented subseconds on a few submission times by only writing in the two decimals: by doing that the system was turning '03' into '003' for example. I checked all other submitted runs and none were affected.