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
- Flights observed
- 91
- Distinct callsigns
- 20
- Country
- LT
- Last broadcast
- 6h ago
Last known position
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 | Nordic Solutions | 12 | 2026-06-01 |
| NVD8524 | Nordic Solutions | 11 | 2026-06-01 |
| NVD8530 | Nordic Solutions | 9 | 2026-06-02 |
| NVD8529 | Nordic Solutions | 8 | 2026-06-02 |
| MLH8321 | - | 6 | 2026-06-02 |
| NVD8652 | - | 4 | 2026-06-01 |
| NVD8651 | - | 4 | 2026-06-01 |
| MLH8322 | - | 4 | 2026-06-02 |
| MLH8346 | - | 2 | 2026-04-25 |
| MLH8345 | - | 2 | 2026-04-25 |
| MLH8344 | - | 2 | 2026-04-25 |
| MLH8343 | - | 2 | 2026-04-25 |
| MLH8342 | - | 2 | 2026-04-25 |
| MLH8341 | - | 2 | 2026-04-24 |
| MLH8332 | - | 2 | 2026-04-29 |
| NVD9530 | - | 1 | 2026-05-31 |
| NVD8703 | Nordic Solutions | 1 | 2026-04-19 |
| NVD8432 | Nordic Solutions | 1 | 2026-05-27 |
| NVD8431 | - | 1 | 2026-05-27 |
| NVD8322 | Nordic Solutions | 1 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | NVD8530 | AYT → VNO | Jun 2, 16:10 UTC | Jun 2, 19:25 UTC | 3h 15m |
| 2026-06-02 | NVD8529 | VNO → AYT | Jun 2, 11:35 UTC | Jun 2, 14:40 UTC | 3h 5m |
| 2026-06-02 | MLH8322 | - | Jun 2, 05:55 UTC | Jun 2, 08:55 UTC | 3h 0m |
| 2026-06-02 | MLH8321 | - | Jun 2, 01:35 UTC | Jun 2, 04:25 UTC | 2h 50m |
| 2026-06-01 | NVD8652 | - | Jun 1, 16:40 UTC | Jun 1, 19:35 UTC | 2h 55m |
| 2026-06-01 | NVD8651 | - | Jun 1, 11:50 UTC | Jun 1, 14:40 UTC | 2h 50m |
| 2026-06-01 | NVD8524 | AYT → VNO | Jun 1, 07:10 UTC | Jun 1, 10:20 UTC | 3h 10m |
| 2026-06-01 | NVD8523 | VNO → AYT | Jun 1, 02:55 UTC | Jun 1, 05:55 UTC | 3h 0m |
| 2026-05-31 | NVD8530 | AYT → VNO | May 31, 18:10 UTC | May 31, 21:20 UTC | 3h 10m |
| 2026-05-31 | NVD9530 | - | May 31, 15:15 UTC | May 31, 16:30 UTC | 1h 15m |
| 2026-05-31 | MLH8451 | VNO → BOJ | May 31, 11:40 UTC | May 31, 13:45 UTC | 2h 5m |
| 2026-05-30 | NVD8524 | AYT → VNO | May 30, 07:25 UTC | May 30, 10:40 UTC | 3h 15m |
| 2026-05-30 | NVD8523 | VNO → AYT | May 30, 02:45 UTC | May 30, 05:50 UTC | 3h 5m |
| 2026-05-29 | MLH8164 | BCN → VNO | May 29, 17:00 UTC | May 29, 20:05 UTC | 3h 5m |
| 2026-05-29 | MLH8163 | VNO → BCN | May 29, 12:20 UTC | May 29, 15:20 UTC | 3h 0m |
| 2026-05-29 | NVD8524 | AYT → VNO | May 29, 07:05 UTC | May 29, 10:25 UTC | 3h 20m |
| 2026-05-29 | NVD8523 | VNO → AYT | May 29, 02:45 UTC | May 29, 05:35 UTC | 2h 50m |
| 2026-05-28 | NVD8530 | AYT → VNO | May 28, 14:35 UTC | May 28, 17:55 UTC | 3h 20m |
| 2026-05-28 | NVD8529 | VNO → AYT | May 28, 10:15 UTC | May 28, 13:10 UTC | 2h 55m |
| 2026-05-28 | NVD8322 | HER → VNO | May 28, 05:30 UTC | May 28, 08:30 UTC | 3h 0m |
| 2026-05-28 | NVD8321 | VNO → HER | May 28, 01:15 UTC | May 28, 03:50 UTC | 2h 35m |
| 2026-05-27 | NVD8530 | AYT → VNO | May 27, 15:55 UTC | May 27, 19:05 UTC | 3h 10m |
| 2026-05-27 | NVD8529 | VNO → AYT | May 27, 11:35 UTC | May 27, 14:30 UTC | 2h 55m |
| 2026-05-27 | NVD8432 | TIV → VNO | May 27, 05:49 UTC | May 27, 07:50 UTC | 2h 1m |
| 2026-05-27 | NVD8431 | - | May 27, 02:39 UTC | May 27, 04:24 UTC | 1h 45m |
| 2026-05-26 | MLH8322 | - | May 26, 05:54 UTC | May 26, 08:50 UTC | 2h 55m |
| 2026-05-26 | MLH8321 | - | May 26, 01:30 UTC | May 26, 04:10 UTC | 2h 40m |
| 2026-05-25 | NVD8652 | - | May 25, 16:30 UTC | May 25, 19:30 UTC | 2h 59m |
| 2026-05-25 | NVD8651 | - | May 25, 11:55 UTC | May 25, 14:35 UTC | 2h 40m |
| 2026-05-25 | NVD8524 | AYT → VNO | May 25, 07:15 UTC | May 25, 10:25 UTC | 3h 10m |
| 2026-05-25 | NVD8523 | VNO → AYT | May 25, 02:50 UTC | May 25, 05:40 UTC | 2h 50m |
| 2026-05-24 | FHY389P | - | May 24, 14:10 UTC | May 24, 17:30 UTC | 3h 20m |
| 2026-05-24 | FHY1388 | PAD → AYT | May 24, 09:25 UTC | May 24, 12:45 UTC | 3h 20m |
| 2026-05-24 | FHY388P | - | May 24, 06:50 UTC | May 24, 07:35 UTC | 45m |
| 2026-05-19 | MLH9947 | VNO → BRU | May 19, 05:40 UTC | May 19, 07:40 UTC | 2h 0m |
| 2026-05-16 | MLH8322 | - | May 16, 16:40 UTC | May 16, 19:30 UTC | 2h 50m |
| 2026-05-16 | MLH8321 | - | May 16, 11:46 UTC | May 16, 14:55 UTC | 3h 10m |
| 2026-05-15 | NVD8524 | AYT → VNO | May 15, 07:15 UTC | May 15, 10:05 UTC | 2h 50m |
| 2026-05-15 | NVD8523 | VNO → AYT | May 15, 02:50 UTC | May 15, 05:50 UTC | 3h 0m |
| 2026-05-14 | NVD8530 | AYT → VNO | May 14, 14:40 UTC | May 14, 17:45 UTC | 3h 5m |
| 2026-05-14 | NVD8529 | VNO → AYT | May 14, 10:15 UTC | May 14, 13:15 UTC | 3h 0m |
| 2026-05-12 | NVD8530 | AYT → VNO | May 12, 16:00 UTC | May 12, 19:05 UTC | 3h 5m |
| 2026-05-12 | NVD8529 | VNO → AYT | May 12, 11:45 UTC | May 12, 14:40 UTC | 2h 55m |
| 2026-05-12 | MLH8322 | - | May 12, 05:50 UTC | May 12, 09:00 UTC | 3h 10m |
| 2026-05-12 | MLH8321 | - | May 12, 02:45 UTC | May 12, 04:25 UTC | 1h 40m |
| 2026-05-11 | NVD8652 | - | May 11, 16:30 UTC | May 11, 19:10 UTC | 2h 41m |
| 2026-05-11 | NVD8651 | - | May 11, 11:45 UTC | May 11, 14:55 UTC | 3h 10m |
| 2026-05-11 | NVD8524 | AYT → VNO | May 11, 07:05 UTC | May 11, 10:05 UTC | 3h 0m |
| 2026-05-11 | NVD8523 | VNO → AYT | May 11, 02:55 UTC | May 11, 05:50 UTC | 2h 55m |
| 2026-05-10 | NVD8530 | AYT → VNO | May 10, 15:55 UTC | May 10, 19:05 UTC | 3h 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-NVE page for operator, model, and routing details .