sensors Mode-S transponder
484370
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-BQI · BOEING 777-200
- Hex
- 484370
- Octal
- 22041560
- Decimal
- 4,735,856
- Country
- NL
- Tail
- PH-BQI
- Type
- B772
- Flights observed
- 176
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 484370 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 |
|---|---|---|---|
| KLM268 | - | 11 | 2026-06-22 |
| KLM896 | - | 8 | 2026-06-12 |
| KLM760 | - | 8 | 2026-06-23 |
| KLM807 | - | 7 | 2026-07-05 |
| KLM895 | KLM Royal Dutch Airlines | 6 | 2026-06-11 |
| KLM808 | - | 6 | 2026-07-05 |
| KLM702 | - | 6 | 2026-07-01 |
| KLM701 | - | 6 | 2026-07-01 |
| KLM195 | - | 6 | 2026-06-16 |
| KLM661 | - | 5 | 2026-06-13 |
| KLM192 | - | 5 | 2026-06-13 |
| KLM115 | KLM Royal Dutch Airlines | 5 | 2026-04-13 |
| KLM877 | - | 4 | 2026-07-10 |
| KLM862 | - | 4 | 2026-06-30 |
| KLM861 | KLM Royal Dutch Airlines | 4 | 2026-06-29 |
| KLM856 | - | 4 | 2026-06-19 |
| KLM855 | - | 4 | 2026-06-19 |
| KLM759 | - | 4 | 2026-06-23 |
| KLM646 | KLM Royal Dutch Airlines | 4 | 2026-06-08 |
| KLM635 | KLM Royal Dutch Airlines | 4 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | KLM565 | AMS → AMS | Jul 12, 10:35 UTC | Jul 13, 05:40 UTC | 19h 5m |
| 2026-07-11 | KLM592 | JNB → AMS | Jul 11, 21:25 UTC | Jul 12, 08:05 UTC | 10h 40m |
| 2026-07-11 | KLM591 | - | Jul 11, 09:20 UTC | Jul 11, 19:20 UTC | 10h 0m |
| 2026-07-10 | KLM878 | - | Jul 10, 20:45 UTC | Jul 11, 05:45 UTC | 9h 0m |
| 2026-07-10 | KLM877 | AMS → BOM | Jul 10, 10:20 UTC | Jul 10, 18:20 UTC | 8h 0m |
| 2026-07-09 | KLM878 | - | Jul 9, 20:55 UTC | Jul 10, 05:50 UTC | 8h 55m |
| 2026-07-09 | KLM877 | AMS → BOM | Jul 9, 10:20 UTC | Jul 9, 18:25 UTC | 8h 5m |
| 2026-07-08 | KLM880 | - | Jul 8, 19:50 UTC | Jul 9, 05:45 UTC | 9h 55m |
| 2026-07-08 | KLM879 | - | Jul 8, 17:05 UTC | Jul 8, 17:35 UTC | 30m |
| 2026-07-08 | KLM879 | - | Jul 8, 08:20 UTC | Jul 8, 15:50 UTC | 7h 30m |
| 2026-07-07 | KLM104 | - | Jul 7, 00:15 UTC | Jul 7, 08:30 UTC | 8h 15m |
| 2026-07-06 | KLM104 | - | Jul 6, 21:20 UTC | Jul 6, 21:35 UTC | 15m |
| 2026-07-06 | KLM105 | - | Jul 6, 19:10 UTC | Jul 6, 19:30 UTC | 20m |
| 2026-07-06 | KLM105 | - | Jul 6, 08:35 UTC | Jul 6, 16:20 UTC | 7h 45m |
| 2026-07-05 | KLM808 | TPE → AMS | Jul 5, 16:20 UTC | Jul 6, 06:10 UTC | 13h 50m |
| 2026-07-05 | KLM808 | - | Jul 5, 12:05 UTC | Jul 5, 13:50 UTC | 1h 45m |
| 2026-07-05 | KLM807 | TPE → MNL | Jul 5, 08:25 UTC | Jul 5, 10:20 UTC | 1h 55m |
| 2026-07-04 | KLM807 | AMS → TPE | Jul 4, 18:35 UTC | Jul 5, 06:45 UTC | 12h 10m |
| 2026-07-04 | KLM610 | - | Jul 4, 04:30 UTC | Jul 4, 12:45 UTC | 8h 15m |
| 2026-07-04 | KLM610 | - | Jul 4, 03:45 UTC | Jul 4, 04:00 UTC | 15m |
| 2026-07-03 | KLM609 | - | Jul 3, 15:50 UTC | Jul 4, 01:25 UTC | 9h 35m |
| 2026-07-03 | KLM686 | - | Jul 3, 02:35 UTC | Jul 3, 12:30 UTC | 9h 55m |
| 2026-07-02 | KLM685 | - | Jul 2, 13:15 UTC | Jul 3, 00:25 UTC | 11h 10m |
| 2026-07-01 | KLM702 | - | Jul 1, 18:05 UTC | Jul 2, 07:00 UTC | 12h 55m |
| 2026-07-01 | KLM701 | COR → EZE | Jul 1, 11:55 UTC | Jul 1, 13:00 UTC | 1h 5m |
| 2026-06-30 | KLM701 | AMS → COR | Jun 30, 19:40 UTC | Jul 1, 10:10 UTC | 14h 30m |
| 2026-06-30 | KLM862 | - | Jun 30, 03:20 UTC | Jun 30, 16:55 UTC | 13h 35m |
| 2026-06-29 | KLM861 | AMS → NRT | Jun 29, 12:14 UTC | Jun 30, 00:49 UTC | 12h 35m |
| 2026-06-28 | KLM188 | - | Jun 28, 12:05 UTC | Jun 29, 07:55 UTC | 19h 50m |
| 2026-06-28 | KLM188 | AMS → AMS | Jun 28, 11:45 UTC | Jun 29, 07:55 UTC | 20h 10m |
| 2026-06-25 | KLM808 | TPE → AMS | Jun 25, 17:39 UTC | Jun 26, 06:39 UTC | 13h 0m |
| 2026-06-25 | KLM808 | - | Jun 25, 13:24 UTC | Jun 25, 15:29 UTC | 2h 5m |
| 2026-06-25 | KLM807 | - | Jun 25, 09:20 UTC | Jun 25, 10:59 UTC | 1h 40m |
| 2026-06-25 | KLM807 | - | Jun 25, 07:09 UTC | Jun 25, 07:45 UTC | 35m |
| 2026-06-24 | KLM807 | - | Jun 24, 19:39 UTC | Jun 25, 06:35 UTC | 10h 55m |
| 2026-06-23 | KLM760 | - | Jun 23, 21:05 UTC | Jun 24, 11:09 UTC | 14h 5m |
| 2026-06-23 | KLM760 | - | Jun 23, 12:05 UTC | Jun 24, 11:09 UTC | 23h 5m |
| 2026-06-23 | KLM759 | - | Jun 23, 11:29 UTC | Jun 24, 09:59 UTC | 22h 30m |
| 2026-06-22 | KLM268 | - | Jun 22, 08:35 UTC | Jun 23, 04:14 UTC | 19h 40m |
| 2026-06-21 | KLM808 | TPE → AMS | Jun 21, 16:10 UTC | Jun 22, 05:44 UTC | 13h 35m |
| 2026-06-21 | KLM808 | - | Jun 21, 12:35 UTC | Jun 21, 14:10 UTC | 1h 35m |
| 2026-06-21 | KLM807 | - | Jun 21, 08:35 UTC | Jun 21, 10:29 UTC | 1h 55m |
| 2026-06-20 | KLM807 | AMS → TPE | Jun 20, 18:45 UTC | Jun 21, 07:04 UTC | 12h 20m |
| 2026-06-19 | KLM856 | - | Jun 19, 14:54 UTC | Jun 20, 02:49 UTC | 11h 55m |
| 2026-06-19 | KLM856 | - | Jun 19, 13:44 UTC | Jun 19, 13:59 UTC | 15m |
| 2026-06-19 | KLM855 | - | Jun 19, 07:09 UTC | Jun 19, 07:29 UTC | 20m |
| 2026-06-18 | KLM855 | - | Jun 18, 20:10 UTC | Jun 18, 22:40 UTC | 2h 30m |
| 2026-06-17 | KLM569 | DAR → AMS | Jun 17, 10:05 UTC | Jun 18, 05:25 UTC | 19h 20m |
| 2026-06-17 | KLM569 | DAR → AMS | Jun 17, 08:45 UTC | Jun 18, 05:25 UTC | 20h 40m |
| 2026-06-16 | KLM195 | - | Jun 16, 07:30 UTC | Jun 17, 03:50 UTC | 20h 21m |
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-BQI page for operator, model, and routing details .