sensors Mode-S transponder

4A2D24

ICAO 24-bit transponder address · allocated to Romania

Currently assigned to YR-KID · AIRBUS A-330-200

Hex
4A2D24
Octal
22426444
Decimal
4,861,220
Country
RO
Tail
YR-KID
Type
A332
No current signal · last broadcast 2d ago
Flights observed
54
Distinct callsigns
6
Country
RO
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 4A2D24.

Country allocation

The ICAO 24-bit address 4A2D24 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 6 distinct

Callsign Airline Flights Last seen
HYS101 - 24 2026-07-15
HYS102 - 22 2026-07-15
HYS7692 HiSky Europe 5 2026-04-26
HYS7691 - 1 2026-04-18
HYS31P - 1 2026-06-01
HYS21P - 1 2026-04-27

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-15 HYS102 JFK → OTP Jul 15, 18:25 UTCJul 16, 02:50 UTC8h 25m
2026-07-15 HYS101 - Jul 15, 06:40 UTCJul 15, 16:05 UTC9h 25m
2026-07-13 HYS102 - Jul 13, 18:10 UTCJul 14, 02:50 UTC8h 40m
2026-07-13 HYS101 - Jul 13, 06:55 UTCJul 13, 16:15 UTC9h 20m
2026-07-11 HYS102 JFK → OTP Jul 11, 18:50 UTCJul 12, 03:15 UTC8h 25m
2026-07-11 HYS101 - Jul 11, 07:05 UTCJul 11, 16:55 UTC9h 50m
2026-07-08 HYS102 - Jul 8, 19:10 UTCJul 9, 03:50 UTC8h 40m
2026-07-08 HYS101 - Jul 8, 07:25 UTCJul 8, 17:10 UTC9h 45m
2026-07-06 HYS102 JFK → OTP Jul 6, 20:35 UTCJul 7, 04:50 UTC8h 15m
2026-07-06 HYS101 - Jul 6, 06:50 UTCJul 6, 17:00 UTC10h 10m
2026-07-03 HYS102 JFK → OTP Jul 3, 19:20 UTCJul 4, 03:30 UTC8h 10m
2026-07-03 HYS101 - Jul 3, 06:55 UTCJul 3, 17:00 UTC10h 5m
2026-07-01 HYS102 JFK → OTP Jul 1, 18:55 UTCJul 2, 03:20 UTC8h 25m
2026-07-01 HYS101 OTP → JFK Jul 1, 06:55 UTCJul 1, 16:35 UTC9h 40m
2026-06-29 HYS102 JFK → OTP Jun 29, 18:39 UTCJun 30, 03:00 UTC8h 21m
2026-06-29 HYS101 OTP → JFK Jun 29, 07:05 UTCJun 29, 16:19 UTC9h 15m
2026-06-26 HYS102 JFK → OTP Jun 26, 19:00 UTCJun 27, 03:15 UTC8h 15m
2026-06-26 HYS101 OTP → JFK Jun 26, 07:10 UTCJun 26, 16:49 UTC9h 40m
2026-06-24 HYS102 JFK → OTP Jun 24, 18:44 UTCJun 25, 03:04 UTC8h 20m
2026-06-24 HYS101 OTP → JFK Jun 24, 15:05 UTCJun 24, 16:34 UTC1h 30m
2026-06-24 HYS101 OTP → JFK Jun 24, 06:50 UTCJun 24, 15:00 UTC8h 10m
2026-06-22 HYS102 JFK → OTP Jun 22, 18:30 UTCJun 23, 02:49 UTC8h 20m
2026-06-22 HYS101 OTP → JFK Jun 22, 06:45 UTCJun 22, 16:24 UTC9h 40m
2026-06-19 HYS102 JFK → OTP Jun 19, 19:14 UTCJun 20, 03:34 UTC8h 20m
2026-06-19 HYS101 OTP → JFK Jun 19, 07:19 UTCJun 19, 16:59 UTC9h 40m
2026-06-15 HYS102 JFK → OTP Jun 15, 18:20 UTCJun 16, 02:40 UTC8h 20m
2026-06-15 HYS101 OTP → JFK Jun 15, 07:00 UTCJun 15, 16:35 UTC9h 35m
2026-06-13 HYS102 JFK → OTP Jun 13, 19:50 UTCJun 14, 04:00 UTC8h 10m
2026-06-13 HYS101 OTP → JFK Jun 13, 07:45 UTCJun 13, 17:40 UTC9h 55m
2026-06-06 HYS102 JFK → OTP Jun 6, 18:55 UTCJun 7, 03:05 UTC8h 10m
2026-06-06 HYS101 OTP → JFK Jun 6, 07:10 UTCJun 6, 16:30 UTC9h 20m
2026-06-03 HYS102 JFK → OTP Jun 3, 18:40 UTCJun 4, 02:55 UTC8h 15m
2026-06-03 HYS101 OTP → JFK Jun 3, 07:00 UTCJun 3, 16:40 UTC9h 40m
2026-06-02 HYS102 JFK → OTP Jun 2, 18:40 UTCJun 3, 02:35 UTC7h 55m
2026-06-02 HYS101 OTP → JFK Jun 2, 06:55 UTCJun 2, 15:55 UTC9h 0m
2026-06-01 HYS31P BUD → OTP Jun 1, 18:15 UTCJun 1, 19:10 UTC55m
2026-04-27 HYS21P - Apr 27, 04:05 UTCApr 27, 05:10 UTC1h 5m
2026-04-26 HYS7692 HKT → OTP Apr 26, 01:55 UTCApr 26, 18:10 UTC16h 15m
2026-04-25 HYS7692 HKT → OTP Apr 25, 21:05 UTCApr 26, 18:10 UTC21h 5m
2026-04-24 HYS102 JFK → OTP Apr 24, 20:30 UTCApr 25, 05:25 UTC8h 55m
2026-04-24 HYS101 OTP → JFK Apr 24, 08:30 UTCApr 24, 17:40 UTC9h 10m
2026-04-19 HYS7692 HKT → OTP Apr 19, 01:25 UTCApr 19, 18:10 UTC16h 45m
2026-04-18 HYS7692 HKT → OTP Apr 18, 21:05 UTCApr 19, 18:10 UTC21h 5m
2026-04-18 HYS7691 - Apr 18, 20:30 UTCApr 19, 18:10 UTC21h 40m
2026-04-18 HYS102 JFK → OTP Apr 18, 01:25 UTCApr 18, 02:55 UTC1h 30m
2026-04-17 HYS102 JFK → OTP Apr 17, 23:25 UTCApr 18, 01:20 UTC1h 55m
2026-04-17 HYS102 JFK → OTP Apr 17, 19:25 UTCApr 17, 20:15 UTC50m
2026-04-17 HYS102 JFK → OTP Apr 17, 18:35 UTCApr 17, 19:20 UTC45m
2026-04-17 HYS101 OTP → JFK Apr 17, 15:20 UTCApr 17, 16:40 UTC1h 20m
2026-04-17 HYS101 OTP → JFK Apr 17, 14:55 UTCApr 17, 15:15 UTC20m

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-KID page for operator, model, and routing details .

Mode-S 4A2D24 frequently asked

What is Mode-S code 4A2D24?
4A2D24 is an ICAO 24-bit transponder address. Allocated to Romania. Assigned to YR-KID.
Where is Mode-S 4A2D24 registered?
Mode-S code 4A2D24 is allocated to Romania (RO). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 4A2D24 broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 4A2D24, octal 22426444, decimal 4,861,220.
What flights does 4A2D24 operate?
Mode-S 4A2D24 has broadcast 6 distinct callsigns, including HYS101, HYS102, HYS7692, HYS7691, HYS31P.