sensors Mode-S transponder
503FD0
ICAO 24-bit transponder address · allocated to Lithuania
Currently assigned to 01 BLUE · LET L-410 Turbolet
- Hex
- 503FD0
- Octal
- 24037720
- Decimal
- 5,259,216
- Country
- LT
- Tail
- 01 BLUE
- Type
- L410
- Flights observed
- 63
- Distinct callsigns
- 3
- Country
- LT
- Last broadcast
- 28d ago
Last known position
Country allocation
The ICAO 24-bit address 503FD0 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 3 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-19 | LYF468 | - | Jun 19, 12:59 UTC | Jun 19, 13:34 UTC | 35m |
| 2026-06-19 | LYF468 | - | Jun 19, 11:30 UTC | Jun 19, 12:25 UTC | 55m |
| 2026-06-19 | LYF468 | - | Jun 19, 10:04 UTC | Jun 19, 10:29 UTC | 25m |
| 2026-06-19 | LYF468 | - | Jun 19, 07:14 UTC | Jun 19, 08:40 UTC | 1h 25m |
| 2026-06-18 | LYF468 | - | Jun 18, 12:20 UTC | Jun 18, 14:10 UTC | 1h 50m |
| 2026-06-18 | LYF468 | - | Jun 18, 09:45 UTC | Jun 18, 11:10 UTC | 1h 25m |
| 2026-06-18 | LYF468 | - | Jun 18, 06:30 UTC | Jun 18, 09:05 UTC | 2h 35m |
| 2026-06-17 | LYF01 | - | Jun 17, 10:50 UTC | Jun 17, 12:40 UTC | 1h 50m |
| 2026-06-17 | LYF01 | - | Jun 17, 07:10 UTC | Jun 17, 09:10 UTC | 2h 0m |
| 2026-06-10 | LYF345 | - | Jun 10, 12:50 UTC | Jun 10, 14:40 UTC | 1h 50m |
| 2026-06-09 | LYF345 | - | Jun 9, 21:05 UTC | Jun 9, 21:35 UTC | 30m |
| 2026-06-09 | LYF345 | TLL → VNO | Jun 9, 20:00 UTC | Jun 9, 21:00 UTC | 1h 0m |
| 2026-06-08 | LYF345 | VNO → TLL | Jun 8, 13:40 UTC | Jun 8, 15:30 UTC | 1h 50m |
| 2026-06-08 | LYF345 | - | Jun 8, 10:30 UTC | Jun 8, 11:10 UTC | 40m |
| 2026-06-05 | LYF345 | - | Jun 5, 09:15 UTC | Jun 5, 11:25 UTC | 2h 10m |
| 2026-06-02 | LYF345 | - | Jun 2, 12:10 UTC | Jun 2, 13:00 UTC | 50m |
| 2026-06-02 | LYF345 | - | Jun 2, 10:55 UTC | Jun 2, 11:15 UTC | 20m |
| 2026-06-02 | LYF345 | - | Jun 2, 09:20 UTC | Jun 2, 09:45 UTC | 25m |
| 2026-06-02 | LYF345 | - | Jun 2, 07:10 UTC | Jun 2, 08:15 UTC | 1h 5m |
| 2026-06-01 | LYF345 | - | Jun 1, 12:40 UTC | Jun 1, 13:25 UTC | 45m |
| 2026-06-01 | LYF345 | - | Jun 1, 11:05 UTC | Jun 1, 11:25 UTC | 20m |
| 2026-06-01 | LYF345 | - | Jun 1, 09:35 UTC | Jun 1, 09:55 UTC | 20m |
| 2026-06-01 | LYF345 | - | Jun 1, 07:05 UTC | Jun 1, 08:15 UTC | 1h 10m |
| 2026-05-29 | LYF345 | - | May 29, 16:15 UTC | May 29, 17:00 UTC | 45m |
| 2026-05-29 | LYF345 | - | May 29, 14:00 UTC | May 29, 15:40 UTC | 1h 40m |
| 2026-05-29 | LYF345 | - | May 29, 10:35 UTC | May 29, 11:35 UTC | 1h 0m |
| 2026-05-28 | LYF345 | - | May 28, 15:10 UTC | May 28, 15:25 UTC | 15m |
| 2026-05-27 | LYF345 | - | May 27, 06:04 UTC | May 27, 07:45 UTC | 1h 40m |
| 2026-05-25 | LYF345 | - | May 25, 10:20 UTC | May 25, 11:10 UTC | 50m |
| 2026-05-25 | LYF345 | - | May 25, 09:00 UTC | May 25, 09:25 UTC | 25m |
| 2026-05-25 | LYF345 | - | May 25, 07:50 UTC | May 25, 08:10 UTC | 20m |
| 2026-05-25 | LYF345 | - | May 25, 06:10 UTC | May 25, 07:20 UTC | 1h 10m |
| 2026-05-17 | LYF468 | - | May 17, 09:05 UTC | May 17, 10:05 UTC | 1h 0m |
| 2026-05-13 | LYF01 | - | May 13, 10:45 UTC | May 13, 12:50 UTC | 2h 5m |
| 2026-05-12 | LYF01 | - | May 12, 11:55 UTC | May 12, 12:50 UTC | 55m |
| 2026-05-12 | LYF01 | - | May 12, 11:30 UTC | May 12, 11:45 UTC | 15m |
| 2026-05-12 | LYF01 | - | May 12, 11:00 UTC | May 12, 11:25 UTC | 25m |
| 2026-05-12 | LYF01 | - | May 12, 07:10 UTC | May 12, 09:30 UTC | 2h 20m |
| 2026-05-11 | LYF01 | - | May 11, 12:50 UTC | May 11, 13:00 UTC | 10m |
| 2026-05-11 | LYF01 | - | May 11, 11:50 UTC | May 11, 12:20 UTC | 30m |
| 2026-05-06 | LYF468 | - | May 6, 12:15 UTC | May 6, 13:00 UTC | 45m |
| 2026-05-06 | LYF468 | - | May 6, 11:20 UTC | May 6, 11:40 UTC | 20m |
| 2026-05-06 | LYF468 | - | May 6, 09:20 UTC | May 6, 10:30 UTC | 1h 10m |
| 2026-05-06 | LYF468 | - | May 6, 06:55 UTC | May 6, 08:50 UTC | 1h 55m |
| 2026-04-22 | LYF345 | - | Apr 22, 13:35 UTC | Apr 22, 14:20 UTC | 45m |
| 2026-04-22 | LYF345 | - | Apr 22, 12:25 UTC | Apr 22, 12:50 UTC | 25m |
| 2026-04-22 | LYF345 | - | Apr 22, 11:15 UTC | Apr 22, 11:35 UTC | 20m |
| 2026-04-22 | LYF345 | - | Apr 22, 10:15 UTC | Apr 22, 10:40 UTC | 25m |
| 2026-04-22 | LYF345 | - | Apr 22, 09:05 UTC | Apr 22, 09:30 UTC | 25m |
| 2026-04-22 | LYF345 | - | Apr 22, 07:10 UTC | Apr 22, 08:25 UTC | 1h 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 01 BLUE page for operator, model, and routing details .