Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

502D65

ICAO 24-bit transponder address · allocated to Latvia

Currently assigned to YL-ARE · EMBRAER EMB-135 Legacy

Hex
502D65
Octal
24026545
Decimal
5,254,501
Country
LV
Tail
YL-ARE
Type
E35L
No current signal · last broadcast 7d ago
Flights observed
95
Distinct callsigns
1
Country
LV
Last broadcast
7d ago

Last known position

Most recent position reported by Mode-S 502D65.

Country allocation

The ICAO 24-bit address 502D65 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 1 distinct

Callsign Airline Flights Last seen
UAG84C - 95 2026-07-12

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-12 UAG84C - Jul 12, 00:01 UTCJul 12, 02:05 UTC2h 5m
2026-07-11 UAG84C - Jul 11, 20:50 UTCJul 11, 22:50 UTC2h 0m
2026-07-11 UAG84C - Jul 11, 19:15 UTCJul 11, 19:45 UTC30m
2026-07-10 UAG84C - Jul 10, 13:50 UTCJul 10, 14:05 UTC15m
2026-07-10 UAG84C - Jul 10, 10:20 UTCJul 10, 12:20 UTC2h 0m
2026-07-09 UAG84C - Jul 9, 17:55 UTCJul 9, 20:00 UTC2h 5m
2026-07-09 UAG84C VNO → KUN Jul 9, 15:30 UTCJul 9, 15:50 UTC20m
2026-07-09 UAG84C NCE → VNO Jul 9, 11:55 UTCJul 9, 14:30 UTC2h 35m
2026-07-07 UAG84C LIN → NCE Jul 7, 17:10 UTCJul 7, 17:45 UTC35m
2026-07-07 UAG84C - Jul 7, 14:25 UTCJul 7, 15:50 UTC1h 25m
2026-07-07 UAG84C - Jul 7, 07:15 UTCJul 7, 08:35 UTC1h 20m
2026-07-06 UAG84C - Jul 6, 08:35 UTCJul 6, 09:40 UTC1h 5m
2026-07-06 UAG84C NCE → LIN Jul 6, 06:55 UTCJul 6, 07:30 UTC35m
2026-07-04 UAG84C VNO → NCE Jul 4, 07:15 UTCJul 4, 09:45 UTC2h 30m
2026-07-01 UAG84C VIE → VNO Jul 1, 17:10 UTCJul 1, 19:00 UTC1h 50m
2026-07-01 UAG84C - Jul 1, 13:55 UTCJul 1, 15:50 UTC1h 55m
2026-06-30 UAG84C - Jun 30, 20:55 UTCJun 30, 21:25 UTC30m
2026-06-30 UAG84C - Jun 30, 18:00 UTCJun 30, 20:40 UTC2h 40m
2026-06-30 UAG84C - Jun 30, 11:50 UTCJun 30, 14:30 UTC2h 40m
2026-06-30 UAG84C RIX → KUN Jun 30, 10:00 UTCJun 30, 10:35 UTC35m
2026-06-27 UAG84C - Jun 27, 16:55 UTCJun 27, 19:24 UTC2h 30m
2026-06-27 UAG84C - Jun 27, 12:34 UTCJun 27, 15:39 UTC3h 5m
2026-06-27 UAG84C - Jun 27, 10:00 UTCJun 27, 10:50 UTC50m
2026-06-27 UAG84C - Jun 27, 07:59 UTCJun 27, 09:04 UTC1h 5m
2026-06-26 UAG84C NCE → ISL Jun 26, 11:34 UTCJun 26, 14:05 UTC2h 30m
2026-06-26 UAG84C TBS → NCE Jun 26, 05:30 UTCJun 26, 09:50 UTC4h 20m
2026-06-25 UAG84C - Jun 25, 03:59 UTCJun 25, 08:24 UTC4h 25m
2026-06-22 UAG84C - Jun 22, 16:05 UTCJun 22, 18:44 UTC2h 40m
2026-06-22 UAG84C - Jun 22, 12:19 UTCJun 22, 14:24 UTC2h 5m
2026-06-22 UAG84C NCE → ORY Jun 22, 10:05 UTCJun 22, 11:14 UTC1h 10m
2026-06-21 UAG84C IBZ → NCE Jun 21, 20:05 UTCJun 21, 21:14 UTC1h 10m
2026-06-21 UAG84C BMA → IBZ Jun 21, 15:09 UTCJun 21, 18:44 UTC3h 35m
2026-06-21 UAG84C - Jun 21, 12:40 UTCJun 21, 13:29 UTC50m
2026-06-20 UAG84C - Jun 20, 10:09 UTCJun 20, 13:59 UTC3h 50m
2026-06-19 UAG84C - Jun 19, 16:44 UTCJun 19, 17:39 UTC55m
2026-06-19 UAG84C - Jun 19, 13:50 UTCJun 19, 14:54 UTC1h 5m
2026-06-19 UAG84C HAM → ISL Jun 19, 10:14 UTCJun 19, 12:54 UTC2h 40m
2026-06-14 UAG84C - Jun 14, 08:45 UTCJun 14, 11:45 UTC3h 0m
2026-06-12 UAG84C - Jun 12, 23:55 UTCJun 13, 00:15 UTC20m
2026-06-12 UAG84C - Jun 12, 19:50 UTCJun 12, 22:20 UTC2h 30m
2026-06-11 UAG84C MAD → NCE Jun 11, 15:25 UTCJun 11, 16:55 UTC1h 30m
2026-06-11 UAG84C - Jun 11, 11:55 UTCJun 11, 13:40 UTC1h 45m
2026-06-10 UAG84C - Jun 10, 07:15 UTCJun 10, 10:20 UTC3h 5m
2026-06-09 UAG84C - Jun 9, 15:10 UTCJun 9, 15:50 UTC40m
2026-06-09 UAG84C - Jun 9, 13:05 UTCJun 9, 14:10 UTC1h 5m
2026-06-09 UAG84C BOH → AMS Jun 9, 09:35 UTCJun 9, 10:30 UTC55m
2026-06-07 UAG84C - Jun 7, 17:20 UTCJun 7, 20:10 UTC2h 50m
2026-06-07 UAG84C - Jun 7, 15:00 UTCJun 7, 16:20 UTC1h 20m
2026-06-05 UAG84C - Jun 5, 11:10 UTCJun 5, 12:30 UTC1h 20m
2026-06-05 UAG84C BOH → VNO Jun 5, 07:55 UTCJun 5, 10:20 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-ARE page for operator, model, and routing details .

Mode-S 502D65 frequently asked

What is Mode-S code 502D65?
502D65 is an ICAO 24-bit transponder address. Allocated to Latvia. Assigned to YL-ARE.
Where is Mode-S 502D65 registered?
Mode-S code 502D65 is allocated to Latvia (LV). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 502D65 broadcasting right now?
No active broadcast right now. Last signal was 7d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 502D65, octal 24026545, decimal 5,254,501.
What flights does 502D65 operate?
Mode-S 502D65 has broadcast 1 distinct callsign, including UAG84C.