he managed to ride just over 48,479km between April and his last ride, with 19,400km over the last 48 days (i.e. just over 400km per day)
Now, Strava does indeed think that he has ridden 30,479.2m in 2015 (~49,000km), but his Strava-recorded total for the last 48 days (25 Sep-12 Nov) is 8,979 miles (13727km). THAT is double-counting the many Group Activities where Miles has erroneously uploaded the same activity twice (I think this happens if you're uploading via that horrible Garmin Connect? His records only start showing this defect from October - where his mileage chart appears to go upwards!) Maybe this is the source of his confusion about how far he'd gone - was he just looking at the weekly mileage bar charts on Strava? Take for example the week 26 Oct - 1 Nov:
Crediting him with the longer of the two distances for every ride double-counted gives him
2.4+90.6+35.4+52.8+2.5+2.3+92.6+60+0+60.5+0+0.8+64.5+58.5+58.1+6.3+4.5+57.7+59.0+4.0+28.5+1.6+39.0+38.0+38.0+42.1+30.0+4.+2.5+121.3+3.4 = 1061.4 miles
The eleven doubly-counted rides come to
62.5+35.1+2.2+91.6+60.2+63.5+57.9+3.8+37.9+29.9+3.1 = 447.7 miles
So, whereas Miles actually only rode 1061.4 miles in a week (151.6 mpd, 0.737 Godwins), he might think he rode 1509.1 (or the Strava-totalled 1510.7, which will exclude, I think, rounding errors) (215.6mpd, 1.048 Godwins).
(Surely it can't be that difficult to tell the difference between a 151.6mpd week and a 215.6mpd week? Does arithmetic work differently on the other side of the planet?)Still nowhere near the 250mpd that the article quotes, but maybe an explanation for the misplaced optimism? The only viable explanation to make up the difference is that he has rides which are not logged on Strava, but, given that the UMCA rules have strict stipulations that rides
should be logged on Strava, it is churlish to argue that unproven miles should be verified. Given his team's level of recording ineptitude, it is a bit rich to vent in the article about "frustrations over inaccurate UMCA records"!