sensors Mode-S transponder

503D79

ICAO 24-bit transponder address · allocated to Lithuania

Currently assigned to LY-JAM · AIRBUS A-320

Hex
503D79
Octal
24036571
Decimal
5,258,617
Country
LT
Tail
LY-JAM
Type
A320
Broadcasting now · callsign AHY8003 · 35,950 ft
Flights observed
86
Distinct callsigns
20
Country
LT
Last broadcast
3h ago

Current position

503D79 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 503D79 falls within the block assigned to Lithuania (LT) by ICAO Annex 10, Volume III. Every aircraft registered in Lithuania 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 AHY036 MXP → GYD May 30, 09:55 UTCMay 30, 13:35 UTC3h 40m
2026-05-30 AHY035 GYD → MXP May 30, 04:20 UTCMay 30, 08:20 UTC4h 0m
2026-05-29 AHY036 MXP → GYD May 29, 10:00 UTCMay 29, 13:55 UTC3h 55m
2026-05-29 AHY035 GYD → MXP May 29, 04:30 UTCMay 29, 08:40 UTC4h 10m
2026-05-28 AHY035 GYD → MXP May 28, 12:50 UTCMay 29, 08:40 UTC19h 50m
2026-05-28 AHY035 GYD → MXP May 28, 10:20 UTCMay 29, 08:40 UTC22h 20m
2026-05-28 AHY036 MXP → GYD May 28, 09:40 UTCMay 29, 08:15 UTC22h 35m
2026-05-28 AHY035 GYD → MXP May 28, 03:35 UTCMay 28, 08:15 UTC4h 40m
2026-05-26 AHY064 BER → GYD May 26, 09:49 UTCMay 26, 13:40 UTC3h 50m
2026-05-26 AHY063 GYD → BER May 26, 06:20 UTCMay 26, 08:19 UTC2h 0m
2026-05-25 AHY063 GYD → BER May 25, 12:20 UTCMay 26, 08:19 UTC19h 59m
2026-05-25 AHY063 GYD → BER May 25, 10:25 UTCMay 26, 08:19 UTC21h 54m
2026-05-25 AHY703 GYD → RMO May 25, 08:40 UTCMay 25, 08:50 UTC10m
2026-05-24 AHY703 GYD → RMO May 24, 12:20 UTCMay 25, 07:40 UTC19h 20m
2026-05-24 AHY704 RMO → GYD May 24, 10:25 UTCMay 25, 07:40 UTC21h 15m
2026-05-24 AHY703 GYD → RMO May 24, 06:05 UTCMay 24, 07:25 UTC1h 20m
2026-05-23 AHY703 GYD → RMO May 23, 09:15 UTCMay 24, 07:25 UTC22h 10m
2026-05-23 AHY8103 GYD → SAW May 23, 05:50 UTCMay 23, 06:00 UTC10m
2026-05-23 AHY8103 GYD → SAW May 23, 04:20 UTCMay 23, 05:10 UTC50m
2026-05-20 AHY8003 GYD → ESB May 20, 16:25 UTCMay 21, 10:05 UTC17h 40m
2026-05-20 AHY703 GYD → RMO May 20, 06:45 UTCMay 20, 13:15 UTC6h 30m
2026-05-19 AHY703 GYD → RMO May 19, 12:20 UTCMay 20, 07:45 UTC19h 26m
2026-05-19 AHY064 BER → GYD May 19, 10:20 UTCMay 20, 07:45 UTC21h 26m
2026-05-19 AHY064 BER → GYD May 19, 10:10 UTCMay 20, 07:45 UTC21h 36m
2026-05-19 AHY063 GYD → BER May 19, 04:05 UTCMay 19, 08:05 UTC4h 0m
2026-05-18 AHY110 PRG → GYD May 18, 11:05 UTCMay 18, 12:55 UTC1h 50m
2026-05-18 AHY109 GYD → PRG May 18, 05:45 UTCMay 18, 09:35 UTC3h 50m
2026-05-17 AHY078 IST → GYD May 17, 20:20 UTCMay 17, 22:10 UTC1h 50m
2026-05-17 AHY077 GYD → IST May 17, 18:30 UTCMay 17, 18:45 UTC15m
2026-05-17 AHY064 BER → GYD May 17, 10:00 UTCMay 17, 17:45 UTC7h 45m
2026-05-17 AHY063 GYD → BER May 17, 04:10 UTCMay 17, 08:15 UTC4h 5m
2026-05-16 AHY110 PRG → GYD May 16, 11:31 UTCMay 16, 15:16 UTC3h 45m
2026-05-15 AHY109 GYD → PRG May 15, 17:30 UTCMay 16, 09:45 UTC16h 16m
2026-05-15 AHY109 GYD → PRG May 15, 13:05 UTCMay 16, 09:45 UTC20h 40m
2026-05-15 AHY109 GYD → PRG May 15, 10:20 UTCMay 16, 09:45 UTC23h 25m
2026-05-15 AHY036 MXP → GYD May 15, 09:45 UTCMay 16, 08:16 UTC22h 30m
2026-05-14 AHY035 GYD → MXP May 14, 14:20 UTCMay 15, 08:25 UTC18h 5m
2026-05-14 AHY035 GYD → MXP May 14, 12:20 UTCMay 15, 08:25 UTC20h 5m
2026-05-14 AHY036 MXP → GYD May 14, 10:45 UTCMay 15, 08:25 UTC21h 40m
2026-05-14 AHY035 GYD → MXP May 14, 03:35 UTCMay 14, 08:05 UTC4h 30m
2026-05-12 AHY8049 GYD → NQZ May 12, 18:30 UTCMay 12, 18:45 UTC15m
2026-05-11 AHY704 RMO → GYD May 11, 06:10 UTCMay 11, 18:45 UTC12h 35m
2026-05-10 AHY704 RMO → GYD May 10, 18:49 UTCMay 11, 13:00 UTC18h 10m
2026-05-09 AHY8004 ESB → GYD May 9, 23:09 UTCMay 10, 19:00 UTC19h 50m
2026-05-09 AHY036 MXP → GYD May 9, 09:35 UTCMay 9, 23:25 UTC13h 50m
2026-05-09 AHY035 GYD → MXP May 9, 03:40 UTCMay 9, 07:55 UTC4h 15m
2026-05-08 AHY074 CDG → GYD May 8, 10:44 UTCMay 8, 15:10 UTC4h 25m
2026-05-08 AHY073 GYD → CDG May 8, 03:39 UTCMay 8, 08:59 UTC5h 20m
2026-05-07 AHY073 GYD → CDG May 7, 12:55 UTCMay 8, 08:59 UTC20h 5m
2026-05-07 AHY073 GYD → CDG May 7, 10:20 UTCMay 8, 08:59 UTC22h 39m

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

Mode-S 503D79 frequently asked

What is Mode-S code 503D79?
503D79 is an ICAO 24-bit transponder address. Allocated to Lithuania. Assigned to LY-JAM.
Where is Mode-S 503D79 registered?
Mode-S code 503D79 is allocated to Lithuania (LT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 503D79 broadcasting right now?
Yes. Mode-S 503D79 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 503D79, octal 24036571, decimal 5,258,617.
What flights does 503D79 operate?
Mode-S 503D79 has broadcast 20 distinct callsigns, including AHY073, AHY035, AHY036, AHY703, AHY109.