sensors Mode-S transponder

503CF5

ICAO 24-bit transponder address · allocated to Lithuania

Currently assigned to LY-DAE · AIRBUS A-320

Hex
503CF5
Octal
24036365
Decimal
5,258,485
Country
LT
Tail
LY-DAE
Type
A320
Broadcasting now · callsign EWG7SV · 35,025 ft
Flights observed
439
Distinct callsigns
20
Country
LT
Last broadcast
44m ago

Current position

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

Country allocation

The ICAO 24-bit address 503CF5 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
EWG84A - 27 2026-07-03
EWG5AB - 25 2026-07-01
EWG98Q - 24 2026-07-12
EWG8EM - 23 2026-07-12
EWG10E - 21 2026-07-13
EWG84T - 18 2026-07-04
EWG9H - 16 2026-07-13
EWG92F - 16 2026-07-01
EWG7VN - 14 2026-07-09
EWG60H - 12 2026-06-30
EWG2AR Eurowings 12 2026-06-27
EWG5PD - 11 2026-06-30
EWG1GC - 11 2026-07-05
EWG18N Eurowings 11 2026-04-26
EWG8M - 10 2026-06-17
EWG6NA - 10 2026-06-26
EWG48K Eurowings 10 2026-06-19
EWG39U - 10 2026-07-13
EWG1E - 10 2026-07-13
EWG7PQ - 9 2026-06-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 EWG7SV - Jul 14, 04:05 UTCJul 14, 05:15 UTC1h 10m
2026-07-13 EWG9H ZRH → HAM Jul 13, 18:45 UTCJul 13, 20:05 UTC1h 20m
2026-07-13 EWG9H - Jul 13, 16:40 UTCJul 13, 17:45 UTC1h 5m
2026-07-13 EWG39U - Jul 13, 13:25 UTCJul 13, 15:40 UTC2h 15m
2026-07-13 EWG1E - Jul 13, 10:00 UTCJul 13, 12:20 UTC2h 20m
2026-07-13 EWG10E MXP → HAM Jul 13, 07:25 UTCJul 13, 08:45 UTC1h 20m
2026-07-13 EWG10E HAM → MXP Jul 13, 05:01 UTCJul 13, 06:25 UTC1h 25m
2026-07-12 EWG11ZA FAO → HAM Jul 12, 17:25 UTCJul 12, 20:25 UTC3h 0m
2026-07-12 EWG98Q HAM → FAO Jul 12, 12:55 UTCJul 12, 16:15 UTC3h 20m
2026-07-12 EWG8EM - Jul 12, 08:35 UTCJul 12, 11:35 UTC3h 0m
2026-07-12 EWG8EM - Jul 12, 04:15 UTCJul 12, 07:10 UTC2h 55m
2026-07-11 EWG6VJ - Jul 11, 18:10 UTCJul 11, 20:30 UTC2h 20m
2026-07-11 EWG7NB - Jul 11, 14:45 UTCJul 11, 17:00 UTC2h 15m
2026-07-11 EWG8EM - Jul 11, 09:05 UTCJul 11, 12:20 UTC3h 15m
2026-07-11 EWG8EM - Jul 11, 04:40 UTCJul 11, 07:30 UTC2h 50m
2026-07-10 EWG2R MXP → HAM Jul 10, 19:40 UTCJul 10, 21:05 UTC1h 25m
2026-07-10 EWG2R - Jul 10, 16:55 UTCJul 10, 18:35 UTC1h 40m
2026-07-09 EWG7VN VIE → HAM Jul 9, 18:20 UTCJul 9, 19:35 UTC1h 15m
2026-07-09 EWG7VN - Jul 9, 15:55 UTCJul 9, 17:10 UTC1h 15m
2026-07-08 EWG55P - Jul 8, 17:55 UTCJul 8, 20:35 UTC2h 40m
2026-07-08 EWG55P - Jul 8, 14:40 UTCJul 8, 16:45 UTC2h 5m
2026-07-08 EWG32G - Jul 8, 08:50 UTCJul 8, 10:50 UTC2h 0m
2026-07-08 EWG32G - Jul 8, 05:45 UTCJul 8, 07:20 UTC1h 35m
2026-07-07 EWG90Y - Jul 7, 15:35 UTCJul 7, 19:00 UTC3h 25m
2026-07-07 EWG90Y HAM → KGS Jul 7, 11:25 UTCJul 7, 14:15 UTC2h 50m
2026-07-07 EWG6ND IBZ → HAM Jul 7, 07:45 UTCJul 7, 10:20 UTC2h 35m
2026-07-07 EWG7SV HAM → IBZ Jul 7, 04:05 UTCJul 7, 06:35 UTC2h 30m
2026-07-06 EWG90Y - Jul 6, 16:00 UTCJul 6, 19:15 UTC3h 15m
2026-07-06 EWG90Y HAM → KGS Jul 6, 11:40 UTCJul 6, 14:45 UTC3h 5m
2026-07-06 EWG10E MXP → HAM Jul 6, 07:50 UTCJul 6, 09:15 UTC1h 25m
2026-07-06 EWG10E HAM → MXP Jul 6, 05:05 UTCJul 6, 06:30 UTC1h 25m
2026-07-05 EWG1GC OPO → HAM Jul 5, 17:45 UTCJul 5, 20:20 UTC2h 35m
2026-07-05 EWG1GC HAM → OPO Jul 5, 13:50 UTCJul 5, 16:40 UTC2h 50m
2026-07-05 EWG8EM - Jul 5, 08:50 UTCJul 5, 11:55 UTC3h 5m
2026-07-05 EWG8EM - Jul 5, 04:25 UTCJul 5, 07:10 UTC2h 45m
2026-07-04 EWG84T ZRH → HAM Jul 4, 13:10 UTCJul 4, 14:20 UTC1h 10m
2026-07-04 EWG84T HAM → ZRH Jul 4, 11:05 UTCJul 4, 12:10 UTC1h 5m
2026-07-04 EWG2RY - Jul 4, 07:40 UTCJul 4, 09:55 UTC2h 15m
2026-07-04 EWG2RY - Jul 4, 04:25 UTCJul 4, 06:10 UTC1h 45m
2026-07-03 EWG6M MAN → HAM Jul 3, 19:25 UTCJul 3, 20:35 UTC1h 10m
2026-07-03 EWG6M HAM → MAN Jul 3, 17:00 UTCJul 3, 18:30 UTC1h 30m
2026-07-03 EWG84H - Jul 3, 12:50 UTCJul 3, 15:55 UTC3h 5m
2026-07-03 EWG5H - Jul 3, 08:50 UTCJul 3, 11:45 UTC2h 55m
2026-07-03 EWG84A - Jul 3, 06:40 UTCJul 3, 07:45 UTC1h 5m
2026-07-03 EWG84A - Jul 3, 04:40 UTCJul 3, 05:40 UTC1h 0m
2026-07-02 EWG7VN VIE → HAM Jul 2, 18:05 UTCJul 2, 19:20 UTC1h 15m
2026-07-02 EWG7VN HAM → VIE Jul 2, 15:50 UTCJul 2, 17:05 UTC1h 15m
2026-07-02 EWG3W DUS → BHX Jul 2, 10:45 UTCJul 2, 12:40 UTC1h 55m
2026-07-02 EWG3W DUS → BHX Jul 2, 04:15 UTCJul 2, 06:00 UTC1h 45m
2026-07-01 EWG92F CDG → HAM Jul 1, 19:30 UTCJul 1, 20:45 UTC1h 15m

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

Mode-S 503CF5 frequently asked

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