sensors Mode-S transponder

502D5F

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-ABN · AIRBUS A220-300

Hex
502D5F
Octal
24026537
Decimal
5,254,495
Country
LV
Tail
YL-ABN
Type
BCS3
Broadcasting now · callsign BTI8FC · 36,000 ft
Flights observed
553
Distinct callsigns
20
Country
LV
Last broadcast
Jul 26, 20:15 UTC

Current position

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

Country allocation

The ICAO 24-bit address 502D5F 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
BTI9KH - 7 2026-07-20
BTI98T Air Baltic 7 2026-06-07
BTI8ZF Air Baltic 7 2026-07-21
BTI8KY Air Baltic 7 2026-06-07
BTI84D Air Baltic 7 2026-06-07
BTI7HB Air Baltic 7 2026-06-07
BTI42U - 7 2026-07-21
BTI2VY Air Baltic 7 2026-07-20
BTI724 - 6 2026-07-09
BTI4ZK - 6 2026-07-12
BTI4ZC Air Baltic 6 2026-07-22
BTI37D - 6 2026-07-09
BTI31G - 6 2026-07-14
BTI9JT - 5 2026-07-09
BTI8LM - 5 2026-07-17
BTI7HA Air Baltic 5 2026-07-22
BTI4WA - 5 2026-07-17
BTI3PR Air Baltic 5 2026-05-21
BTI3FL Air Baltic 5 2026-05-21
BTI32M Air Baltic 5 2026-07-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 BTI9YF CDG → RIX Jul 26, 18:00 UTCJul 26, 20:15 UTC2h 15m
2026-07-26 BTI84F RIX → CDG Jul 26, 14:20 UTCJul 26, 16:50 UTC2h 30m
2026-07-26 BTI1F6 ARN → RIX Jul 26, 12:50 UTCJul 26, 13:30 UTC40m
2026-07-26 BTI1F5 RIX → ARN Jul 26, 11:05 UTCJul 26, 11:55 UTC50m
2026-07-26 BTI8FX TIV → RIX Jul 26, 04:25 UTCJul 26, 10:10 UTC5h 46m
2026-07-26 BTI32M HEL → RIX Jul 26, 02:35 UTCJul 26, 03:15 UTC40m
2026-07-25 BTI32B RIX → HEL Jul 25, 22:20 UTCJul 25, 23:00 UTC40m
2026-07-25 BTI716 AYT → RIX Jul 25, 18:00 UTCJul 25, 21:20 UTC3h 20m
2026-07-25 BTI715 RIX → AYT Jul 25, 13:00 UTCJul 25, 16:40 UTC3h 40m
2026-07-25 BTI7718 AYT → RIX Jul 25, 08:25 UTCJul 25, 11:50 UTC3h 25m
2026-07-25 BTI7717 RIX → AYT Jul 25, 03:55 UTCJul 25, 06:55 UTC3h 0m
2026-07-24 BTI4UJ BER → RIX Jul 24, 19:55 UTCJul 24, 21:15 UTC1h 20m
2026-07-24 BTI6UN RIX → BER Jul 24, 17:40 UTCJul 24, 19:00 UTC1h 20m
2026-07-24 BTI31B TLL → RIX Jul 24, 16:10 UTCJul 24, 16:45 UTC35m
2026-07-24 BTI31C RIX → TLL Jul 24, 14:45 UTCJul 24, 15:15 UTC30m
2026-07-24 BTI8RY CDG → TLL Jul 24, 09:55 UTCJul 24, 13:45 UTC3h 50m
2026-07-24 BTI28P CDG → TLL Jul 24, 04:45 UTCJul 24, 08:35 UTC3h 50m
2026-07-24 BTI8ME PLQ → RIX Jul 24, 02:40 UTCJul 24, 03:10 UTC30m
2026-07-23 BTI7JW RIX → PLQ Jul 23, 22:40 UTCJul 23, 23:05 UTC25m
2026-07-23 BTI83U VIE → RIX Jul 23, 19:00 UTCJul 23, 20:40 UTC1h 40m
2026-07-23 BTI7BA RIX → VIE Jul 23, 16:15 UTCJul 23, 17:55 UTC1h 40m
2026-07-23 BTI3MD TMP → RIX Jul 23, 14:35 UTCJul 23, 15:30 UTC55m
2026-07-23 BTI9FY RIX → TMP Jul 23, 12:55 UTCJul 23, 13:45 UTC50m
2026-07-23 BTI31J TLL → RIX Jul 23, 11:30 UTCJul 23, 12:00 UTC30m
2026-07-23 BTI9UG AMS → TLL Jul 23, 08:20 UTCJul 23, 10:30 UTC2h 10m
2026-07-23 BTI8FH TLL → AMS Jul 23, 04:45 UTCJul 23, 06:45 UTC2h 0m
2026-07-22 BTI7NK TLL → FNC Jul 22, 20:15 UTCJul 22, 21:50 UTC1h 35m
2026-07-22 BTI3ZN TLL → HAM Jul 22, 17:45 UTCJul 22, 19:15 UTC1h 30m
2026-07-22 BTI4ZC VIE → TLL Jul 22, 14:45 UTCJul 22, 16:45 UTC2h 0m
2026-07-22 BTI7HA TLL → VIE Jul 22, 11:25 UTCJul 22, 13:20 UTC1h 55m
2026-07-22 BTI8FH TLL → AMS Jul 22, 04:35 UTCJul 22, 05:25 UTC50m
2026-07-21 BTI9UZ VNO → TLL Jul 21, 19:35 UTCJul 21, 20:25 UTC50m
2026-07-21 BTI6EY TLL → VNO Jul 21, 17:50 UTCJul 21, 18:40 UTC50m
2026-07-21 BTI42U - Jul 21, 10:10 UTCJul 21, 14:30 UTC4h 20m
2026-07-21 BTI8ZF TLL → AGP Jul 21, 04:15 UTCJul 21, 08:35 UTC4h 20m
2026-07-20 BTI92L - Jul 20, 18:05 UTCJul 20, 20:40 UTC2h 35m
2026-07-20 BTI7HQ TLL → CDG Jul 20, 14:05 UTCJul 20, 16:45 UTC2h 40m
2026-07-20 BTI4ZC VIE → TLL Jul 20, 11:10 UTCJul 20, 13:00 UTC1h 50m
2026-07-20 BTI7HA TLL → VIE Jul 20, 07:55 UTCJul 20, 10:05 UTC2h 10m
2026-07-20 BTI2VY VNO → TLL Jul 20, 06:00 UTCJul 20, 06:50 UTC50m
2026-07-20 BTI9KH - Jul 20, 04:10 UTCJul 20, 05:00 UTC50m
2026-07-19 BTI3YK CDG → TLL Jul 19, 19:10 UTCJul 19, 21:30 UTC2h 20m
2026-07-19 BTI3KC TLL → CDG Jul 19, 14:55 UTCJul 19, 17:30 UTC2h 35m
2026-07-19 BTI4YE - Jul 19, 13:15 UTCJul 19, 13:45 UTC30m
2026-07-19 BTI688 PMI → RIX Jul 19, 09:15 UTCJul 19, 12:15 UTC3h 0m
2026-07-19 BTI687 RIX → PMI Jul 19, 04:15 UTCJul 19, 08:00 UTC3h 45m
2026-07-19 BTI36V TLL → RIX Jul 19, 02:45 UTCJul 19, 03:20 UTC35m
2026-07-18 BTI8YW BOJ → TLL Jul 18, 20:05 UTCJul 18, 22:50 UTC2h 45m
2026-07-18 BTI86L TLL → BOJ Jul 18, 15:55 UTCJul 18, 19:00 UTC3h 5m
2026-07-18 BTI42U - Jul 18, 10:35 UTCJul 18, 14:40 UTC4h 5m

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

Mode-S 502D5F frequently asked

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