sensors Mode-S transponder

502D23

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-AAU · AIRBUS A220-300

Hex
502D23
Octal
24026443
Decimal
5,254,435
Country
LV
Tail
YL-AAU
Type
BCS3
No current signal · last broadcast 10h ago
Flights observed
296
Distinct callsigns
20
Country
LV
Last broadcast
10h ago

Last known position

Most recent position reported by Mode-S 502D23.

Country allocation

The ICAO 24-bit address 502D23 falls within the block assigned to Latvia (LV) by ICAO Annex 10, Volume III. Every aircraft registered in Latvia 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 BTI72X BER → TLL May 29, 13:05 UTCMay 29, 14:45 UTC1h 40m
2026-05-29 BTI3BP TLL → BER May 29, 10:40 UTCMay 29, 12:10 UTC1h 30m
2026-05-29 BTI4ZC VIE → TLL May 29, 07:40 UTCMay 29, 09:50 UTC2h 10m
2026-05-29 BTI7HA TLL → VIE May 29, 04:15 UTCMay 29, 06:05 UTC1h 50m
2026-05-28 BTI36D RIX → TLL May 28, 20:55 UTCMay 28, 21:35 UTC40m
2026-05-28 BTI6BM LGW → RIX May 28, 16:50 UTCMay 28, 19:10 UTC2h 20m
2026-05-28 BTI6BL RIX → LGW May 28, 13:05 UTCMay 28, 15:45 UTC2h 40m
2026-05-28 BTI69R CDG → RIX May 28, 08:35 UTCMay 28, 11:00 UTC2h 25m
2026-05-28 BTI8GJ RIX → CDG May 28, 04:35 UTCMay 28, 07:00 UTC2h 25m
2026-05-28 BTI3WX TKU → RIX May 28, 02:35 UTCMay 28, 03:20 UTC45m
2026-05-27 BTI3U9 RIX → TKU May 27, 21:10 UTCMay 27, 21:50 UTC40m
2026-05-27 BTI15L OSL → RIX May 27, 18:55 UTCMay 27, 20:05 UTC1h 10m
2026-05-27 BTI15M RIX → OSL May 27, 16:35 UTCMay 27, 17:55 UTC1h 20m
2026-05-27 BTI696 NCE → RIX May 27, 10:30 UTCMay 27, 10:50 UTC20m
2026-05-27 BTI696 NCE → RIX May 27, 08:10 UTCMay 27, 10:00 UTC1h 50m
2026-05-27 BTI695 RIX → NCE May 27, 04:19 UTCMay 27, 07:05 UTC2h 46m
2026-05-26 BTI716 AYT → RIX May 26, 17:44 UTCMay 26, 21:20 UTC3h 35m
2026-05-26 BTI715 RIX → AYT May 26, 13:04 UTCMay 26, 16:15 UTC3h 10m
2026-05-26 BTI31J TLL → RIX May 26, 11:20 UTCMay 26, 11:54 UTC35m
2026-05-26 BTI9UG AMS → TLL May 26, 08:30 UTCMay 26, 10:25 UTC1h 55m
2026-05-26 BTI8FH TLL → AMS May 26, 04:39 UTCMay 26, 06:54 UTC2h 15m
2026-05-25 BTI9UZ VNO → TLL May 25, 19:40 UTCMay 25, 20:40 UTC1h 0m
2026-05-25 BTI6EY TLL → VNO May 25, 18:00 UTCMay 25, 18:50 UTC50m
2026-05-25 BTI4WA NCE → TLL May 25, 14:55 UTCMay 25, 17:05 UTC2h 10m
2026-05-25 BTI4WA NCE → TLL May 25, 14:10 UTCMay 25, 14:50 UTC40m
2026-05-25 BTI8LM TLL → NCE May 25, 09:45 UTCMay 25, 12:50 UTC3h 5m
2026-05-25 BTI31G RIX → TLL May 25, 05:00 UTCMay 25, 05:35 UTC35m
2026-05-24 BTI6C4 BRU → RIX May 24, 18:00 UTCMay 24, 20:05 UTC2h 5m
2026-05-24 BEL2WM BLQ → BRU May 24, 14:35 UTCMay 24, 16:05 UTC1h 30m
2026-05-24 BEL5NZ BRU → BLQ May 24, 11:55 UTCMay 24, 13:15 UTC1h 20m
2026-05-24 BEL4QA VIE → BRU May 24, 07:30 UTCMay 24, 09:00 UTC1h 30m
2026-05-24 BEL5RA BRU → VIE May 24, 05:05 UTCMay 24, 06:30 UTC1h 25m
2026-05-23 BEL6DN GVA → BRU May 23, 19:00 UTCMay 23, 21:15 UTC2h 15m
2026-05-23 BEL4AR BRU → ALC May 23, 15:40 UTCMay 23, 17:40 UTC2h 0m
2026-05-23 BEL9SW MUC → BRU May 23, 13:25 UTCMay 23, 14:25 UTC1h 0m
2026-05-23 BEL7LF BRU → MUC May 23, 11:05 UTCMay 23, 12:00 UTC55m
2026-05-23 BEL4QA VIE → BRU May 23, 07:40 UTCMay 23, 09:00 UTC1h 20m
2026-05-23 BEL5RA BRU → VIE May 23, 05:10 UTCMay 23, 06:40 UTC1h 30m
2026-05-22 BEL7JN BCN → BRU May 22, 20:25 UTCMay 22, 22:10 UTC1h 45m
2026-05-22 BEL3FJ BRU → BCN May 22, 16:45 UTCMay 22, 18:30 UTC1h 45m
2026-05-22 BEL5EF FRA → BRU May 22, 14:45 UTCMay 22, 15:20 UTC35m
2026-05-22 BEL2SR BRU → FRA May 22, 12:45 UTCMay 22, 13:15 UTC30m
2026-05-22 BEL2JE CPH → BRU May 22, 10:25 UTCMay 22, 11:40 UTC1h 15m
2026-05-22 BEL1ZT BRU → CPH May 22, 07:55 UTCMay 22, 09:10 UTC1h 15m
2026-05-22 BEL94L LYS → BRU May 22, 05:15 UTCMay 22, 06:20 UTC1h 5m
2026-05-21 BEL3LY BRU → LYS May 21, 19:20 UTCMay 21, 20:20 UTC1h 0m
2026-05-21 BEL6HI LJU → BRU May 21, 16:40 UTCMay 21, 18:00 UTC1h 20m
2026-05-21 BEL7PK BRU → LJU May 21, 14:25 UTCMay 21, 15:40 UTC1h 15m
2026-05-21 BEL4SF LYS → BRU May 21, 11:30 UTCMay 21, 12:35 UTC1h 5m
2026-05-21 BEL3JY BRU → LYS May 21, 09:25 UTCMay 21, 10:25 UTC1h 0m

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

Mode-S 502D23 frequently asked

What is Mode-S code 502D23?
502D23 is an ICAO 24-bit transponder address. Allocated to Latvia. Assigned to YL-AAU.
Where is Mode-S 502D23 registered?
Mode-S code 502D23 is allocated to Latvia (LV). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 502D23 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 502D23, octal 24026443, decimal 5,254,435.
What flights does 502D23 operate?
Mode-S 502D23 has broadcast 20 distinct callsigns, including BTI6D9, BTI62D, BTI8GJ, BTI762, BTI761.