Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

502D0E

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-AAR · AIRBUS A220-300

Hex
502D0E
Octal
24026416
Decimal
5,254,414
Country
LV
Tail
YL-AAR
Type
BCS3
Broadcasting now · callsign BTI36V · 10,675 ft
Flights observed
584
Distinct callsigns
20
Country
LV
Last broadcast
4h ago

Current position

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

Country allocation

The ICAO 24-bit address 502D0E 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
BTI43N - 20 2026-07-13
BTI79E - 18 2026-07-13
BTI6UQ Air Baltic 12 2026-07-02
BTI13G - 12 2026-07-11
BTI8MT - 10 2026-07-11
BTI8BX - 10 2026-07-02
BTI3VL - 10 2026-07-11
BTI13F - 10 2026-07-11
BTI9YF Air Baltic 9 2026-07-06
BTI97L - 9 2026-06-30
BTI84F - 9 2026-07-06
BTI7JW - 9 2026-07-04
BTI9RG - 8 2026-06-30
BTI8GJ - 7 2026-07-06
BTI87A - 7 2026-07-10
BTI83U Air Baltic 7 2026-06-19
BTI7BA - 7 2026-06-19
BTI6UN Air Baltic 7 2026-06-01
BTI69R - 7 2026-07-06
BTI65T - 7 2026-07-10

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 BTI36D - Jul 13, 21:55 UTCJul 13, 22:25 UTC30m
2026-07-13 BTI8GC ZRH → RIX Jul 13, 18:40 UTCJul 13, 20:45 UTC2h 5m
2026-07-13 BTI9AG - Jul 13, 15:15 UTCJul 13, 17:30 UTC2h 15m
2026-07-13 BTI79E - Jul 13, 12:25 UTCJul 13, 14:10 UTC1h 45m
2026-07-13 BTI43N - Jul 13, 09:30 UTCJul 13, 11:20 UTC1h 50m
2026-07-13 BTI3G2 VNO → RIX Jul 13, 08:10 UTCJul 13, 08:40 UTC30m
2026-07-13 BTI9801 - Jul 13, 06:50 UTCJul 13, 07:20 UTC30m
2026-07-13 BTI3KB KEF → RIX Jul 13, 01:20 UTCJul 13, 04:45 UTC3h 25m
2026-07-12 BTI2HU - Jul 12, 20:40 UTCJul 13, 00:10 UTC3h 30m
2026-07-12 BTI2PG HEL → RIX Jul 12, 18:30 UTCJul 12, 19:10 UTC40m
2026-07-12 BTI24X - Jul 12, 16:55 UTCJul 12, 17:35 UTC40m
2026-07-12 BTI15U OSL → RIX Jul 12, 14:50 UTCJul 12, 16:10 UTC1h 20m
2026-07-12 BTI1C5 - Jul 12, 12:40 UTCJul 12, 13:50 UTC1h 10m
2026-07-12 BTI6A2 - Jul 12, 08:50 UTCJul 12, 11:35 UTC2h 45m
2026-07-12 BTI6A1 - Jul 12, 05:25 UTCJul 12, 07:35 UTC2h 10m
2026-07-12 BTI6A1 - Jul 12, 04:45 UTCJul 12, 05:20 UTC35m
2026-07-11 BTI8MT PRG → RIX Jul 11, 17:50 UTCJul 11, 19:25 UTC1h 35m
2026-07-11 BTI3VL - Jul 11, 15:20 UTCJul 11, 16:45 UTC1h 25m
2026-07-11 BTI79E - Jul 11, 12:20 UTCJul 11, 14:20 UTC2h 0m
2026-07-11 BTI43N - Jul 11, 09:00 UTCJul 11, 10:50 UTC1h 50m
2026-07-11 BTI13G CPH → RIX Jul 11, 06:40 UTCJul 11, 07:50 UTC1h 10m
2026-07-11 BTI13F - Jul 11, 04:35 UTCJul 11, 05:40 UTC1h 5m
2026-07-11 BTI9FJ SKG → RIX Jul 11, 00:40 UTCJul 11, 03:15 UTC2h 35m
2026-07-10 BTI7EJ - Jul 10, 21:20 UTCJul 10, 23:45 UTC2h 25m
2026-07-10 BTI6BM LGW → RIX Jul 10, 17:45 UTCJul 10, 20:05 UTC2h 20m
2026-07-10 BTI6BL - Jul 10, 12:55 UTCJul 10, 15:30 UTC2h 35m
2026-07-10 BTI65T LGW → RIX Jul 10, 09:05 UTCJul 10, 11:20 UTC2h 15m
2026-07-10 BTI87A - Jul 10, 04:35 UTCJul 10, 07:10 UTC2h 35m
2026-07-10 BTI35G - Jul 10, 02:30 UTCJul 10, 03:00 UTC30m
2026-07-09 BTI3PR - Jul 9, 18:00 UTCJul 9, 20:15 UTC2h 15m
2026-07-09 BTI3FL - Jul 9, 14:35 UTCJul 9, 16:55 UTC2h 20m
2026-07-09 BTI7DB HAM → VNO Jul 9, 12:05 UTCJul 9, 13:35 UTC1h 30m
2026-07-09 BTI38N VNO → HAM Jul 9, 09:35 UTCJul 9, 11:05 UTC1h 30m
2026-07-09 BTI9KH TLL → VNO Jul 9, 07:45 UTCJul 9, 08:35 UTC50m
2026-07-09 BTI2VY VNO → TLL Jul 9, 06:05 UTCJul 9, 07:00 UTC55m
2026-07-09 BTI9803 - Jul 9, 04:40 UTCJul 9, 05:10 UTC30m
2026-07-09 BTI2VE - Jul 9, 02:00 UTCJul 9, 03:20 UTC1h 20m
2026-07-08 BTI2YQ RIX → OUL Jul 8, 21:50 UTCJul 8, 23:10 UTC1h 20m
2026-07-08 BTI3DV DUS → RIX Jul 8, 18:45 UTCJul 8, 20:35 UTC1h 50m
2026-07-08 BTI3TG - Jul 8, 15:25 UTCJul 8, 17:10 UTC1h 45m
2026-07-08 BTI3MD TMP → RIX Jul 8, 12:45 UTCJul 8, 13:35 UTC50m
2026-07-08 BTI9FY - Jul 8, 11:15 UTCJul 8, 12:00 UTC45m
2026-07-08 BTI7EG - Jul 8, 08:05 UTCJul 8, 10:05 UTC2h 0m
2026-07-08 BTI83L - Jul 8, 05:05 UTCJul 8, 06:55 UTC1h 50m
2026-07-07 BTI79E - Jul 7, 12:25 UTCJul 7, 14:10 UTC1h 45m
2026-07-07 BTI43N - Jul 7, 09:05 UTCJul 7, 11:15 UTC2h 10m
2026-07-07 BTI31T - Jul 7, 06:55 UTCJul 7, 07:25 UTC30m
2026-07-07 BTI31G - Jul 7, 05:30 UTCJul 7, 06:00 UTC30m
2026-07-07 BTI9FJ - Jul 7, 01:35 UTCJul 7, 04:15 UTC2h 40m
2026-07-06 BTI7EJ RIX → SKG Jul 6, 22:05 UTCJul 7, 00:30 UTC2h 25m

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

Mode-S 502D0E frequently asked

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