Flight
BPO348
Flight history and live tracking for BPO348. Recent flights from the PlaneTrack independent receiver network, with departure and arrival times, aircraft used, and a real-time position feed.
Flight history 15 flights since Jan 2026
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| No flights in the last 30 days. | ||||||
Earlier flights (15) - back to 2026-01-05
| Date | From | To | Dep | Arr | Duration | Aircraft |
|---|---|---|---|---|---|---|
| 2026-02-25 | EDWU | EDKB | 13:49 CET | 15:26 CET | 1h 36m | D-HSHS |
| 2026-02-25 | EDKB | EDWU | 09:38 CET | 11:30 CET | 1h 51m | D-HSHS |
| 2026-01-09 | ETNN | EDDK | 11:08 CET | 11:38 CET | 0h 29m | D-HSHD |
| 2026-01-09 | EDKB | ETNN | 09:43 CET | 10:44 CET | 1h 01m | D-HSHD |
| 2026-01-08 | EDLM | EDKB | 14:42 CET | 15:42 CET | 0h 59m | D-HSHK |
| 2026-01-08estimated | EDLW | EDLI | 10:32 CET | 11:22 CET | 0h 50m | D-HSHK |
| 2026-01-07 | EDDL | EDKB | 16:04 CET | 16:34 CET | 0h 29m | D-HSHK |
| 2026-01-07partial | EDDL | ? | 11:08 CET | D-HSHK | ||
| 2026-01-07 | EDKB | EDDL | 09:50 CET | 11:02 CET | 1h 12m | D-HSHK |
| 2026-01-06 | EDDL | EDLM | 11:07 CET | 14:42 CET | 3h 35m | D-HSHE |
| 2026-01-06partial | EDDL | ? | 10:29 CET | D-HSHE | ||
| 2026-01-06partial | EDDK | ? | 09:57 CET | D-HSHE | ||
| 2026-01-05estimated | EDKB | EDDK | 11:50 CET | 15:35 CET | 3h 45m | D-HSHK |
| 2026-01-05estimated | EDDL | EDKB | 11:18 CET | 11:50 CET | 0h 31m | D-HSHK |
| 2026-01-05estimated | EDDK | EDDL | 10:40 CET | 11:18 CET | 0h 37m | D-HSHK |
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 BPO348 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]