sensors Mode-S transponder
484498
ICAO 24-bit transponder address · allocated to Netherlands
- Hex
- 484498
- Octal
- 22042230
- Decimal
- 4,736,152
- Country
- NL
- Flights observed
- 47
- Distinct callsigns
- 1
- Country
- NL
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 484498 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| P4GL5T | - | 47 | 2026-06-25 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-25 | P4GL5T | - | Jun 25, 18:45 UTC | Jun 25, 21:29 UTC | 2h 45m |
| 2026-06-25 | P4GL5T | - | Jun 25, 09:34 UTC | Jun 25, 16:45 UTC | 7h 10m |
| 2026-06-24 | P4GL5T | - | Jun 24, 14:04 UTC | Jun 24, 18:44 UTC | 4h 40m |
| 2026-06-23 | P4GL5T | - | Jun 23, 22:05 UTC | Jun 24, 18:44 UTC | 20h 40m |
| 2026-06-23 | P4GL5T | - | Jun 23, 20:04 UTC | Jun 24, 18:44 UTC | 22h 40m |
| 2026-06-23 | P4GL5T | - | Jun 23, 19:44 UTC | Jun 24, 14:29 UTC | 18h 45m |
| 2026-06-21 | P4GL5T | - | Jun 21, 10:19 UTC | Jun 21, 12:49 UTC | 2h 30m |
| 2026-06-20 | P4GL5T | - | Jun 20, 18:14 UTC | Jun 20, 20:25 UTC | 2h 10m |
| 2026-06-19 | P4GL5T | OPO → CAT | Jun 19, 09:19 UTC | Jun 19, 10:04 UTC | 45m |
| 2026-06-19 | P4GL5T | - | Jun 19, 00:29 UTC | Jun 19, 07:45 UTC | 7h 15m |
| 2026-06-17 | P4GL5T | - | Jun 17, 01:35 UTC | Jun 17, 14:45 UTC | 13h 10m |
| 2026-06-15 | P4GL5T | - | Jun 15, 20:30 UTC | Jun 15, 20:40 UTC | 10m |
| 2026-06-14 | P4GL5T | - | Jun 14, 20:35 UTC | Jun 15, 03:55 UTC | 7h 20m |
| 2026-06-13 | P4GL5T | - | Jun 13, 18:10 UTC | Jun 14, 02:40 UTC | 8h 30m |
| 2026-06-12 | P4GL5T | - | Jun 12, 19:15 UTC | Jun 13, 02:25 UTC | 7h 10m |
| 2026-06-06 | P4GL5T | - | Jun 6, 22:34 UTC | Jun 7, 05:55 UTC | 7h 20m |
| 2026-06-05 | P4GL5T | - | Jun 5, 01:55 UTC | Jun 5, 04:10 UTC | 2h 15m |
| 2026-06-04 | P4GL5T | - | Jun 4, 20:35 UTC | Jun 5, 00:40 UTC | 4h 5m |
| 2026-06-03 | P4GL5T | - | Jun 3, 10:00 UTC | Jun 3, 19:55 UTC | 9h 55m |
| 2026-06-02 | P4GL5T | - | Jun 2, 20:55 UTC | Jun 3, 03:45 UTC | 6h 50m |
| 2026-05-31 | P4GL5T | - | May 31, 22:15 UTC | Jun 1, 06:40 UTC | 8h 25m |
| 2026-05-31 | P4GL5T | - | May 31, 21:25 UTC | May 31, 21:40 UTC | 15m |
| 2026-05-31 | P4GL5T | - | May 31, 11:20 UTC | May 31, 18:55 UTC | 7h 35m |
| 2026-05-31 | P4GL5T | - | May 31, 09:35 UTC | May 31, 10:20 UTC | 45m |
| 2026-05-29 | P4GL5T | - | May 29, 12:55 UTC | May 29, 16:30 UTC | 3h 35m |
| 2026-05-29 | P4GL5T | - | May 29, 02:25 UTC | May 29, 11:40 UTC | 9h 15m |
| 2026-05-28 | P4GL5T | - | May 28, 01:10 UTC | May 28, 02:00 UTC | 50m |
| 2026-05-27 | P4GL5T | - | May 27, 18:00 UTC | May 27, 18:35 UTC | 35m |
| 2026-05-25 | P4GL5T | - | May 25, 16:40 UTC | May 26, 03:00 UTC | 10h 20m |
| 2026-05-24 | P4GL5T | - | May 24, 19:15 UTC | May 24, 21:40 UTC | 2h 25m |
| 2026-05-23 | P4GL5T | - | May 23, 14:45 UTC | May 23, 19:55 UTC | 5h 10m |
| 2026-05-20 | P4GL5T | - | May 20, 17:25 UTC | May 21, 04:15 UTC | 10h 50m |
| 2026-05-19 | P4GL5T | - | May 19, 00:30 UTC | May 19, 01:20 UTC | 50m |
| 2026-05-18 | P4GL5T | - | May 18, 11:15 UTC | May 18, 11:30 UTC | 15m |
| 2026-05-18 | P4GL5T | - | May 18, 07:45 UTC | May 18, 10:15 UTC | 2h 30m |
| 2026-05-17 | P4GL5T | - | May 17, 09:10 UTC | May 17, 16:05 UTC | 6h 55m |
| 2026-05-17 | P4GL5T | - | May 17, 00:05 UTC | May 17, 07:10 UTC | 7h 5m |
| 2026-05-15 | P4GL5T | - | May 15, 11:45 UTC | May 15, 19:45 UTC | 7h 59m |
| 2026-05-15 | P4GL5T | - | May 15, 08:15 UTC | May 15, 09:20 UTC | 1h 5m |
| 2026-05-14 | P4GL5T | - | May 14, 12:10 UTC | May 14, 20:10 UTC | 8h 0m |
| 2026-05-13 | P4GL5T | BQH → LAD | May 13, 20:20 UTC | May 14, 04:10 UTC | 7h 50m |
| 2026-05-12 | P4GL5T | - | May 12, 10:05 UTC | May 12, 18:20 UTC | 8h 15m |
| 2026-05-11 | P4GL5T | - | May 11, 19:15 UTC | May 11, 20:00 UTC | 45m |
| 2026-05-05 | P4GL5T | - | May 5, 15:15 UTC | May 5, 23:55 UTC | 8h 40m |
| 2026-05-04 | P4GL5T | - | May 4, 15:20 UTC | May 4, 22:40 UTC | 7h 21m |
| 2026-05-03 | P4GL5T | LIS → LAD | May 3, 11:30 UTC | May 3, 18:30 UTC | 7h 0m |
| 2026-05-03 | P4GL5T | BOH → LIS | May 3, 07:45 UTC | May 3, 09:40 UTC | 1h 55m |
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.