sensors Mode-S transponder
4A08A5
ICAO 24-bit transponder address · allocated to Romania
Currently assigned to YR-BEE · AIRBUS A-320
- Hex
- 4A08A5
- Octal
- 22404245
- Decimal
- 4,851,877
- Country
- RO
- Tail
- YR-BEE
- Type
- A320
- Flights observed
- 82
- Distinct callsigns
- 20
- Country
- RO
- Last broadcast
- 14d ago
Last known position
Country allocation
The ICAO 24-bit address 4A08A5 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 |
|---|---|---|---|
| HYS276 | HiSky Europe | 5 | 2026-04-24 |
| HYS473 | HiSky Europe | 4 | 2026-05-06 |
| HYS275 | HiSky Europe | 4 | 2026-04-24 |
| HYS252 | HiSky Europe | 4 | 2026-04-17 |
| HYS251 | - | 4 | 2026-04-16 |
| HYS7117 | - | 3 | 2026-04-13 |
| HYS5617 | - | 3 | 2026-04-18 |
| HYM346 | Himalayan Airlines | 3 | 2026-05-08 |
| HYS8814 | - | 2 | 2026-04-17 |
| HYS8813 | - | 2 | 2026-04-17 |
| HYS5514 | - | 2 | 2026-04-17 |
| HYS5513 | - | 2 | 2026-04-17 |
| HYS474 | HiSky Europe | 2 | 2026-05-06 |
| HYS258 | HiSky Europe | 2 | 2026-05-01 |
| HYS257 | HiSky Europe | 2 | 2026-05-01 |
| HYS254 | HiSky Europe | 2 | 2026-04-24 |
| HYS253 | HiSky Europe | 2 | 2026-04-24 |
| HYM345 | - | 2 | 2026-05-04 |
| HYM315 | - | 2 | 2026-05-05 |
| HYS8717 | - | 1 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-15 | HYS21 | - | May 15, 13:30 UTC | May 15, 13:55 UTC | 25m |
| 2026-05-08 | HYM346 | SSH → RMO | May 8, 09:30 UTC | May 8, 16:25 UTC | 6h 55m |
| 2026-05-06 | HYS474 | DUB → RMO | May 6, 23:05 UTC | May 7, 02:10 UTC | 3h 5m |
| 2026-05-06 | HYS473 | RMO → DUB | May 6, 03:50 UTC | May 6, 22:05 UTC | 18h 14m |
| 2026-05-06 | HYS473 | RMO → DUB | May 6, 01:20 UTC | May 6, 22:05 UTC | 20h 44m |
| 2026-05-06 | HYS473 | RMO → DUB | May 6, 00:15 UTC | May 6, 22:05 UTC | 21h 49m |
| 2026-05-05 | HYM315 | - | May 5, 21:30 UTC | May 5, 22:55 UTC | 1h 25m |
| 2026-05-04 | HYS474 | DUB → RMO | May 4, 23:25 UTC | May 5, 02:30 UTC | 3h 5m |
| 2026-05-04 | HYS243 | IAS → DUB | May 4, 19:10 UTC | May 4, 22:25 UTC | 3h 15m |
| 2026-05-04 | HYS244 | DUB → IAS | May 4, 14:55 UTC | May 4, 17:50 UTC | 2h 55m |
| 2026-05-04 | HYS473 | RMO → DUB | May 4, 10:50 UTC | May 4, 13:45 UTC | 2h 55m |
| 2026-05-04 | HYM346 | SSH → RMO | May 4, 05:35 UTC | May 4, 08:15 UTC | 2h 40m |
| 2026-05-04 | HYM345 | - | May 4, 01:10 UTC | May 4, 03:40 UTC | 2h 30m |
| 2026-05-03 | HYS446 | BVA → RMO | May 3, 15:50 UTC | May 3, 18:09 UTC | 2h 20m |
| 2026-05-03 | HYS225 | BAY → BVA | May 3, 12:50 UTC | May 3, 14:55 UTC | 2h 5m |
| 2026-05-03 | HYS226 | BVA → BAY | May 3, 09:55 UTC | May 3, 11:50 UTC | 1h 55m |
| 2026-05-03 | HYS445 | RMO → BVA | May 3, 06:25 UTC | May 3, 09:00 UTC | 2h 35m |
| 2026-05-03 | HYM316 | - | May 3, 03:05 UTC | May 3, 04:25 UTC | 1h 19m |
| 2026-05-03 | HYM315 | - | May 3, 00:30 UTC | May 3, 01:35 UTC | 1h 5m |
| 2026-05-02 | HYM458 | TLV → RMO | May 2, 21:10 UTC | May 2, 23:15 UTC | 2h 5m |
| 2026-05-02 | HYM457 | RMO → TLV | May 2, 17:10 UTC | May 2, 19:25 UTC | 2h 15m |
| 2026-05-02 | HYM346 | SSH → RMO | May 2, 11:25 UTC | May 2, 13:50 UTC | 2h 25m |
| 2026-05-02 | HYM345 | - | May 2, 07:40 UTC | May 2, 09:30 UTC | 1h 50m |
| 2026-05-02 | HYS21P | - | May 2, 05:20 UTC | May 2, 05:45 UTC | 25m |
| 2026-05-01 | HYS258 | DUB → OTP | May 1, 22:30 UTC | May 2, 01:55 UTC | 3h 25m |
| 2026-05-01 | HYS257 | OTP → DUB | May 1, 17:55 UTC | May 1, 21:10 UTC | 3h 15m |
| 2026-05-01 | HYS264 | BCN → OTP | May 1, 11:35 UTC | May 1, 14:10 UTC | 2h 35m |
| 2026-05-01 | HYS263 | OTP → BCN | May 1, 07:15 UTC | May 1, 10:10 UTC | 2h 55m |
| 2026-04-30 | HYS256 | TSR → OTP | Apr 30, 17:40 UTC | Apr 30, 18:15 UTC | 35m |
| 2026-04-30 | HYS255 | OTP → TSR | Apr 30, 16:15 UTC | Apr 30, 16:50 UTC | 35m |
| 2026-04-26 | HYS202 | FRA → OTP | Apr 26, 14:25 UTC | Apr 26, 16:15 UTC | 1h 50m |
| 2026-04-26 | HYS201 | OTP → FRA | Apr 26, 10:35 UTC | Apr 26, 12:40 UTC | 2h 5m |
| 2026-04-25 | HYS238 | TLV → OTP | Apr 25, 20:40 UTC | Apr 25, 22:55 UTC | 2h 15m |
| 2026-04-25 | HYS237 | OTP → TLV | Apr 25, 17:20 UTC | Apr 25, 19:35 UTC | 2h 15m |
| 2026-04-25 | HYS7622 | - | Apr 25, 06:10 UTC | Apr 25, 07:35 UTC | 1h 25m |
| 2026-04-25 | HYS7621 | - | Apr 25, 03:20 UTC | Apr 25, 04:40 UTC | 1h 20m |
| 2026-04-24 | HYS258 | DUB → OTP | Apr 24, 23:10 UTC | Apr 25, 02:10 UTC | 3h 0m |
| 2026-04-24 | HYS257 | OTP → DUB | Apr 24, 18:30 UTC | Apr 24, 22:05 UTC | 3h 35m |
| 2026-04-24 | HYS275 | CLJ → OTP | Apr 24, 16:45 UTC | Apr 24, 17:15 UTC | 30m |
| 2026-04-24 | HYS276 | OTP → CLJ | Apr 24, 15:05 UTC | Apr 24, 15:35 UTC | 30m |
| 2026-04-24 | HYS7582 | - | Apr 24, 11:10 UTC | Apr 24, 13:25 UTC | 2h 15m |
| 2026-04-24 | HYS7581 | - | Apr 24, 07:50 UTC | Apr 24, 09:40 UTC | 1h 50m |
| 2026-04-24 | HYS254 | TSR → OTP | Apr 24, 06:05 UTC | Apr 24, 06:40 UTC | 35m |
| 2026-04-24 | HYS253 | OTP → TSR | Apr 24, 04:40 UTC | Apr 24, 05:10 UTC | 30m |
| 2026-04-20 | HYS254 | TSR → OTP | Apr 20, 06:35 UTC | Apr 20, 07:10 UTC | 35m |
| 2026-04-20 | HYS253 | OTP → TSR | Apr 20, 05:05 UTC | Apr 20, 05:40 UTC | 35m |
| 2026-04-19 | HYS275 | CLJ → OTP | Apr 19, 15:50 UTC | Apr 19, 16:30 UTC | 40m |
| 2026-04-19 | HYS8717 | - | Apr 19, 06:45 UTC | Apr 19, 14:20 UTC | 7h 35m |
| 2026-04-18 | HYS7615 | - | Apr 18, 13:00 UTC | Apr 18, 20:40 UTC | 7h 40m |
| 2026-04-18 | HYS5617 | - | Apr 18, 05:25 UTC | Apr 18, 06:55 UTC | 1h 30m |
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-BEE page for operator, model, and routing details .