Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

502CCE

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-CSE · AIRBUS A220-300

Hex
502CCE
Octal
24026316
Decimal
5,254,350
Country
LV
Tail
YL-CSE
Type
BCS3
No current signal · last broadcast 4h ago
Flights observed
488
Distinct callsigns
20
Country
LV
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S 502CCE.

Country allocation

The ICAO 24-bit address 502CCE 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
BTI724 Air Baltic 9 2026-06-30
BTI35G - 8 2026-07-05
BTI9TZ - 6 2026-07-11
BTI8ED Air Baltic 6 2026-06-05
BTI89G Air Baltic 6 2026-06-05
BTI84D - 6 2026-07-09
BTI3PR - 6 2026-07-02
BTI3LR - 6 2026-07-08
BTI3FL - 6 2026-07-02
BTI26R - 6 2026-07-11
BTI98T - 5 2026-07-09
BTI8KY - 5 2026-07-09
BTI8HM Air Baltic 5 2026-05-15
BTI7HB - 5 2026-07-09
BTI7FR Air Baltic 5 2026-05-15
BTI9KH - 4 2026-07-02
BTI8MT Air Baltic 4 2026-05-28
BTI8DN Air Baltic 4 2026-04-17
BTI79M - 4 2026-06-18
BTI725 - 4 2026-06-30

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 BTI6BM LGW → RIX Jul 14, 16:30 UTCJul 14, 18:50 UTC2h 20m
2026-07-14 BTI6BL - Jul 14, 12:45 UTCJul 14, 15:05 UTC2h 20m
2026-07-14 BTI69R - Jul 14, 09:15 UTCJul 14, 11:35 UTC2h 20m
2026-07-14 BTI8GJ - Jul 14, 04:25 UTCJul 14, 06:50 UTC2h 25m
2026-07-14 BTI9FJ SKG → RIX Jul 14, 00:50 UTCJul 14, 03:25 UTC2h 35m
2026-07-13 BTI7EJ - Jul 13, 21:20 UTCJul 13, 23:45 UTC2h 25m
2026-07-13 BTI11X - Jul 13, 18:25 UTCJul 13, 19:10 UTC45m
2026-07-13 BTI1X9 - Jul 13, 16:40 UTCJul 13, 17:25 UTC45m
2026-07-13 BTI6YC - Jul 13, 14:00 UTCJul 13, 15:35 UTC1h 35m
2026-07-13 BTI26F - Jul 13, 11:25 UTCJul 13, 13:00 UTC1h 35m
2026-07-13 BTI6RZ - Jul 13, 08:40 UTCJul 13, 10:25 UTC1h 45m
2026-07-13 BTI6RV - Jul 13, 05:01 UTCJul 13, 06:55 UTC1h 55m
2026-07-13 BTI36V TLL → RIX Jul 13, 02:40 UTCJul 13, 03:10 UTC30m
2026-07-12 BTI7NK - Jul 12, 20:35 UTCJul 12, 22:05 UTC1h 30m
2026-07-12 BTI3ZN TLL → HAM Jul 12, 17:50 UTCJul 12, 19:25 UTC1h 35m
2026-07-12 BTI2RX - Jul 12, 15:30 UTCJul 12, 16:50 UTC1h 20m
2026-07-12 BTI9QU TLL → BLL Jul 12, 13:01 UTCJul 12, 14:30 UTC1h 30m
2026-07-12 BTI4YE - Jul 12, 11:35 UTCJul 12, 12:10 UTC35m
2026-07-12 BTI8FX - Jul 12, 08:25 UTCJul 12, 10:45 UTC2h 20m
2026-07-12 BTI3EB - Jul 12, 04:25 UTCJul 12, 06:30 UTC2h 5m
2026-07-11 BTI26R BCN → RIX Jul 11, 09:20 UTCJul 11, 12:40 UTC3h 20m
2026-07-11 BTI9TZ - Jul 11, 04:45 UTCJul 11, 07:55 UTC3h 10m
2026-07-11 BTI3WX - Jul 11, 02:25 UTCJul 11, 03:10 UTC45m
2026-07-10 BTI3U9 - Jul 10, 21:10 UTCJul 10, 21:50 UTC40m
2026-07-10 BTI6C4 BRU → RIX Jul 10, 17:40 UTCJul 10, 19:45 UTC2h 5m
2026-07-10 BTI6C3 - Jul 10, 14:40 UTCJul 10, 16:40 UTC2h 0m
2026-07-10 BTI34G - Jul 10, 13:05 UTCJul 10, 13:40 UTC35m
2026-07-10 BTI7ZV - Jul 10, 09:05 UTCJul 10, 12:05 UTC3h 0m
2026-07-10 BTI76Q - Jul 10, 05:05 UTCJul 10, 07:50 UTC2h 45m
2026-07-09 BTI9GR - Jul 9, 19:50 UTCJul 9, 21:10 UTC1h 20m
2026-07-09 BTI6CD VNO → BER Jul 9, 17:50 UTCJul 9, 19:00 UTC1h 10m
2026-07-09 BTI84D - Jul 9, 14:55 UTCJul 9, 16:50 UTC1h 55m
2026-07-09 BTI98T - Jul 9, 11:35 UTCJul 9, 13:35 UTC2h 0m
2026-07-09 BTI8KY - Jul 9, 08:40 UTCJul 9, 10:35 UTC1h 55m
2026-07-09 BTI7HB VNO → AMS Jul 9, 04:55 UTCJul 9, 07:00 UTC2h 5m
2026-07-08 BTI3LR - Jul 8, 21:20 UTCJul 8, 21:50 UTC30m
2026-07-07 BTI2J4 HAM → RIX Jul 7, 18:35 UTCJul 7, 19:55 UTC1h 20m
2026-07-07 BTI84W RIX → HAM Jul 7, 16:00 UTCJul 7, 17:30 UTC1h 30m
2026-07-07 BTI97L - Jul 7, 13:45 UTCJul 7, 13:55 UTC10m
2026-07-07 BTI97L - Jul 7, 12:00 UTCJul 7, 13:05 UTC1h 5m
2026-07-07 BTI9RG - Jul 7, 09:00 UTCJul 7, 11:05 UTC2h 5m
2026-07-07 BTI1R2 - Jul 7, 06:25 UTCJul 7, 07:35 UTC1h 10m
2026-07-07 BTI15P - Jul 7, 04:05 UTCJul 7, 05:25 UTC1h 20m
2026-07-06 BTI72C PSA → RIX Jul 6, 18:25 UTCJul 6, 21:00 UTC2h 35m
2026-07-06 BTI2WT - Jul 6, 14:35 UTCJul 6, 17:10 UTC2h 35m
2026-07-06 BTI1B6 - Jul 6, 12:30 UTCJul 6, 13:30 UTC1h 0m
2026-07-06 BTI1A5 RIX → CPH Jul 6, 10:30 UTCJul 6, 11:45 UTC1h 15m
2026-07-06 BTI7LZ - Jul 6, 07:40 UTCJul 6, 09:45 UTC2h 5m
2026-07-06 BTI7PY - Jul 6, 04:15 UTCJul 6, 06:25 UTC2h 10m
2026-07-05 BTI2J4 - Jul 5, 18:20 UTCJul 5, 19:55 UTC1h 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-CSE page for operator, model, and routing details .

Mode-S 502CCE frequently asked

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