sensors Mode-S transponder
502DA4
ICAO 24-bit transponder address · allocated to Latvia
Currently assigned to YL-ECT · EMBRAER EMB-135 Legacy
- Hex
- 502DA4
- Octal
- 24026644
- Decimal
- 5,254,564
- Country
- LV
- Tail
- YL-ECT
- Type
- E35L
- Flights observed
- 73
- Distinct callsigns
- 2
- Country
- LV
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 502DA4 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-18 | UAG34L | - | Jul 18, 09:35 UTC | Jul 18, 11:40 UTC | 2h 5m |
| 2026-07-18 | UAG34L | - | Jul 18, 07:35 UTC | Jul 18, 08:10 UTC | 35m |
| 2026-07-16 | UAG34L | MAN → BUD | Jul 16, 22:40 UTC | Jul 17, 00:55 UTC | 2h 15m |
| 2026-07-16 | UAG34L | - | Jul 16, 08:25 UTC | Jul 16, 10:59 UTC | 2h 35m |
| 2026-07-15 | UAG34L | - | Jul 15, 16:05 UTC | Jul 15, 16:35 UTC | 30m |
| 2026-07-08 | UAG34L | - | Jul 8, 09:50 UTC | Jul 8, 12:00 UTC | 2h 10m |
| 2026-07-07 | UAG34L | - | Jul 7, 11:05 UTC | Jul 7, 13:55 UTC | 2h 50m |
| 2026-07-06 | UAG34L | - | Jul 6, 13:25 UTC | Jul 7, 12:35 UTC | 23h 10m |
| 2026-07-06 | UAG34L | - | Jul 6, 10:20 UTC | Jul 6, 13:55 UTC | 3h 35m |
| 2026-07-04 | UAG34L | - | Jul 4, 12:20 UTC | Jul 4, 13:25 UTC | 1h 5m |
| 2026-07-02 | UAG34L | - | Jul 2, 15:30 UTC | Jul 2, 16:40 UTC | 1h 10m |
| 2026-07-02 | UAG34L | - | Jul 2, 09:30 UTC | Jul 2, 10:40 UTC | 1h 10m |
| 2026-07-02 | UAG34L | - | Jul 2, 07:30 UTC | Jul 2, 08:15 UTC | 45m |
| 2026-06-30 | UAG34L | - | Jun 30, 16:10 UTC | Jun 30, 17:00 UTC | 50m |
| 2026-06-30 | UAG34L | - | Jun 30, 10:05 UTC | Jun 30, 14:50 UTC | 4h 45m |
| 2026-06-26 | UAG34L | - | Jun 26, 07:45 UTC | Jun 26, 08:15 UTC | 30m |
| 2026-06-22 | UAG34L | - | Jun 22, 06:49 UTC | Jun 22, 09:30 UTC | 2h 40m |
| 2026-06-21 | UAG34L | MUC → NCE | Jun 21, 17:54 UTC | Jun 21, 19:05 UTC | 1h 10m |
| 2026-06-21 | UAG34L | - | Jun 21, 12:04 UTC | Jun 21, 15:54 UTC | 3h 50m |
| 2026-06-21 | UAG34L | - | Jun 21, 07:59 UTC | Jun 21, 08:20 UTC | 20m |
| 2026-06-20 | UAG34L | - | Jun 20, 11:54 UTC | Jun 20, 13:59 UTC | 2h 5m |
| 2026-06-20 | UAG34L | - | Jun 20, 07:59 UTC | Jun 20, 09:59 UTC | 2h 0m |
| 2026-06-17 | UAG34L | - | Jun 17, 14:40 UTC | Jun 17, 17:45 UTC | 3h 5m |
| 2026-06-17 | UAG34L | - | Jun 17, 12:10 UTC | Jun 17, 13:10 UTC | 1h 0m |
| 2026-06-16 | UAG34L | - | Jun 16, 07:40 UTC | Jun 16, 10:15 UTC | 2h 35m |
| 2026-06-16 | UAG34L | - | Jun 16, 04:20 UTC | Jun 16, 06:45 UTC | 2h 25m |
| 2026-06-15 | UAG34L | - | Jun 15, 09:40 UTC | Jun 15, 12:25 UTC | 2h 45m |
| 2026-06-15 | UAG34L | - | Jun 15, 05:55 UTC | Jun 15, 08:40 UTC | 2h 45m |
| 2026-06-11 | UAG34L | - | Jun 11, 07:10 UTC | Jun 11, 09:00 UTC | 1h 50m |
| 2026-06-07 | UAG34L | - | Jun 7, 04:00 UTC | Jun 7, 04:30 UTC | 30m |
| 2026-06-06 | UAG34L | NCE → TLV | Jun 6, 22:50 UTC | Jun 7, 02:25 UTC | 3h 35m |
| 2026-06-06 | UAG34L | PRG → NCE | Jun 6, 19:50 UTC | Jun 6, 21:20 UTC | 1h 30m |
| 2026-05-31 | UAG34L | VIE → PRG | May 31, 12:55 UTC | May 31, 13:35 UTC | 40m |
| 2026-05-30 | UAG34L | VIE → MUC | May 30, 11:40 UTC | May 30, 12:20 UTC | 40m |
| 2026-05-30 | UAG34L | - | May 30, 09:35 UTC | May 30, 11:00 UTC | 1h 25m |
| 2026-05-30 | UAG34L | GVA → BRU | May 30, 06:00 UTC | May 30, 07:00 UTC | 1h 0m |
| 2026-05-29 | UAG34L | - | May 29, 02:25 UTC | May 29, 04:10 UTC | 1h 45m |
| 2026-05-28 | UAG34L | - | May 28, 20:50 UTC | May 29, 00:35 UTC | 3h 45m |
| 2026-05-26 | UAG34L | - | May 26, 15:54 UTC | May 26, 17:15 UTC | 1h 20m |
| 2026-05-26 | UAG34L | - | May 26, 13:40 UTC | May 26, 15:05 UTC | 1h 25m |
| 2026-05-25 | UAG34L | - | May 25, 11:30 UTC | May 25, 13:40 UTC | 2h 10m |
| 2026-05-19 | UAG34L | - | May 19, 16:00 UTC | May 19, 17:15 UTC | 1h 15m |
| 2026-05-19 | UAG34L | - | May 19, 12:20 UTC | May 19, 15:10 UTC | 2h 50m |
| 2026-05-19 | UAG34L | - | May 19, 08:55 UTC | May 19, 10:15 UTC | 1h 20m |
| 2026-05-18 | UAG34L | - | May 18, 13:35 UTC | May 18, 15:15 UTC | 1h 40m |
| 2026-05-18 | UAG34L | - | May 18, 10:15 UTC | May 18, 12:05 UTC | 1h 50m |
| 2026-05-17 | UAG034L | IBZ → GVA | May 17, 13:25 UTC | May 17, 14:55 UTC | 1h 30m |
| 2026-05-14 | UAG034L | - | May 14, 08:10 UTC | May 14, 09:45 UTC | 1h 35m |
| 2026-05-14 | UAG34L | ZRH → GVA | May 14, 06:25 UTC | May 14, 07:00 UTC | 35m |
| 2026-05-11 | UAG34L | BUD → ZRH | May 11, 18:20 UTC | May 11, 19:55 UTC | 1h 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-ECT page for operator, model, and routing details .