Apparatus

Try JFK, AAL1290, BAW, or N225AN.

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
No current signal · last broadcast 1h ago
Flights observed
583
Distinct callsigns
20
Country
LV
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 502D0F.

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
BTI98T - 6 2026-07-11
BTI84D - 6 2026-07-11
BTI83U Air Baltic 6 2026-06-26
BTI7BA - 6 2026-06-26
BTI3TG - 6 2026-07-10
SWR868L - 5 2026-06-18
SWR4WG - 5 2026-06-18
BTI3DV - 5 2026-07-10
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
SWR2WZ Swiss International Air Lines 4 2026-06-04
SWR2279 - 4 2026-06-22
SWR2275 - 4 2026-06-17
SWR2274 - 4 2026-06-17
BTI9BN - 4 2026-07-10
BTI97T - 4 2026-07-07

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 BTI2J4 - Jul 14, 18:20 UTCJul 14, 19:45 UTC1h 25m
2026-07-14 BTI84W - Jul 14, 15:45 UTCJul 14, 17:05 UTC1h 20m
2026-07-14 BTI8MT - Jul 14, 13:30 UTCJul 14, 14:55 UTC1h 25m
2026-07-14 BTI3VL RIX → PRG Jul 14, 11:05 UTCJul 14, 12:45 UTC1h 40m
2026-07-14 BTI60L - Jul 14, 08:05 UTCJul 14, 10:10 UTC2h 5m
2026-07-14 BTI60K - Jul 14, 04:40 UTCJul 14, 06:50 UTC2h 10m
2026-07-13 BTI62D - Jul 13, 17:35 UTCJul 13, 19:25 UTC1h 50m
2026-07-13 BTI6D9 - Jul 13, 14:15 UTCJul 13, 16:15 UTC2h 0m
2026-07-13 BTI9802 - Jul 13, 12:50 UTCJul 13, 13:30 UTC40m
2026-07-13 BTI8KY - Jul 13, 10:05 UTCJul 13, 12:05 UTC2h 0m
2026-07-13 BTI7HB VNO → AMS Jul 13, 06:55 UTCJul 13, 08:55 UTC2h 0m
2026-07-13 BTI3ZB - Jul 13, 05:20 UTCJul 13, 05:55 UTC35m
2026-07-13 BTI3WX - Jul 13, 02:35 UTCJul 13, 03:20 UTC45m
2026-07-12 BTI3U9 - Jul 12, 21:50 UTCJul 12, 22:30 UTC40m
2026-07-12 BTI62D - Jul 12, 17:55 UTCJul 12, 19:50 UTC1h 55m
2026-07-12 BTI6D9 - Jul 12, 14:30 UTCJul 12, 16:30 UTC2h 0m
2026-07-12 BTI658 - Jul 12, 09:50 UTCJul 12, 13:25 UTC3h 35m
2026-07-12 BTI657 - Jul 12, 04:35 UTCJul 12, 08:15 UTC3h 40m
2026-07-12 BTI35G VNO → RIX Jul 12, 02:45 UTCJul 12, 03:20 UTC35m
2026-07-11 BTI2CJ NCE → VNO Jul 11, 21:25 UTCJul 11, 23:50 UTC2h 25m
2026-07-11 BTI9YR VNO → NCE Jul 11, 17:50 UTCJul 11, 20:25 UTC2h 35m
2026-07-11 BTI84D - Jul 11, 15:00 UTCJul 11, 16:55 UTC1h 55m
2026-07-11 BTI98T VNO → AMS Jul 11, 11:40 UTCJul 11, 13:35 UTC1h 55m
2026-07-11 BTI8KY - Jul 11, 08:45 UTCJul 11, 10:45 UTC2h 0m
2026-07-11 BTI7HB VNO → AMS Jul 11, 04:55 UTCJul 11, 06:55 UTC2h 0m
2026-07-10 BTI3LR - Jul 10, 21:25 UTCJul 10, 22:00 UTC35m
2026-07-10 BTI3DV DUS → RIX Jul 10, 18:25 UTCJul 10, 20:20 UTC1h 55m
2026-07-10 BTI3TG - Jul 10, 15:30 UTCJul 10, 17:20 UTC1h 50m
2026-07-10 BTI6GN - Jul 10, 12:25 UTCJul 10, 14:30 UTC2h 5m
2026-07-10 BTI9BN - Jul 10, 09:15 UTCJul 10, 11:15 UTC2h 0m
2026-07-10 BTI1R2 - Jul 10, 06:30 UTCJul 10, 07:50 UTC1h 20m
2026-07-10 BTI15P - Jul 10, 04:10 UTCJul 10, 05:20 UTC1h 10m
2026-07-09 BTI9YF CDG → RIX Jul 9, 17:25 UTCJul 9, 19:50 UTC2h 25m
2026-07-09 BTI84F - Jul 9, 13:40 UTCJul 9, 16:05 UTC2h 25m
2026-07-09 BTI34G VNO → RIX Jul 9, 12:15 UTCJul 9, 12:50 UTC35m
2026-07-09 BTI34K - Jul 9, 10:55 UTCJul 9, 11:25 UTC30m
2026-07-09 BTI7KL VIE → RIX Jul 9, 07:25 UTCJul 9, 09:10 UTC1h 45m
2026-07-09 BTI9LE - Jul 9, 04:35 UTCJul 9, 06:10 UTC1h 35m
2026-07-08 BTI4LF - Jul 8, 17:45 UTCJul 8, 19:05 UTC1h 20m
2026-07-08 BTI7BU - Jul 8, 15:25 UTCJul 8, 16:50 UTC1h 25m
2026-07-08 BTI79E - Jul 8, 12:35 UTCJul 8, 14:35 UTC2h 0m
2026-07-08 BTI43N - Jul 8, 09:15 UTCJul 8, 11:10 UTC1h 55m
2026-07-08 BTI1R2 - Jul 8, 06:40 UTCJul 8, 07:50 UTC1h 10m
2026-07-08 BTI15P RIX → OSL Jul 8, 04:15 UTCJul 8, 05:30 UTC1h 15m
2026-07-07 BTI3DV DUS → RIX Jul 7, 18:50 UTCJul 7, 20:40 UTC1h 50m
2026-07-07 BTI3TG - Jul 7, 15:25 UTCJul 7, 17:20 UTC1h 55m
2026-07-07 BTI3FA SOF → RIX Jul 7, 12:20 UTCJul 7, 14:35 UTC2h 15m
2026-07-07 BTI3VR - Jul 7, 08:55 UTCJul 7, 11:10 UTC2h 15m
2026-07-07 BTI97T - Jul 7, 06:35 UTCJul 7, 07:50 UTC1h 15m
2026-07-07 BTI74A - Jul 7, 04:10 UTCJul 7, 05:40 UTC1h 30m

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?
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 502D0F, octal 24026417, decimal 5,254,415.
What flights does 502D0F operate?
Mode-S 502D0F has broadcast 20 distinct callsigns, including BTI8KY, BTI7HB, BTI98T, BTI84D, BTI83U.