Flight
RYS5082
Flight history and live tracking for RYS5082, operated by Royal Sky. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Route
| Airline | Royal Sky |
| Observed route | LTAI → EPSC |
Flight history 13 flights since Jun 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-10-02estimated | LTAI | EPSC | 05:03 +03 | 07:04 CEST | 3h 01m | SP-RSL |
| 2026-09-25estimated | LTAI | EPSC | 04:49 +03 | 06:46 CEST | 2h 56m | 48C1A2 |
| 2026-09-18estimated | ? | ? | 02:25Z | 05:02Z | 2h 36m | SP-RSN |
| 2026-09-11estimated | LTAI | EPSC | 05:06 +03 | 06:54 CEST | 2h 48m | SP-RSQ |
Earlier flights (9) - back to 2026-06-19
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-09-04estimated | LTAI | EPSC | 04:49 +03 | 07:05 CEST | 3h 15m | SP-RSP |
| 2026-08-28estimated | LTAI | EPSC | 04:40 +03 | 06:50 CEST | 3h 09m | SP-RSZ |
| 2026-08-21estimated | ? | ? | 02:24Z | 06:48Z | 4h 23m | 48EA4D |
| 2026-08-14estimated | ? | ? | 02:02Z | 04:36Z | 2h 33m | SP-RKS |
| 2026-07-17estimated | LTAI | EPSC | 05:13 +03 | 07:08 CEST | 2h 54m | SP-RKH |
| 2026-07-10estimated | LTAI | EPSC | 05:29 +03 | 07:26 CEST | 2h 57m | SP-RKL |
| 2026-07-03estimated | LTAI | EPSC | 04:38 +03 | 06:40 CEST | 3h 02m | SP-RSN |
| 2026-06-26estimated | LTAI | EPSC | 05:07 +03 | 07:02 CEST | 2h 54m | 48C1A4 |
| 2026-06-19estimated | LTAI | EPSC | 04:56 +03 | 07:02 CEST | 3h 05m | SP-RSO |
Times are local to each airport. Hover for UTC. Flights marked estimated were completed with route prediction or partial coverage; partial records have a confirmed departure but no reliable arrival fix.
Follow this flight
Get an email when RYS5082 flies + if it runs late.
Data access
Live positions and 365-day history for this flight are available through the PlaneTrack API (commercial use from $29/month) and as one-off CSV extracts from our archive (from $9.99, with a free one-day sample). Questions: [email protected]