sensors Mode-S transponder

502D5E

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-ABM · AIRBUS A220-300

Hex
502D5E
Octal
24026536
Decimal
5,254,494
Country
LV
Tail
YL-ABM
Type
BCS3
No current signal · last broadcast 1h ago
Flights observed
307
Distinct callsigns
20
Country
LV
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 502D5E.

Country allocation

The ICAO 24-bit address 502D5E 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-30 BTI8TK CTA → RIX May 30, 16:15 UTCMay 30, 19:15 UTC3h 0m
2026-05-30 BTI7HT RIX → CTA May 30, 11:50 UTCMay 30, 14:50 UTC3h 0m
2026-05-30 BTI6RZ AMS → RIX May 30, 08:30 UTCMay 30, 10:15 UTC1h 45m
2026-05-30 BTI6RV RIX → AMS May 30, 04:55 UTCMay 30, 06:50 UTC1h 55m
2026-05-29 BTI7JW RIX → PLQ May 29, 21:40 UTCMay 29, 22:00 UTC20m
2026-05-29 BTI9YF CDG → RIX May 29, 17:35 UTCMay 29, 19:55 UTC2h 20m
2026-05-29 BTI84F RIX → CDG May 29, 13:50 UTCMay 29, 16:20 UTC2h 30m
2026-05-29 BTI69R CDG → RIX May 29, 08:30 UTCMay 29, 10:50 UTC2h 20m
2026-05-29 BTI8GJ RIX → CDG May 29, 04:25 UTCMay 29, 06:50 UTC2h 25m
2026-05-28 BTI3DV DUS → RIX May 28, 18:20 UTCMay 28, 20:05 UTC1h 45m
2026-05-28 BTI3TG RIX → DUS May 28, 15:40 UTCMay 28, 17:25 UTC1h 45m
2026-05-28 BTI1B6 CPH → RIX May 28, 12:30 UTCMay 28, 13:30 UTC1h 0m
2026-05-28 BTI1A5 RIX → CPH May 28, 10:20 UTCMay 28, 11:35 UTC1h 15m
2026-05-28 BTI8ED MUC → RIX May 28, 07:35 UTCMay 28, 09:25 UTC1h 50m
2026-05-28 BTI89G RIX → MUC May 28, 04:20 UTCMay 28, 06:10 UTC1h 50m
2026-05-27 BTI3DV DUS → RIX May 27, 18:30 UTCMay 27, 20:15 UTC1h 45m
2026-05-27 BTI3TG RIX → DUS May 27, 15:35 UTCMay 27, 17:30 UTC1h 55m
2026-05-27 BTI30E HEL → RIX May 27, 13:45 UTCMay 27, 14:25 UTC40m
2026-05-27 BTI30K RIX → HEL May 27, 11:40 UTCMay 27, 12:40 UTC1h 0m
2026-05-27 BTI8FX TIV → RIX May 27, 07:55 UTCMay 27, 10:20 UTC2h 25m
2026-05-27 BTI3EB RIX → TIV May 27, 04:24 UTCMay 27, 06:34 UTC2h 10m
2026-05-26 BTI11X ARN → RIX May 26, 18:30 UTCMay 26, 19:10 UTC40m
2026-05-26 BTI1X9 RIX → ARN May 26, 16:45 UTCMay 26, 17:44 UTC1h 0m
2026-05-26 BTI612 ATH → RIX May 26, 12:40 UTCMay 26, 15:39 UTC3h 0m
2026-05-26 BTI611 RIX → ATH May 26, 08:24 UTCMay 26, 11:15 UTC2h 50m
2026-05-26 BTI31T TLL → RIX May 26, 06:34 UTCMay 26, 07:05 UTC30m
2026-05-26 BTI31G RIX → TLL May 26, 05:00 UTCMay 26, 05:40 UTC40m
2026-05-25 BTI6UQ MUC → RIX May 25, 18:20 UTCMay 25, 20:15 UTC1h 55m
2026-05-25 BTI8BX RIX → MUC May 25, 15:15 UTCMay 25, 17:15 UTC2h 0m
2026-05-25 BTI8MT PRG → RIX May 25, 12:20 UTCMay 25, 13:55 UTC1h 35m
2026-05-25 BTI3VL RIX → PRG May 25, 09:50 UTCMay 25, 11:20 UTC1h 30m
2026-05-25 BTI25K HAM → RIX May 25, 06:55 UTCMay 25, 08:10 UTC1h 15m
2026-05-25 BTI8PW RIX → HAM May 25, 04:25 UTCMay 25, 05:55 UTC1h 30m
2026-05-24 BTI8GC ZRH → RIX May 24, 18:25 UTCMay 24, 20:35 UTC2h 10m
2026-05-24 BTI9AG RIX → ZRH May 24, 14:55 UTCMay 24, 17:00 UTC2h 5m
2026-05-24 BTI30E HEL → RIX May 24, 13:10 UTCMay 24, 13:50 UTC40m
2026-05-24 BTI30K RIX → HEL May 24, 11:20 UTCMay 24, 12:15 UTC55m
2026-05-24 BTI8FX TIV → RIX May 24, 07:30 UTCMay 24, 10:05 UTC2h 35m
2026-05-24 BTI3EB RIX → TIV May 24, 04:15 UTCMay 24, 06:10 UTC1h 55m
2026-05-24 BTI36V TLL → RIX May 24, 02:35 UTCMay 24, 03:10 UTC35m
2026-05-23 BTI3UB HER → TLL May 23, 19:35 UTCMay 23, 23:10 UTC3h 35m
2026-05-23 BTI34C TLL → HER May 23, 14:35 UTCMay 23, 17:55 UTC3h 20m
2026-05-23 BTI4VP PMI → TLL May 23, 08:10 UTCMay 23, 11:55 UTC3h 45m
2026-05-23 BTI6FU TLL → PMI May 23, 03:25 UTCMay 23, 07:00 UTC3h 35m
2026-05-22 BTI4ZK - May 22, 18:55 UTCMay 22, 19:30 UTC35m
2026-05-22 BTI8KT WAW → RIX May 22, 16:25 UTCMay 22, 17:25 UTC1h 0m
2026-05-22 BTI7KP RIX → WAW May 22, 14:40 UTCMay 22, 15:35 UTC55m
2026-05-22 BTI1B6 CPH → RIX May 22, 12:35 UTCMay 22, 13:35 UTC1h 0m
2026-05-22 BTI1A5 RIX → CPH May 22, 10:30 UTCMay 22, 11:40 UTC1h 10m
2026-05-22 BTI8ED MUC → RIX May 22, 07:40 UTCMay 22, 09:35 UTC1h 55m

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

Mode-S 502D5E frequently asked

What is Mode-S code 502D5E?
502D5E is an ICAO 24-bit transponder address. Allocated to Latvia. Assigned to YL-ABM.
Where is Mode-S 502D5E registered?
Mode-S code 502D5E is allocated to Latvia (LV). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 502D5E broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 502D5E, octal 24026536, decimal 5,254,494.
What flights does 502D5E operate?
Mode-S 502D5E has broadcast 20 distinct callsigns, including SWR1317, SWR4CA, SWR319V, SWR248Z, SWR2279.