Incorrectly Timed Run
For the category of "Highest Possible Position", the user VirtualCoins is currently holding the record of 00.02.220. After attempting to break this world record, I have tried countless of times using the exact same strategy. After being off by a few milliseconds every time, I decided to try and time the user's run. After timing it, I found that the actual time was 00.02.335, which means that the run was timed incorrectly.
Evidence:
Reverse likes this
This could indeed be like such because of the way my editing program times it (I add a timer after completing the run)
Recent runs