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