Flight
SEGYE
Flight history and live tracking for SEGYE. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 16 flights since Apr 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-17partial | ESKA | ? | 13:56 CEST | SE-GYE | ||
| 2026-08-15estimated | ESSA | ESKA | 08:49 CEST | 18:44 CEST | 9h 55m | SE-GYE |
| 2026-08-12estimated | ESSB | ESHG | 10:44 CEST | 12:00 CEST | 1h 15m | SE-GYE |
Earlier flights (13) - back to 2026-04-14
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-04estimated | ESSV | ESKA | 15:35 CEST | 17:54 CEST | 2h 19m | SE-GYE |
| 2026-07-02partial | ESSV | ? | 11:15 CEST | SE-GYE | ||
| 2026-06-29estimated | ESSV | ESKA | 14:19 CEST | 15:44 CEST | 1h 24m | SE-GYE |
| 2026-06-26estimated | ESKA | ESSV | 11:32 CEST | 12:34 CEST | 1h 02m | SE-GYE |
| 2026-06-22partial | ESSA | ? | 14:16 CEST | SE-GYE | ||
| 2026-05-21partial | ESSB | ? | 18:22 CEST | SE-GYE | ||
| 2026-05-10estimated | ESSB | ESKA | 13:12 CEST | 14:02 CEST | 0h 49m | SE-GYE |
| 2026-05-06partial | ESKA | ? | 09:44 CEST | SE-GYE | ||
| 2026-05-01estimated | EDHL | ESHG | 09:53 CEST | 14:16 CEST | 4h 23m | SE-GYE |
| 2026-04-21estimated | ESCN | ESSB | 12:54 CEST | 14:10 CEST | 1h 15m | SE-GYE |
| 2026-04-19estimated | ESSA | ESSB | 11:50 CEST | 13:46 CEST | 1h 55m | SE-GYE |
| 2026-04-17estimated | ESSB | ESSA | 10:44 CEST | 12:12 CEST | 1h 27m | SE-GYE |
| 2026-04-14estimated | ESSB | ESSV | 10:32 CEST | 17:00 CEST | 6h 27m | SE-GYE |
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 SEGYE 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 own receiver network archive. Questions: [email protected]