sensors Mode-S transponder
502DAD
ICAO 24-bit transponder address · allocated to Latvia
- Hex
- 502DAD
- Octal
- 24026655
- Decimal
- 5,254,573
- Country
- LV
- Flights observed
- 50
- Distinct callsigns
- 2
- Country
- LV
- Last broadcast
- 7d ago
Last known position
Country allocation
The ICAO 24-bit address 502DAD 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | UAG202 | - | Jul 25, 12:10 UTC | Jul 25, 15:45 UTC | 3h 35m |
| 2026-07-25 | UAG202 | - | Jul 25, 09:35 UTC | Jul 25, 10:15 UTC | 40m |
| 2026-07-23 | UAG202 | - | Jul 23, 10:45 UTC | Jul 23, 12:35 UTC | 1h 50m |
| 2026-07-20 | UAG202 | - | Jul 20, 16:35 UTC | Jul 20, 18:50 UTC | 2h 15m |
| 2026-07-20 | UAG202 | - | Jul 20, 13:25 UTC | Jul 20, 15:50 UTC | 2h 25m |
| 2026-07-20 | UAG202 | - | Jul 20, 08:50 UTC | Jul 20, 10:10 UTC | 1h 20m |
| 2026-07-17 | UAG202 | - | Jul 17, 13:40 UTC | Jul 17, 20:20 UTC | 6h 40m |
| 2026-07-17 | UAG202 | VNO → NCE | Jul 17, 07:14 UTC | Jul 17, 09:55 UTC | 2h 40m |
| 2026-07-08 | UAG202 | - | Jul 8, 16:00 UTC | Jul 8, 17:25 UTC | 1h 25m |
| 2026-07-07 | UAG202 | - | Jul 7, 08:55 UTC | Jul 7, 11:20 UTC | 2h 25m |
| 2026-07-01 | UAG202 | - | Jul 1, 16:05 UTC | Jul 1, 18:40 UTC | 2h 35m |
| 2026-06-29 | UAG202 | VNO → CIA | Jun 29, 10:10 UTC | Jun 29, 12:29 UTC | 2h 20m |
| 2026-06-22 | UAG202 | IBZ → VNO | Jun 22, 06:19 UTC | Jun 22, 09:40 UTC | 3h 20m |
| 2026-06-22 | UAG202 | - | Jun 22, 04:40 UTC | Jun 22, 04:59 UTC | 20m |
| 2026-06-19 | UAG202 | - | Jun 19, 14:34 UTC | Jun 19, 14:54 UTC | 20m |
| 2026-06-19 | UAG202 | VNO → IBZ | Jun 19, 09:49 UTC | Jun 19, 13:14 UTC | 3h 25m |
| 2026-06-16 | UAG202 | ZRH → VNO | Jun 16, 16:55 UTC | Jun 16, 18:55 UTC | 2h 0m |
| 2026-06-15 | UAG202 | VNO → ZRH | Jun 15, 11:00 UTC | Jun 15, 13:05 UTC | 2h 5m |
| 2026-06-14 | UAG202 | - | Jun 14, 18:30 UTC | Jun 14, 19:05 UTC | 35m |
| 2026-06-14 | UAG202 | - | Jun 14, 14:00 UTC | Jun 14, 16:30 UTC | 2h 30m |
| 2026-06-13 | UAG202 | - | Jun 13, 10:10 UTC | Jun 13, 14:30 UTC | 4h 20m |
| 2026-06-13 | UAG202 | - | Jun 13, 06:30 UTC | Jun 13, 06:50 UTC | 20m |
| 2026-06-11 | UAG202 | - | Jun 11, 19:15 UTC | Jun 11, 21:45 UTC | 2h 30m |
| 2026-06-08 | UAG101 | - | Jun 8, 17:50 UTC | Jun 9, 10:15 UTC | 16h 25m |
| 2026-06-07 | UAG101 | - | Jun 7, 04:00 UTC | Jun 7, 05:25 UTC | 1h 25m |
| 2026-06-06 | UAG101 | - | Jun 6, 07:40 UTC | Jun 6, 20:39 UTC | 13h 0m |
| 2026-06-05 | UAG101 | - | Jun 5, 01:05 UTC | Jun 5, 04:25 UTC | 3h 20m |
| 2026-06-04 | UAG101 | - | Jun 4, 20:55 UTC | Jun 4, 21:15 UTC | 20m |
| 2026-06-04 | UAG202 | - | Jun 4, 08:35 UTC | Jun 4, 09:35 UTC | 1h 0m |
| 2026-06-04 | UAG202 | - | Jun 4, 06:15 UTC | Jun 4, 06:45 UTC | 30m |
| 2026-05-31 | UAG202 | BOD → TLS | May 31, 21:05 UTC | May 31, 21:35 UTC | 30m |
| 2026-05-31 | UAG202 | VNO → BOD | May 31, 17:00 UTC | May 31, 20:00 UTC | 3h 0m |
| 2026-05-26 | UAG202 | - | May 26, 13:54 UTC | May 26, 15:45 UTC | 1h 50m |
| 2026-05-25 | UAG202 | - | May 25, 15:10 UTC | May 25, 15:40 UTC | 30m |
| 2026-05-24 | UAG202 | - | May 24, 08:45 UTC | May 24, 09:25 UTC | 40m |
| 2026-05-18 | UAG202 | VNO → STN | May 18, 05:10 UTC | May 18, 07:30 UTC | 2h 20m |
| 2026-05-17 | UAG202 | STN → VNO | May 17, 09:40 UTC | May 17, 11:55 UTC | 2h 15m |
| 2026-05-14 | UAG202 | VNO → STN | May 14, 14:45 UTC | May 14, 17:15 UTC | 2h 30m |
| 2026-05-10 | UAG202 | VIE → VNO | May 10, 10:19 UTC | May 10, 11:45 UTC | 1h 25m |
| 2026-05-08 | UAG202 | VNO → VIE | May 8, 12:04 UTC | May 8, 13:40 UTC | 1h 35m |
| 2026-05-08 | UAG202 | - | May 8, 07:14 UTC | May 8, 09:25 UTC | 2h 10m |
| 2026-05-07 | UAG202 | VNO → GVA | May 7, 06:00 UTC | May 7, 08:30 UTC | 2h 30m |
| 2026-05-06 | UAG202 | - | May 6, 05:15 UTC | May 6, 07:40 UTC | 2h 25m |
| 2026-05-04 | UAG202 | - | May 4, 21:15 UTC | May 5, 01:10 UTC | 3h 55m |
| 2026-05-04 | UAG202 | - | May 4, 12:40 UTC | May 4, 19:50 UTC | 7h 11m |
| 2026-05-03 | UAG202 | LAX → FLL | May 3, 18:20 UTC | May 3, 22:39 UTC | 4h 20m |
| 2026-04-30 | UAG202 | - | Apr 30, 21:30 UTC | May 1, 13:35 UTC | 16h 5m |
| 2026-04-30 | UAG202 | VNO → LIN | Apr 30, 06:35 UTC | Apr 30, 08:40 UTC | 2h 5m |
| 2026-04-19 | UAG202 | INN → VNO | Apr 19, 11:15 UTC | Apr 19, 13:05 UTC | 1h 50m |
| 2026-04-17 | UAG202 | - | Apr 17, 11:20 UTC | Apr 17, 13:10 UTC | 1h 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.