sensors Mode-S transponder
486525
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-EYE · CIRRUS SR-20
- Hex
- 486525
- Octal
- 22062445
- Decimal
- 4,744,485
- Country
- NL
- Tail
- PH-EYE
- Type
- SR20
- Flights observed
- 67
- Distinct callsigns
- 1
- Country
- NL
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 486525 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 |
|---|---|---|---|
| PHEYE | - | 67 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | PHEYE | LEY → RTM | Jul 17, 12:04 UTC | Jul 17, 14:00 UTC | 1h 55m |
| 2026-07-17 | PHEYE | RTM → LEY | Jul 17, 10:40 UTC | Jul 17, 11:15 UTC | 35m |
| 2026-07-16 | PHEYE | - | Jul 16, 17:00 UTC | Jul 16, 17:40 UTC | 40m |
| 2026-07-16 | PHEYE | - | Jul 16, 14:20 UTC | Jul 16, 14:55 UTC | 35m |
| 2026-07-08 | PHEYE | RTM → RTM | Jul 8, 13:25 UTC | Jul 8, 14:05 UTC | 40m |
| 2026-07-06 | PHEYE | RTM → RTM | Jul 6, 14:25 UTC | Jul 6, 15:10 UTC | 45m |
| 2026-07-06 | PHEYE | RTM → RTM | Jul 6, 11:00 UTC | Jul 6, 12:00 UTC | 1h 0m |
| 2026-07-04 | PHEYE | - | Jul 4, 12:00 UTC | Jul 4, 12:50 UTC | 50m |
| 2026-07-04 | PHEYE | - | Jul 4, 08:05 UTC | Jul 4, 08:55 UTC | 50m |
| 2026-06-30 | PHEYE | - | Jun 30, 14:30 UTC | Jun 30, 15:10 UTC | 40m |
| 2026-06-30 | PHEYE | - | Jun 30, 13:20 UTC | Jun 30, 14:15 UTC | 55m |
| 2026-06-30 | PHEYE | - | Jun 30, 11:30 UTC | Jun 30, 12:45 UTC | 1h 15m |
| 2026-06-30 | PHEYE | - | Jun 30, 08:25 UTC | Jun 30, 09:25 UTC | 1h 0m |
| 2026-06-26 | PHEYE | - | Jun 26, 08:45 UTC | Jun 26, 11:30 UTC | 2h 45m |
| 2026-06-23 | PHEYE | RTM → RKE | Jun 23, 08:09 UTC | Jun 23, 10:49 UTC | 2h 40m |
| 2026-06-22 | PHEYE | GRQ → RTM | Jun 22, 15:24 UTC | Jun 22, 16:20 UTC | 55m |
| 2026-06-22 | PHEYE | RTM → GRQ | Jun 22, 07:25 UTC | Jun 22, 08:25 UTC | 1h 0m |
| 2026-06-21 | PHEYE | - | Jun 21, 13:44 UTC | Jun 21, 14:30 UTC | 45m |
| 2026-06-21 | PHEYE | - | Jun 21, 11:55 UTC | Jun 21, 12:35 UTC | 40m |
| 2026-06-21 | PHEYE | RTM → GRQ | Jun 21, 09:29 UTC | Jun 21, 10:44 UTC | 1h 15m |
| 2026-06-20 | PHEYE | - | Jun 20, 09:44 UTC | Jun 20, 10:25 UTC | 40m |
| 2026-06-19 | PHEYE | - | Jun 19, 14:34 UTC | Jun 19, 15:14 UTC | 40m |
| 2026-06-15 | PHEYE | - | Jun 15, 12:30 UTC | Jun 15, 13:34 UTC | 1h 5m |
| 2026-06-15 | PHEYE | - | Jun 15, 09:49 UTC | Jun 15, 11:05 UTC | 1h 15m |
| 2026-06-15 | PHEYE | RTM → RTM | Jun 15, 07:40 UTC | Jun 15, 09:05 UTC | 1h 25m |
| 2026-06-14 | PHEYE | - | Jun 14, 14:00 UTC | Jun 14, 15:10 UTC | 1h 10m |
| 2026-06-14 | PHEYE | - | Jun 14, 08:45 UTC | Jun 14, 09:55 UTC | 1h 10m |
| 2026-06-13 | PHEYE | RTM → RTM | Jun 13, 13:55 UTC | Jun 13, 16:35 UTC | 2h 40m |
| 2026-06-12 | PHEYE | RTM → RTM | Jun 12, 13:30 UTC | Jun 12, 14:40 UTC | 1h 10m |
| 2026-06-08 | PHEYE | - | Jun 8, 10:35 UTC | Jun 8, 11:20 UTC | 45m |
| 2026-06-08 | PHEYE | - | Jun 8, 08:35 UTC | Jun 8, 09:30 UTC | 55m |
| 2026-06-03 | PHEYE | RTM → RTM | Jun 3, 08:55 UTC | Jun 3, 10:30 UTC | 1h 35m |
| 2026-05-29 | PHEYE | - | May 29, 14:10 UTC | May 29, 14:50 UTC | 40m |
| 2026-05-29 | PHEYE | - | May 29, 11:00 UTC | May 29, 13:05 UTC | 2h 5m |
| 2026-05-29 | PHEYE | - | May 29, 08:45 UTC | May 29, 09:20 UTC | 35m |
| 2026-05-27 | PHEYE | - | May 27, 14:45 UTC | May 27, 15:55 UTC | 1h 10m |
| 2026-05-27 | PHEYE | BQH → LYX | May 27, 11:50 UTC | May 27, 12:15 UTC | 25m |
| 2026-05-27 | PHEYE | RTM → BQH | May 27, 08:45 UTC | May 27, 10:10 UTC | 1h 25m |
| 2026-05-24 | PHEYE | - | May 24, 15:40 UTC | May 24, 17:10 UTC | 1h 30m |
| 2026-05-24 | PHEYE | - | May 24, 10:00 UTC | May 24, 11:35 UTC | 1h 35m |
| 2026-05-21 | PHEYE | - | May 21, 11:05 UTC | May 21, 11:30 UTC | 25m |
| 2026-05-21 | PHEYE | - | May 21, 09:10 UTC | May 21, 09:40 UTC | 30m |
| 2026-05-20 | PHEYE | RTM → RTM | May 20, 14:20 UTC | May 20, 15:05 UTC | 45m |
| 2026-05-20 | PHEYE | RTM → RTM | May 20, 08:10 UTC | May 20, 09:10 UTC | 1h 0m |
| 2026-05-19 | PHEYE | RTM → RTM | May 19, 10:00 UTC | May 19, 11:50 UTC | 1h 50m |
| 2026-05-18 | PHEYE | RTM → RTM | May 18, 13:10 UTC | May 18, 13:40 UTC | 30m |
| 2026-05-14 | PHEYE | - | May 14, 15:35 UTC | May 14, 16:25 UTC | 50m |
| 2026-05-14 | PHEYE | - | May 14, 13:10 UTC | May 14, 14:15 UTC | 1h 5m |
| 2026-05-14 | PHEYE | - | May 14, 09:50 UTC | May 14, 10:20 UTC | 30m |
| 2026-05-09 | PHEYE | - | May 9, 15:40 UTC | May 9, 16:55 UTC | 1h 15m |
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-EYE page for operator, model, and routing details .