That can happen if your GPS reception was suboptimal and therefore Strava treated some parts of your run as pause.

What does suboptimal mean😭😭

Not exact enough to get the correct location every second or partly not there at all.

With a 30k under 3 hrs, Strava really shouldn't think that your pace was so slow that it's not worth considering to be “moving” 🫠 that's not cool. 

Seriously though, what device are you using? Here's some details on what ​@Jan_Mantau mentioned: 

https://support.strava.com/hc/en-us/articles/216917707-Bad-GPS-Data

Also, it might be worth trying the “correct distance” feature - not sure if it helps but just in case: 

I mean I just used my phone and I did take a couple of small breaks to drink and rest a bit during which I never paused the tracking so I guess thats why. But again, is the time for my pr 2 hours 33 then or 2 hours 54?

The PR would be the elapsed time. If you go to your Best Efforts, you'll see it there (tab You > profile pic in left upper corner > scroll a bit down and tap Best Efforts > find 30k)

So what is moving time good for then? Is it just a random stat?

Not all runs are aimed to be PRs, actually 80% of the volume should be slow low-effort runs 🙂 and that's where the moving pace / moving time comes in handy.

When training for a marathon, let's say that I plan to run 25 km in my marathon pace. But I might be forced to stop at crossroads / traffic lights and such. If I used the elapsed pace / elapsed time, I'd either get a “slower” result - or would have to run faster for a bit to catch up after the traffic lights wait. Which would beat the purpose of the training, which expects me to maintain a certain pace, not slower, not faster. 

The elapsed time is obviously important for a race or similar kind of run - even if I stop at the aid station for a bit, the clock is still ticking. (And if I mark a run as a race, Strava will show the elapsed time instead of moving time in the main stats.)

Bottom line is - the purpose of the run matters 🙂

Thanks for the answers! At the moment Im not training for anything specific, just running every now and then, trying to hit some prs when I can and want to. So theoretically, moving time isnt really anything I really have to worry about, right?

Not really - not to “worry”, it's rather for your information. Both “moving” and “elapsed” time are useful - maybe not now, but at some point you may decide that you want to look back at your running data, and it will help you to see your progress 👍🙂

​@Elliot_johansson - Just to give you an idea of how I use the moving time versus elapsed time.  I do a lot of biking with friends.  Sometimes we go out for a longer ride, but it is more social than going for a hard workout.  I like to see how much of the time we were out that I was actually riding.  Hey, we were out on the trails for 4 hours, but really, I was only riding for about 3 hours of that.  It gives me a better idea of how much exercise I actually got during the activity.  I can’t really count the full 4 hours as being as active, but I know I got a solid 3 hours of moving time. 

I also have a long ride planned for a couple weeks from now.  It is about 150 miles of mountain biking with 21,000 feet of climbing.  I will most likely sleep for a while at night somewhere along the way.  I will be really interested to see both how long the overall ride took and how long I was actually riding my bike within that timeframe.  

Really, all the stuff you see is data that you can choose to use or not.  Some (many?) don’t really use much of it.  Some only want to know how far they went. Others only want to know how long they were out.  Some want every little piece of data to track and analyze.  You can find what works for you.  The good thing is that the data is there if you want it.