sensors Mode-S transponder
484368
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-BQA · BOEING 777-200
- Hex
- 484368
- Octal
- 22041550
- Decimal
- 4,735,848
- Country
- NL
- Tail
- PH-BQA
- Type
- B772
- Flights observed
- 160
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 484368 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 | - | 23 | 2026-07-11 |
| KLM701 | - | 21 | 2026-07-11 |
| KLM686 | - | 12 | 2026-07-05 |
| KLM685 | - | 9 | 2026-07-04 |
| KLM595 | KLM Royal Dutch Airlines | 7 | 2026-05-11 |
| KLM862 | KLM Royal Dutch Airlines | 6 | 2026-05-27 |
| KLM596 | KLM Royal Dutch Airlines | 6 | 2026-05-11 |
| KLM636 | - | 5 | 2026-07-13 |
| KLM861 | KLM Royal Dutch Airlines | 4 | 2026-05-26 |
| KLM635 | - | 4 | 2026-07-12 |
| KLM661 | KLM Royal Dutch Airlines | 3 | 2026-06-09 |
| KLM268 | - | 3 | 2026-06-25 |
| KLM105 | KLM Royal Dutch Airlines | 3 | 2026-06-26 |
| KLM896 | KLM Royal Dutch Airlines | 2 | 2026-05-15 |
| KLM895 | KLM Royal Dutch Airlines | 2 | 2026-05-14 |
| KLM888 | - | 2 | 2026-06-23 |
| KLM878 | KLM Royal Dutch Airlines | 2 | 2026-04-20 |
| KLM856 | - | 2 | 2026-07-02 |
| KLM855 | - | 2 | 2026-07-02 |
| KLM844 | - | 2 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | KLM248 | ATL → AMS | Jul 14, 03:00 UTC | Jul 14, 11:05 UTC | 8h 5m |
| 2026-07-13 | KLM133 | - | Jul 13, 15:50 UTC | Jul 14, 00:10 UTC | 8h 20m |
| 2026-07-13 | KLM636 | LAS → AMS | Jul 13, 03:50 UTC | Jul 13, 13:25 UTC | 9h 35m |
| 2026-07-12 | KLM635 | - | Jul 12, 15:10 UTC | Jul 13, 01:25 UTC | 10h 15m |
| 2026-07-11 | KLM702 | EZE → AMS | Jul 11, 18:00 UTC | Jul 12, 06:40 UTC | 12h 40m |
| 2026-07-11 | KLM702 | - | Jul 11, 15:05 UTC | Jul 11, 15:40 UTC | 35m |
| 2026-07-11 | KLM702 | - | Jul 11, 14:10 UTC | Jul 11, 14:20 UTC | 10m |
| 2026-07-11 | KLM701 | - | Jul 11, 10:30 UTC | Jul 11, 11:00 UTC | 30m |
| 2026-07-10 | KLM701 | - | Jul 10, 19:35 UTC | Jul 11, 08:45 UTC | 13h 10m |
| 2026-07-08 | KLM702 | EZE → AMS | Jul 8, 18:20 UTC | Jul 9, 07:05 UTC | 12h 45m |
| 2026-07-08 | KLM702 | - | Jul 8, 15:25 UTC | Jul 8, 16:00 UTC | 35m |
| 2026-07-08 | KLM702 | - | Jul 8, 14:30 UTC | Jul 8, 14:40 UTC | 10m |
| 2026-07-08 | KLM701 | - | Jul 8, 10:45 UTC | Jul 8, 11:10 UTC | 25m |
| 2026-07-07 | KLM701 | - | Jul 7, 19:35 UTC | Jul 8, 08:50 UTC | 13h 15m |
| 2026-07-07 | KLM844 | - | Jul 7, 05:10 UTC | Jul 7, 17:05 UTC | 11h 55m |
| 2026-07-06 | KLM843 | AMS → BKK | Jul 6, 15:30 UTC | Jul 7, 02:05 UTC | 10h 35m |
| 2026-07-06 | KLM610 | - | Jul 6, 04:15 UTC | Jul 6, 13:00 UTC | 8h 45m |
| 2026-07-05 | KLM609 | - | Jul 5, 15:50 UTC | Jul 6, 01:30 UTC | 9h 40m |
| 2026-07-05 | KLM686 | - | Jul 5, 02:35 UTC | Jul 5, 12:35 UTC | 10h 0m |
| 2026-07-04 | KLM685 | - | Jul 4, 12:55 UTC | Jul 4, 23:50 UTC | 10h 55m |
| 2026-07-03 | KLM567 | - | Jul 3, 10:05 UTC | Jul 4, 05:25 UTC | 19h 20m |
| 2026-07-03 | KLM567 | - | Jul 3, 08:30 UTC | Jul 4, 05:25 UTC | 20h 55m |
| 2026-07-02 | KLM856 | - | Jul 2, 15:00 UTC | Jul 3, 02:40 UTC | 11h 40m |
| 2026-07-02 | KLM856 | - | Jul 2, 13:45 UTC | Jul 2, 14:05 UTC | 20m |
| 2026-07-02 | KLM855 | - | Jul 2, 06:55 UTC | Jul 2, 07:15 UTC | 20m |
| 2026-07-01 | KLM855 | - | Jul 1, 19:55 UTC | Jul 2, 00:00 UTC | 4h 5m |
| 2026-07-01 | KLM636 | LAS → AMS | Jul 1, 03:40 UTC | Jul 1, 12:50 UTC | 9h 10m |
| 2026-06-30 | KLM635 | - | Jun 30, 15:10 UTC | Jul 1, 01:20 UTC | 10h 10m |
| 2026-06-30 | KLM610 | - | Jun 30, 04:15 UTC | Jun 30, 12:50 UTC | 8h 35m |
| 2026-06-29 | KLM609 | - | Jun 29, 16:44 UTC | Jun 30, 01:50 UTC | 9h 6m |
| 2026-06-29 | KLM686 | - | Jun 29, 03:05 UTC | Jun 29, 12:55 UTC | 9h 50m |
| 2026-06-28 | KLM685 | AMS → MEX | Jun 28, 12:44 UTC | Jun 28, 23:34 UTC | 10h 50m |
| 2026-06-27 | KLM163 | - | Jun 27, 12:09 UTC | Jun 28, 07:44 UTC | 19h 35m |
| 2026-06-26 | KLM104 | CPT → AMS | Jun 26, 21:10 UTC | Jun 27, 08:35 UTC | 11h 25m |
| 2026-06-26 | KLM105 | - | Jun 26, 18:54 UTC | Jun 26, 19:14 UTC | 20m |
| 2026-06-26 | KLM105 | - | Jun 26, 08:34 UTC | Jun 26, 10:30 UTC | 1h 55m |
| 2026-06-25 | KLM268 | - | Jun 25, 08:04 UTC | Jun 26, 03:29 UTC | 19h 25m |
| 2026-06-25 | KLM268 | - | Jun 25, 07:30 UTC | Jun 26, 03:29 UTC | 20h 0m |
| 2026-06-23 | KLM888 | - | Jun 23, 22:40 UTC | Jun 24, 03:15 UTC | 4h 35m |
| 2026-06-23 | KLM888 | - | Jun 23, 14:29 UTC | Jun 23, 14:44 UTC | 15m |
| 2026-06-22 | KLM887 | - | Jun 22, 21:40 UTC | Jun 23, 08:54 UTC | 11h 15m |
| 2026-06-19 | KLM702 | - | Jun 19, 18:09 UTC | Jun 20, 07:00 UTC | 12h 50m |
| 2026-06-19 | KLM702 | - | Jun 19, 15:29 UTC | Jun 19, 15:59 UTC | 30m |
| 2026-06-19 | KLM702 | - | Jun 19, 14:24 UTC | Jun 19, 14:34 UTC | 10m |
| 2026-06-19 | KLM701 | - | Jun 19, 10:35 UTC | Jun 19, 10:59 UTC | 25m |
| 2026-06-18 | KLM701 | - | Jun 18, 19:35 UTC | Jun 19, 08:44 UTC | 13h 9m |
| 2026-06-18 | KLM636 | LAS → AMS | Jun 18, 03:45 UTC | Jun 18, 13:25 UTC | 9h 40m |
| 2026-06-17 | KLM635 | AMS → LAS | Jun 17, 15:25 UTC | Jun 18, 01:40 UTC | 10h 15m |
| 2026-06-17 | KLM686 | - | Jun 17, 02:25 UTC | Jun 17, 12:25 UTC | 10h 0m |
| 2026-06-16 | KLM685 | - | Jun 16, 12:45 UTC | Jun 16, 23:45 UTC | 11h 1m |
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-BQA page for operator, model, and routing details .