sensors Mode-S transponder
486044
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-4U3 · TECNAM P-92 Echo
- Hex
- 486044
- Octal
- 22060104
- Decimal
- 4,743,236
- Country
- NL
- Tail
- PH-4U3
- Type
- ECHO
- Flights observed
- 58
- Distinct callsigns
- 1
- Country
- NL
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 486044 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 |
|---|---|---|---|
| PH4U3 | - | 58 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | PH4U3 | - | Jul 17, 17:50 UTC | Jul 17, 18:25 UTC | 35m |
| 2026-07-15 | PH4U3 | - | Jul 15, 11:10 UTC | Jul 15, 11:40 UTC | 30m |
| 2026-07-15 | PH4U3 | - | Jul 15, 08:15 UTC | Jul 15, 09:00 UTC | 45m |
| 2026-07-13 | PH4U3 | - | Jul 13, 18:00 UTC | Jul 13, 18:25 UTC | 25m |
| 2026-07-13 | PH4U3 | - | Jul 13, 16:20 UTC | Jul 13, 16:50 UTC | 30m |
| 2026-07-13 | PH4U3 | - | Jul 13, 07:50 UTC | Jul 13, 08:35 UTC | 45m |
| 2026-07-11 | PH4U3 | - | Jul 11, 14:35 UTC | Jul 11, 15:30 UTC | 55m |
| 2026-07-11 | PH4U3 | - | Jul 11, 12:45 UTC | Jul 11, 13:35 UTC | 50m |
| 2026-07-11 | PH4U3 | - | Jul 11, 10:35 UTC | Jul 11, 12:00 UTC | 1h 25m |
| 2026-07-10 | PH4U3 | - | Jul 10, 18:10 UTC | Jul 10, 18:45 UTC | 35m |
| 2026-07-10 | PH4U3 | - | Jul 10, 09:25 UTC | Jul 10, 09:55 UTC | 30m |
| 2026-07-09 | PH4U3 | - | Jul 9, 17:20 UTC | Jul 9, 17:50 UTC | 30m |
| 2026-07-03 | PH4U3 | - | Jul 3, 12:00 UTC | Jul 3, 12:35 UTC | 35m |
| 2026-07-03 | PH4U3 | - | Jul 3, 09:05 UTC | Jul 3, 09:40 UTC | 35m |
| 2026-07-03 | PH4U3 | - | Jul 3, 08:00 UTC | Jul 3, 08:30 UTC | 30m |
| 2026-07-01 | PH4U3 | - | Jul 1, 13:25 UTC | Jul 1, 14:00 UTC | 35m |
| 2026-07-01 | PH4U3 | - | Jul 1, 11:20 UTC | Jul 1, 12:50 UTC | 1h 30m |
| 2026-06-28 | PH4U3 | - | Jun 28, 09:10 UTC | Jun 28, 10:04 UTC | 55m |
| 2026-06-28 | PH4U3 | - | Jun 28, 08:00 UTC | Jun 28, 08:19 UTC | 20m |
| 2026-06-21 | PH4U3 | - | Jun 21, 15:25 UTC | Jun 21, 15:54 UTC | 30m |
| 2026-06-21 | PH4U3 | - | Jun 21, 13:15 UTC | Jun 21, 13:50 UTC | 35m |
| 2026-06-21 | PH4U3 | - | Jun 21, 07:45 UTC | Jun 21, 08:40 UTC | 55m |
| 2026-06-20 | PH4U3 | - | Jun 20, 11:05 UTC | Jun 20, 11:49 UTC | 45m |
| 2026-06-20 | PH4U3 | - | Jun 20, 08:44 UTC | Jun 20, 09:19 UTC | 35m |
| 2026-06-18 | PH4U3 | - | Jun 18, 17:45 UTC | Jun 18, 18:25 UTC | 40m |
| 2026-05-30 | PH4U3 | - | May 30, 18:00 UTC | May 30, 18:35 UTC | 35m |
| 2026-05-30 | PH4U3 | - | May 30, 13:15 UTC | May 30, 14:00 UTC | 45m |
| 2026-05-25 | PH4U3 | - | May 25, 09:50 UTC | May 25, 10:30 UTC | 40m |
| 2026-05-23 | PH4U3 | - | May 23, 14:25 UTC | May 23, 14:55 UTC | 30m |
| 2026-05-23 | PH4U3 | - | May 23, 12:05 UTC | May 23, 12:30 UTC | 25m |
| 2026-05-23 | PH4U3 | - | May 23, 07:50 UTC | May 23, 09:05 UTC | 1h 15m |
| 2026-05-22 | PH4U3 | - | May 22, 14:35 UTC | May 22, 15:20 UTC | 45m |
| 2026-05-22 | PH4U3 | - | May 22, 12:50 UTC | May 22, 13:25 UTC | 35m |
| 2026-05-16 | PH4U3 | - | May 16, 14:46 UTC | May 16, 15:25 UTC | 40m |
| 2026-05-16 | PH4U3 | - | May 16, 07:25 UTC | May 16, 08:01 UTC | 35m |
| 2026-05-10 | PH4U3 | - | May 10, 08:40 UTC | May 10, 10:05 UTC | 1h 25m |
| 2026-05-09 | PH4U3 | - | May 9, 13:55 UTC | May 9, 14:20 UTC | 25m |
| 2026-05-08 | PH4U3 | - | May 8, 17:20 UTC | May 8, 18:35 UTC | 1h 15m |
| 2026-05-02 | PH4U3 | - | May 2, 13:50 UTC | May 2, 15:50 UTC | 2h 0m |
| 2026-05-02 | PH4U3 | - | May 2, 11:50 UTC | May 2, 12:35 UTC | 45m |
| 2026-05-01 | PH4U3 | - | May 1, 18:20 UTC | May 1, 18:45 UTC | 25m |
| 2026-04-25 | PH4U3 | - | Apr 25, 12:45 UTC | Apr 25, 14:25 UTC | 1h 40m |
| 2026-04-25 | PH4U3 | - | Apr 25, 11:40 UTC | Apr 25, 11:55 UTC | 15m |
| 2026-04-25 | PH4U3 | - | Apr 25, 10:25 UTC | Apr 25, 10:40 UTC | 15m |
| 2026-04-22 | PH4U3 | - | Apr 22, 16:10 UTC | Apr 22, 17:00 UTC | 50m |
| 2026-04-22 | PH4U3 | - | Apr 22, 12:30 UTC | Apr 22, 13:35 UTC | 1h 5m |
| 2026-04-19 | PH4U3 | - | Apr 19, 11:05 UTC | Apr 19, 11:45 UTC | 40m |
| 2026-04-19 | PH4U3 | - | Apr 19, 09:00 UTC | Apr 19, 09:20 UTC | 20m |
| 2026-04-19 | PH4U3 | - | Apr 19, 08:10 UTC | Apr 19, 08:25 UTC | 15m |
| 2026-04-18 | PH4U3 | - | Apr 18, 11:05 UTC | Apr 18, 11:30 UTC | 25m |
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-4U3 page for operator, model, and routing details .