sensors Mode-S transponder
4851F7
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-BVU · BOEING 777-300ER
- Hex
- 4851F7
- Octal
- 22050767
- Decimal
- 4,739,575
- Country
- NL
- Tail
- PH-BVU
- Type
- B77W
- Flights observed
- 141
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- Jul 26, 15:30 UTC
Last known position
Country allocation
The ICAO 24-bit address 4851F7 falls within the block assigned to Netherlands (NL) by ICAO Annex 10, Volume III. Every aircraft registered in Netherlands receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.
Callsign history 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| KLM758 | KLM Royal Dutch Airlines | 9 | 2026-07-20 |
| KLM744 | - | 9 | 2026-07-10 |
| KLM268 | - | 9 | 2026-07-18 |
| KLM743 | - | 8 | 2026-07-10 |
| KLM226 | KLM Royal Dutch Airlines | 8 | 2026-07-26 |
| KLM219 | KLM Royal Dutch Airlines | 8 | 2026-07-25 |
| KLM791 | KLM Royal Dutch Airlines | 7 | 2026-07-23 |
| KLM590 | KLM Royal Dutch Airlines | 7 | 2026-07-22 |
| KLM589 | KLM Royal Dutch Airlines | 7 | 2026-07-26 |
| KLM248 | KLM Royal Dutch Airlines | 7 | 2026-07-25 |
| KLM133 | - | 7 | 2026-07-24 |
| KLM792 | KLM Royal Dutch Airlines | 6 | 2026-07-24 |
| KLM835 | - | 4 | 2026-06-23 |
| KLM757 | KLM Royal Dutch Airlines | 4 | 2026-07-20 |
| KLM105 | KLM Royal Dutch Airlines | 4 | 2026-06-14 |
| KLM104 | - | 4 | 2026-06-15 |
| KLM896 | - | 3 | 2026-06-19 |
| KLM844 | - | 3 | 2026-07-08 |
| KLM843 | - | 3 | 2026-07-07 |
| KLM836 | KLM Royal Dutch Airlines | 3 | 2026-06-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | KLM589 | AMS → ACC | Jul 26, 13:35 UTC | Jul 26, 15:30 UTC | 1h 55m |
| 2026-07-26 | KLM226 | - | Jul 26, 01:05 UTC | Jul 26, 09:25 UTC | 8h 21m |
| 2026-07-25 | KLM219 | AMS → YVR | Jul 25, 13:40 UTC | Jul 25, 22:50 UTC | 9h 10m |
| 2026-07-25 | KLM248 | ATL → AMS | Jul 25, 02:55 UTC | Jul 25, 10:30 UTC | 7h 35m |
| 2026-07-24 | KLM133 | AMS → ATL | Jul 24, 15:30 UTC | Jul 25, 00:05 UTC | 8h 35m |
| 2026-07-24 | KLM792 | GRU → AMS | Jul 24, 01:25 UTC | Jul 24, 12:15 UTC | 10h 50m |
| 2026-07-23 | KLM791 | AMS → GRU | Jul 23, 11:35 UTC | Jul 23, 22:55 UTC | 11h 20m |
| 2026-07-22 | KLM590 | ACC → AMS | Jul 22, 13:40 UTC | Jul 23, 04:10 UTC | 14h 30m |
| 2026-07-21 | KLM590 | ACC → AMS | Jul 21, 13:45 UTC | Jul 22, 04:30 UTC | 14h 45m |
| 2026-07-20 | KLM758 | PTY → AMS | Jul 20, 19:25 UTC | Jul 21, 10:25 UTC | 14h 59m |
| 2026-07-20 | KLM758 | PTY → AMS | Jul 20, 11:50 UTC | Jul 21, 10:25 UTC | 22h 34m |
| 2026-07-20 | KLM757 | AMS → PTY | Jul 20, 11:20 UTC | Jul 21, 09:45 UTC | 22h 25m |
| 2026-07-19 | KLM188 | - | Jul 19, 11:50 UTC | Jul 20, 08:15 UTC | 20h 25m |
| 2026-07-18 | KLM268 | - | Jul 18, 01:34 UTC | Jul 18, 03:50 UTC | 2h 16m |
| 2026-07-17 | KLM268 | - | Jul 17, 07:50 UTC | Jul 18, 03:50 UTC | 20h 1m |
| 2026-07-17 | KLM268 | - | Jul 17, 07:30 UTC | Jul 18, 03:50 UTC | 20h 21m |
| 2026-07-16 | KLM268 | - | Jul 16, 10:45 UTC | Jul 17, 03:55 UTC | 17h 10m |
| 2026-07-16 | KLM268 | - | Jul 16, 07:50 UTC | Jul 17, 03:55 UTC | 20h 5m |
| 2026-07-16 | KLM268 | AMS → AMS | Jul 16, 07:25 UTC | Jul 17, 03:55 UTC | 20h 30m |
| 2026-07-15 | KLM792 | - | Jul 15, 01:05 UTC | Jul 15, 11:55 UTC | 10h 50m |
| 2026-07-14 | KLM791 | - | Jul 14, 11:55 UTC | Jul 14, 23:00 UTC | 11h 4m |
| 2026-07-14 | KLM226 | - | Jul 14, 00:55 UTC | Jul 14, 09:25 UTC | 8h 30m |
| 2026-07-13 | KLM219 | - | Jul 13, 13:40 UTC | Jul 13, 22:50 UTC | 9h 10m |
| 2026-07-13 | KLM226 | - | Jul 13, 01:05 UTC | Jul 13, 09:55 UTC | 8h 50m |
| 2026-07-12 | KLM219 | - | Jul 12, 13:50 UTC | Jul 12, 22:55 UTC | 9h 5m |
| 2026-07-12 | KLM248 | ATL → AMS | Jul 12, 03:01 UTC | Jul 12, 10:45 UTC | 7h 45m |
| 2026-07-11 | KLM133 | - | Jul 11, 15:45 UTC | Jul 12, 00:15 UTC | 8h 30m |
| 2026-07-10 | KLM744 | - | Jul 10, 23:10 UTC | Jul 11, 10:40 UTC | 11h 30m |
| 2026-07-10 | KLM743 | - | Jul 10, 08:20 UTC | Jul 10, 20:05 UTC | 11h 45m |
| 2026-07-08 | KLM844 | - | Jul 8, 05:20 UTC | Jul 8, 17:00 UTC | 11h 40m |
| 2026-07-07 | KLM843 | AMS → BKK | Jul 7, 15:30 UTC | Jul 8, 01:55 UTC | 10h 25m |
| 2026-07-07 | KLM792 | - | Jul 7, 01:25 UTC | Jul 7, 12:10 UTC | 10h 45m |
| 2026-07-06 | KLM791 | AMS → GRU | Jul 6, 11:50 UTC | Jul 6, 23:05 UTC | 11h 15m |
| 2026-07-05 | KLM758 | - | Jul 5, 01:35 UTC | Jul 5, 09:55 UTC | 8h 20m |
| 2026-07-04 | KLM758 | - | Jul 4, 11:50 UTC | Jul 5, 09:55 UTC | 22h 5m |
| 2026-07-04 | KLM758 | - | Jul 4, 11:15 UTC | Jul 5, 09:45 UTC | 22h 30m |
| 2026-07-02 | KLM571 | - | Jul 2, 08:55 UTC | Jul 2, 16:35 UTC | 7h 40m |
| 2026-07-01 | KLM192 | - | Jul 1, 20:55 UTC | Jul 2, 05:35 UTC | 8h 40m |
| 2026-07-01 | KLM661 | - | Jul 1, 08:35 UTC | Jul 1, 18:30 UTC | 9h 55m |
| 2026-06-29 | KLM589 | - | Jun 29, 13:39 UTC | Jun 30, 04:25 UTC | 14h 46m |
| 2026-06-28 | KLM744 | - | Jun 28, 16:49 UTC | Jun 29, 10:40 UTC | 17h 50m |
| 2026-06-28 | KLM744 | - | Jun 28, 09:50 UTC | Jun 29, 09:44 UTC | 23h 55m |
| 2026-06-28 | KLM743 | - | Jun 28, 08:55 UTC | Jun 29, 03:14 UTC | 18h 20m |
| 2026-06-27 | KLM844 | - | Jun 27, 05:19 UTC | Jun 27, 16:44 UTC | 11h 25m |
| 2026-06-26 | KLM843 | AMS → BKK | Jun 26, 15:45 UTC | Jun 27, 02:14 UTC | 10h 30m |
| 2026-06-26 | KLM792 | - | Jun 26, 01:20 UTC | Jun 26, 12:05 UTC | 10h 45m |
| 2026-06-25 | KLM791 | AMS → GRU | Jun 25, 11:30 UTC | Jun 25, 22:54 UTC | 11h 25m |
| 2026-06-24 | KLM592 | - | Jun 24, 21:40 UTC | Jun 25, 08:04 UTC | 10h 25m |
| 2026-06-24 | KLM591 | AMS → JNB | Jun 24, 09:24 UTC | Jun 24, 19:24 UTC | 10h 0m |
| 2026-06-23 | KLM836 | SIN → AMS | Jun 23, 17:30 UTC | Jun 24, 05:59 UTC | 12h 30m |
About Mode-S
A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.
Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.
Prefer a tail-number view? See the PH-BVU page for operator, model, and routing details .