sensors Mode-S transponder
486398
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-TAX · DIAMOND DA-50 Magnum
- Hex
- 486398
- Octal
- 22061630
- Decimal
- 4,744,088
- Country
- NL
- Tail
- PH-TAX
- Type
- DA50
- Flights observed
- 87
- Distinct callsigns
- 1
- Country
- NL
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 486398 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 |
|---|---|---|---|
| PHTAX | - | 87 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | PHTAX | - | Jul 17, 07:44 UTC | Jul 17, 09:10 UTC | 1h 25m |
| 2026-07-16 | PHTAX | - | Jul 16, 12:14 UTC | Jul 16, 14:05 UTC | 1h 50m |
| 2026-07-16 | PHTAX | - | Jul 16, 09:30 UTC | Jul 16, 10:55 UTC | 1h 25m |
| 2026-07-13 | PHTAX | - | Jul 13, 11:40 UTC | Jul 13, 13:25 UTC | 1h 45m |
| 2026-07-13 | PHTAX | - | Jul 13, 08:45 UTC | Jul 13, 10:25 UTC | 1h 40m |
| 2026-07-10 | PHTAX | - | Jul 10, 13:35 UTC | Jul 10, 14:25 UTC | 50m |
| 2026-07-09 | PHTAX | - | Jul 9, 13:10 UTC | Jul 9, 13:50 UTC | 40m |
| 2026-07-09 | PHTAX | - | Jul 9, 11:20 UTC | Jul 9, 12:00 UTC | 40m |
| 2026-07-08 | PHTAX | - | Jul 8, 13:50 UTC | Jul 8, 14:50 UTC | 1h 0m |
| 2026-07-08 | PHTAX | - | Jul 8, 11:45 UTC | Jul 8, 12:25 UTC | 40m |
| 2026-07-07 | PHTAX | - | Jul 7, 17:20 UTC | Jul 7, 18:55 UTC | 1h 35m |
| 2026-07-04 | PHTAX | - | Jul 4, 11:50 UTC | Jul 4, 12:20 UTC | 30m |
| 2026-07-04 | PHTAX | - | Jul 4, 09:30 UTC | Jul 4, 09:50 UTC | 20m |
| 2026-07-02 | PHTAX | - | Jul 2, 16:55 UTC | Jul 2, 18:40 UTC | 1h 45m |
| 2026-07-02 | PHTAX | - | Jul 2, 14:10 UTC | Jul 2, 16:15 UTC | 2h 5m |
| 2026-07-02 | PHTAX | - | Jul 2, 10:20 UTC | Jul 2, 13:00 UTC | 2h 40m |
| 2026-06-30 | PHTAX | LEY → LEY | Jun 30, 09:05 UTC | Jun 30, 10:55 UTC | 1h 50m |
| 2026-06-29 | PHTAX | - | Jun 29, 14:29 UTC | Jun 29, 15:09 UTC | 40m |
| 2026-06-29 | PHTAX | - | Jun 29, 06:34 UTC | Jun 29, 08:09 UTC | 1h 35m |
| 2026-06-24 | PHTAX | - | Jun 24, 12:20 UTC | Jun 24, 13:14 UTC | 55m |
| 2026-06-24 | PHTAX | - | Jun 24, 09:55 UTC | Jun 24, 10:49 UTC | 55m |
| 2026-06-21 | PHTAX | - | Jun 21, 17:15 UTC | Jun 21, 17:35 UTC | 20m |
| 2026-06-21 | PHTAX | - | Jun 21, 09:29 UTC | Jun 21, 10:14 UTC | 45m |
| 2026-06-20 | PHTAX | - | Jun 20, 13:34 UTC | Jun 20, 14:19 UTC | 45m |
| 2026-06-20 | PHTAX | - | Jun 20, 09:59 UTC | Jun 20, 10:34 UTC | 35m |
| 2026-06-19 | PHTAX | - | Jun 19, 18:39 UTC | Jun 19, 19:04 UTC | 25m |
| 2026-06-19 | PHTAX | - | Jun 19, 15:49 UTC | Jun 19, 17:14 UTC | 1h 25m |
| 2026-06-18 | PHTAX | - | Jun 18, 15:10 UTC | Jun 18, 17:21 UTC | 2h 11m |
| 2026-06-18 | PHTAX | - | Jun 18, 12:25 UTC | Jun 18, 13:45 UTC | 1h 20m |
| 2026-06-18 | PHTAX | - | Jun 18, 07:35 UTC | Jun 18, 09:35 UTC | 2h 0m |
| 2026-06-17 | PHTAX | - | Jun 17, 15:35 UTC | Jun 17, 17:45 UTC | 2h 10m |
| 2026-06-16 | PHTAX | - | Jun 16, 12:39 UTC | Jun 16, 16:55 UTC | 4h 15m |
| 2026-06-15 | PHTAX | - | Jun 15, 08:49 UTC | Jun 15, 09:35 UTC | 45m |
| 2026-06-14 | PHTAX | - | Jun 14, 11:05 UTC | Jun 14, 12:25 UTC | 1h 20m |
| 2026-06-11 | PHTAX | - | Jun 11, 10:55 UTC | Jun 11, 11:55 UTC | 1h 0m |
| 2026-06-09 | PHTAX | - | Jun 9, 08:05 UTC | Jun 9, 08:35 UTC | 30m |
| 2026-06-08 | PHTAX | - | Jun 8, 08:30 UTC | Jun 8, 10:10 UTC | 1h 40m |
| 2026-06-07 | PHTAX | - | Jun 7, 08:00 UTC | Jun 7, 08:45 UTC | 45m |
| 2026-06-06 | PHTAX | - | Jun 6, 08:35 UTC | Jun 6, 09:50 UTC | 1h 15m |
| 2026-06-05 | PHTAX | - | Jun 5, 09:35 UTC | Jun 5, 12:25 UTC | 2h 50m |
| 2026-05-31 | PHTAX | ENS → LEY | May 31, 09:10 UTC | May 31, 09:40 UTC | 30m |
| 2026-05-29 | PHTAX | LEY → ENS | May 29, 08:15 UTC | May 29, 08:45 UTC | 30m |
| 2026-05-27 | PHTAX | - | May 27, 16:10 UTC | May 27, 17:55 UTC | 1h 45m |
| 2026-05-26 | PHTAX | - | May 26, 09:59 UTC | May 26, 11:09 UTC | 1h 10m |
| 2026-05-26 | PHTAX | - | May 26, 08:10 UTC | May 26, 08:54 UTC | 45m |
| 2026-05-25 | PHTAX | - | May 25, 08:05 UTC | May 25, 10:35 UTC | 2h 30m |
| 2026-05-24 | PHTAX | - | May 24, 13:15 UTC | May 24, 13:40 UTC | 25m |
| 2026-05-24 | PHTAX | - | May 24, 11:20 UTC | May 24, 12:10 UTC | 50m |
| 2026-05-24 | PHTAX | - | May 24, 09:15 UTC | May 24, 09:50 UTC | 35m |
| 2026-05-23 | PHTAX | - | May 23, 10:30 UTC | May 23, 12:50 UTC | 2h 20m |
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-TAX page for operator, model, and routing details .