sensors Mode-S transponder

503EAA

ICAO 24-bit transponder address · allocated to Lithuania

Currently assigned to LY-TUI · BOEING 737-800

Hex
503EAA
Octal
24037252
Decimal
5,258,922
Country
LT
Tail
LY-TUI
Type
B738
No current signal · last broadcast 50m ago
Flights observed
337
Distinct callsigns
20
Country
LT
Last broadcast
50m ago

Last known position

Most recent position reported by Mode-S 503EAA.

Country allocation

The ICAO 24-bit address 503EAA 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
GJT9NV - 63 2026-07-14
GJT25H - 60 2026-07-14
GJM3327 - 34 2026-07-10
GJM3328 - 32 2026-07-10
GJT8VZ - 25 2026-07-13
GJT2XJ - 23 2026-07-13
GJT7PN - 11 2026-07-12
GJT46R - 11 2026-07-12
GJT8EH - 9 2026-07-11
GJT57X - 9 2026-07-11
GJT7MN - 6 2026-07-05
GJT7KL - 5 2026-06-28
GJM3374 - 5 2026-07-08
GJM3373 - 5 2026-07-08
GJT78G - 4 2026-05-29
GJT66T Gestion Aerea Ajecutiva 4 2026-05-29
GJM3302 Airhub Airlines 4 2026-05-01
GJM3301 Airhub Airlines 4 2026-04-24
GJT8GU - 3 2026-07-10
GJT7XU Gestion Aerea Ajecutiva 3 2026-05-16

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 GJT9NV - Jul 14, 06:55 UTCJul 14, 09:55 UTC3h 0m
2026-07-14 GJT25H VNO → AYT Jul 14, 02:40 UTCJul 14, 05:40 UTC3h 0m
2026-07-13 GJT2XJ FNC → VNO Jul 13, 18:15 UTCJul 13, 22:55 UTC4h 40m
2026-07-13 GJT8VZ VNO → FNC Jul 13, 11:20 UTCJul 13, 17:00 UTC5h 40m
2026-07-13 GJT9NV AYT → VNO Jul 13, 07:01 UTCJul 13, 10:00 UTC3h 0m
2026-07-13 GJT25H VNO → AYT Jul 13, 02:35 UTCJul 13, 05:35 UTC3h 0m
2026-07-12 GJT7PN - Jul 12, 16:10 UTCJul 12, 17:50 UTC1h 40m
2026-07-12 GJT46R - Jul 12, 12:05 UTCJul 12, 14:20 UTC2h 15m
2026-07-12 GJT9NV AYT → VNO Jul 12, 07:10 UTCJul 12, 10:05 UTC2h 55m
2026-07-12 GJT25H VNO → AYT Jul 12, 02:40 UTCJul 12, 05:50 UTC3h 10m
2026-07-11 GJT8EH RHO → VNO Jul 11, 16:55 UTCJul 11, 19:55 UTC3h 0m
2026-07-11 GJT57X VNO → RHO Jul 11, 12:20 UTCJul 11, 15:15 UTC2h 55m
2026-07-11 GJT9NV - Jul 11, 07:15 UTCJul 11, 10:15 UTC3h 0m
2026-07-11 GJT25H VNO → AYT Jul 11, 02:35 UTCJul 11, 05:55 UTC3h 20m
2026-07-10 GJM3328 - Jul 10, 16:55 UTCJul 10, 19:45 UTC2h 50m
2026-07-10 GJM3327 - Jul 10, 12:55 UTCJul 10, 15:40 UTC2h 45m
2026-07-10 GJT8GU - Jul 10, 07:00 UTCJul 10, 09:10 UTC2h 10m
2026-07-10 GJT2LW - Jul 10, 03:35 UTCJul 10, 05:40 UTC2h 5m
2026-07-09 GJT7PN - Jul 9, 15:35 UTCJul 9, 17:45 UTC2h 10m
2026-07-09 GJT46R - Jul 9, 12:05 UTCJul 9, 14:15 UTC2h 10m
2026-07-09 GJT78Y - Jul 9, 08:05 UTCJul 9, 10:45 UTC2h 40m
2026-07-09 GJT8AV - Jul 9, 03:50 UTCJul 9, 06:20 UTC2h 30m
2026-07-08 GJM3374 RHO → VNO Jul 8, 16:40 UTCJul 8, 19:45 UTC3h 5m
2026-07-08 GJM3373 VNO → RHO Jul 8, 12:30 UTCJul 8, 15:30 UTC3h 0m
2026-07-08 GJT9NV - Jul 8, 07:00 UTCJul 8, 10:10 UTC3h 10m
2026-07-08 GJT25H VNO → AYT Jul 8, 02:30 UTCJul 8, 05:40 UTC3h 10m
2026-07-07 GJT9NV - Jul 7, 11:30 UTCJul 7, 12:10 UTC40m
2026-07-07 GJT9NV - Jul 7, 09:00 UTCJul 7, 11:25 UTC2h 25m
2026-07-07 GJT25H - Jul 7, 04:30 UTCJul 7, 07:30 UTC3h 0m
2026-07-06 GJT5WB - Jul 6, 16:25 UTCJul 6, 18:45 UTC2h 20m
2026-07-06 GJT73G - Jul 6, 12:20 UTCJul 6, 14:25 UTC2h 5m
2026-07-06 GJM3328 - Jul 6, 05:40 UTCJul 6, 08:40 UTC3h 0m
2026-07-06 GJM3327 - Jul 6, 01:10 UTCJul 6, 04:00 UTC2h 50m
2026-07-05 GJT7MN - Jul 5, 18:10 UTCJul 5, 21:10 UTC3h 0m
2026-07-05 GJT7PN - Jul 5, 15:40 UTCJul 5, 16:55 UTC1h 15m
2026-07-05 GJT46R VNO → BOJ Jul 5, 12:00 UTCJul 5, 14:20 UTC2h 20m
2026-07-05 GJT9NV - Jul 5, 07:00 UTCJul 5, 10:10 UTC3h 10m
2026-07-05 GJT25H - Jul 5, 02:35 UTCJul 5, 05:35 UTC3h 0m
2026-07-04 GJT8EH RHO → VNO Jul 4, 17:00 UTCJul 4, 20:00 UTC3h 0m
2026-07-04 GJT57X VNO → RHO Jul 4, 12:15 UTCJul 4, 15:10 UTC2h 55m
2026-07-04 GJT9NV - Jul 4, 07:00 UTCJul 4, 10:10 UTC3h 10m
2026-07-04 GJT25H - Jul 4, 02:15 UTCJul 4, 05:35 UTC3h 20m
2026-07-03 GJM3328 - Jul 3, 16:30 UTCJul 3, 19:20 UTC2h 50m
2026-07-03 GJM3327 - Jul 3, 12:00 UTCJul 3, 14:55 UTC2h 55m
2026-07-02 GJT7PN - Jul 2, 15:55 UTCJul 2, 18:00 UTC2h 5m
2026-07-02 GJT46R VNO → BOJ Jul 2, 12:15 UTCJul 2, 14:40 UTC2h 25m
2026-07-02 GJT9NV AYT → VNO Jul 2, 07:20 UTCJul 2, 10:20 UTC3h 0m
2026-07-02 GJT25H VNO → AYT Jul 2, 02:25 UTCJul 2, 05:45 UTC3h 20m
2026-07-01 GJM3374 RHO → VNO Jul 1, 16:40 UTCJul 1, 19:25 UTC2h 45m
2026-07-01 GJM3373 VNO → RHO Jul 1, 12:10 UTCJul 1, 15:20 UTC3h 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 LY-TUI page for operator, model, and routing details .

Mode-S 503EAA frequently asked

What is Mode-S code 503EAA?
503EAA is an ICAO 24-bit transponder address. Allocated to Lithuania. Assigned to LY-TUI.
Where is Mode-S 503EAA registered?
Mode-S code 503EAA is allocated to Lithuania (LT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 503EAA broadcasting right now?
No active broadcast right now. Last signal was 50m ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 503EAA, octal 24037252, decimal 5,258,922.
What flights does 503EAA operate?
Mode-S 503EAA has broadcast 20 distinct callsigns, including GJT9NV, GJT25H, GJM3327, GJM3328, GJT8VZ.