When submitting and specifying the milliseconds, most timers just show 2 digits, which is why most people only submit their runs with 2 digits for the milliseconds. If they specify "69", it doesn't get interpreted as .69, but as .069 which is clearly wrong. If they would've wanted to submit the time as .069, they would need to put a 0 in front, just like in .069, if they don't, they most likely don't want to submit the time as that. I've had to fix a lot of verified runs in the past, cause neither the runner, nor the other moderators noticed this, so this is definitely a common issue. Probably with almost all if not all runs that have a digit other than 0 in the third place and a 0 in the first place.

Good point, changed.