Uploaded August 2013 | Updated November 2026, 3 hours ago
A long, mathy, complicated explanation for what I think.
For those too lazy to watch the whole video...
If you have a time that used a timer that only goes to the hundredths (x.xx) after the WSSA switched to the StackMat Pro (as of 2013), add a 9 to the end.
However, for times that used a timer that goes to the hundredths (x.xx) stacked before the WSSA switched to the StackMat Pro, add a 0.
A 6.12 stacked in 2012 would be a 6.120, while a 6.12 stacked in 2013 would be a 6.129.
This is to prevent people from using a Gen 2 timer as a way to cheat (stacking a 5.51 and making it count as 5.510). The reason why I'm doing this for times stacked in 2013 and onward is because that is when the WSSA started using the StackMat Pro. For times before the switch, a 0 is added because that's what the WSSA did for old records.
We will never know what the third decimal is on timers that don't have the third decimal, so to prevent cheating, we add a 9.
A long, mathy, complicated explanation for what I think.
For those too lazy to watch the whole video...
If you have a time that used a timer that only goes to the hundredths (x.xx) after the WSSA switched to the StackMat Pro (as of 2013), add a 9 to the end.
However, for times that used a timer that goes to the hundredths (x.xx) stacked before the WSSA switched to the StackMat Pro, add a 0.
A 6.12 stacked in 2012 would be a 6.120, while a 6.12 stacked in 2013 would be a 6.129.
This is to prevent people from using a Gen 2 timer as a way to cheat (stacking a 5.51 and making it count as 5.510). The reason why I'm doing this for times stacked in 2013 and onward is because that is when the WSSA started using the StackMat Pro. For times before the switch, a 0 is added because that's what the WSSA did for old records.
We will never know what the third decimal is on timers that don't have the third decimal, so to prevent cheating, we add a 9.










