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