sensors Mode-S transponder

502D5A

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-ABI · AIRBUS A220-300

Hex
502D5A
Octal
24026532
Decimal
5,254,490
Country
LV
Tail
YL-ABI
Type
BCS3
No current signal · last broadcast 1h ago
Flights observed
509
Distinct callsigns
20
Country
LV
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 502D5A.

Country allocation

The ICAO 24-bit address 502D5A 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

Callsign Airline Flights Last seen
BTI98T Air Baltic 7 2026-05-31
SWR2275 - 6 2026-06-22
SWR2274 - 6 2026-06-22
BTI8KY Air Baltic 6 2026-05-31
BTI84D Air Baltic 5 2026-05-31
BTI7HB Air Baltic 5 2026-04-15
BTI6D9 Air Baltic 5 2026-06-04
BTI4YE - 5 2026-07-14
BTI2PG Air Baltic 5 2026-06-07
BTI24X Air Baltic 5 2026-06-07
SWR92T - 4 2026-06-20
SWR8YP Swiss International Air Lines 4 2026-06-24
SWR3HB - 4 2026-06-20
SWR2DK - 4 2026-06-24
BTI8PW Air Baltic 4 2026-05-07
BTI62D Air Baltic 4 2026-06-04
BTI60L - 4 2026-07-13
BTI60K - 4 2026-07-13
BTI35Z - 4 2026-07-11
BTI35T - 4 2026-07-12

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 BTI97H OLB → RIX Jul 14, 16:55 UTCJul 14, 19:40 UTC2h 45m
2026-07-14 BTI44T - Jul 14, 12:50 UTCJul 14, 15:35 UTC2h 45m
2026-07-14 BTI31J - Jul 14, 11:20 UTCJul 14, 11:55 UTC35m
2026-07-14 BTI4YE - Jul 14, 09:55 UTCJul 14, 10:25 UTC30m
2026-07-14 BTI8ED - Jul 14, 07:15 UTCJul 14, 09:10 UTC1h 55m
2026-07-14 BTI89G - Jul 14, 04:20 UTCJul 14, 06:15 UTC1h 55m
2026-07-13 BTI6UQ - Jul 13, 18:15 UTCJul 13, 20:00 UTC1h 45m
2026-07-13 BTI8BX - Jul 13, 15:10 UTCJul 13, 17:10 UTC2h 0m
2026-07-13 BTI30E - Jul 13, 13:10 UTCJul 13, 13:55 UTC45m
2026-07-13 BTI30K - Jul 13, 11:25 UTCJul 13, 12:10 UTC45m
2026-07-13 BTI60L BRU → RIX Jul 13, 08:15 UTCJul 13, 10:15 UTC2h 0m
2026-07-13 BTI60K - Jul 13, 04:50 UTCJul 13, 07:05 UTC2h 15m
2026-07-13 BTI8ME - Jul 13, 02:45 UTCJul 13, 03:10 UTC25m
2026-07-12 BTI7JW - Jul 12, 22:00 UTCJul 12, 22:25 UTC25m
2026-07-12 BTI15L - Jul 12, 18:30 UTCJul 12, 19:45 UTC1h 15m
2026-07-12 BTI15M - Jul 12, 16:35 UTCJul 12, 17:45 UTC1h 10m
2026-07-12 BTI3MD - Jul 12, 14:45 UTCJul 12, 15:30 UTC45m
2026-07-12 BTI9FY - Jul 12, 13:10 UTCJul 12, 13:55 UTC45m
2026-07-12 BTI1F6 ARN → RIX Jul 12, 11:20 UTCJul 12, 12:10 UTC50m
2026-07-12 BTI1F5 - Jul 12, 09:20 UTCJul 12, 10:05 UTC45m
2026-07-12 BTI4LF - Jul 12, 07:05 UTCJul 12, 08:25 UTC1h 20m
2026-07-12 BTI7BU - Jul 12, 04:50 UTCJul 12, 06:10 UTC1h 20m
2026-07-12 BTI35T TMP → RIX Jul 12, 02:30 UTCJul 12, 03:15 UTC45m
2026-07-11 BTI35Z - Jul 11, 21:05 UTCJul 11, 21:55 UTC50m
2026-07-11 BTI7TX - Jul 11, 17:00 UTCJul 11, 19:35 UTC2h 35m
2026-07-11 BTI6CV - Jul 11, 13:10 UTCJul 11, 15:45 UTC2h 35m
2026-07-11 BTI7FN - Jul 11, 09:10 UTCJul 11, 12:05 UTC2h 55m
2026-07-11 BTI46P - Jul 11, 04:20 UTCJul 11, 07:20 UTC3h 0m
2026-07-10 BTI8GC ZRH → RIX Jul 10, 18:20 UTCJul 10, 20:30 UTC2h 10m
2026-07-10 BTI9AG - Jul 10, 15:10 UTCJul 10, 17:15 UTC2h 5m
2026-07-10 BTI3MD TMP → RIX Jul 10, 13:15 UTCJul 10, 14:15 UTC1h 0m
2026-07-10 BTI9FY - Jul 10, 11:35 UTCJul 10, 12:25 UTC50m
2026-07-10 BTI60L BRU → RIX Jul 10, 08:20 UTCJul 10, 10:25 UTC2h 5m
2026-07-10 BTI60K - Jul 10, 04:40 UTCJul 10, 06:50 UTC2h 10m
2026-07-10 BTI36V TLL → RIX Jul 10, 02:40 UTCJul 10, 03:15 UTC35m
2026-07-09 BTI36D - Jul 9, 21:30 UTCJul 9, 22:05 UTC35m
2026-07-09 BTI3DV - Jul 9, 18:25 UTCJul 9, 20:15 UTC1h 50m
2026-07-09 BTI3TG - Jul 9, 15:20 UTCJul 9, 17:15 UTC1h 55m
2026-07-09 BTI8MT PRG → RIX Jul 9, 12:50 UTCJul 9, 14:25 UTC1h 35m
2026-07-09 BTI3VL RIX → PRG Jul 9, 10:20 UTCJul 9, 11:50 UTC1h 30m
2026-07-09 BTI8ED MUC → RIX Jul 9, 07:20 UTCJul 9, 09:20 UTC2h 0m
2026-07-09 BTI89G - Jul 9, 04:20 UTCJul 9, 06:05 UTC1h 45m
2026-07-08 BTI83U VIE → RIX Jul 8, 18:50 UTCJul 8, 20:30 UTC1h 40m
2026-07-08 BTI7BA - Jul 8, 15:55 UTCJul 8, 17:30 UTC1h 35m
2026-07-08 BTI3FA - Jul 8, 12:30 UTCJul 8, 14:45 UTC2h 15m
2026-07-08 BTI3VR - Jul 8, 09:15 UTCJul 8, 11:20 UTC2h 5m
2026-07-08 BTI1M2 - Jul 8, 07:20 UTCJul 8, 08:10 UTC50m
2026-07-08 BTI1M1 RIX → ARN Jul 8, 05:15 UTCJul 8, 06:05 UTC50m
2026-07-08 BTI36V TLL → RIX Jul 8, 02:40 UTCJul 8, 03:10 UTC30m
2026-07-07 BTI42U - Jul 7, 21:00 UTCJul 8, 01:15 UTC4h 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 YL-ABI page for operator, model, and routing details .

Mode-S 502D5A frequently asked

What is Mode-S code 502D5A?
502D5A is an ICAO 24-bit transponder address. Allocated to Latvia. Assigned to YL-ABI.
Where is Mode-S 502D5A registered?
Mode-S code 502D5A is allocated to Latvia (LV). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 502D5A 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 502D5A, octal 24026532, decimal 5,254,490.
What flights does 502D5A operate?
Mode-S 502D5A has broadcast 20 distinct callsigns, including BTI98T, SWR2275, SWR2274, BTI8KY, BTI84D.