sensors Mode-S transponder
502D61
ICAO 24-bit transponder address · allocated to Latvia
Currently assigned to YL-REX · EMBRAER EMB-135 Legacy
- Hex
- 502D61
- Octal
- 24026541
- Decimal
- 5,254,497
- Country
- LV
- Tail
- YL-REX
- Type
- E35L
- Flights observed
- 89
- Distinct callsigns
- 2
- Country
- LV
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 502D61 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-12 | UAG37B | JMK → DWC | Jul 12, 16:01 UTC | Jul 12, 21:10 UTC | 5h 10m |
| 2026-07-12 | UAG37B | - | Jul 12, 14:20 UTC | Jul 12, 14:55 UTC | 35m |
| 2026-07-10 | UAG37B | - | Jul 10, 17:35 UTC | Jul 10, 17:45 UTC | 10m |
| 2026-07-10 | UAG37B | - | Jul 10, 07:20 UTC | Jul 10, 15:55 UTC | 8h 35m |
| 2026-07-09 | UAG37B | - | Jul 9, 09:10 UTC | Jul 9, 14:40 UTC | 5h 30m |
| 2026-07-08 | UAG37B | - | Jul 8, 15:45 UTC | Jul 8, 16:50 UTC | 1h 5m |
| 2026-07-07 | UAG37B | - | Jul 7, 16:20 UTC | Jul 8, 16:15 UTC | 23h 55m |
| 2026-07-07 | UAG37B | - | Jul 7, 12:10 UTC | Jul 7, 16:25 UTC | 4h 15m |
| 2026-07-07 | UAG37B | - | Jul 7, 09:05 UTC | Jul 7, 10:25 UTC | 1h 20m |
| 2026-07-06 | UAG37B | - | Jul 6, 08:40 UTC | Jul 6, 09:30 UTC | 50m |
| 2026-07-06 | UAG37B | BRU → LBG | Jul 6, 05:55 UTC | Jul 6, 06:30 UTC | 35m |
| 2026-07-05 | UAG37B | - | Jul 5, 09:35 UTC | Jul 5, 14:15 UTC | 4h 40m |
| 2026-07-05 | UAG37B | - | Jul 5, 04:35 UTC | Jul 5, 05:50 UTC | 1h 15m |
| 2026-07-02 | UAG37B | - | Jul 2, 15:15 UTC | Jul 2, 15:55 UTC | 40m |
| 2026-07-02 | UAG37B | - | Jul 2, 13:25 UTC | Jul 2, 14:10 UTC | 45m |
| 2026-07-01 | UAG37B | - | Jul 1, 10:10 UTC | Jul 1, 13:30 UTC | 3h 20m |
| 2026-07-01 | UAG37B | NCE → AMS | Jul 1, 07:05 UTC | Jul 1, 08:45 UTC | 1h 40m |
| 2026-06-30 | UAG37B | - | Jun 30, 09:15 UTC | Jun 30, 13:00 UTC | 3h 45m |
| 2026-06-29 | UAG37B | - | Jun 29, 16:19 UTC | Jun 30, 13:00 UTC | 20h 41m |
| 2026-06-29 | UAG37B | TBS → NCE | Jun 29, 14:34 UTC | Jun 30, 13:00 UTC | 22h 26m |
| 2026-06-29 | UAG37B | LCA → TBS | Jun 29, 12:00 UTC | Jun 29, 13:44 UTC | 1h 45m |
| 2026-06-28 | UAG37B | - | Jun 28, 06:30 UTC | Jun 28, 07:20 UTC | 50m |
| 2026-06-28 | UAG37B | - | Jun 28, 01:29 UTC | Jun 28, 06:00 UTC | 4h 30m |
| 2026-06-26 | UAG37B | - | Jun 26, 12:50 UTC | Jun 26, 18:29 UTC | 5h 40m |
| 2026-06-22 | UAG37B | - | Jun 22, 18:04 UTC | Jun 22, 19:14 UTC | 1h 10m |
| 2026-06-22 | UAG37B | - | Jun 22, 14:34 UTC | Jun 22, 16:29 UTC | 1h 55m |
| 2026-06-21 | UAG37B | - | Jun 21, 16:10 UTC | Jun 21, 18:25 UTC | 2h 15m |
| 2026-06-21 | UAG37B | - | Jun 21, 13:44 UTC | Jun 21, 14:54 UTC | 1h 10m |
| 2026-06-21 | UAG37B | TLL → MXP | Jun 21, 09:35 UTC | Jun 21, 12:14 UTC | 2h 40m |
| 2026-06-19 | UAG37B | - | Jun 19, 16:19 UTC | Jun 19, 20:24 UTC | 4h 5m |
| 2026-06-18 | UAG37B | - | Jun 18, 20:30 UTC | Jun 18, 21:05 UTC | 35m |
| 2026-06-18 | UAG37B | - | Jun 18, 15:20 UTC | Jun 18, 19:35 UTC | 4h 15m |
| 2026-06-18 | UAG37B | - | Jun 18, 11:45 UTC | Jun 18, 13:00 UTC | 1h 15m |
| 2026-06-17 | UAG37B | - | Jun 17, 17:25 UTC | Jun 17, 19:50 UTC | 2h 25m |
| 2026-06-17 | UAG37B | TLL → RIX | Jun 17, 08:50 UTC | Jun 17, 09:25 UTC | 35m |
| 2026-06-15 | UAG37B | - | Jun 15, 17:25 UTC | Jun 15, 19:39 UTC | 2h 15m |
| 2026-06-14 | UAG37B | - | Jun 14, 13:45 UTC | Jun 14, 17:40 UTC | 3h 55m |
| 2026-06-08 | UAG37B | - | Jun 8, 14:10 UTC | Jun 8, 17:05 UTC | 2h 55m |
| 2026-06-04 | UAG37B | - | Jun 4, 21:45 UTC | Jun 4, 23:40 UTC | 1h 55m |
| 2026-06-04 | UAG37B | - | Jun 4, 19:35 UTC | Jun 4, 21:05 UTC | 1h 30m |
| 2026-06-04 | UAG37B | - | Jun 4, 11:50 UTC | Jun 4, 12:30 UTC | 40m |
| 2026-06-01 | UAG37B | AMM → CIA | Jun 1, 08:25 UTC | Jun 1, 11:15 UTC | 2h 50m |
| 2026-06-01 | UAG37B | - | Jun 1, 02:25 UTC | Jun 1, 05:55 UTC | 3h 30m |
| 2026-05-31 | UAG37B | - | May 31, 12:25 UTC | May 31, 14:05 UTC | 1h 40m |
| 2026-05-31 | UAG37B | PRG → BUD | May 31, 10:10 UTC | May 31, 11:10 UTC | 1h 0m |
| 2026-05-30 | UAG37B | BUD → PRG | May 30, 09:25 UTC | May 30, 10:20 UTC | 55m |
| 2026-05-30 | UAG37B | - | May 30, 06:40 UTC | May 30, 08:10 UTC | 1h 30m |
| 2026-05-29 | UAG37B | - | May 29, 11:15 UTC | May 29, 15:20 UTC | 4h 5m |
| 2026-05-27 | UAG37B | - | May 27, 15:15 UTC | May 27, 17:20 UTC | 2h 5m |
| 2026-05-27 | UAG37B | - | May 27, 08:30 UTC | May 27, 10:30 UTC | 2h 0m |
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-REX page for operator, model, and routing details .