sensors Mode-S transponder
48088C
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to Q-43 · MCDONNELL DOUGLAS AH-64 Apache
- Hex
- 48088C
- Octal
- 22004214
- Decimal
- 4,720,780
- Country
- NL
- Tail
- Q-43
- Type
- H64
- Flights observed
- 49
- Distinct callsigns
- 11
- Country
- NL
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address 48088C 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 11 distinct
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-03 | NAF301A | - | Jul 3, 11:30 UTC | Jul 3, 12:45 UTC | 1h 15m |
| 2026-07-03 | NAF301A | - | Jul 3, 07:55 UTC | Jul 3, 09:55 UTC | 2h 0m |
| 2026-07-01 | APACHE2 | - | Jul 1, 17:35 UTC | Jul 1, 18:10 UTC | 35m |
| 2026-07-01 | APACHE2 | - | Jul 1, 15:55 UTC | Jul 1, 16:05 UTC | 10m |
| 2026-06-25 | APACHE3 | - | Jun 25, 17:05 UTC | Jun 25, 17:14 UTC | 10m |
| 2026-06-25 | APACHE2 | - | Jun 25, 14:09 UTC | Jun 25, 14:39 UTC | 30m |
| 2026-06-22 | APACHE2 | - | Jun 22, 17:00 UTC | Jun 22, 17:04 UTC | 5m |
| 2026-06-22 | APACHE2 | - | Jun 22, 14:45 UTC | Jun 22, 15:05 UTC | 20m |
| 2026-06-19 | APACHE4 | - | Jun 19, 10:19 UTC | Jun 19, 10:29 UTC | 10m |
| 2026-06-18 | APACHE2 | - | Jun 18, 15:05 UTC | Jun 18, 15:25 UTC | 20m |
| 2026-06-18 | APACHE2 | - | Jun 18, 13:00 UTC | Jun 18, 13:05 UTC | 5m |
| 2026-06-17 | APACHE2 | - | Jun 17, 14:55 UTC | Jun 17, 15:05 UTC | 10m |
| 2026-06-16 | APACHE2 | - | Jun 16, 23:00 UTC | Jun 16, 23:10 UTC | 10m |
| 2026-06-16 | APACHE2 | - | Jun 16, 20:40 UTC | Jun 16, 21:00 UTC | 20m |
| 2026-06-16 | APACHE2 | - | Jun 16, 17:24 UTC | Jun 16, 19:10 UTC | 1h 45m |
| 2026-06-10 | APACHE5 | - | Jun 10, 12:35 UTC | Jun 10, 12:50 UTC | 15m |
| 2026-06-10 | APACHE5 | GLZ → GLZ | Jun 10, 11:35 UTC | Jun 10, 11:55 UTC | 20m |
| 2026-06-09 | APACHE6 | GLZ → GLZ | Jun 9, 13:45 UTC | Jun 9, 14:15 UTC | 30m |
| 2026-06-09 | APACHE6 | GLZ → GLZ | Jun 9, 13:00 UTC | Jun 9, 13:15 UTC | 15m |
| 2026-06-01 | APCHE1 | GLZ → GLZ | Jun 1, 08:40 UTC | Jun 1, 11:30 UTC | 2h 50m |
| 2026-06-01 | APCHE1 | GLZ → GLZ | Jun 1, 07:05 UTC | Jun 1, 08:35 UTC | 1h 30m |
| 2026-05-28 | BAT04 | GLZ → GLZ | May 28, 09:00 UTC | May 28, 10:30 UTC | 1h 30m |
| 2026-05-28 | BAT04 | GLZ → GLZ | May 28, 08:40 UTC | May 28, 08:55 UTC | 15m |
| 2026-05-21 | APACHE1 | GLZ → GLZ | May 21, 10:25 UTC | May 21, 11:10 UTC | 45m |
| 2026-05-21 | APACHE1 | GLZ → GLZ | May 21, 10:05 UTC | May 21, 10:20 UTC | 15m |
| 2026-05-21 | BAT1 | GLZ → GLZ | May 21, 08:10 UTC | May 21, 09:35 UTC | 1h 25m |
| 2026-05-04 | APACHE3 | - | May 4, 15:10 UTC | May 4, 15:45 UTC | 35m |
| 2026-05-04 | APACHE3 | - | May 4, 12:40 UTC | May 4, 12:55 UTC | 15m |
| 2026-05-03 | APACHE2 | - | May 3, 08:25 UTC | May 3, 09:15 UTC | 50m |
| 2026-05-03 | APACHE2 | - | May 3, 07:20 UTC | May 3, 07:50 UTC | 30m |
| 2026-05-02 | APACHE1 | - | May 2, 13:30 UTC | May 2, 13:55 UTC | 25m |
| 2026-05-01 | APACHE3 | - | May 1, 06:35 UTC | May 1, 07:05 UTC | 30m |
| 2026-04-30 | APACHE3 | - | Apr 30, 10:40 UTC | Apr 30, 11:10 UTC | 30m |
| 2026-04-29 | APACHE1 | - | Apr 29, 10:35 UTC | Apr 29, 11:05 UTC | 30m |
| 2026-04-29 | APACHE1 | - | Apr 29, 08:20 UTC | Apr 29, 08:45 UTC | 25m |
| 2026-04-29 | APACHE1 | - | Apr 29, 06:29 UTC | Apr 29, 07:45 UTC | 1h 15m |
| 2026-04-28 | APACHE2 | - | Apr 28, 12:45 UTC | Apr 28, 12:55 UTC | 10m |
| 2026-04-28 | APACHE2 | - | Apr 28, 09:40 UTC | Apr 28, 09:55 UTC | 15m |
| 2026-04-28 | APACHE2 | - | Apr 28, 06:45 UTC | Apr 28, 07:15 UTC | 30m |
| 2026-04-24 | APACHE1 | - | Apr 24, 12:10 UTC | Apr 24, 12:45 UTC | 35m |
| 2026-04-24 | APACHE1 | - | Apr 24, 10:40 UTC | Apr 24, 11:15 UTC | 35m |
| 2026-04-24 | APACHE1 | - | Apr 24, 08:35 UTC | Apr 24, 09:05 UTC | 30m |
| 2026-04-24 | APACHE1 | - | Apr 24, 07:05 UTC | Apr 24, 07:35 UTC | 30m |
| 2026-04-23 | NAF301C | - | Apr 23, 07:45 UTC | Apr 23, 08:45 UTC | 1h 0m |
| 2026-04-13 | APACHE2 | GLZ → GLZ | Apr 13, 12:35 UTC | Apr 13, 14:25 UTC | 1h 50m |
| 2026-04-13 | APACHE3 | - | Apr 13, 10:45 UTC | Apr 13, 12:00 UTC | 1h 15m |
| 2026-04-13 | APACHE1 | - | Apr 13, 09:00 UTC | Apr 13, 10:10 UTC | 1h 10m |
| 2026-04-13 | APACHE1 | - | Apr 13, 07:55 UTC | Apr 13, 08:15 UTC | 20m |
| 2026-04-13 | APACHE1 | - | Apr 13, 07:35 UTC | Apr 13, 08:15 UTC | 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 Q-43 page for operator, model, and routing details .