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