sensors Mode-S transponder
4A5DF7
ICAO 24-bit transponder address · allocated to Romania
Currently assigned to YR-WOW · AIRBUS A-321neo
- Hex
- 4A5DF7
- Octal
- 22456767
- Decimal
- 4,873,719
- Country
- RO
- Tail
- YR-WOW
- Type
- A21N
- Flights observed
- 81
- Distinct callsigns
- 20
- Country
- RO
- Last broadcast
- 47m ago
Current position
Country allocation
The ICAO 24-bit address 4A5DF7 falls within the block assigned to Romania (RO) by ICAO Annex 10, Volume III. Every aircraft registered in Romania 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HYS7551 | - | 7 | 2026-05-15 |
| HYS7552 | - | 6 | 2026-05-29 |
| HYS7413 | - | 6 | 2026-05-28 |
| HYS7615 | - | 5 | 2026-05-23 |
| HYS263 | HiSky Europe | 5 | 2026-04-15 |
| HYS8511 | HiSky Europe | 4 | 2026-05-22 |
| HYS7414 | - | 4 | 2026-05-28 |
| HYS7411 | - | 4 | 2026-05-21 |
| HYS264 | HiSky Europe | 4 | 2026-04-15 |
| HYS8569 | HiSky Europe | 3 | 2026-04-18 |
| HYS8512 | - | 3 | 2026-05-29 |
| HYS7616 | - | 3 | 2026-05-16 |
| HYS7412 | - | 3 | 2026-05-14 |
| HYS258 | HiSky Europe | 3 | 2026-05-29 |
| HYS257 | HiSky Europe | 3 | 2026-05-29 |
| HYS8711 | - | 2 | 2026-05-17 |
| HYS7611 | - | 2 | 2026-05-23 |
| HYS222 | HiSky Europe | 2 | 2026-05-24 |
| HYS221 | HiSky Europe | 2 | 2026-05-24 |
| HYS8570 | - | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | HYS258 | DUB → OTP | May 29, 23:20 UTC | May 29, 23:45 UTC | 25m |
| 2026-05-29 | HYS257 | OTP → DUB | May 29, 18:30 UTC | May 29, 22:10 UTC | 3h 40m |
| 2026-05-29 | HYS8512 | - | May 29, 11:15 UTC | May 29, 17:20 UTC | 6h 5m |
| 2026-05-29 | HYS7552 | - | May 29, 01:35 UTC | May 29, 08:55 UTC | 7h 20m |
| 2026-05-28 | HYS7413 | - | May 28, 12:45 UTC | May 28, 20:00 UTC | 7h 15m |
| 2026-05-28 | HYS7414 | - | May 28, 04:10 UTC | May 28, 11:30 UTC | 7h 20m |
| 2026-05-24 | HYS238 | TLV → OTP | May 24, 21:10 UTC | May 24, 23:30 UTC | 2h 20m |
| 2026-05-24 | HYS237 | OTP → TLV | May 24, 17:40 UTC | May 24, 19:50 UTC | 2h 10m |
| 2026-05-24 | HYS222 | CDG → OTP | May 24, 13:10 UTC | May 24, 15:40 UTC | 2h 30m |
| 2026-05-24 | HYS221 | OTP → CDG | May 24, 09:10 UTC | May 24, 11:40 UTC | 2h 30m |
| 2026-05-23 | HYS7615 | - | May 23, 13:50 UTC | May 23, 21:15 UTC | 7h 25m |
| 2026-05-23 | HYS7611 | - | May 23, 05:15 UTC | May 23, 12:30 UTC | 7h 15m |
| 2026-05-23 | HYS258 | DUB → OTP | May 23, 01:00 UTC | May 23, 04:10 UTC | 3h 9m |
| 2026-05-22 | HYS257 | OTP → DUB | May 22, 20:35 UTC | May 23, 00:00 UTC | 3h 25m |
| 2026-05-22 | HYS8511 | OTP → OTP | May 22, 03:45 UTC | May 22, 19:25 UTC | 15h 40m |
| 2026-05-21 | HYS7413 | - | May 21, 12:45 UTC | May 21, 19:40 UTC | 6h 55m |
| 2026-05-21 | HYS7411 | - | May 21, 04:05 UTC | May 21, 11:15 UTC | 7h 10m |
| 2026-05-17 | HYS256 | TSR → OTP | May 17, 16:30 UTC | May 17, 17:10 UTC | 40m |
| 2026-05-17 | HYS255 | OTP → TSR | May 17, 14:50 UTC | May 17, 15:25 UTC | 35m |
| 2026-05-17 | HYS8711 | - | May 17, 06:35 UTC | May 17, 13:50 UTC | 7h 15m |
| 2026-05-16 | HYS7615 | - | May 16, 19:30 UTC | May 17, 02:55 UTC | 7h 25m |
| 2026-05-16 | HYS7616 | - | May 16, 10:46 UTC | May 16, 18:05 UTC | 7h 20m |
| 2026-05-16 | HYS222 | CDG → OTP | May 16, 07:05 UTC | May 16, 09:31 UTC | 2h 25m |
| 2026-05-16 | HYS221 | OTP → CDG | May 16, 03:15 UTC | May 16, 05:51 UTC | 2h 36m |
| 2026-05-15 | HYS7551 | - | May 15, 12:50 UTC | May 15, 20:00 UTC | 7h 10m |
| 2026-05-15 | HYS7552 | - | May 15, 04:15 UTC | May 15, 11:25 UTC | 7h 10m |
| 2026-05-14 | HYS7412 | - | May 14, 12:35 UTC | May 14, 19:35 UTC | 7h 0m |
| 2026-05-14 | HYS7411 | - | May 14, 04:25 UTC | May 14, 11:20 UTC | 6h 55m |
| 2026-05-13 | HYS277 | CLJ → OTP | May 13, 03:50 UTC | May 13, 04:20 UTC | 30m |
| 2026-05-12 | HYS276 | OTP → CLJ | May 12, 17:10 UTC | May 12, 17:35 UTC | 25m |
| 2026-05-09 | HYS7615 | - | May 9, 13:55 UTC | May 9, 21:40 UTC | 7h 45m |
| 2026-05-09 | HYS7616 | - | May 9, 05:20 UTC | May 9, 12:45 UTC | 7h 25m |
| 2026-05-08 | HYS7551 | - | May 8, 13:05 UTC | May 8, 20:05 UTC | 7h 0m |
| 2026-05-08 | HYS7552 | - | May 8, 04:19 UTC | May 8, 11:34 UTC | 7h 15m |
| 2026-05-02 | HYS7615 | - | May 2, 13:35 UTC | May 2, 20:55 UTC | 7h 20m |
| 2026-05-02 | HYS7611 | - | May 2, 05:10 UTC | May 2, 12:20 UTC | 7h 10m |
| 2026-05-01 | HYS7551 | - | May 1, 12:50 UTC | May 1, 20:00 UTC | 7h 10m |
| 2026-05-01 | HYS7552 | - | May 1, 04:15 UTC | May 1, 11:20 UTC | 7h 5m |
| 2026-04-26 | HYS258 | DUB → OTP | Apr 26, 22:40 UTC | Apr 27, 01:45 UTC | 3h 5m |
| 2026-04-26 | HYS257 | OTP → DUB | Apr 26, 18:00 UTC | Apr 26, 21:40 UTC | 3h 40m |
| 2026-04-25 | HYS7615 | - | Apr 25, 13:50 UTC | Apr 25, 21:15 UTC | 7h 25m |
| 2026-04-25 | HYS7616 | - | Apr 25, 05:10 UTC | Apr 25, 12:35 UTC | 7h 25m |
| 2026-04-24 | HYS7551 | - | Apr 24, 13:00 UTC | Apr 24, 20:05 UTC | 7h 5m |
| 2026-04-24 | HYS8511 | OTP → OTP | Apr 24, 04:15 UTC | Apr 24, 11:30 UTC | 7h 15m |
| 2026-04-23 | HYS7413 | - | Apr 23, 14:55 UTC | Apr 23, 22:10 UTC | 7h 14m |
| 2026-04-23 | HYS7414 | - | Apr 23, 06:05 UTC | Apr 23, 13:20 UTC | 7h 15m |
| 2026-04-20 | HYS7111 | - | Apr 20, 07:35 UTC | Apr 20, 14:50 UTC | 7h 15m |
| 2026-04-19 | HYS8711 | - | Apr 19, 18:10 UTC | Apr 20, 00:55 UTC | 6h 45m |
| 2026-04-19 | HYS202 | - | Apr 19, 14:15 UTC | Apr 19, 16:10 UTC | 1h 55m |
| 2026-04-19 | HYS201 | OTP → FRA | Apr 19, 10:40 UTC | Apr 19, 12:50 UTC | 2h 10m |
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 YR-WOW page for operator, model, and routing details .