BEG → PUYBelgrade to Pula

live

Direct flights from Belgrade (BEG) to Pula (PUY) run nonstop between the two airports. The nonstop covers 503 km, an estimated 1 hour 9 minutes in the air.

BEG Belgrade busy · +24
PUY Pula tracking
503 km · ~1h 09m est.
Under pressure · 0 airlines · nonstop
68 / 100

route health from live BEG and PUY delay boards

Flight time~1h 09mestimated from route distance

Airports right now

live boards
BEGBelgrade +24 min busy 🌤 mostly cloudy · E 9 kt Full BEG delay board →
PUYPula tracking Full PUY delay board →

How the Belgrade to Pula route actually runs

Pro Flight Search records official board updates for nonstop BEG to PUY flights through the day: schedules, estimates, gate pushes and actual departures. The verdict above comes from operated flights, so it reflects what this route does rather than what the timetable promises.

Planning around a delay? Live airport delays · Weather delay risk map · Will a delayed flight be cancelled? · Do planes make up time in the air? · How we measure

Cite this data

Journalists, bloggers, and researchers may cite this page with attribution and a link to Pro Flight Search.

Suggested citation

Pro Flight Search: Belgrade (BEG) to Pula (PUY) route reliability, measured from operated flights on official airport boards.

Canonical URL
https://proflightsearch.com/search-flights/BEG-PUY
How we measure this →

BEG to PUY questions

Is BEG–PUY running on time right now?

Mostly on schedule. The departure side at BEG is the weaker end, route health score 68/100. The airports section above carries the live status and delay window at both ends.

How long is the flight from BEG to PUY?

Great-circle distance is 503 km. With typical jet cruise speed plus taxi, climb and descent, expect roughly 66–73 min gate-to-gate on this route.

What does the route health score measure?

A blend of departure-side delay at BEG and arrival-side delay at PUY, computed from rolling delay windows (refreshed every 40 minutes) with a daily-rollup fallback. Current MVFR, IFR, or LIFR endpoint weather caps the score when flight rules can limit throughput. Higher is healthier: 100 means operations are clean at both ends.