sensors Mode-S transponder
503CC6
ICAO 24-bit transponder address · allocated to Lithuania
Currently assigned to LY-NOW · AIRBUS A-320
- Hex
- 503CC6
- Octal
- 24036306
- Decimal
- 5,258,438
- Country
- LT
- Tail
- LY-NOW
- Type
- A320
- Flights observed
- 42
- Distinct callsigns
- 20
- Country
- LT
- Last broadcast
- 59m ago
Last known position
Country allocation
The ICAO 24-bit address 503CC6 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 |
|---|---|---|---|
| GJT9901 | Gestion Aerea Ajecutiva | 3 | 2026-05-29 |
| EWG95P | Eurowings | 2 | 2026-05-14 |
| EWG7WB | - | 2 | 2026-04-16 |
| EWG6AZ | - | 2 | 2026-04-16 |
| EWG6900 | Eurowings | 2 | 2026-04-17 |
| EWG5SP | - | 2 | 2026-04-16 |
| EWG55E | Eurowings | 2 | 2026-04-16 |
| EWG2R | Eurowings | 2 | 2026-05-13 |
| EWG1GC | - | 2 | 2026-05-24 |
| UVL7464 | - | 1 | 2026-05-23 |
| UVL7463 | - | 1 | 2026-05-23 |
| UVL7462 | - | 1 | 2026-05-23 |
| UVL742P | - | 1 | 2026-05-24 |
| UVL741P | - | 1 | 2026-05-23 |
| TOM979P | TUI Airways | 1 | 2026-05-31 |
| TOM970P | TUI Airways | 1 | 2026-05-31 |
| TOM969P | TUI Airways | 1 | 2026-05-30 |
| TOM71V | TUI Airways | 1 | 2026-05-30 |
| TOM6677 | TUI Airways | 1 | 2026-05-31 |
| TOM5LT | TUI Airways | 1 | 2026-05-30 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | RZO3561 | - | Jun 2, 16:20 UTC | Jun 2, 18:55 UTC | 2h 35m |
| 2026-06-02 | RZO3560 | - | Jun 2, 12:30 UTC | Jun 2, 14:55 UTC | 2h 25m |
| 2026-06-01 | RZO3223 | PDL → BOS | Jun 1, 17:50 UTC | Jun 1, 18:20 UTC | 30m |
| 2026-06-01 | RZO3128 | - | Jun 1, 14:50 UTC | Jun 1, 15:55 UTC | 1h 5m |
| 2026-06-01 | RZO3127 | - | Jun 1, 09:50 UTC | Jun 1, 10:20 UTC | 30m |
| 2026-06-01 | RZO9127 | PDL → TER | Jun 1, 04:10 UTC | Jun 1, 08:25 UTC | 4h 15m |
| 2026-05-31 | TOM970P | GLA → MAN | May 31, 20:10 UTC | May 31, 22:45 UTC | 2h 35m |
| 2026-05-31 | TOM6677 | PFO → BRS | May 31, 14:10 UTC | May 31, 18:50 UTC | 4h 40m |
| 2026-05-31 | TOM979P | NCL → MAN | May 31, 08:25 UTC | May 31, 12:25 UTC | 4h 0m |
| 2026-05-30 | TOM1VK | IBZ → BHX | May 30, 19:45 UTC | May 30, 23:35 UTC | 3h 50m |
| 2026-05-30 | BY5648 | - | May 30, 14:30 UTC | May 30, 18:15 UTC | 3h 45m |
| 2026-05-30 | TOM5LT | IBZ → LGW | May 30, 10:10 UTC | May 30, 12:10 UTC | 2h 0m |
| 2026-05-30 | TOM71V | ZTH → BHX | May 30, 06:05 UTC | May 30, 07:50 UTC | 1h 45m |
| 2026-05-30 | TOM969P | BHX → BHX | May 30, 01:50 UTC | May 30, 04:30 UTC | 2h 40m |
| 2026-05-29 | GJT9901 | CAY → PLS | May 29, 16:10 UTC | May 29, 16:35 UTC | 25m |
| 2026-05-28 | GJT9901 | CAY → PLS | May 28, 10:25 UTC | May 28, 11:45 UTC | 1h 20m |
| 2026-05-24 | EWG1GC | OPO → HAM | May 24, 17:55 UTC | May 24, 20:35 UTC | 2h 40m |
| 2026-05-24 | EWG1GC | HAM → OPO | May 24, 13:55 UTC | May 24, 16:30 UTC | 2h 35m |
| 2026-05-24 | UVL742P | BRN → HAM | May 24, 05:45 UTC | May 24, 07:00 UTC | 1h 15m |
| 2026-05-23 | UVL7464 | - | May 23, 12:50 UTC | May 23, 14:10 UTC | 1h 20m |
| 2026-05-23 | UVL7463 | - | May 23, 11:30 UTC | May 23, 11:40 UTC | 10m |
| 2026-05-23 | UVL7462 | BRN → JER | May 23, 09:05 UTC | May 23, 10:20 UTC | 1h 15m |
| 2026-05-23 | UVL741P | - | May 23, 05:30 UTC | May 23, 07:30 UTC | 2h 0m |
| 2026-05-16 | GJT9902 | - | May 16, 12:01 UTC | May 16, 13:15 UTC | 1h 15m |
| 2026-05-15 | EWG84H | - | May 15, 12:40 UTC | May 15, 15:45 UTC | 3h 4m |
| 2026-05-15 | EWG5H | DUS → IBZ | May 15, 08:35 UTC | May 15, 11:30 UTC | 2h 55m |
| 2026-05-14 | EWG95P | MAN → MAN | May 14, 09:55 UTC | May 14, 13:15 UTC | 3h 20m |
| 2026-05-14 | EWG95P | MAN → MAN | May 14, 04:50 UTC | May 14, 08:10 UTC | 3h 20m |
| 2026-05-13 | EWG2R | HAM → DUS | May 13, 18:45 UTC | May 13, 20:05 UTC | 1h 20m |
| 2026-05-13 | EWG2R | HAM → DUS | May 13, 16:15 UTC | May 13, 17:45 UTC | 1h 30m |
| 2026-05-13 | GJT9901 | CAY → PLS | May 13, 12:25 UTC | May 13, 13:45 UTC | 1h 20m |
| 2026-04-17 | EWG6900 | STR → VIE | Apr 17, 09:20 UTC | Apr 17, 09:55 UTC | 35m |
| 2026-04-17 | EWG6900 | STR → VIE | Apr 17, 08:35 UTC | Apr 17, 09:15 UTC | 40m |
| 2026-04-16 | EWG6AZ | - | Apr 16, 19:15 UTC | Apr 16, 20:50 UTC | 1h 35m |
| 2026-04-16 | EWG6AZ | - | Apr 16, 17:50 UTC | Apr 16, 19:10 UTC | 1h 20m |
| 2026-04-16 | EWG7WB | - | Apr 16, 15:15 UTC | Apr 16, 16:25 UTC | 1h 10m |
| 2026-04-16 | EWG7WB | - | Apr 16, 13:20 UTC | Apr 16, 15:10 UTC | 1h 50m |
| 2026-04-16 | EWG55E | LHR → DUS | Apr 16, 11:09 UTC | Apr 16, 12:00 UTC | 50m |
| 2026-04-16 | EWG55E | LHR → DUS | Apr 16, 09:39 UTC | Apr 16, 11:04 UTC | 1h 25m |
| 2026-04-16 | EWG5SP | - | Apr 16, 07:09 UTC | Apr 16, 08:15 UTC | 1h 5m |
| 2026-04-16 | EWG5SP | - | Apr 16, 05:45 UTC | Apr 16, 07:05 UTC | 1h 20m |
| 2026-04-15 | EWG6906 | CGN → STR | Apr 15, 17:55 UTC | Apr 15, 19:00 UTC | 1h 5m |
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-NOW page for operator, model, and routing details .