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