sensors Mode-S transponder
4851B3
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-BVP · BOEING 777-300ER
- Hex
- 4851B3
- Octal
- 22050663
- Decimal
- 4,739,507
- Country
- NL
- Tail
- PH-BVP
- Type
- B77W
- Flights observed
- 171
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 4851B3 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 |
|---|---|---|---|
| KLM836 | - | 13 | 2026-07-12 |
| KLM226 | - | 13 | 2026-07-01 |
| KLM835 | - | 10 | 2026-07-12 |
| KLM592 | - | 10 | 2026-07-13 |
| KLM591 | - | 10 | 2026-07-13 |
| KLM219 | - | 10 | 2026-06-30 |
| KLM744 | - | 9 | 2026-07-05 |
| KLM743 | - | 8 | 2026-07-05 |
| KLM248 | KLM Royal Dutch Airlines | 7 | 2026-06-11 |
| KLM207 | - | 6 | 2026-07-03 |
| KLM792 | - | 5 | 2026-06-21 |
| KLM791 | KLM Royal Dutch Airlines | 5 | 2026-06-20 |
| KLM758 | - | 5 | 2026-06-24 |
| KLM646 | - | 5 | 2026-07-04 |
| KLM268 | KLM Royal Dutch Airlines | 5 | 2026-05-10 |
| KLM133 | - | 5 | 2026-06-10 |
| KLM590 | - | 4 | 2026-07-01 |
| KLM105 | KLM Royal Dutch Airlines | 4 | 2026-05-14 |
| KLM862 | KLM Royal Dutch Airlines | 3 | 2026-05-13 |
| KLM861 | KLM Royal Dutch Airlines | 3 | 2026-05-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | KLM592 | - | Jul 13, 21:40 UTC | Jul 14, 08:05 UTC | 10h 25m |
| 2026-07-13 | KLM591 | - | Jul 13, 09:05 UTC | Jul 13, 19:10 UTC | 10h 5m |
| 2026-07-12 | KLM836 | - | Jul 12, 17:20 UTC | Jul 13, 05:55 UTC | 12h 35m |
| 2026-07-12 | KLM836 | - | Jul 12, 15:05 UTC | Jul 12, 15:15 UTC | 10m |
| 2026-07-12 | KLM835 | - | Jul 12, 09:15 UTC | Jul 12, 09:25 UTC | 10m |
| 2026-07-11 | KLM835 | - | Jul 11, 19:30 UTC | Jul 12, 07:20 UTC | 11h 50m |
| 2026-07-11 | KLM844 | - | Jul 11, 05:25 UTC | Jul 11, 17:00 UTC | 11h 35m |
| 2026-07-10 | KLM843 | - | Jul 10, 15:25 UTC | Jul 11, 01:40 UTC | 10h 15m |
| 2026-07-09 | KLM592 | - | Jul 9, 21:25 UTC | Jul 10, 08:05 UTC | 10h 40m |
| 2026-07-09 | KLM591 | - | Jul 9, 08:55 UTC | Jul 9, 19:00 UTC | 10h 5m |
| 2026-07-08 | KLM836 | - | Jul 8, 17:15 UTC | Jul 9, 05:55 UTC | 12h 40m |
| 2026-07-08 | KLM836 | SIN → AMS | Jul 8, 15:00 UTC | Jul 8, 15:10 UTC | 10m |
| 2026-07-07 | KLM835 | - | Jul 7, 19:30 UTC | Jul 8, 07:10 UTC | 11h 40m |
| 2026-07-07 | KLM898 | - | Jul 7, 10:25 UTC | Jul 7, 15:10 UTC | 4h 45m |
| 2026-07-07 | KLM898 | - | Jul 7, 03:30 UTC | Jul 7, 03:40 UTC | 10m |
| 2026-07-07 | KLM897 | - | Jul 7, 00:05 UTC | Jul 7, 00:25 UTC | 20m |
| 2026-07-06 | KLM897 | - | Jul 6, 14:30 UTC | Jul 6, 18:25 UTC | 3h 55m |
| 2026-07-05 | KLM744 | - | Jul 5, 22:55 UTC | Jul 6, 10:20 UTC | 11h 25m |
| 2026-07-05 | KLM743 | - | Jul 5, 08:20 UTC | Jul 5, 19:55 UTC | 11h 35m |
| 2026-07-05 | KLM174 | - | Jul 5, 02:10 UTC | Jul 5, 05:45 UTC | 3h 35m |
| 2026-07-05 | KLM174 | - | Jul 5, 01:15 UTC | Jul 5, 01:55 UTC | 40m |
| 2026-07-04 | KLM565 | - | Jul 4, 10:50 UTC | Jul 4, 14:35 UTC | 3h 45m |
| 2026-07-04 | KLM646 | - | Jul 4, 00:00 UTC | Jul 4, 06:15 UTC | 6h 15m |
| 2026-07-03 | KLM207 | - | Jul 3, 13:30 UTC | Jul 3, 20:55 UTC | 7h 25m |
| 2026-07-02 | KLM744 | - | Jul 2, 23:00 UTC | Jul 3, 10:25 UTC | 11h 25m |
| 2026-07-02 | KLM743 | - | Jul 2, 08:35 UTC | Jul 2, 20:10 UTC | 11h 35m |
| 2026-07-01 | KLM590 | - | Jul 1, 14:00 UTC | Jul 2, 04:50 UTC | 14h 50m |
| 2026-07-01 | KLM226 | - | Jul 1, 01:15 UTC | Jul 1, 10:00 UTC | 8h 45m |
| 2026-06-30 | KLM219 | AMS → YVR | Jun 30, 14:00 UTC | Jun 30, 22:55 UTC | 8h 55m |
| 2026-06-30 | KLM226 | - | Jun 30, 01:04 UTC | Jun 30, 09:55 UTC | 8h 51m |
| 2026-06-29 | KLM219 | - | Jun 29, 13:49 UTC | Jun 29, 22:39 UTC | 8h 50m |
| 2026-06-29 | KLM226 | - | Jun 29, 01:00 UTC | Jun 29, 09:54 UTC | 8h 55m |
| 2026-06-28 | KLM219 | AMS → YVR | Jun 28, 13:45 UTC | Jun 28, 22:20 UTC | 8h 35m |
| 2026-06-27 | KLM744 | - | Jun 27, 19:24 UTC | Jun 28, 10:30 UTC | 15h 5m |
| 2026-06-27 | KLM743 | - | Jun 27, 08:44 UTC | Jun 28, 02:39 UTC | 17h 55m |
| 2026-06-25 | KLM589 | - | Jun 25, 13:45 UTC | Jun 26, 04:39 UTC | 14h 55m |
| 2026-06-24 | KLM758 | - | Jun 24, 20:05 UTC | Jun 25, 10:15 UTC | 14h 10m |
| 2026-06-24 | KLM758 | - | Jun 24, 12:50 UTC | Jun 25, 10:15 UTC | 21h 25m |
| 2026-06-24 | KLM758 | AMS → AMS | Jun 24, 11:39 UTC | Jun 25, 10:15 UTC | 22h 35m |
| 2026-06-23 | KLM592 | - | Jun 23, 21:29 UTC | Jun 24, 07:54 UTC | 10h 25m |
| 2026-06-23 | KLM591 | AMS → JNB | Jun 23, 09:09 UTC | Jun 23, 19:10 UTC | 10h 0m |
| 2026-06-22 | KLM836 | SIN → AMS | Jun 22, 17:40 UTC | Jun 23, 06:09 UTC | 12h 30m |
| 2026-06-22 | KLM836 | SIN → AMS | Jun 22, 15:35 UTC | Jun 22, 15:45 UTC | 10m |
| 2026-06-21 | KLM835 | - | Jun 21, 19:45 UTC | Jun 22, 07:30 UTC | 11h 45m |
| 2026-06-21 | KLM792 | - | Jun 21, 01:05 UTC | Jun 21, 11:59 UTC | 10h 55m |
| 2026-06-20 | KLM791 | AMS → GRU | Jun 20, 11:34 UTC | Jun 20, 15:14 UTC | 3h 40m |
| 2026-06-20 | KLM646 | - | Jun 20, 00:24 UTC | Jun 20, 01:44 UTC | 1h 20m |
| 2026-06-19 | KLM207 | - | Jun 19, 19:04 UTC | Jun 19, 20:55 UTC | 1h 50m |
| 2026-06-19 | KLM207 | - | Jun 19, 13:20 UTC | Jun 19, 14:54 UTC | 1h 35m |
| 2026-06-18 | KLM836 | SIN → AMS | Jun 18, 17:35 UTC | Jun 19, 05:59 UTC | 12h 24m |
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-BVP page for operator, model, and routing details .