sensors Mode-S transponder

502DB3

ICAO 24-bit transponder address · allocated to Latvia

Hex
502DB3
Octal
24026663
Decimal
5,254,579
Country
LV
Broadcasting now · callsign BTI725 · 36,975 ft
Flights observed
645
Distinct callsigns
20
Country
LV
Last broadcast
Jul 26, 22:45 UTC

Current position

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

Country allocation

The ICAO 24-bit address 502DB3 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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 DLH2466 MUC → HEL Jul 26, 20:40 UTCJul 26, 22:45 UTC2h 5m
2026-07-26 DLH05U CDG → MUC Jul 26, 17:05 UTCJul 26, 19:00 UTC1h 55m
2026-07-26 DLH77M FRA → VLC Jul 26, 14:00 UTCJul 26, 15:30 UTC1h 30m
2026-07-26 DLH8KK ZRH → MUC Jul 26, 11:25 UTCJul 26, 12:05 UTC40m
2026-07-26 DLH2AW MUC → CGN Jul 26, 09:30 UTCJul 26, 10:15 UTC45m
2026-07-26 DLH11X FRA → OPO Jul 26, 07:00 UTCJul 26, 08:05 UTC1h 5m
2026-07-26 DLH05M MUC → NCE Jul 26, 04:45 UTCJul 26, 05:50 UTC1h 5m
2026-07-25 DLH4NV VCE → FRA Jul 25, 16:40 UTCJul 25, 18:35 UTC1h 55m
2026-07-25 DLH3FU MUC → BGO Jul 25, 13:50 UTCJul 25, 15:35 UTC1h 45m
2026-07-25 DLH96K BIO → MUC Jul 25, 10:25 UTCJul 25, 12:10 UTC1h 45m
2026-07-25 DLH63M FRA → SPC Jul 25, 07:00 UTCJul 25, 08:45 UTC1h 45m
2026-07-25 DLH2467 HEL → MUC Jul 25, 03:15 UTCJul 25, 05:30 UTC2h 15m
2026-07-24 BTI32B RIX → HEL Jul 24, 22:45 UTCJul 24, 23:30 UTC45m
2026-07-24 BTI8HM LIS → RIX Jul 24, 16:50 UTCJul 24, 20:45 UTC3h 55m
2026-07-24 BTI7FR RIX → LIS Jul 24, 11:10 UTCJul 24, 15:40 UTC4h 30m
2026-07-24 BTI60L BRU → RIX Jul 24, 08:15 UTCJul 24, 10:15 UTC2h 0m
2026-07-24 BTI60K RIX → BRU Jul 24, 04:40 UTCJul 24, 06:45 UTC2h 5m
2026-07-23 BTI6UQ MUC → RIX Jul 23, 18:15 UTCJul 23, 20:05 UTC1h 50m
2026-07-23 BTI8BX RIX → MUC Jul 23, 15:15 UTCJul 23, 17:05 UTC1h 50m
2026-07-23 BTI6GN OTP → RIX Jul 23, 12:15 UTCJul 23, 14:20 UTC2h 5m
2026-07-23 BTI9BN RIX → OTP Jul 23, 09:05 UTCJul 23, 11:10 UTC2h 5m
2026-07-23 BTI1M2 ARN → RIX Jul 23, 07:05 UTCJul 23, 07:50 UTC45m
2026-07-23 BTI1M1 RIX → ARN Jul 23, 05:20 UTCJul 23, 06:10 UTC50m
2026-07-23 BTI3KB KEF → RIX Jul 23, 01:10 UTCJul 23, 04:35 UTC3h 25m
2026-07-22 BTI2HU RIX → KEF Jul 22, 20:35 UTCJul 23, 00:10 UTC3h 35m
2026-07-22 BTI79M TLL → RIX Jul 22, 19:10 UTCJul 22, 19:40 UTC30m
2026-07-22 BTI4ZK RIX → TLL Jul 22, 17:50 UTCJul 22, 18:25 UTC35m
2026-07-22 BTI6GB FCO → RIX Jul 22, 14:15 UTCJul 22, 16:55 UTC2h 40m
2026-07-22 BTI9KV RIX → FCO Jul 22, 10:20 UTCJul 22, 11:55 UTC1h 35m
2026-07-22 BTI13F RIX → CPH Jul 22, 04:15 UTCJul 22, 05:25 UTC1h 10m
2026-07-21 BTI88Q ABZ → RIX Jul 21, 17:20 UTCJul 21, 19:20 UTC2h 0m
2026-07-21 BTI3MQ RIX → ABZ Jul 21, 14:10 UTCJul 21, 16:25 UTC2h 15m
2026-07-21 BTI7FN HER → RIX Jul 21, 09:25 UTCJul 21, 12:30 UTC3h 5m
2026-07-21 BTI46P RIX → HER Jul 21, 04:55 UTCJul 21, 08:00 UTC3h 5m
2026-07-21 BTI35G VNO → RIX Jul 21, 02:35 UTCJul 21, 03:10 UTC35m
2026-07-20 BTI3LR - Jul 20, 21:35 UTCJul 20, 22:05 UTC30m
2026-07-20 BTI15L OSL → RIX Jul 20, 18:50 UTCJul 20, 20:05 UTC1h 15m
2026-07-20 BTI15M - Jul 20, 16:45 UTCJul 20, 18:00 UTC1h 15m
2026-07-20 BTI6GB FCO → RIX Jul 20, 12:55 UTCJul 20, 15:20 UTC2h 25m
2026-07-20 BTI9KV RIX → FCO Jul 20, 08:35 UTCJul 20, 11:20 UTC2h 45m
2026-07-20 BTI13G CPH → RIX Jul 20, 06:35 UTCJul 20, 07:45 UTC1h 10m
2026-07-20 BTI13F RIX → CPH Jul 20, 04:10 UTCJul 20, 05:20 UTC1h 10m
2026-07-20 BTI8ME PLQ → RIX Jul 20, 02:45 UTCJul 20, 03:10 UTC25m
2026-07-19 BTI7JW - Jul 19, 21:30 UTCJul 19, 21:50 UTC20m
2026-07-19 BTI83U VIE → RIX Jul 19, 18:50 UTCJul 19, 20:25 UTC1h 35m
2026-07-19 BTI7BA - Jul 19, 16:10 UTCJul 19, 17:55 UTC1h 45m
2026-07-19 BTI1B6 CPH → RIX Jul 19, 14:15 UTCJul 19, 15:15 UTC1h 0m
2026-07-19 BTI1A5 RIX → CPH Jul 19, 12:20 UTCJul 19, 13:25 UTC1h 5m
2026-07-19 BTI6A2 DUB → RIX Jul 19, 08:45 UTCJul 19, 11:25 UTC2h 40m
2026-07-19 BTI6A1 RIX → DUB Jul 19, 04:40 UTCJul 19, 07:30 UTC2h 50m

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.

Mode-S 502DB3 frequently asked

What is Mode-S code 502DB3?
502DB3 is an ICAO 24-bit transponder address. Allocated to Latvia.
Where is Mode-S 502DB3 registered?
Mode-S code 502DB3 is allocated to Latvia (LV). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 502DB3 broadcasting right now?
Yes. Mode-S 502DB3 is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 502DB3, octal 24026663, decimal 5,254,579.
What flights does 502DB3 operate?
Mode-S 502DB3 has broadcast 20 distinct callsigns, including BEL5BN, BEL2SC, BEL2JE, BEL1ZT, BEL4SF.