sensors Mode-S transponder

502D3F

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-ABA · AIRBUS A220-300

Hex
502D3F
Octal
24026477
Decimal
5,254,463
Country
LV
Tail
YL-ABA
Type
BCS3
No current signal · last broadcast 15d ago
Flights observed
439
Distinct callsigns
20
Country
LV
Last broadcast
15d ago

Last known position

Most recent position reported by Mode-S 502D3F.

Country allocation

The ICAO 24-bit address 502D3F 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
AUA718 - 5 2026-04-16
BTI9AG Air Baltic 4 2026-06-16
BTI98T Air Baltic 4 2026-06-01
BTI8KY Air Baltic 4 2026-06-01
BTI8GC Air Baltic 4 2026-06-16
BTI8ED - 4 2026-06-15
BTI8BX - 4 2026-06-18
BTI89G - 4 2026-06-15
BTI84D Air Baltic 4 2026-06-01
BTI7HB Air Baltic 4 2026-06-01
BTI724 Air Baltic 4 2026-06-09
BTI6UQ Air Baltic 4 2026-06-18
BTI6RZ - 4 2026-06-26
BTI6RV - 4 2026-06-26
BTI3ZB - 4 2026-06-25
BTI3LR Air Baltic 4 2026-05-30
BTI3G2 - 4 2026-06-25
BTI15M - 4 2026-06-24
BTI15L - 4 2026-06-24
BEL4OZ Brussels Airlines 4 2026-05-06

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-29 BTI9809 - Jun 29, 07:34 UTCJun 29, 10:55 UTC3h 20m
2026-06-26 BTI8MT - Jun 26, 17:44 UTCJun 26, 19:14 UTC1h 30m
2026-06-26 BTI3VL - Jun 26, 15:15 UTCJun 26, 16:44 UTC1h 30m
2026-06-26 BTI30E HEL → RIX Jun 26, 12:59 UTCJun 26, 13:45 UTC45m
2026-06-26 BTI30K - Jun 26, 11:24 UTCJun 26, 12:05 UTC40m
2026-06-26 BTI6RZ - Jun 26, 08:45 UTCJun 26, 10:30 UTC1h 45m
2026-06-26 BTI6RV - Jun 26, 05:19 UTCJun 26, 07:10 UTC1h 50m
2026-06-26 BTI7ZP TIA → RIX Jun 26, 01:15 UTCJun 26, 03:29 UTC2h 15m
2026-06-25 BTI4WC RIX → TIA Jun 25, 21:25 UTCJun 25, 23:30 UTC2h 5m
2026-06-25 BTI12G RIX → GOT Jun 25, 18:39 UTCJun 25, 19:39 UTC1h 0m
2026-06-25 BTI12H GOT → RIX Jun 25, 16:35 UTCJun 25, 17:44 UTC1h 10m
2026-06-25 BTI421 - Jun 25, 11:54 UTCJun 25, 14:04 UTC2h 10m
2026-06-25 BTI420 - Jun 25, 08:50 UTCJun 25, 10:39 UTC1h 50m
2026-06-25 BTI3G2 - Jun 25, 06:14 UTCJun 25, 06:50 UTC35m
2026-06-25 BTI3ZB - Jun 25, 05:00 UTCJun 25, 05:29 UTC30m
2026-06-25 BTI2VE - Jun 25, 02:05 UTCJun 25, 03:20 UTC1h 15m
2026-06-24 BTI2YQ RIX → OUL Jun 24, 21:04 UTCJun 24, 22:35 UTC1h 30m
2026-06-24 BTI15L - Jun 24, 18:55 UTCJun 24, 20:05 UTC1h 10m
2026-06-24 BTI15M - Jun 24, 16:24 UTCJun 24, 17:50 UTC1h 25m
2026-06-24 BTI31B - Jun 24, 14:50 UTCJun 24, 15:14 UTC25m
2026-06-24 BTI31C - Jun 24, 13:14 UTCJun 24, 13:50 UTC35m
2026-06-24 BTI696 - Jun 24, 08:14 UTCJun 24, 10:59 UTC2h 45m
2026-06-24 BTI695 - Jun 24, 04:34 UTCJun 24, 07:05 UTC2h 30m
2026-06-22 BTI8RY ALC → RIX Jun 22, 15:40 UTCJun 22, 19:24 UTC3h 45m
2026-06-22 BTI28P - Jun 22, 10:44 UTCJun 22, 14:29 UTC3h 45m
2026-06-22 BTI7LZ - Jun 22, 07:34 UTCJun 22, 09:45 UTC2h 10m
2026-06-22 BTI7PY - Jun 22, 04:19 UTCJun 22, 06:29 UTC2h 10m
2026-06-21 BTI3FT MAD → RIX Jun 21, 18:54 UTCJun 21, 22:20 UTC3h 25m
2026-06-21 BTI8EP - Jun 21, 11:20 UTCJun 21, 15:05 UTC3h 45m
2026-06-21 BTI7FN HER → RIX Jun 21, 07:09 UTCJun 21, 10:19 UTC3h 10m
2026-06-21 BTI46P RIX → HER Jun 21, 02:35 UTCJun 21, 05:35 UTC3h 0m
2026-06-20 BTI97H OLB → RIX Jun 20, 17:10 UTCJun 20, 19:55 UTC2h 45m
2026-06-20 BTI44T - Jun 20, 12:59 UTCJun 20, 15:54 UTC2h 55m
2026-06-20 BTI7718 - Jun 20, 08:25 UTCJun 20, 11:44 UTC3h 20m
2026-06-20 BTI7717 - Jun 20, 03:44 UTCJun 20, 06:54 UTC3h 10m
2026-06-19 BTI2PG HEL → RIX Jun 19, 18:44 UTCJun 19, 19:25 UTC40m
2026-06-19 BTI24X - Jun 19, 17:09 UTCJun 19, 17:55 UTC45m
2026-06-19 BTI26R BCN → RIX Jun 19, 13:09 UTCJun 19, 16:09 UTC3h 0m
2026-06-19 BTI9TZ - Jun 19, 08:14 UTCJun 19, 11:34 UTC3h 20m
2026-06-19 BTI30Y - Jun 19, 06:20 UTCJun 19, 06:59 UTC40m
2026-06-19 BTI30W - Jun 19, 04:50 UTCJun 19, 05:30 UTC40m
2026-06-19 BTI35T - Jun 19, 02:24 UTCJun 19, 03:09 UTC45m
2026-06-18 BTI35Z RIX → TMP Jun 18, 21:40 UTCJun 18, 22:30 UTC50m
2026-06-18 BTI6UQ MUC → RIX Jun 18, 18:40 UTCJun 18, 20:30 UTC1h 50m
2026-06-18 BTI8BX RIX → MUC Jun 18, 15:35 UTCJun 18, 17:30 UTC1h 55m
2026-06-18 BTI97L - Jun 18, 12:35 UTCJun 18, 14:40 UTC2h 5m
2026-06-18 BTI9RG - Jun 18, 09:45 UTCJun 18, 11:30 UTC1h 45m
2026-06-18 BTI7KL - Jun 18, 07:05 UTCJun 18, 08:50 UTC1h 45m
2026-06-18 BTI9LE - Jun 18, 04:20 UTCJun 18, 05:55 UTC1h 35m
2026-06-18 BTI3WX - Jun 18, 02:25 UTCJun 18, 03:00 UTC35m

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

Mode-S 502D3F frequently asked

What is Mode-S code 502D3F?
502D3F is an ICAO 24-bit transponder address. Allocated to Latvia. Assigned to YL-ABA.
Where is Mode-S 502D3F registered?
Mode-S code 502D3F is allocated to Latvia (LV). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 502D3F broadcasting right now?
No active broadcast right now. Last signal was 15d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 502D3F, octal 24026477, decimal 5,254,463.
What flights does 502D3F operate?
Mode-S 502D3F has broadcast 20 distinct callsigns, including AUA718, BTI9AG, BTI98T, BTI8KY, BTI8GC.