sensors Mode-S transponder

503E99

ICAO 24-bit transponder address · allocated to Lithuania

Currently assigned to LY-CIN · BOEING 737-800

Hex
503E99
Octal
24037231
Decimal
5,258,905
Country
LT
Tail
LY-CIN
Type
B738
No current signal · last broadcast 1d ago
Flights observed
210
Distinct callsigns
20
Country
LT
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 503E99.

Country allocation

The ICAO 24-bit address 503E99 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
GJM3327 - 32 2026-07-26
GJM3328 - 31 2026-07-26
GJT9NV - 11 2026-07-09
GJT25H - 11 2026-07-09
GJT96D - 10 2026-07-25
GJT2CJ Gestion Aerea Ajecutiva 10 2026-07-25
GJT73G - 7 2026-07-20
GJT8EH - 6 2026-06-20
GJT78G - 6 2026-07-03
GJT75C - 6 2026-07-12
GJT66T Gestion Aerea Ajecutiva 6 2026-07-03
GJT5WB - 6 2026-07-20
GJT57X - 6 2026-06-20
GJT4Q - 6 2026-07-12
GJT8AV - 5 2026-06-25
GJT7XU Gestion Aerea Ajecutiva 5 2026-05-28
GJT78Y - 5 2026-06-25
GJT44P - 5 2026-07-08
GJT2PZ - 5 2026-07-08
GJT7PN - 4 2026-07-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 GJM3328 - Jul 26, 16:30 UTCJul 26, 19:25 UTC2h 55m
2026-07-26 GJM3327 - Jul 26, 12:15 UTCJul 26, 14:55 UTC2h 40m
2026-07-25 GJM3328 - Jul 25, 16:45 UTCJul 25, 19:45 UTC3h 0m
2026-07-25 GJM3327 - Jul 25, 11:25 UTCJul 25, 14:05 UTC2h 40m
2026-07-25 GJT96D - Jul 25, 07:20 UTCJul 25, 10:10 UTC2h 50m
2026-07-25 GJT2CJ VNO → GPA Jul 25, 03:05 UTCJul 25, 05:15 UTC2h 10m
2026-07-21 GJM3328 KUN → VNO Jul 21, 12:00 UTCJul 21, 12:15 UTC15m
2026-07-21 GJM3328 - Jul 21, 07:30 UTCJul 21, 10:40 UTC3h 10m
2026-07-21 GJM3327 - Jul 21, 02:45 UTCJul 21, 05:35 UTC2h 50m
2026-07-20 GJT5WB - Jul 20, 17:55 UTCJul 20, 20:00 UTC2h 5m
2026-07-20 GJT73G - Jul 20, 12:20 UTCJul 20, 14:35 UTC2h 15m
2026-07-19 GJM3328 - Jul 19, 16:20 UTCJul 19, 19:05 UTC2h 45m
2026-07-19 GJM3327 - Jul 19, 11:55 UTCJul 19, 14:40 UTC2h 45m
2026-07-18 GJM3328 - Jul 18, 16:10 UTCJul 18, 19:00 UTC2h 50m
2026-07-18 GJM3327 - Jul 18, 11:30 UTCJul 18, 14:15 UTC2h 45m
2026-07-18 GJM3327 - Jul 18, 10:00 UTCJul 18, 10:40 UTC40m
2026-07-18 GJT96D - Jul 18, 07:10 UTCJul 18, 09:40 UTC2h 30m
2026-07-18 GJT2CJ VNO → GPA Jul 18, 03:00 UTCJul 18, 05:20 UTC2h 20m
2026-07-15 GJM3328 - Jul 15, 07:20 UTCJul 15, 10:20 UTC3h 0m
2026-07-15 GJM3327 - Jul 15, 03:05 UTCJul 15, 05:55 UTC2h 50m
2026-07-14 GJT7PN - Jul 14, 16:15 UTCJul 14, 17:50 UTC1h 35m
2026-07-14 GJT46R - Jul 14, 12:05 UTCJul 14, 14:25 UTC2h 20m
2026-07-14 GJM3328 - Jul 14, 07:15 UTCJul 14, 10:10 UTC2h 55m
2026-07-14 GJM3327 - Jul 14, 02:40 UTCJul 14, 05:35 UTC2h 55m
2026-07-13 GJT73G VNO → VNO Jul 13, 12:20 UTCJul 13, 18:30 UTC6h 10m
2026-07-12 GJM3328 - Jul 12, 16:15 UTCJul 12, 19:05 UTC2h 50m
2026-07-12 GJM3327 - Jul 12, 11:45 UTCJul 12, 14:40 UTC2h 55m
2026-07-12 GJT4Q - Jul 12, 07:05 UTCJul 12, 09:40 UTC2h 35m
2026-07-12 GJT75C - Jul 12, 03:15 UTCJul 12, 05:45 UTC2h 30m
2026-07-11 GJM3328 - Jul 11, 16:05 UTCJul 11, 18:50 UTC2h 45m
2026-07-11 GJM3327 - Jul 11, 11:35 UTCJul 11, 14:30 UTC2h 55m
2026-07-11 GJT96D - Jul 11, 07:00 UTCJul 11, 09:30 UTC2h 30m
2026-07-11 GJT2CJ - Jul 11, 03:01 UTCJul 11, 05:20 UTC2h 20m
2026-07-09 GJM3328 - Jul 9, 15:25 UTCJul 9, 18:30 UTC3h 5m
2026-07-09 GJM3327 - Jul 9, 11:20 UTCJul 9, 14:05 UTC2h 45m
2026-07-09 GJT9NV - Jul 9, 07:10 UTCJul 9, 10:15 UTC3h 5m
2026-07-09 GJT25H - Jul 9, 02:25 UTCJul 9, 05:25 UTC3h 0m
2026-07-08 GJT2PZ - Jul 8, 15:40 UTCJul 8, 17:50 UTC2h 10m
2026-07-08 GJT44P VNO → RMI Jul 8, 12:05 UTCJul 8, 14:10 UTC2h 5m
2026-07-08 GJM3328 - Jul 8, 07:25 UTCJul 8, 10:25 UTC3h 0m
2026-07-08 GJM3327 - Jul 8, 03:00 UTCJul 8, 05:45 UTC2h 45m
2026-07-07 GJT7PN - Jul 7, 15:25 UTCJul 7, 17:35 UTC2h 10m
2026-07-07 GJT46R VNO → BOJ Jul 7, 12:00 UTCJul 7, 14:20 UTC2h 20m
2026-07-07 GJM3328 - Jul 7, 07:20 UTCJul 7, 10:20 UTC3h 0m
2026-07-07 GJM3327 - Jul 7, 02:40 UTCJul 7, 05:30 UTC2h 50m
2026-07-06 GJT2XJ FNC → VNO Jul 6, 18:20 UTCJul 6, 23:25 UTC5h 5m
2026-07-06 GJT8VZ - Jul 6, 11:45 UTCJul 6, 16:05 UTC4h 20m
2026-07-06 GJT9NV - Jul 6, 07:10 UTCJul 6, 10:20 UTC3h 10m
2026-07-06 GJT25H - Jul 6, 02:25 UTCJul 6, 05:25 UTC3h 0m
2026-07-05 GJM3328 - Jul 5, 16:15 UTCJul 5, 19:05 UTC2h 50m

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

Mode-S 503E99 frequently asked

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