sensors Mode-S transponder

503D00

ICAO 24-bit transponder address · allocated to Lithuania

Currently assigned to LY-NVE · AIRBUS A-320

Hex
503D00
Octal
24036400
Decimal
5,258,496
Country
LT
Tail
LY-NVE
Type
A320
No current signal · last broadcast 10h ago
Flights observed
192
Distinct callsigns
20
Country
LT
Last broadcast
10h ago

Last known position

Most recent position reported by Mode-S 503D00.

Country allocation

The ICAO 24-bit address 503D00 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
NVD8523 - 18 2026-07-06
NVD8530 - 16 2026-07-07
NVD8524 - 16 2026-07-06
NVD8529 - 14 2026-07-07
MLH8321 - 14 2026-07-07
MLH8322 - 12 2026-07-07
NVD8652 - 8 2026-07-06
NVD8651 - 8 2026-07-06
MLH8451 - 8 2026-07-01
MLH8452 - 6 2026-07-01
MLH8164 - 5 2026-06-26
MLH8163 - 5 2026-06-26
NVD8322 Nordic Solutions 4 2026-06-25
NVD8321 Nordic Solutions 4 2026-06-25
NVD8432 Nordic Solutions 3 2026-07-01
NVD8431 - 3 2026-07-01
NVD9530 - 2 2026-06-10
MLH8346 - 2 2026-04-25
MLH8345 - 2 2026-04-25
MLH8344 - 2 2026-04-25

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 FIE584 - Jul 17, 16:59 UTCJul 17, 17:25 UTC25m
2026-07-17 FIE583 - Jul 17, 15:20 UTCJul 17, 15:44 UTC25m
2026-07-17 FIE7491 - Jul 17, 06:15 UTCJul 17, 12:00 UTC5h 45m
2026-07-15 FIE248 - Jul 15, 18:55 UTCJul 15, 22:10 UTC3h 15m
2026-07-15 FIE247 - Jul 15, 13:50 UTCJul 15, 17:40 UTC3h 50m
2026-07-13 FIE878 - Jul 13, 16:55 UTCJul 13, 17:30 UTC35m
2026-07-13 FIE872 - Jul 13, 08:20 UTCJul 13, 15:40 UTC7h 20m
2026-07-13 FIE871 - Jul 13, 05:31 UTCJul 13, 07:05 UTC1h 35m
2026-07-12 FIE248 - Jul 12, 20:40 UTCJul 12, 22:50 UTC2h 10m
2026-07-12 FIE247 - Jul 12, 15:01 UTCJul 12, 18:45 UTC3h 45m
2026-07-11 FIE878 - Jul 11, 16:35 UTCJul 11, 17:00 UTC25m
2026-07-11 FIE877 - Jul 11, 13:40 UTCJul 11, 15:15 UTC1h 35m
2026-07-11 NVD9991 - Jul 11, 06:20 UTCJul 11, 08:45 UTC2h 25m
2026-07-07 NVD8530 - Jul 7, 16:00 UTCJul 7, 19:10 UTC3h 10m
2026-07-07 NVD8529 - Jul 7, 11:45 UTCJul 7, 14:45 UTC3h 0m
2026-07-07 MLH8322 - Jul 7, 05:50 UTCJul 7, 08:45 UTC2h 55m
2026-07-07 MLH8321 - Jul 7, 01:35 UTCJul 7, 04:20 UTC2h 45m
2026-07-06 NVD8652 - Jul 6, 16:20 UTCJul 6, 19:25 UTC3h 5m
2026-07-06 NVD8651 - Jul 6, 11:55 UTCJul 6, 14:40 UTC2h 45m
2026-07-06 NVD8524 - Jul 6, 07:05 UTCJul 6, 10:10 UTC3h 5m
2026-07-06 NVD8523 - Jul 6, 02:40 UTCJul 6, 05:35 UTC2h 55m
2026-07-01 MLH8452 BOJ → VNO Jul 1, 15:30 UTCJul 1, 17:35 UTC2h 5m
2026-07-01 MLH8451 VNO → BOJ Jul 1, 11:45 UTCJul 1, 14:10 UTC2h 25m
2026-07-01 NVD8432 TIV → VNO Jul 1, 06:05 UTCJul 1, 08:00 UTC1h 55m
2026-07-01 NVD8431 - Jul 1, 02:45 UTCJul 1, 04:40 UTC1h 55m
2026-06-30 TRA083 AMS → AMS Jun 30, 23:55 UTCJul 1, 01:35 UTC1h 40m
2026-06-30 TRA73F - Jun 30, 20:20 UTCJun 30, 22:30 UTC2h 10m
2026-06-30 TRA38K - Jun 30, 17:10 UTCJun 30, 19:15 UTC2h 5m
2026-06-29 TRA83L - Jun 29, 19:20 UTCJun 29, 21:50 UTC2h 30m
2026-06-29 TRA5791 - Jun 29, 14:44 UTCJun 29, 16:59 UTC2h 15m
2026-06-28 TRA4W - Jun 28, 15:44 UTCJun 28, 17:55 UTC2h 10m
2026-06-28 TRA6G AMS → ALC Jun 28, 11:59 UTCJun 28, 14:25 UTC2h 25m
2026-06-28 TRA082 - Jun 28, 06:55 UTCJun 28, 08:55 UTC2h 0m
2026-06-27 MLH8322 - Jun 27, 16:30 UTCJun 27, 19:15 UTC2h 45m
2026-06-27 MLH8321 - Jun 27, 11:55 UTCJun 27, 14:39 UTC2h 45m
2026-06-26 MLH8164 BCN → VNO Jun 26, 17:04 UTCJun 26, 20:04 UTC3h 0m
2026-06-26 MLH8163 VNO → BCN Jun 26, 12:10 UTCJun 26, 15:10 UTC3h 0m
2026-06-25 NVD8530 - Jun 25, 14:24 UTCJun 25, 17:30 UTC3h 5m
2026-06-25 NVD8529 - Jun 25, 10:04 UTCJun 25, 13:00 UTC2h 55m
2026-06-25 NVD8322 HER → VNO Jun 25, 05:35 UTCJun 25, 08:24 UTC2h 50m
2026-06-25 NVD8321 VNO → HER Jun 25, 00:59 UTCJun 25, 03:44 UTC2h 45m
2026-06-24 MLH8452 - Jun 24, 15:14 UTCJun 24, 17:29 UTC2h 15m
2026-06-24 MLH8451 - Jun 24, 11:45 UTCJun 24, 14:00 UTC2h 15m
2026-06-23 MLH8322 - Jun 23, 05:59 UTCJun 23, 08:54 UTC2h 55m
2026-06-23 MLH8321 - Jun 23, 01:30 UTCJun 23, 04:19 UTC2h 50m
2026-06-22 NVD8652 NBE → VNO Jun 22, 16:20 UTCJun 22, 19:19 UTC3h 0m
2026-06-22 NVD8651 VNO → NBE Jun 22, 11:54 UTCJun 22, 15:05 UTC3h 10m
2026-06-21 MLH8452 BOJ → VNO Jun 21, 15:05 UTCJun 21, 17:10 UTC2h 5m
2026-06-21 MLH8451 VNO → BOJ Jun 21, 11:40 UTCJun 21, 13:59 UTC2h 20m
2026-06-20 MLH8322 - Jun 20, 16:24 UTCJun 20, 17:59 UTC1h 35m

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

Mode-S 503D00 frequently asked

What is Mode-S code 503D00?
503D00 is an ICAO 24-bit transponder address. Allocated to Lithuania. Assigned to LY-NVE.
Where is Mode-S 503D00 registered?
Mode-S code 503D00 is allocated to Lithuania (LT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 503D00 broadcasting right now?
No active broadcast right now. Last signal was 10h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 503D00, octal 24036400, decimal 5,258,496.
What flights does 503D00 operate?
Mode-S 503D00 has broadcast 20 distinct callsigns, including NVD8523, NVD8530, NVD8524, NVD8529, MLH8321.