sensors Mode-S transponder
4843F2
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-BQO · BOEING 777-200
- Hex
- 4843F2
- Octal
- 22041762
- Decimal
- 4,735,986
- Country
- NL
- Tail
- PH-BQO
- Type
- B772
- Flights observed
- 166
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4843F2 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 | - | 18 | 2026-06-13 |
| KLM701 | - | 14 | 2026-07-14 |
| KLM874 | - | 10 | 2026-07-07 |
| KLM268 | - | 9 | 2026-07-03 |
| KLM862 | - | 8 | 2026-06-12 |
| KLM878 | - | 6 | 2026-07-06 |
| KLM686 | - | 6 | 2026-07-12 |
| KLM685 | - | 6 | 2026-07-11 |
| KLM896 | KLM Royal Dutch Airlines | 5 | 2026-05-20 |
| KLM877 | - | 5 | 2026-07-06 |
| KLM861 | KLM Royal Dutch Airlines | 5 | 2026-06-11 |
| KLM610 | - | 4 | 2026-07-13 |
| KLM609 | - | 4 | 2026-07-12 |
| KLM895 | KLM Royal Dutch Airlines | 3 | 2026-05-19 |
| KLM844 | - | 3 | 2026-07-14 |
| KLM843 | - | 3 | 2026-07-13 |
| KLM646 | - | 3 | 2026-06-30 |
| KLM636 | KLM Royal Dutch Airlines | 3 | 2026-05-29 |
| KLM635 | KLM Royal Dutch Airlines | 3 | 2026-05-28 |
| KLM207 | - | 3 | 2026-06-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | KLM701 | - | Jul 14, 19:30 UTC | Jul 14, 20:30 UTC | 1h 0m |
| 2026-07-14 | KLM844 | - | Jul 14, 05:25 UTC | Jul 14, 16:55 UTC | 11h 30m |
| 2026-07-13 | KLM843 | - | Jul 13, 15:30 UTC | Jul 14, 02:05 UTC | 10h 35m |
| 2026-07-13 | KLM610 | SLC → AMS | Jul 13, 04:15 UTC | Jul 13, 12:50 UTC | 8h 35m |
| 2026-07-12 | KLM609 | - | Jul 12, 15:50 UTC | Jul 13, 01:20 UTC | 9h 30m |
| 2026-07-12 | KLM686 | - | Jul 12, 02:40 UTC | Jul 12, 12:45 UTC | 10h 5m |
| 2026-07-11 | KLM685 | - | Jul 11, 12:55 UTC | Jul 12, 00:15 UTC | 11h 20m |
| 2026-07-10 | KLM104 | - | Jul 10, 21:15 UTC | Jul 11, 08:25 UTC | 11h 10m |
| 2026-07-10 | KLM105 | AMS → CPT | Jul 10, 08:35 UTC | Jul 10, 19:15 UTC | 10h 40m |
| 2026-07-09 | KLM808 | - | Jul 9, 16:35 UTC | Jul 10, 06:10 UTC | 13h 35m |
| 2026-07-09 | KLM808 | - | Jul 9, 12:45 UTC | Jul 9, 14:50 UTC | 2h 5m |
| 2026-07-09 | KLM807 | - | Jul 9, 08:30 UTC | Jul 9, 10:20 UTC | 1h 50m |
| 2026-07-08 | KLM807 | AMS → TPE | Jul 8, 18:30 UTC | Jul 9, 06:35 UTC | 12h 5m |
| 2026-07-07 | KLM874 | - | Jul 7, 12:35 UTC | Jul 8, 06:35 UTC | 18h 0m |
| 2026-07-07 | KLM874 | - | Jul 7, 10:35 UTC | Jul 8, 06:35 UTC | 20h 0m |
| 2026-07-07 | KLM874 | AMS → AMS | Jul 7, 10:05 UTC | Jul 8, 06:35 UTC | 20h 30m |
| 2026-07-06 | KLM878 | - | Jul 6, 20:45 UTC | Jul 7, 05:50 UTC | 9h 5m |
| 2026-07-06 | KLM877 | AMS → BOM | Jul 6, 10:00 UTC | Jul 6, 18:35 UTC | 8h 35m |
| 2026-07-05 | KLM192 | - | Jul 5, 21:45 UTC | Jul 6, 06:05 UTC | 8h 20m |
| 2026-07-05 | KLM661 | - | Jul 5, 09:45 UTC | Jul 5, 19:20 UTC | 9h 35m |
| 2026-07-03 | KLM268 | - | Jul 3, 08:35 UTC | Jul 4, 03:50 UTC | 19h 15m |
| 2026-07-03 | KLM195 | - | Jul 3, 07:20 UTC | Jul 4, 03:50 UTC | 20h 30m |
| 2026-07-02 | KLM296 | IAD → AMS | Jul 2, 22:30 UTC | Jul 3, 05:00 UTC | 6h 30m |
| 2026-07-02 | KLM225 | AMS → IAD | Jul 2, 11:35 UTC | Jul 2, 19:40 UTC | 8h 5m |
| 2026-07-02 | KLM644 | - | Jul 2, 01:55 UTC | Jul 2, 08:10 UTC | 6h 15m |
| 2026-07-01 | KLM643 | - | Jul 1, 15:55 UTC | Jul 1, 23:20 UTC | 7h 25m |
| 2026-07-01 | KLM686 | - | Jul 1, 03:15 UTC | Jul 1, 13:20 UTC | 10h 5m |
| 2026-06-30 | KLM685 | - | Jun 30, 12:45 UTC | Jun 30, 23:50 UTC | 11h 5m |
| 2026-06-30 | KLM646 | JFK → AMS | Jun 30, 00:04 UTC | Jun 30, 06:25 UTC | 6h 20m |
| 2026-06-29 | KLM207 | - | Jun 29, 13:24 UTC | Jun 29, 20:44 UTC | 7h 20m |
| 2026-06-29 | KLM174 | - | Jun 29, 01:50 UTC | Jun 29, 05:30 UTC | 3h 40m |
| 2026-06-28 | KLM565 | - | Jun 28, 11:04 UTC | Jun 28, 14:50 UTC | 3h 45m |
| 2026-06-26 | KLM280 | - | Jun 26, 10:35 UTC | Jun 27, 05:15 UTC | 18h 40m |
| 2026-06-26 | KLM280 | - | Jun 26, 08:40 UTC | Jun 27, 05:15 UTC | 20h 35m |
| 2026-06-25 | KLM250 | MSP → AMS | Jun 25, 20:25 UTC | Jun 26, 04:00 UTC | 7h 35m |
| 2026-06-25 | KLM655 | - | Jun 25, 09:14 UTC | Jun 25, 17:20 UTC | 8h 5m |
| 2026-06-25 | KLM646 | JFK → AMS | Jun 25, 00:35 UTC | Jun 25, 06:44 UTC | 6h 10m |
| 2026-06-24 | KLM207 | AMS → JFK | Jun 24, 13:50 UTC | Jun 24, 21:14 UTC | 7h 25m |
| 2026-06-23 | KLM642 | JFK → AMS | Jun 23, 21:05 UTC | Jun 24, 03:35 UTC | 6h 30m |
| 2026-06-23 | KLM641 | AMS → JFK | Jun 23, 10:59 UTC | Jun 23, 18:25 UTC | 7h 25m |
| 2026-06-23 | KLM644 | JFK → AMS | Jun 23, 01:54 UTC | Jun 23, 08:09 UTC | 6h 15m |
| 2026-06-22 | KLM643 | - | Jun 22, 15:54 UTC | Jun 22, 23:20 UTC | 7h 25m |
| 2026-06-22 | KLM686 | - | Jun 22, 02:59 UTC | Jun 22, 12:44 UTC | 9h 45m |
| 2026-06-21 | KLM685 | - | Jun 21, 12:49 UTC | Jun 21, 23:50 UTC | 11h 0m |
| 2026-06-20 | KLM166 | AUS → AMS | Jun 20, 23:34 UTC | Jun 21, 08:30 UTC | 8h 55m |
| 2026-06-20 | KLM115 | AMS → AUS | Jun 20, 11:05 UTC | Jun 20, 20:55 UTC | 9h 50m |
| 2026-06-19 | KLM874 | - | Jun 19, 10:35 UTC | Jun 20, 06:19 UTC | 19h 45m |
| 2026-06-19 | KLM874 | AMS → AMS | Jun 19, 10:19 UTC | Jun 20, 06:19 UTC | 20h 0m |
| 2026-06-17 | KLM250 | - | Jun 17, 20:55 UTC | Jun 18, 04:20 UTC | 7h 25m |
| 2026-06-17 | KLM655 | AMS → MSP | Jun 17, 09:15 UTC | Jun 17, 17:15 UTC | 8h 0m |
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-BQO page for operator, model, and routing details .