Not currently tracked · last seen Jul 26, 22:35 UTC
- Flights observed
- 205 showing last 50
- Avg flight time
- 11h 49m
- Typical route
- SIN → AMS
- Last seen
- Jul 26, 22:35 UTC
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-26 | AMS → GRU | Jul 26, 11:25 UTC | Jul 26, 22:35 UTC | 11h 10m |
| 2026-07-25 | JNB → AMS | Jul 25, 21:25 UTC | Jul 26, 07:45 UTC | 10h 21m |
| 2026-07-25 | AMS → JNB | Jul 25, 08:55 UTC | Jul 25, 19:10 UTC | 10h 15m |
| 2026-07-25 | SIN → AMS | Jul 25, 04:35 UTC | Jul 25, 05:30 UTC | 55m |
| 2026-07-24 | SIN → AMS | Jul 24, 17:10 UTC | Jul 25, 04:30 UTC | 11h 20m |
| 2026-07-24 | SIN → AMS | Jul 24, 15:15 UTC | Jul 24, 15:25 UTC | 10m |
| 2026-07-23 | AMS → SIN | Jul 23, 19:40 UTC | Jul 24, 08:00 UTC | 12h 20m |
| 2026-07-22 | - | Jul 22, 12:50 UTC | Jul 23, 07:55 UTC | 19h 5m |
| 2026-07-22 | - | Jul 22, 11:50 UTC | Jul 23, 07:55 UTC | 20h 5m |
| 2026-07-22 | AMS → CHS | Jul 22, 02:00 UTC | Jul 22, 03:00 UTC | 1h 0m |
| 2026-07-21 | AMS → YYZ | Jul 21, 16:15 UTC | Jul 21, 23:40 UTC | 7h 25m |
| 2026-07-20 | JNB → AMS | Jul 20, 21:45 UTC | Jul 21, 08:00 UTC | 10h 14m |
| 2026-07-20 | - | Jul 20, 09:30 UTC | Jul 20, 19:40 UTC | 10h 10m |
| 2026-07-19 | - | Jul 19, 05:15 UTC | Jul 19, 17:05 UTC | 11h 50m |
| 2026-07-18 | - | Jul 18, 17:25 UTC | Jul 19, 16:45 UTC | 23h 20m |
| 2026-07-18 | - | Jul 18, 14:50 UTC | Jul 19, 14:45 UTC | 23h 55m |
| 2026-07-18 | - | Jul 18, 13:40 UTC | Jul 19, 12:45 UTC | 23h 5m |
| 2026-07-17 | - | Jul 17, 23:25 UTC | Jul 18, 10:50 UTC | 11h 26m |
| 2026-07-17 | - | Jul 17, 08:35 UTC | Jul 17, 20:00 UTC | 11h 25m |
| 2026-07-16 | IAD → AMS | Jul 16, 22:40 UTC | Jul 17, 05:50 UTC | 7h 10m |
| 2026-07-16 | - | Jul 16, 11:34 UTC | Jul 16, 19:10 UTC | 7h 35m |
| 2026-07-15 | CPT → AMS | Jul 15, 21:10 UTC | Jul 16, 08:15 UTC | 11h 5m |
| 2026-07-15 | - | Jul 15, 08:25 UTC | Jul 15, 19:15 UTC | 10h 50m |
| 2026-07-15 | - | Jul 15, 01:50 UTC | Jul 15, 04:05 UTC | 2h 15m |
| 2026-07-14 | - | Jul 14, 07:15 UTC | Jul 15, 04:05 UTC | 20h 49m |
| 2026-07-12 | - | Jul 12, 13:40 UTC | Jul 13, 04:25 UTC | 14h 45m |
| 2026-07-11 | - | Jul 11, 19:00 UTC | Jul 12, 10:10 UTC | 15h 10m |
| 2026-07-11 | - | Jul 11, 12:50 UTC | Jul 12, 10:10 UTC | 21h 20m |
| 2026-07-11 | - | Jul 11, 11:35 UTC | Jul 12, 10:10 UTC | 22h 35m |
| 2026-07-10 | - | Jul 10, 12:50 UTC | Jul 11, 07:55 UTC | 19h 5m |
| 2026-07-10 | - | Jul 10, 12:00 UTC | Jul 11, 07:55 UTC | 19h 55m |
| 2026-07-09 | - | Jul 9, 12:50 UTC | Jul 10, 07:45 UTC | 18h 55m |
| 2026-07-09 | - | Jul 9, 11:50 UTC | Jul 10, 07:45 UTC | 19h 55m |
| 2026-07-08 | CPT → AMS | Jul 8, 21:15 UTC | Jul 9, 08:30 UTC | 11h 15m |
| 2026-07-08 | - | Jul 8, 18:55 UTC | Jul 8, 19:15 UTC | 20m |
| 2026-07-08 | - | Jul 8, 08:40 UTC | Jul 8, 16:10 UTC | 7h 30m |
| 2026-07-07 | - | Jul 7, 13:35 UTC | Jul 8, 04:25 UTC | 14h 50m |
| 2026-07-07 | - | Jul 7, 01:30 UTC | Jul 7, 09:45 UTC | 8h 15m |
| 2026-07-06 | AMS → YVR | Jul 6, 14:15 UTC | Jul 6, 23:20 UTC | 9h 5m |
| 2026-07-06 | - | Jul 6, 04:00 UTC | Jul 6, 11:20 UTC | 7h 20m |
| 2026-07-05 | - | Jul 5, 16:30 UTC | Jul 6, 01:15 UTC | 8h 45m |
| 2026-07-05 | YVR → AMS | Jul 5, 01:05 UTC | Jul 5, 09:40 UTC | 8h 35m |
| 2026-07-04 | - | Jul 4, 13:40 UTC | Jul 4, 22:55 UTC | 9h 15m |
| 2026-07-03 | - | Jul 3, 23:55 UTC | Jul 4, 10:10 UTC | 10h 15m |
| 2026-07-03 | - | Jul 3, 08:20 UTC | Jul 3, 20:05 UTC | 11h 45m |
| 2026-06-29 | - | Jun 29, 05:20 UTC | Jun 29, 16:35 UTC | 11h 15m |
| 2026-06-28 | - | Jun 28, 15:29 UTC | Jun 29, 02:00 UTC | 10h 30m |
| 2026-06-28 | - | Jun 28, 12:15 UTC | Jun 28, 12:44 UTC | 30m |
| 2026-06-28 | - | Jun 28, 01:59 UTC | Jun 28, 12:09 UTC | 10h 10m |
| 2026-06-27 | AMS → GRU | Jun 27, 12:25 UTC | Jun 27, 23:10 UTC | 10h 45m |
Specifications
| Registration | PH-BVG |
| Aircraft type | BOEING 777-300ER (B77W) |
| Mode-S code | 484CBB · 22046273 (octal) |
Looking for transponder-level data? View the Mode-S 484CBB page for country allocation, callsign history, and ADS-B signal details.
PH-BVG frequently asked
What type of aircraft is PH-BVG?
PH-BVG is a BOEING 777-300ER (ICAO type code B77W).
What is the Mode-S transponder code for PH-BVG?
PH-BVG broadcasts on Mode-S (ICAO 24-bit) address 484CBB (octal 22046273). View the transponder page.
What route does PH-BVG typically fly?
PH-BVG most frequently flies between SIN and AMS based on observed flights.
Where is PH-BVG right now?
PH-BVG is not currently being tracked; last seen Jul 26, 22:35 UTC.