Flight
HBVYM
Flight history and live tracking for HBVYM. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 18 flights since Mar 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-08-18partial | LSZG | ? | 10:38 CEST | HB-VYM |
Earlier flights (17) - back to 2026-03-15
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-07-14 | LSGG | LSZG | 15:09 CEST | 18:40 CEST | 3h 30m | HB-VYM |
| 2026-07-10partial | LSGG | ? | 12:35 CEST | HB-VYM | ||
| 2026-07-09 | LSZG | LSGG | 16:31 CEST | 17:04 CEST | 0h 32m | HB-VYM |
| 2026-07-06 | LSZR | LSZG | 15:24 CEST | 15:50 CEST | 0h 25m | HB-VYM |
| 2026-06-30 | LSZG | LSZR | 08:04 CEST | 08:28 CEST | 0h 23m | HB-VYM |
| 2026-06-29partial | LSZG | ? | 10:43 CEST | HB-VYM | ||
| 2026-06-26partial | LSZG | ? | 09:21 CEST | HB-VYM | ||
| 2026-06-18 | LSZG | LSMP | 15:09 CEST | 19:32 CEST | 4h 22m | HB-VYM |
| 2026-05-23partial | LSZG | ? | 12:23 CEST | HB-VYM | ||
| 2026-05-22 | EGKB | LSZG | 08:14 BST | 10:20 CEST | 1h 05m | HB-VYM |
| 2026-05-21 | LSZG | EGKB | 15:00 CEST | 15:14 BST | 1h 13m | HB-VYM |
| 2026-05-03partial | LSZG | ? | 12:00 CEST | HB-VYM | ||
| 2026-05-01 | EGKB | LSZG | 07:22 BST | 09:32 CEST | 1h 09m | HB-VYM |
| 2026-04-30 | LSZG | EGKB | 08:26 CEST | 08:36 BST | 1h 09m | HB-VYM |
| 2026-04-15partial | LSZG | ? | 08:11 CEST | HB-VYM | ||
| 2026-04-12 | ? | LGAV | 08:10Z | 13:18 EEST | 2h 07m | HB-VYM |
| 2026-03-15estimated | ? | ? | 09:58Z | 14:56Z | 4h 58m | HB-VYM |
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 HBVYM 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]