Not currently tracked · last seen 5h ago
- Flights observed
- 526 showing last 50
- Avg flight time
- 1h 18m
- Typical route
- DBV → AMS
- Last seen
- 5h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 19:30 UTC | Jul 13, 21:20 UTC | 1h 50m |
| 2026-07-13 | TLS → AMS | Jul 13, 15:50 UTC | Jul 13, 17:15 UTC | 1h 25m |
| 2026-07-13 | AMS → TLS | Jul 13, 13:10 UTC | Jul 13, 14:45 UTC | 1h 35m |
| 2026-07-13 | - | Jul 13, 10:50 UTC | Jul 13, 12:00 UTC | 1h 10m |
| 2026-07-13 | - | Jul 13, 08:25 UTC | Jul 13, 09:40 UTC | 1h 15m |
| 2026-07-13 | DBV → AMS | Jul 13, 04:40 UTC | Jul 13, 06:45 UTC | 2h 5m |
| 2026-07-12 | AMS → DBV | Jul 12, 19:25 UTC | Jul 12, 21:15 UTC | 1h 50m |
| 2026-07-12 | - | Jul 12, 16:55 UTC | Jul 12, 17:50 UTC | 55m |
| 2026-07-12 | - | Jul 12, 15:05 UTC | Jul 12, 15:55 UTC | 50m |
| 2026-07-12 | MAD → AMS | Jul 12, 11:30 UTC | Jul 12, 13:25 UTC | 1h 55m |
| 2026-07-12 | - | Jul 12, 08:05 UTC | Jul 12, 10:05 UTC | 2h 0m |
| 2026-07-12 | - | Jul 12, 05:10 UTC | Jul 12, 06:10 UTC | 1h 0m |
| 2026-07-11 | AMS → MUC | Jul 11, 19:30 UTC | Jul 11, 20:25 UTC | 55m |
| 2026-07-11 | - | Jul 11, 17:05 UTC | Jul 11, 17:45 UTC | 40m |
| 2026-07-11 | - | Jul 11, 14:40 UTC | Jul 11, 15:30 UTC | 50m |
| 2026-07-11 | - | Jul 11, 10:15 UTC | Jul 11, 12:30 UTC | 2h 15m |
| 2026-07-11 | - | Jul 11, 06:45 UTC | Jul 11, 08:45 UTC | 2h 0m |
| 2026-07-10 | - | Jul 10, 18:35 UTC | Jul 10, 19:15 UTC | 40m |
| 2026-07-10 | AMS → CDG | Jul 10, 16:10 UTC | Jul 10, 17:05 UTC | 55m |
| 2026-07-09 | - | Jul 9, 08:25 UTC | Jul 9, 09:35 UTC | 1h 10m |
| 2026-07-09 | - | Jul 9, 06:20 UTC | Jul 9, 07:25 UTC | 1h 5m |
| 2026-07-08 | LIN → AMS | Jul 8, 04:45 UTC | Jul 8, 06:05 UTC | 1h 20m |
| 2026-07-07 | - | Jul 7, 20:05 UTC | Jul 7, 21:10 UTC | 1h 5m |
| 2026-07-07 | - | Jul 7, 16:45 UTC | Jul 7, 18:05 UTC | 1h 20m |
| 2026-07-07 | - | Jul 7, 14:30 UTC | Jul 7, 15:40 UTC | 1h 10m |
| 2026-07-07 | - | Jul 7, 11:15 UTC | Jul 7, 13:10 UTC | 1h 55m |
| 2026-07-07 | AMS → BLQ | Jul 7, 09:05 UTC | Jul 7, 10:20 UTC | 1h 15m |
| 2026-07-07 | DBV → AMS | Jul 7, 04:25 UTC | Jul 7, 06:45 UTC | 2h 20m |
| 2026-07-06 | AMS → DBV | Jul 6, 19:45 UTC | Jul 6, 21:35 UTC | 1h 50m |
| 2026-07-06 | - | Jul 6, 16:55 UTC | Jul 6, 17:50 UTC | 55m |
| 2026-07-06 | - | Jul 6, 15:05 UTC | Jul 6, 16:10 UTC | 1h 5m |
| 2026-07-06 | BER → AMS | Jul 6, 12:50 UTC | Jul 6, 13:55 UTC | 1h 5m |
| 2026-07-06 | AMS → BER | Jul 6, 10:45 UTC | Jul 6, 11:40 UTC | 55m |
| 2026-07-06 | - | Jul 6, 08:40 UTC | Jul 6, 09:20 UTC | 40m |
| 2026-07-06 | - | Jul 6, 06:50 UTC | Jul 6, 07:40 UTC | 50m |
| 2026-07-05 | - | Jul 5, 15:55 UTC | Jul 5, 18:30 UTC | 2h 35m |
| 2026-07-05 | - | Jul 5, 12:35 UTC | Jul 5, 14:50 UTC | 2h 15m |
| 2026-07-05 | - | Jul 5, 10:00 UTC | Jul 5, 10:55 UTC | 55m |
| 2026-07-05 | AMS → BLL | Jul 5, 08:15 UTC | Jul 5, 09:05 UTC | 50m |
| 2026-07-05 | LIN → AMS | Jul 5, 04:45 UTC | Jul 5, 06:20 UTC | 1h 35m |
| 2026-07-04 | AMS → LIN | Jul 4, 19:35 UTC | Jul 4, 20:45 UTC | 1h 10m |
| 2026-06-27 | LYS → AMS | Jun 27, 17:25 UTC | Jun 27, 18:35 UTC | 1h 10m |
| 2026-06-27 | - | Jun 27, 14:54 UTC | Jun 27, 16:04 UTC | 1h 10m |
| 2026-06-27 | - | Jun 27, 10:10 UTC | Jun 27, 11:09 UTC | 1h 0m |
| 2026-06-27 | AMS → MUC | Jun 27, 08:05 UTC | Jun 27, 09:09 UTC | 1h 5m |
| 2026-06-27 | NCL → AMS | Jun 27, 05:29 UTC | Jun 27, 06:30 UTC | 1h 0m |
| 2026-06-26 | AMS → NCL | Jun 26, 21:04 UTC | Jun 26, 21:55 UTC | 50m |
| 2026-06-26 | - | Jun 26, 18:49 UTC | Jun 26, 19:35 UTC | 45m |
| 2026-06-26 | AMS → BHX | Jun 26, 16:49 UTC | Jun 26, 17:35 UTC | 45m |
| 2026-06-26 | DBV → AMS | Jun 26, 11:40 UTC | Jun 26, 13:45 UTC | 2h 5m |
Specifications
| Registration | PH-BGI |
| Aircraft type | BOEING 737-700 (B737) |
| Mode-S code | 484B90 · 22045620 (octal) |
Looking for transponder-level data? View the Mode-S 484B90 page for country allocation, callsign history, and ADS-B signal details.
PH-BGI frequently asked
What type of aircraft is PH-BGI?
PH-BGI is a BOEING 737-700 (ICAO type code B737).
What is the Mode-S transponder code for PH-BGI?
PH-BGI broadcasts on Mode-S (ICAO 24-bit) address 484B90 (octal 22045620). View the transponder page.
What route does PH-BGI typically fly?
PH-BGI most frequently flies between DBV and AMS based on observed flights.
Where is PH-BGI right now?
PH-BGI is not currently being tracked; last seen 5h ago.