sensors Mode-S transponder

502D0F

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-AAS · AIRBUS A220-300

Hex
502D0F
Octal
24026417
Decimal
5,254,415
Country
LV
Tail
YL-AAS
Type
BCS3
Broadcasting now · callsign BTI25K · 8,350 ft
Flights observed
668
Distinct callsigns
20
Country
LV
Last broadcast
Jul 26, 20:00 UTC

Current position

502D0F is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 502D0F 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
BTI8KY - 7 2026-07-13
BTI7HB - 7 2026-07-13
BTI79E Air Baltic 7 2026-07-23
BTI98T - 6 2026-07-11
BTI84D - 6 2026-07-11
BTI83U Air Baltic 6 2026-06-26
BTI7BA - 6 2026-06-26
BTI43N Air Baltic 6 2026-07-23
BTI3TG - 6 2026-07-10
SWR868L - 5 2026-06-18
SWR4WG - 5 2026-06-18
BTI7JW Air Baltic 5 2026-07-24
BTI3DV - 5 2026-07-10
BTI36V - 5 2026-07-18
BTI1R2 Air Baltic 5 2026-07-25
BTI15P Air Baltic 5 2026-07-25
SWR96E Swiss International Air Lines 4 2026-06-06
SWR759G Swiss International Air Lines 4 2026-06-05
SWR41P Swiss International Air Lines 4 2026-06-03
SWR3ME Swiss International Air Lines 4 2026-06-21

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 BTI14B CPH → RIX Jul 26, 19:00 UTCJul 26, 20:00 UTC1h 0m
2026-07-26 BTI1P9 RIX → CPH Jul 26, 17:05 UTCJul 26, 18:15 UTC1h 10m
2026-07-26 BTI26R BCN → RIX Jul 26, 12:50 UTCJul 26, 16:05 UTC3h 15m
2026-07-26 BTI9TZ RIX → BCN Jul 26, 08:00 UTCJul 26, 11:15 UTC3h 15m
2026-07-26 BTI30Y HEL → RIX Jul 26, 06:10 UTCJul 26, 06:55 UTC46m
2026-07-26 BTI30W RIX → HEL Jul 26, 04:35 UTCJul 26, 05:20 UTC45m
2026-07-25 BTI15L OSL → RIX Jul 25, 19:50 UTCJul 25, 21:00 UTC1h 10m
2026-07-25 BTI15M RIX → OSL Jul 25, 17:20 UTCJul 25, 18:40 UTC1h 20m
2026-07-25 BTI7QT MLA → RIX Jul 25, 12:55 UTCJul 25, 16:20 UTC3h 25m
2026-07-25 BTI8XQ RIX → MLA Jul 25, 08:45 UTCJul 25, 11:45 UTC3h 0m
2026-07-25 BTI1R2 OSL → RIX Jul 25, 06:40 UTCJul 25, 07:50 UTC1h 10m
2026-07-25 BTI15P RIX → OSL Jul 25, 04:30 UTCJul 25, 05:50 UTC1h 20m
2026-07-25 BTI8ME PLQ → RIX Jul 25, 03:00 UTCJul 25, 03:30 UTC30m
2026-07-24 BTI7JW RIX → PLQ Jul 24, 22:40 UTCJul 24, 23:10 UTC30m
2026-07-24 BTI9YF CDG → RIX Jul 24, 19:20 UTCJul 24, 21:40 UTC2h 20m
2026-07-24 BTI84F RIX → CDG Jul 24, 15:30 UTCJul 24, 17:55 UTC2h 25m
2026-07-24 BTI3MD TMP → RIX Jul 24, 13:50 UTCJul 24, 14:40 UTC50m
2026-07-24 BTI9FY RIX → TMP Jul 24, 12:00 UTCJul 24, 12:55 UTC55m
2026-07-24 BTI69R CDG → RIX Jul 24, 08:45 UTCJul 24, 11:00 UTC2h 15m
2026-07-24 BTI8GJ RIX → CDG Jul 24, 04:50 UTCJul 24, 07:15 UTC2h 25m
2026-07-24 BTI7ZP TIA → RIX Jul 24, 01:25 UTCJul 24, 03:40 UTC2h 15m
2026-07-23 BTI4WC RIX → TIA Jul 23, 21:50 UTCJul 23, 23:50 UTC2h 0m
2026-07-23 BTI62D AMS → RIX Jul 23, 18:30 UTCJul 23, 20:30 UTC2h 0m
2026-07-23 BTI6D9 RIX → AMS Jul 23, 15:40 UTCJul 23, 17:25 UTC1h 45m
2026-07-23 BTI79E AMS → RIX Jul 23, 12:40 UTCJul 23, 14:40 UTC2h 0m
2026-07-23 BTI43N RIX → AMS Jul 23, 09:40 UTCJul 23, 11:25 UTC1h 45m
2026-07-23 BTI7KL VIE → RIX Jul 23, 07:10 UTCJul 23, 08:50 UTC1h 40m
2026-07-23 BTI9LE RIX → VIE Jul 23, 04:35 UTCJul 23, 06:10 UTC1h 35m
2026-07-23 BTI32M HEL → RIX Jul 23, 02:50 UTCJul 23, 03:30 UTC40m
2026-07-22 BTI32B RIX → HEL Jul 22, 22:15 UTCJul 22, 23:00 UTC45m
2026-07-22 BTI4PM OPO → RIX Jul 22, 16:25 UTCJul 22, 20:00 UTC3h 35m
2026-07-22 BTI74L RIX → OPO Jul 22, 11:20 UTCJul 22, 15:20 UTC4h 0m
2026-07-22 BTI6RV RIX → AMS Jul 22, 04:55 UTCJul 22, 05:25 UTC30m
2026-07-21 BTI15L - Jul 21, 19:05 UTCJul 21, 20:20 UTC1h 15m
2026-07-21 BTI15M - Jul 21, 16:55 UTCJul 21, 18:10 UTC1h 15m
2026-07-21 BTI612 ATH → RIX Jul 21, 13:05 UTCJul 21, 15:55 UTC2h 50m
2026-07-21 BTI611 RIX → ATH Jul 21, 08:50 UTCJul 21, 11:50 UTC3h 0m
2026-07-21 BTI13G CPH → RIX Jul 21, 06:35 UTCJul 21, 07:45 UTC1h 10m
2026-07-21 BTI13F RIX → CPH Jul 21, 04:20 UTCJul 21, 05:25 UTC1h 5m
2026-07-21 BTI2VE OUL → RIX Jul 21, 02:10 UTCJul 21, 03:25 UTC1h 15m
2026-07-20 BTI2YQ RIX → OUL Jul 20, 21:30 UTCJul 20, 22:55 UTC1h 25m
2026-07-20 BTI8GC ZRH → RIX Jul 20, 18:40 UTCJul 20, 20:45 UTC2h 5m
2026-07-20 BTI9AG - Jul 20, 15:25 UTCJul 20, 17:40 UTC2h 15m
2026-07-20 BTI79E - Jul 20, 12:30 UTCJul 20, 14:25 UTC1h 55m
2026-07-20 BTI43N RIX → AMS Jul 20, 09:00 UTCJul 20, 10:45 UTC1h 45m
2026-07-20 BTI12G RIX → GOT Jul 20, 06:20 UTCJul 20, 07:25 UTC1h 5m
2026-07-20 BTI12H GOT → RIX Jul 20, 04:25 UTCJul 20, 05:25 UTC1h 0m
2026-07-20 BTI35T TMP → RIX Jul 20, 02:30 UTCJul 20, 03:30 UTC1h 0m
2026-07-19 BTI35Z - Jul 19, 22:25 UTCJul 19, 23:15 UTC50m
2026-07-19 BTI630 MXP → RIX Jul 19, 18:15 UTCJul 19, 20:25 UTC2h 10m

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

Mode-S 502D0F frequently asked

What is Mode-S code 502D0F?
502D0F is an ICAO 24-bit transponder address. Allocated to Latvia. Assigned to YL-AAS.
Where is Mode-S 502D0F registered?
Mode-S code 502D0F is allocated to Latvia (LV). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 502D0F broadcasting right now?
Yes. Mode-S 502D0F is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 502D0F, octal 24026417, decimal 5,254,415.
What flights does 502D0F operate?
Mode-S 502D0F has broadcast 20 distinct callsigns, including BTI8KY, BTI7HB, BTI79E, BTI98T, BTI84D.