sensors Mode-S transponder
4851F5
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-BVR · BOEING 777-300ER
- Hex
- 4851F5
- Octal
- 22050765
- Decimal
- 4,739,573
- Country
- NL
- Tail
- PH-BVR
- Type
- B77W
- Flights observed
- 170
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4851F5 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 | - | 17 | 2026-07-10 |
| KLM104 | - | 12 | 2026-07-13 |
| KLM836 | KLM Royal Dutch Airlines | 11 | 2026-07-04 |
| KLM835 | - | 11 | 2026-07-03 |
| KLM590 | - | 11 | 2026-07-08 |
| KLM105 | - | 9 | 2026-07-13 |
| KLM744 | - | 8 | 2026-07-07 |
| KLM743 | - | 8 | 2026-07-07 |
| KLM188 | - | 8 | 2026-05-15 |
| KLM757 | - | 6 | 2026-07-05 |
| KLM248 | - | 5 | 2026-07-02 |
| KLM133 | - | 5 | 2026-07-01 |
| KLM706 | KLM Royal Dutch Airlines | 4 | 2026-04-15 |
| KLM592 | - | 4 | 2026-06-29 |
| KLM591 | KLM Royal Dutch Airlines | 4 | 2026-06-29 |
| KLM571 | KLM Royal Dutch Airlines | 4 | 2026-06-18 |
| KLM896 | - | 3 | 2026-06-20 |
| KLM705 | KLM Royal Dutch Airlines | 3 | 2026-04-14 |
| KLM569 | KLM Royal Dutch Airlines | 3 | 2026-06-01 |
| KLM226 | - | 3 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | KLM104 | - | Jul 13, 21:25 UTC | Jul 14, 01:05 UTC | 3h 40m |
| 2026-07-13 | KLM105 | AMS → CPT | Jul 13, 08:45 UTC | Jul 13, 19:25 UTC | 10h 40m |
| 2026-07-12 | KLM226 | YVR → AMS | Jul 12, 01:00 UTC | Jul 12, 09:35 UTC | 8h 35m |
| 2026-07-11 | KLM219 | - | Jul 11, 13:40 UTC | Jul 11, 23:00 UTC | 9h 20m |
| 2026-07-10 | KLM758 | - | Jul 10, 19:30 UTC | Jul 11, 10:05 UTC | 14h 35m |
| 2026-07-10 | KLM758 | - | Jul 10, 11:40 UTC | Jul 11, 10:05 UTC | 22h 25m |
| 2026-07-09 | KLM104 | CPT → AMS | Jul 9, 21:20 UTC | Jul 10, 08:40 UTC | 11h 20m |
| 2026-07-09 | KLM105 | - | Jul 9, 08:40 UTC | Jul 9, 19:20 UTC | 10h 40m |
| 2026-07-08 | KLM590 | - | Jul 8, 13:50 UTC | Jul 9, 04:35 UTC | 14h 45m |
| 2026-07-07 | KLM744 | - | Jul 7, 22:50 UTC | Jul 8, 10:30 UTC | 11h 40m |
| 2026-07-07 | KLM743 | - | Jul 7, 08:25 UTC | Jul 7, 20:00 UTC | 11h 35m |
| 2026-07-06 | KLM590 | - | Jul 6, 13:35 UTC | Jul 7, 04:25 UTC | 14h 50m |
| 2026-07-05 | KLM758 | - | Jul 5, 19:15 UTC | Jul 6, 10:05 UTC | 14h 50m |
| 2026-07-05 | KLM757 | - | Jul 5, 11:45 UTC | Jul 6, 10:05 UTC | 22h 20m |
| 2026-07-04 | KLM836 | SIN → AMS | Jul 4, 17:20 UTC | Jul 4, 22:20 UTC | 5h 0m |
| 2026-07-03 | KLM835 | - | Jul 3, 19:25 UTC | Jul 4, 07:15 UTC | 11h 50m |
| 2026-07-02 | KLM590 | - | Jul 2, 14:20 UTC | Jul 3, 04:45 UTC | 14h 25m |
| 2026-07-02 | KLM248 | - | Jul 2, 02:55 UTC | Jul 2, 10:25 UTC | 7h 30m |
| 2026-07-01 | KLM133 | - | Jul 1, 15:45 UTC | Jul 2, 00:15 UTC | 8h 30m |
| 2026-07-01 | KLM792 | - | Jul 1, 01:05 UTC | Jul 1, 12:10 UTC | 11h 5m |
| 2026-06-30 | KLM791 | AMS → GRU | Jun 30, 11:35 UTC | Jun 30, 22:50 UTC | 11h 15m |
| 2026-06-29 | KLM592 | - | Jun 29, 22:00 UTC | Jun 30, 08:05 UTC | 10h 6m |
| 2026-06-29 | KLM591 | AMS → JNB | Jun 29, 09:34 UTC | Jun 29, 19:35 UTC | 10h 0m |
| 2026-06-28 | KLM836 | SIN → AMS | Jun 28, 17:25 UTC | Jun 29, 05:54 UTC | 12h 30m |
| 2026-06-28 | KLM836 | SIN → AMS | Jun 28, 14:59 UTC | Jun 28, 15:09 UTC | 10m |
| 2026-06-27 | KLM835 | - | Jun 27, 19:24 UTC | Jun 28, 07:25 UTC | 12h 0m |
| 2026-06-27 | KLM248 | ATL → AMS | Jun 27, 02:55 UTC | Jun 27, 10:40 UTC | 7h 45m |
| 2026-06-26 | KLM133 | AMS → ATL | Jun 26, 15:34 UTC | Jun 27, 00:20 UTC | 8h 45m |
| 2026-06-25 | KLM758 | - | Jun 25, 19:20 UTC | Jun 26, 09:55 UTC | 14h 35m |
| 2026-06-25 | KLM758 | - | Jun 25, 11:30 UTC | Jun 26, 09:55 UTC | 22h 25m |
| 2026-06-24 | KLM104 | CPT → AMS | Jun 24, 21:29 UTC | Jun 25, 08:45 UTC | 11h 15m |
| 2026-06-24 | KLM105 | - | Jun 24, 18:39 UTC | Jun 24, 19:04 UTC | 25m |
| 2026-06-24 | KLM105 | - | Jun 24, 08:24 UTC | Jun 24, 16:09 UTC | 7h 45m |
| 2026-06-23 | KLM878 | - | Jun 23, 20:54 UTC | Jun 24, 05:40 UTC | 8h 45m |
| 2026-06-23 | KLM877 | - | Jun 23, 10:10 UTC | Jun 23, 17:34 UTC | 7h 25m |
| 2026-06-20 | KLM896 | - | Jun 20, 23:04 UTC | Jun 21, 17:05 UTC | 18h 0m |
| 2026-06-20 | KLM896 | - | Jun 20, 17:19 UTC | Jun 21, 17:05 UTC | 23h 45m |
| 2026-06-20 | KLM896 | - | Jun 20, 15:19 UTC | Jun 21, 15:15 UTC | 23h 55m |
| 2026-06-20 | KLM895 | - | Jun 20, 13:29 UTC | Jun 21, 13:15 UTC | 23h 45m |
| 2026-06-19 | KLM744 | - | Jun 19, 18:44 UTC | Jun 20, 10:20 UTC | 15h 35m |
| 2026-06-19 | KLM744 | - | Jun 19, 09:19 UTC | Jun 20, 09:14 UTC | 23h 55m |
| 2026-06-19 | KLM743 | - | Jun 19, 08:14 UTC | Jun 20, 02:19 UTC | 18h 5m |
| 2026-06-18 | KLM571 | DAR → AMS | Jun 18, 08:35 UTC | Jun 18, 16:20 UTC | 7h 45m |
| 2026-06-14 | KLM590 | - | Jun 14, 13:25 UTC | Jun 15, 04:50 UTC | 15h 24m |
| 2026-06-13 | KLM744 | LIM → AMS | Jun 13, 18:55 UTC | Jun 14, 10:15 UTC | 15h 20m |
| 2026-06-13 | KLM743 | AMS → LIM | Jun 13, 09:20 UTC | Jun 14, 09:15 UTC | 23h 55m |
| 2026-06-13 | KLM743 | AMS → LIM | Jun 13, 08:45 UTC | Jun 13, 23:05 UTC | 14h 20m |
| 2026-06-12 | KLM888 | - | Jun 12, 22:40 UTC | Jun 13, 03:35 UTC | 4h 55m |
| 2026-06-12 | KLM888 | HKG → AMS | Jun 12, 14:40 UTC | Jun 12, 14:50 UTC | 10m |
| 2026-06-11 | KLM887 | AMS → HKG | Jun 11, 21:40 UTC | Jun 12, 06:15 UTC | 8h 36m |
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-BVR page for operator, model, and routing details .