sensors Mode-S transponder

502D7B

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-ABQ · AIRBUS A220-300

Hex
502D7B
Octal
24026573
Decimal
5,254,523
Country
LV
Tail
YL-ABQ
Type
BCS3
No current signal · last broadcast 5h ago
Flights observed
481
Distinct callsigns
20
Country
LV
Last broadcast
5h ago

Last known position

Most recent position reported by Mode-S 502D7B.

Country allocation

The ICAO 24-bit address 502D7B 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
ASL423 - 7 2026-06-30
ASL422 - 7 2026-06-30
ASL98C - 6 2026-06-29
ASL90F - 6 2026-06-29
ASL64R Spurling Aviation 6 2026-06-16
ASL54W - 6 2026-07-01
ASL22G - 6 2026-07-01
SWR49P Swiss International Air Lines 5 2026-05-17
SWR2GZ Swiss International Air Lines 5 2026-05-17
ASL96K - 5 2026-06-24
ASL76H - 5 2026-06-24
ASL63H - 5 2026-06-20
ASL49U - 5 2026-07-02
ASL39F - 5 2026-07-02
ASL38K - 5 2026-06-28
ASL37H - 5 2026-06-30
ASL18A Spurling Aviation 5 2026-05-25
ASL96D Spurling Aviation 4 2026-06-16
ASL83Z - 4 2026-06-23
ASL82Y - 4 2026-06-30

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 BTI79M TLL → RIX Jul 14, 18:35 UTCJul 14, 19:10 UTC35m
2026-07-14 BTI29K - Jul 14, 14:40 UTCJul 14, 16:40 UTC2h 0m
2026-07-14 BTI78V - Jul 14, 11:30 UTCJul 14, 13:35 UTC2h 5m
2026-07-14 BTI98R BRU → TLL Jul 14, 08:20 UTCJul 14, 10:35 UTC2h 15m
2026-07-14 BTI2YH TLL → BRU Jul 14, 04:40 UTCJul 14, 07:10 UTC2h 30m
2026-07-14 BTI8FC - Jul 14, 03:10 UTCJul 14, 03:20 UTC10m
2026-07-14 BTI8FC - Jul 14, 00:45 UTCJul 14, 02:25 UTC1h 40m
2026-07-13 BTI29P - Jul 13, 20:45 UTCJul 13, 23:10 UTC2h 25m
2026-07-13 BTI4ZK - Jul 13, 19:20 UTCJul 13, 19:50 UTC30m
2026-07-13 BTI79M TLL → RIX Jul 13, 17:55 UTCJul 13, 18:30 UTC35m
2026-07-13 BTI860 - Jul 13, 14:55 UTCJul 13, 17:00 UTC2h 5m
2026-07-13 BTI859 TLL → AMS Jul 13, 11:45 UTCJul 13, 13:45 UTC2h 0m
2026-07-13 BTI98R BRU → TLL Jul 13, 08:40 UTCJul 13, 10:50 UTC2h 10m
2026-07-13 BTI2YH - Jul 13, 04:45 UTCJul 13, 07:05 UTC2h 20m
2026-07-12 BTI9BQ - Jul 12, 20:40 UTCJul 12, 22:10 UTC1h 30m
2026-07-12 BTI89U TLL → BER Jul 12, 18:20 UTCJul 12, 19:50 UTC1h 30m
2026-07-12 BTI860 - Jul 12, 15:20 UTCJul 12, 17:15 UTC1h 55m
2026-07-12 BTI859 TLL → AMS Jul 12, 12:05 UTCJul 12, 14:10 UTC2h 5m
2026-07-12 BTI3PQ - Jul 12, 08:40 UTCJul 12, 11:10 UTC2h 30m
2026-07-12 BTI6FG - Jul 12, 05:35 UTCJul 12, 07:31 UTC1h 55m
2026-07-12 BTI32M HEL → RIX Jul 12, 02:30 UTCJul 12, 03:10 UTC40m
2026-07-11 DLH2466 - Jul 11, 20:40 UTCJul 11, 23:00 UTC2h 20m
2026-07-11 DLH05U - Jul 11, 17:40 UTCJul 11, 19:25 UTC1h 45m
2026-07-11 DLH77M MUC → BCN Jul 11, 14:35 UTCJul 11, 16:25 UTC1h 50m
2026-07-11 DLH65X - Jul 11, 12:05 UTCJul 11, 13:05 UTC1h 0m
2026-07-11 DLH02J - Jul 11, 09:30 UTCJul 11, 10:35 UTC1h 5m
2026-07-11 DLH11X - Jul 11, 07:25 UTCJul 11, 08:30 UTC1h 5m
2026-07-11 DLH2270 - Jul 11, 05:20 UTCJul 11, 06:25 UTC1h 5m
2026-07-10 DLH5PR ARN → MUC Jul 10, 17:00 UTCJul 10, 18:45 UTC1h 45m
2026-07-10 DLH2PM MUC → ARN Jul 10, 13:45 UTCJul 10, 15:45 UTC2h 0m
2026-07-10 DLH9VT - Jul 10, 10:10 UTCJul 10, 11:45 UTC1h 35m
2026-07-10 DLH8CF - Jul 10, 07:30 UTCJul 10, 09:05 UTC1h 35m
2026-07-10 DLH2467 HEL → MUC Jul 10, 03:05 UTCJul 10, 05:20 UTC2h 15m
2026-07-09 DLH2466 MUC → HEL Jul 9, 20:30 UTCJul 9, 22:55 UTC2h 25m
2026-07-09 DLH05U BCN → MUC Jul 9, 16:55 UTCJul 9, 18:40 UTC1h 45m
2026-07-09 DLH77M MUC → BCN Jul 9, 14:00 UTCJul 9, 15:45 UTC1h 45m
2026-07-09 DLH8KK - Jul 9, 11:20 UTCJul 9, 12:10 UTC50m
2026-07-09 DLH2AW - Jul 9, 09:30 UTCJul 9, 10:15 UTC45m
2026-07-09 DLH11X NCE → MUC Jul 9, 07:00 UTCJul 9, 08:05 UTC1h 5m
2026-07-09 DLH05M MUC → NCE Jul 9, 04:50 UTCJul 9, 05:55 UTC1h 5m
2026-07-08 DLH05U BCN → MUC Jul 8, 16:45 UTCJul 8, 18:35 UTC1h 50m
2026-07-08 DLH77M - Jul 8, 14:05 UTCJul 8, 15:40 UTC1h 35m
2026-07-08 DLH96K - Jul 8, 10:20 UTCJul 8, 12:10 UTC1h 50m
2026-07-08 DLH63M - Jul 8, 07:10 UTCJul 8, 08:55 UTC1h 45m
2026-07-08 DLH2467 HEL → MUC Jul 8, 03:10 UTCJul 8, 05:25 UTC2h 15m
2026-07-07 BTI32B RIX → HEL Jul 7, 21:40 UTCJul 7, 22:20 UTC40m
2026-07-07 BTI97H OLB → RIX Jul 7, 16:45 UTCJul 7, 19:40 UTC2h 55m
2026-07-07 BTI44T RIX → OLB Jul 7, 12:30 UTCJul 7, 15:35 UTC3h 5m
2026-07-07 BTI65T - Jul 7, 08:50 UTCJul 7, 10:55 UTC2h 5m
2026-07-07 BTI87A - Jul 7, 04:40 UTCJul 7, 07:15 UTC2h 35m

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

Mode-S 502D7B frequently asked

What is Mode-S code 502D7B?
502D7B is an ICAO 24-bit transponder address. Allocated to Latvia. Assigned to YL-ABQ.
Where is Mode-S 502D7B registered?
Mode-S code 502D7B is allocated to Latvia (LV). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 502D7B broadcasting right now?
No active broadcast right now. Last signal was 5h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 502D7B, octal 24026573, decimal 5,254,523.
What flights does 502D7B operate?
Mode-S 502D7B has broadcast 20 distinct callsigns, including ASL423, ASL422, ASL98C, ASL90F, ASL64R.