There is that ride of a local dude on Strava, where he smashes quite hard KOMs around Dartmoor (road) – now he’s ahead on all of them about 3 minutes. None of them was mine though! 😆

But the question I’ve got: he normally uses Garmin Edge 810 or 510 (he’s got both, plus expensive bike and full Sky Team outfit). But this one ride was made using “mobile”. That’s what Strava says – no “Android App” or “IPhone App”, or “Garmin blah blah”… Just “mobile”. Was the ride fabricated in any way?

It looks very odd, especially that it looks to be ridden against the traffic, like here:

The guy normally struggles with any steepish climbs and the only KOM’s he has are the ones after that ride.

The question is: is it possible to actually fabricate a ride like that? ❓

We have this –

medoramas – Member
There is that ride of a local dude on Strava, where he smashes quite hard KOMs around Dartmoor

and then this?

The guy normally struggles with any steepish climbs

How come?

Reversed the track, so fast descents become fast climbs?

You can manipulate your data before uploading it to strava.

http://www.digitalepo.com/

especially that it looks to be ridden against the traffic

my garmin 500 isn’t that accurate. a mobile won’t be.

You can manipulate your data before uploading it to strava.

http://www.digitalepo.com/
I know that site – I used it ones to see what happens (on private ride, deleted after the test) and where it says what device was used to record the ride it displayed “from file” – that would be quite obvious to spot… But I’ve never seen “mobile” before.

How come?

That’s what I want to know! 😆

Reversed the track, so fast descents become fast climbs?

Might explain why he rode around the roundabout the wrong way.

Forgotten to turn GPS off, got in car, starts driving? Track looks exactly where it would be if phone was in pocket.

My Garmin devices are pretty accurate when they want to be and can easily place my position to within 3 feet on the road when moving.

Link to it

More to the point, who makes a frikkin segment that goes round what appears to be a rather large roundabout??

my garmin 500 isn’t that accurate. a mobile won’t be.

As observed though – he’s gone the wrong way around the roundabout. The track clearly shows he’s not cut the corner, so it’s not GPS accuracy per se. My money is on:

Reversed the track, so fast descents become fast climbs?

But I would also be interested to see the track.

That’s the ride: https://www.strava.com/activities/256969581

Edit: stalking fail.

Something going on on that ride – that’s really weird!

You guys need to be on the road.cc forum

It’s definitely not right – https://www.strava.com/segments/7428976 251m climb in under 8 minutes, averaging 17kph (yet only 21kph for the whole ride)

More to the point, who makes a frikkin segment that goes round what appears to be a rather large roundabout??

A shared use path (sustrans – Lon Eifion) has segments on it by me. Some people are just strange.

You guys need to be on the road.cc forum

😆

I’m more interested about the way it’s done!

Not that I want to repeat it or something… 🙄

it’s like nosy neighbours peakying out the net curtains “ooooo look norman they’re doing it again, where do they get the money”

From aracer’s link – that really iffy segment is interesting – apparently it’s got a section of -272%, dunno if that’s significant.

Something happens at 1:29:46 until 1:30:10 too – he sits at 10.3 mph, and a calculated power >1,000w for nearly 30 seconds.

Not reversed, going too fast on the downhills for that.

The performance analysis for that segment, but extending slightly before and slightly after the segment is illuminating
https://www.strava.com/activities/256969581/analysis/629/688
Note the steady speed through the segment and how the speed suddenly drops when the gradient eases at the end. Note the wide variation in estimated power to maintain steady speed.

Then compare with the analysis of the same stretch of ride for the previous KOM
https://www.strava.com/activities/100317135/analysis/1221/1575

Definitely manipulated data post ride

Just a glitch in the elevation data. The >1000W bit can be seen in the links I just posted – I nearly made a comment about that as well (though the previous KOM peaked at 900W there, it wasn’t maintained).

Yep, we’ve said the same thing, you just highlighted it across the whole segment! It’s not right.

FIL used to live of Reynells road, its only uphill from the green dot to the roundabout, then its flat for 0.5km then all down

surely the speed camera would have flashed them!

OP d’you really care that much that some-one else is cheating on Strava?

really? 😐

More to the point, who makes a frikkin segment that goes round what appears to be a rather large roundabout??

That isn’t a segment, that’s just the start of the ride. But going the wrong way around a roundabout is definitely peculiar.

It can’t be a reversed ride though, as the speed going downhills is faster than the speed going uphills, which if the whole trace were reversed would be what you would see.

There are no signature “blips” in the speed which would point to digitalepo either (unless that has been eradicated by the developers of digitalepo).

To be honest, it just looks like he smashed himself for a couple of climbs. Though taking a KOM down from 12m27 to 7m54 does look dodgy.

Why not just flag the ride, give him the chance to answer Strava’s questions about it, and move on.

E-Bike? Pedal assist would explain why the top speed is still low.

OP d’you really care that much that some-one else is cheating on Strava?

really?

nickc I’ve never seen a ride done/edited/whateverhappenedtoit like this, hence is my interest in it. As you can see above – few other guys find it weird too. That’s it. 😉

Just flag it as dubious – someone at Strava will look at it and either delete it or ask the person in question to remove it or resubmit it.

I’ve had Strava email me about a ride, my reaction was, “yeah, I rode it”, next email asked me to look at the speed: I’d maintained exactly 20kph up hill and down dale for about 30 Km! Something had just gone wrong in the unit, there’s no way I could have kept that accurately to a speed in a car (even with cruise control) on the roads in question. I just deleted the ride. Whether someone had flagged it or Strava have some algorithm that picks up on this sort of thing I don’t know.

I was just wondering that myself. Have found another climb of similar gradient which doesn’t have a segment, but has the same flat line 10mph speed.

Though taking a KOM down from 12m27 to 7m54 does look dodgy.

Particularly from someone who’s clearly not very fast.

E-Bike? Pedal assist would explain why the top speed is still low

Could be actually!

Been flagged now anyway – was that you OP?

OP d’you really care that much that some-one else is cheating on Strava?
really?

As said, not sure anyone ‘cares’ as such, just intriguing!

Coming to the conclusion that e-bike is most likely – just look at how little variation there is in the KOM speeds as the average gradient changes.

who cares its on the road

‘mobile’ just indicates it was an uploaded or synced GPX where it can’t tell what device it was.

Probably just some glitch, and as said, road so “meh” 😛

love the backwards roundabout 🙂

the backwards roundabout will be down to however made the segment, and will have gone round backwards, however its near enough to be picked up as a segment for people riding the right way round

I didn’t flag it – I suppose it was the guy who lost those KOMs! 😆

Nope – it’s not part of a segment.

Been flagged now anyway – was that you OP?

Some bitter roadie probably 😆

Last time I had a big crash on the quantocks I only stopped recording the ride outside A & E. Once my phone’s internet was turned on again after leaving hospital and the ride uploaded it was flagged literally within about 3 mins 😯

Had a load of road kom’s for a few mins though 😆

The “Mobile” Device thing.
If its a phone, then its an app, but if its a gps which Strava don’t support, then its marked as Mobile.
I have a Bryton Rider50/Dakota20 and those go under the Mobile tag.