Not currently tracked · last seen 8h ago
- Flights observed
- 257 showing last 50
- Avg flight time
- 1h 22m
- Typical route
- BUD → AMS
- Last seen
- 8h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | BUD → AMS | May 29, 18:35 UTC | May 29, 20:30 UTC | 1h 55m |
| 2026-05-29 | AMS → BUD | May 29, 15:40 UTC | May 29, 17:30 UTC | 1h 50m |
| 2026-05-29 | LYS → AMS | May 29, 12:20 UTC | May 29, 13:40 UTC | 1h 20m |
| 2026-05-29 | AMS → LYS | May 29, 10:00 UTC | May 29, 11:10 UTC | 1h 10m |
| 2026-05-29 | MUC → AMS | May 29, 07:45 UTC | May 29, 08:50 UTC | 1h 5m |
| 2026-05-29 | AMS → VIE | May 29, 05:40 UTC | May 29, 06:45 UTC | 1h 5m |
| 2026-05-28 | BUD → AMS | May 28, 18:00 UTC | May 28, 19:50 UTC | 1h 50m |
| 2026-05-28 | AMS → BUD | May 28, 15:30 UTC | May 28, 17:05 UTC | 1h 35m |
| 2026-05-28 | LYS → AMS | May 28, 12:20 UTC | May 28, 13:30 UTC | 1h 10m |
| 2026-05-28 | AMS → LYS | May 28, 10:10 UTC | May 28, 11:20 UTC | 1h 10m |
| 2026-05-28 | MUC → AMS | May 28, 07:55 UTC | May 28, 09:05 UTC | 1h 10m |
| 2026-05-28 | AMS → VIE | May 28, 06:00 UTC | May 28, 07:05 UTC | 1h 5m |
| 2026-05-27 | BUD → AMS | May 27, 19:10 UTC | May 27, 20:55 UTC | 1h 45m |
| 2026-05-27 | AMS → BUD | May 27, 16:30 UTC | May 27, 18:10 UTC | 1h 40m |
| 2026-05-27 | LYS → AMS | May 27, 14:05 UTC | May 27, 15:15 UTC | 1h 10m |
| 2026-05-27 | AMS → LYS | May 27, 10:35 UTC | May 27, 11:45 UTC | 1h 10m |
| 2026-05-27 | MUC → AMS | May 27, 07:55 UTC | May 27, 09:05 UTC | 1h 10m |
| 2026-05-27 | AMS → VIE | May 27, 05:55 UTC | May 27, 07:00 UTC | 1h 6m |
| 2026-05-26 | BUD → AMS | May 26, 17:50 UTC | May 26, 19:45 UTC | 1h 55m |
| 2026-05-26 | AMS → BUD | May 26, 15:20 UTC | May 26, 16:59 UTC | 1h 40m |
| 2026-05-26 | LYS → AMS | May 26, 12:50 UTC | May 26, 14:00 UTC | 1h 10m |
| 2026-05-26 | AMS → LYS | May 26, 10:29 UTC | May 26, 11:44 UTC | 1h 15m |
| 2026-05-25 | BUD → AMS | May 25, 17:50 UTC | May 25, 19:40 UTC | 1h 50m |
| 2026-05-25 | AMS → BUD | May 25, 15:20 UTC | May 25, 17:00 UTC | 1h 40m |
| 2026-05-25 | LYS → AMS | May 25, 12:20 UTC | May 25, 13:30 UTC | 1h 10m |
| 2026-05-25 | AMS → LYS | May 25, 10:05 UTC | May 25, 11:15 UTC | 1h 10m |
| 2026-05-25 | MUC → AMS | May 25, 07:40 UTC | May 25, 08:55 UTC | 1h 15m |
| 2026-05-25 | AMS → VIE | May 25, 05:35 UTC | May 25, 06:30 UTC | 55m |
| 2026-05-24 | BUD → AMS | May 24, 17:55 UTC | May 24, 19:45 UTC | 1h 50m |
| 2026-05-24 | AMS → BUD | May 24, 15:25 UTC | May 24, 17:05 UTC | 1h 40m |
| 2026-05-24 | LYS → AMS | May 24, 12:30 UTC | May 24, 13:35 UTC | 1h 5m |
| 2026-05-24 | AMS → LYS | May 24, 10:05 UTC | May 24, 11:20 UTC | 1h 15m |
| 2026-05-24 | MUC → AMS | May 24, 07:50 UTC | May 24, 08:55 UTC | 1h 5m |
| 2026-05-24 | AMS → VIE | May 24, 05:40 UTC | May 24, 06:45 UTC | 1h 5m |
| 2026-05-23 | BUD → AMS | May 23, 17:45 UTC | May 23, 19:35 UTC | 1h 50m |
| 2026-05-23 | AMS → BUD | May 23, 15:15 UTC | May 23, 16:55 UTC | 1h 40m |
| 2026-05-23 | LYS → AMS | May 23, 12:25 UTC | May 23, 13:35 UTC | 1h 10m |
| 2026-05-23 | AMS → LYS | May 23, 10:15 UTC | May 23, 11:20 UTC | 1h 5m |
| 2026-05-23 | MUC → AMS | May 23, 07:50 UTC | May 23, 09:00 UTC | 1h 10m |
| 2026-05-23 | AMS → VIE | May 23, 05:40 UTC | May 23, 06:40 UTC | 1h 0m |
| 2026-05-22 | BUD → AMS | May 22, 17:55 UTC | May 22, 19:45 UTC | 1h 50m |
| 2026-05-22 | AMS → BUD | May 22, 15:25 UTC | May 22, 17:05 UTC | 1h 40m |
| 2026-05-22 | LYS → AMS | May 22, 12:20 UTC | May 22, 13:40 UTC | 1h 20m |
| 2026-05-22 | AMS → LYS | May 22, 10:05 UTC | May 22, 11:25 UTC | 1h 20m |
| 2026-05-22 | MUC → AMS | May 22, 07:35 UTC | May 22, 08:45 UTC | 1h 10m |
| 2026-05-22 | AMS → VIE | May 22, 05:25 UTC | May 22, 06:25 UTC | 1h 0m |
| 2026-05-21 | BUD → AMS | May 21, 17:55 UTC | May 21, 19:40 UTC | 1h 45m |
| 2026-05-21 | AMS → BUD | May 21, 15:15 UTC | May 21, 16:55 UTC | 1h 40m |
| 2026-05-21 | LYS → AMS | May 21, 12:35 UTC | May 21, 13:50 UTC | 1h 15m |
| 2026-05-21 | AMS → LYS | May 21, 10:20 UTC | May 21, 11:30 UTC | 1h 10m |
Specifications
| Registration | F-HBLE |
| Aircraft type | EMBRAER ERJ-190-100 (E190) |
| Mode-S code | 398564 · 16302544 (octal) |
Looking for transponder-level data? View the Mode-S 398564 page for country allocation, callsign history, and ADS-B signal details.
F-HBLE frequently asked
What type of aircraft is F-HBLE?
F-HBLE is a EMBRAER ERJ-190-100 (ICAO type code E190).
What is the Mode-S transponder code for F-HBLE?
F-HBLE broadcasts on Mode-S (ICAO 24-bit) address 398564 (octal 16302544). View the transponder page.
What route does F-HBLE typically fly?
F-HBLE most frequently flies between BUD and AMS based on observed flights.
Where is F-HBLE right now?
F-HBLE is not currently being tracked; last seen 8h ago.