sensors Mode-S transponder
502DB6
ICAO 24-bit transponder address · allocated to Latvia
Currently assigned to YL-ELF · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 502DB6
- Octal
- 24026666
- Decimal
- 5,254,582
- Country
- LV
- Tail
- YL-ELF
- Type
- GLEX
- Flights observed
- 50
- Distinct callsigns
- 1
- Country
- LV
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 502DB6 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 |
|---|---|---|---|
| UAG99W | - | 50 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | UAG99W | - | Jul 26, 13:30 UTC | Jul 26, 14:00 UTC | 30m |
| 2026-07-26 | UAG99W | - | Jul 26, 10:40 UTC | Jul 26, 11:15 UTC | 35m |
| 2026-07-26 | UAG99W | - | Jul 26, 07:00 UTC | Jul 26, 08:25 UTC | 1h 25m |
| 2026-07-15 | UAG99W | - | Jul 15, 17:00 UTC | Jul 15, 18:20 UTC | 1h 20m |
| 2026-07-15 | UAG99W | NCE → OLB | Jul 15, 14:45 UTC | Jul 15, 15:30 UTC | 45m |
| 2026-07-14 | UAG99W | VIE → NCE | Jul 14, 15:35 UTC | Jul 14, 16:55 UTC | 1h 20m |
| 2026-07-13 | UAG99W | - | Jul 13, 15:40 UTC | Jul 13, 17:15 UTC | 1h 35m |
| 2026-07-10 | UAG99W | NCE → BQH | Jul 10, 11:00 UTC | Jul 10, 12:55 UTC | 1h 55m |
| 2026-07-10 | UAG99W | - | Jul 10, 07:15 UTC | Jul 10, 08:55 UTC | 1h 40m |
| 2026-07-10 | UAG99W | VIE → EFL | Jul 10, 04:15 UTC | Jul 10, 05:55 UTC | 1h 40m |
| 2026-07-04 | UAG99W | - | Jul 4, 16:35 UTC | Jul 4, 17:50 UTC | 1h 15m |
| 2026-07-04 | UAG99W | - | Jul 4, 13:45 UTC | Jul 4, 15:05 UTC | 1h 20m |
| 2026-07-04 | UAG99W | - | Jul 4, 11:55 UTC | Jul 4, 12:30 UTC | 35m |
| 2026-07-02 | UAG99W | - | Jul 2, 19:20 UTC | Jul 2, 19:45 UTC | 25m |
| 2026-07-02 | UAG99W | VIE → NCE | Jul 2, 17:20 UTC | Jul 2, 18:50 UTC | 1h 30m |
| 2026-06-30 | UAG99W | - | Jun 30, 21:05 UTC | Jun 30, 21:30 UTC | 25m |
| 2026-06-30 | UAG99W | - | Jun 30, 15:35 UTC | Jun 30, 17:25 UTC | 1h 50m |
| 2026-06-26 | UAG99W | VIE → NCE | Jun 26, 12:55 UTC | Jun 26, 14:19 UTC | 1h 25m |
| 2026-06-25 | UAG99W | - | Jun 25, 07:49 UTC | Jun 25, 09:05 UTC | 1h 15m |
| 2026-06-25 | UAG99W | - | Jun 25, 05:39 UTC | Jun 25, 06:50 UTC | 1h 10m |
| 2026-06-24 | UAG99W | - | Jun 24, 07:30 UTC | Jun 24, 08:39 UTC | 1h 10m |
| 2026-06-24 | UAG99W | - | Jun 24, 05:20 UTC | Jun 24, 05:44 UTC | 25m |
| 2026-06-22 | UAG99W | - | Jun 22, 15:05 UTC | Jun 22, 15:29 UTC | 25m |
| 2026-06-22 | UAG99W | - | Jun 22, 13:10 UTC | Jun 22, 14:24 UTC | 1h 15m |
| 2026-06-22 | UAG99W | NCE → ANR | Jun 22, 06:54 UTC | Jun 22, 08:15 UTC | 1h 20m |
| 2026-06-22 | UAG99W | - | Jun 22, 04:34 UTC | Jun 22, 04:59 UTC | 25m |
| 2026-06-21 | UAG99W | NCE → GOA | Jun 21, 10:44 UTC | Jun 21, 11:05 UTC | 20m |
| 2026-06-20 | UAG99W | JMK → NCE | Jun 20, 11:54 UTC | Jun 20, 14:09 UTC | 2h 15m |
| 2026-06-20 | UAG99W | - | Jun 20, 09:14 UTC | Jun 20, 11:05 UTC | 1h 50m |
| 2026-06-10 | UAG99W | - | Jun 10, 18:35 UTC | Jun 10, 20:20 UTC | 1h 45m |
| 2026-06-10 | UAG99W | NCE → ATH | Jun 10, 14:55 UTC | Jun 10, 17:25 UTC | 2h 30m |
| 2026-06-09 | UAG99W | VIE → NCE | Jun 9, 13:30 UTC | Jun 9, 14:55 UTC | 1h 25m |
| 2026-06-08 | UAG99W | - | Jun 8, 16:50 UTC | Jun 8, 17:25 UTC | 35m |
| 2026-06-08 | UAG99W | - | Jun 8, 11:50 UTC | Jun 8, 12:30 UTC | 40m |
| 2026-06-07 | UAG99W | - | Jun 7, 19:15 UTC | Jun 7, 20:40 UTC | 1h 25m |
| 2026-06-05 | UAG99W | VIE → LBG | Jun 5, 10:05 UTC | Jun 5, 11:35 UTC | 1h 30m |
| 2026-06-05 | UAG99W | - | Jun 5, 03:00 UTC | Jun 5, 05:50 UTC | 2h 50m |
| 2026-06-02 | UAG99W | VIE → LCA | Jun 2, 16:25 UTC | Jun 2, 18:50 UTC | 2h 25m |
| 2026-05-30 | UAG99W | - | May 30, 13:50 UTC | May 30, 14:15 UTC | 25m |
| 2026-05-30 | UAG99W | - | May 30, 12:25 UTC | May 30, 12:55 UTC | 30m |
| 2026-05-30 | UAG99W | NCE → VIE | May 30, 10:30 UTC | May 30, 11:45 UTC | 1h 15m |
| 2026-05-20 | UAG99W | - | May 20, 14:20 UTC | May 20, 14:55 UTC | 35m |
| 2026-05-20 | UAG99W | - | May 20, 13:35 UTC | May 20, 14:15 UTC | 40m |
| 2026-05-15 | UAG99W | - | May 15, 11:40 UTC | May 15, 12:25 UTC | 45m |
| 2026-05-10 | UAG99W | VIE → MUC | May 10, 14:49 UTC | May 10, 15:35 UTC | 45m |
| 2026-05-02 | UAG99W | - | May 2, 22:30 UTC | May 3, 07:35 UTC | 9h 4m |
| 2026-04-27 | UAG99W | - | Apr 27, 14:45 UTC | Apr 27, 14:55 UTC | 10m |
| 2026-04-23 | UAG99W | - | Apr 23, 20:40 UTC | Apr 23, 20:50 UTC | 10m |
| 2026-04-23 | UAG99W | - | Apr 23, 13:45 UTC | Apr 23, 16:15 UTC | 2h 30m |
| 2026-04-12 | UAG99W | - | Apr 12, 17:25 UTC | Apr 12, 20:00 UTC | 2h 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-ELF page for operator, model, and routing details .