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
- Flights observed
- 136
- Distinct callsigns
- 20
- Country
- LT
- Last broadcast
- 2h ago
Last known 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
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AHY109 | - | 12 | 2026-06-16 |
| AHY073 | Azerbaijan Airlines | 10 | 2026-05-08 |
| AHY035 | Azerbaijan Airlines | 10 | 2026-05-30 |
| AHY8105 | - | 9 | 2026-06-16 |
| AHY036 | Azerbaijan Airlines | 9 | 2026-05-30 |
| AHY8103 | - | 6 | 2026-06-19 |
| AHY8041 | - | 6 | 2026-07-14 |
| AHY703 | Azerbaijan Airlines | 6 | 2026-05-25 |
| AHY063 | Azerbaijan Airlines | 6 | 2026-05-26 |
| AHY8106 | Azerbaijan Airlines | 5 | 2026-06-11 |
| AHY8042 | - | 5 | 2026-07-14 |
| AHY8003 | Azerbaijan Airlines | 5 | 2026-06-12 |
| AHY071 | - | 5 | 2026-06-19 |
| AHY110 | - | 4 | 2026-06-17 |
| AHY074 | Azerbaijan Airlines | 4 | 2026-05-08 |
| AHY064 | Azerbaijan Airlines | 4 | 2026-05-26 |
| AHY704 | Azerbaijan Airlines | 3 | 2026-05-24 |
| AHY077 | - | 3 | 2026-07-14 |
| AHY025 | - | 3 | 2026-06-18 |
| AHY8104 | - | 2 | 2026-06-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | AHY077 | - | Jul 14, 16:15 UTC | Jul 14, 17:40 UTC | 1h 25m |
| 2026-07-14 | AHY8042 | - | Jul 14, 10:10 UTC | Jul 14, 12:05 UTC | 1h 55m |
| 2026-07-14 | AHY8041 | - | Jul 14, 05:50 UTC | Jul 14, 08:20 UTC | 2h 30m |
| 2026-06-20 | AHY072 | - | Jun 20, 11:34 UTC | Jun 20, 21:34 UTC | 10h 0m |
| 2026-06-19 | AHY071 | - | Jun 19, 14:19 UTC | Jun 20, 09:54 UTC | 19h 35m |
| 2026-06-19 | AHY071 | BUS → VIE | Jun 19, 14:09 UTC | Jun 20, 09:54 UTC | 19h 45m |
| 2026-06-19 | AHY8104 | - | Jun 19, 07:54 UTC | Jun 19, 13:09 UTC | 5h 15m |
| 2026-06-19 | AHY8103 | - | Jun 19, 05:54 UTC | Jun 19, 06:14 UTC | 20m |
| 2026-06-18 | AHY8103 | - | Jun 18, 22:05 UTC | Jun 19, 05:19 UTC | 7h 14m |
| 2026-06-18 | AHY026 | - | Jun 18, 08:20 UTC | Jun 18, 20:40 UTC | 12h 20m |
| 2026-06-18 | AHY025 | - | Jun 18, 06:20 UTC | Jun 18, 06:45 UTC | 25m |
| 2026-06-17 | AHY110 | - | Jun 17, 11:15 UTC | Jun 18, 05:40 UTC | 18h 25m |
| 2026-06-16 | AHY109 | - | Jun 16, 14:20 UTC | Jun 17, 09:55 UTC | 19h 36m |
| 2026-06-16 | AHY109 | - | Jun 16, 13:09 UTC | Jun 17, 09:55 UTC | 20h 46m |
| 2026-06-16 | AHY8105 | - | Jun 16, 09:15 UTC | Jun 16, 11:45 UTC | 2h 30m |
| 2026-06-14 | AHY8042 | ADB → GYD | Jun 14, 10:00 UTC | Jun 14, 12:05 UTC | 2h 5m |
| 2026-06-13 | AHY8041 | GYD → ADB | Jun 13, 22:10 UTC | Jun 14, 08:10 UTC | 10h 0m |
| 2026-06-13 | AHY8104 | SAW → GYD | Jun 13, 07:45 UTC | Jun 13, 20:45 UTC | 13h 0m |
| 2026-06-13 | AHY8103 | GYD → SAW | Jun 13, 05:45 UTC | Jun 13, 06:00 UTC | 15m |
| 2026-06-13 | AHY8103 | GYD → SAW | Jun 13, 03:35 UTC | Jun 13, 05:05 UTC | 1h 29m |
| 2026-06-12 | AHY8003 | GYD → ESB | Jun 12, 16:45 UTC | Jun 12, 21:35 UTC | 4h 50m |
| 2026-06-12 | AHY8234 | TBS → GYD | Jun 12, 13:40 UTC | Jun 12, 14:10 UTC | 30m |
| 2026-06-12 | AHY8233 | GYD → TBS | Jun 12, 08:15 UTC | Jun 12, 12:00 UTC | 3h 45m |
| 2026-06-12 | AHY8223 | - | Jun 12, 06:20 UTC | Jun 12, 06:50 UTC | 30m |
| 2026-06-11 | AHY8106 | SAW → GYD | Jun 11, 13:15 UTC | Jun 11, 15:10 UTC | 1h 55m |
| 2026-06-11 | AHY8105 | GYD → SAW | Jun 11, 09:30 UTC | Jun 11, 11:45 UTC | 2h 15m |
| 2026-06-09 | AHY034 | TIV → GYD | Jun 9, 10:45 UTC | Jun 9, 13:40 UTC | 2h 55m |
| 2026-06-09 | AHY033 | GYD → TIV | Jun 9, 06:10 UTC | Jun 9, 09:10 UTC | 3h 0m |
| 2026-06-07 | AHY8106 | SAW → GYD | Jun 7, 13:20 UTC | Jun 7, 15:10 UTC | 1h 50m |
| 2026-06-07 | AHY8105 | GYD → SAW | Jun 7, 09:30 UTC | Jun 7, 11:50 UTC | 2h 20m |
| 2026-06-06 | AHY8105 | GYD → SAW | Jun 6, 14:20 UTC | Jun 7, 11:50 UTC | 21h 30m |
| 2026-06-06 | AHY8105 | GYD → SAW | Jun 6, 12:20 UTC | Jun 7, 11:50 UTC | 23h 30m |
| 2026-06-06 | AHY110 | PRG → GYD | Jun 6, 11:09 UTC | Jun 7, 10:15 UTC | 23h 5m |
| 2026-06-05 | AHY109 | GYD → PRG | Jun 5, 14:20 UTC | Jun 6, 09:50 UTC | 19h 30m |
| 2026-06-05 | AHY109 | GYD → PRG | Jun 5, 12:20 UTC | Jun 6, 09:50 UTC | 21h 30m |
| 2026-06-05 | AHY109 | GYD → PRG | Jun 5, 11:20 UTC | Jun 6, 09:50 UTC | 22h 30m |
| 2026-06-05 | AHY109 | GYD → PRG | Jun 5, 06:20 UTC | Jun 5, 09:45 UTC | 3h 25m |
| 2026-06-04 | AHY078 | IST → GYD | Jun 4, 20:15 UTC | Jun 4, 22:30 UTC | 2h 15m |
| 2026-06-04 | AHY077 | GYD → IST | Jun 4, 18:15 UTC | Jun 4, 18:35 UTC | 20m |
| 2026-06-04 | AHY034 | TIV → GYD | Jun 4, 10:45 UTC | Jun 4, 17:40 UTC | 6h 55m |
| 2026-06-04 | AHY033 | GYD → TIV | Jun 4, 06:00 UTC | Jun 4, 09:10 UTC | 3h 10m |
| 2026-06-02 | AHY072 | VIE → GYD | Jun 2, 11:30 UTC | Jun 2, 14:40 UTC | 3h 10m |
| 2026-06-02 | AHY071 | GYD → VIE | Jun 2, 06:40 UTC | Jun 2, 09:55 UTC | 3h 15m |
| 2026-06-01 | AHY071 | GYD → VIE | Jun 1, 12:20 UTC | Jun 2, 09:55 UTC | 21h 35m |
| 2026-06-01 | AHY071 | GYD → VIE | Jun 1, 10:35 UTC | Jun 2, 09:55 UTC | 23h 20m |
| 2026-05-31 | AHY8106 | SAW → GYD | May 31, 13:20 UTC | Jun 1, 07:50 UTC | 18h 30m |
| 2026-05-31 | AHY8105 | GYD → SAW | May 31, 11:30 UTC | May 31, 11:50 UTC | 20m |
| 2026-05-30 | AHY8105 | GYD → SAW | May 30, 16:55 UTC | May 31, 11:00 UTC | 18h 5m |
| 2026-05-30 | AHY8105 | GYD → SAW | May 30, 12:50 UTC | May 31, 11:00 UTC | 22h 10m |
| 2026-05-30 | AHY036 | MXP → GYD | May 30, 10:20 UTC | May 31, 10:15 UTC | 23h 55m |
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 .