sensors Mode-S transponder
48436F
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-BQH · BOEING 777-200
- Hex
- 48436F
- Octal
- 22041557
- Decimal
- 4,735,855
- Country
- NL
- Tail
- PH-BQH
- Type
- B772
- Flights observed
- 182
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 48436F 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 |
|---|---|---|---|
| KLM702 | - | 14 | 2026-07-10 |
| KLM701 | - | 13 | 2026-07-10 |
| KLM635 | - | 12 | 2026-07-03 |
| KLM636 | - | 10 | 2026-07-04 |
| KLM685 | - | 9 | 2026-06-23 |
| KLM268 | KLM Royal Dutch Airlines | 9 | 2026-06-12 |
| KLM686 | - | 7 | 2026-06-24 |
| KLM896 | KLM Royal Dutch Airlines | 6 | 2026-05-03 |
| KLM861 | KLM Royal Dutch Airlines | 6 | 2026-07-05 |
| KLM843 | - | 6 | 2026-06-25 |
| KLM695 | - | 6 | 2026-07-04 |
| KLM100 | - | 6 | 2026-07-05 |
| KLM895 | KLM Royal Dutch Airlines | 5 | 2026-05-02 |
| KLM878 | - | 5 | 2026-07-11 |
| KLM862 | - | 5 | 2026-07-06 |
| KLM610 | - | 5 | 2026-06-25 |
| KLM609 | - | 5 | 2026-06-24 |
| KLM856 | KLM Royal Dutch Airlines | 4 | 2026-06-02 |
| KLM855 | KLM Royal Dutch Airlines | 4 | 2026-06-02 |
| KLM759 | - | 4 | 2026-07-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | KLM759 | - | Jul 14, 11:35 UTC | Jul 14, 21:45 UTC | 10h 10m |
| 2026-07-13 | KLM48 | - | Jul 13, 22:20 UTC | Jul 14, 06:00 UTC | 7h 40m |
| 2026-07-13 | KLM611 | - | Jul 13, 11:40 UTC | Jul 13, 19:20 UTC | 7h 40m |
| 2026-07-12 | KLM250 | MSP → AMS | Jul 12, 20:35 UTC | Jul 13, 04:00 UTC | 7h 25m |
| 2026-07-12 | KLM655 | - | Jul 12, 09:15 UTC | Jul 12, 17:20 UTC | 8h 5m |
| 2026-07-11 | KLM878 | - | Jul 11, 20:45 UTC | Jul 12, 05:35 UTC | 8h 50m |
| 2026-07-11 | KLM877 | - | Jul 11, 10:05 UTC | Jul 11, 18:10 UTC | 8h 5m |
| 2026-07-10 | KLM702 | - | Jul 10, 18:20 UTC | Jul 11, 06:50 UTC | 12h 31m |
| 2026-07-10 | KLM702 | - | Jul 10, 16:05 UTC | Jul 10, 16:35 UTC | 30m |
| 2026-07-10 | KLM701 | - | Jul 10, 12:35 UTC | Jul 10, 12:45 UTC | 10m |
| 2026-07-10 | KLM701 | - | Jul 10, 10:50 UTC | Jul 10, 11:15 UTC | 25m |
| 2026-07-09 | KLM701 | - | Jul 9, 19:35 UTC | Jul 10, 08:45 UTC | 13h 10m |
| 2026-07-08 | KLM760 | - | Jul 8, 02:45 UTC | Jul 8, 11:00 UTC | 8h 15m |
| 2026-07-07 | KLM759 | - | Jul 7, 11:25 UTC | Jul 7, 21:55 UTC | 10h 30m |
| 2026-07-06 | KLM862 | - | Jul 6, 03:15 UTC | Jul 6, 16:55 UTC | 13h 40m |
| 2026-07-05 | KLM861 | AMS → NRT | Jul 5, 12:15 UTC | Jul 6, 00:55 UTC | 12h 40m |
| 2026-07-05 | KLM100 | YYZ → AMS | Jul 5, 02:10 UTC | Jul 5, 08:45 UTC | 6h 35m |
| 2026-07-04 | KLM695 | AMS → YYZ | Jul 4, 16:00 UTC | Jul 4, 23:40 UTC | 7h 40m |
| 2026-07-04 | KLM636 | LAS → AMS | Jul 4, 03:45 UTC | Jul 4, 13:20 UTC | 9h 35m |
| 2026-07-03 | KLM635 | - | Jul 3, 15:25 UTC | Jul 4, 01:30 UTC | 10h 5m |
| 2026-07-03 | KLM100 | YYZ → AMS | Jul 3, 02:30 UTC | Jul 3, 09:00 UTC | 6h 30m |
| 2026-07-02 | KLM695 | AMS → YYZ | Jul 2, 16:15 UTC | Jul 2, 23:50 UTC | 7h 35m |
| 2026-07-02 | KLM636 | LAS → AMS | Jul 2, 03:50 UTC | Jul 2, 13:00 UTC | 9h 10m |
| 2026-07-01 | KLM635 | - | Jul 1, 15:50 UTC | Jul 2, 01:40 UTC | 9h 50m |
| 2026-07-01 | KLM760 | - | Jul 1, 01:15 UTC | Jul 1, 10:55 UTC | 9h 40m |
| 2026-06-30 | KLM759 | - | Jun 30, 11:35 UTC | Jun 30, 22:05 UTC | 10h 30m |
| 2026-06-29 | KLM702 | EZE → AMS | Jun 29, 18:10 UTC | Jun 30, 06:55 UTC | 12h 46m |
| 2026-06-29 | KLM702 | - | Jun 29, 15:34 UTC | Jun 29, 16:10 UTC | 35m |
| 2026-06-29 | KLM701 | - | Jun 29, 11:10 UTC | Jun 29, 11:35 UTC | 25m |
| 2026-06-28 | KLM701 | AMS → EZE | Jun 28, 19:55 UTC | Jun 29, 09:05 UTC | 13h 10m |
| 2026-06-27 | KLM702 | - | Jun 27, 18:20 UTC | Jun 28, 07:09 UTC | 12h 50m |
| 2026-06-27 | KLM702 | - | Jun 27, 15:30 UTC | Jun 27, 16:10 UTC | 40m |
| 2026-06-27 | KLM702 | - | Jun 27, 14:35 UTC | Jun 27, 14:45 UTC | 10m |
| 2026-06-26 | KLM701 | AMS → EZE | Jun 26, 19:30 UTC | Jun 27, 08:44 UTC | 13h 15m |
| 2026-06-26 | KLM844 | - | Jun 26, 05:19 UTC | Jun 26, 16:54 UTC | 11h 35m |
| 2026-06-25 | KLM843 | AMS → BKK | Jun 25, 15:34 UTC | Jun 26, 02:14 UTC | 10h 40m |
| 2026-06-25 | KLM610 | SLC → AMS | Jun 25, 03:50 UTC | Jun 25, 12:44 UTC | 8h 55m |
| 2026-06-24 | KLM609 | - | Jun 24, 15:54 UTC | Jun 25, 01:24 UTC | 9h 30m |
| 2026-06-24 | KLM686 | - | Jun 24, 02:34 UTC | Jun 24, 12:25 UTC | 9h 50m |
| 2026-06-23 | KLM685 | - | Jun 23, 13:19 UTC | Jun 24, 00:25 UTC | 11h 5m |
| 2026-06-22 | KLM758 | - | Jun 22, 19:40 UTC | Jun 23, 10:04 UTC | 14h 25m |
| 2026-06-22 | KLM758 | - | Jun 22, 11:50 UTC | Jun 23, 10:04 UTC | 22h 15m |
| 2026-06-22 | KLM757 | - | Jun 22, 11:35 UTC | Jun 23, 09:45 UTC | 22h 10m |
| 2026-06-21 | KLM188 | - | Jun 21, 19:45 UTC | Jun 22, 07:49 UTC | 12h 5m |
| 2026-06-21 | KLM163 | - | Jun 21, 11:49 UTC | Jun 22, 07:49 UTC | 20h 0m |
| 2026-06-21 | KLM100 | - | Jun 21, 02:24 UTC | Jun 21, 09:00 UTC | 6h 35m |
| 2026-06-20 | KLM695 | - | Jun 20, 16:05 UTC | Jun 20, 23:25 UTC | 7h 20m |
| 2026-06-19 | KLM296 | - | Jun 19, 21:59 UTC | Jun 20, 04:29 UTC | 6h 30m |
| 2026-06-19 | KLM225 | AMS → IAD | Jun 19, 11:45 UTC | Jun 19, 19:39 UTC | 7h 55m |
| 2026-06-19 | KLM100 | - | Jun 19, 02:19 UTC | Jun 19, 08:59 UTC | 6h 40m |
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-BQH page for operator, model, and routing details .