sensors Mode-S transponder
507C59
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-78706 · BOEING 787-8 Dreamliner
- Hex
- 507C59
- Octal
- 24076131
- Decimal
- 5,274,713
- Country
- UZ
- Tail
- UK-78706
- Type
- B788
- Flights observed
- 103
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 507C59 falls within the block assigned to Uzbekistan (UZ) by ICAO Annex 10, Volume III. Every aircraft registered in Uzbekistan 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UZB101 | Uzbekistan Airways | 27 | 2026-05-30 |
| UZB102 | Uzbekistan Airways | 25 | 2026-05-28 |
| UZB201 | Uzbekistan Airways | 8 | 2026-05-29 |
| UZB202 | Uzbekistan Airways | 5 | 2026-05-15 |
| UZB203 | Uzbekistan Airways | 4 | 2026-05-30 |
| UZB614 | Uzbekistan Airways | 3 | 2026-06-02 |
| UZB562 | Uzbekistan Airways | 3 | 2026-05-10 |
| UZB554 | Uzbekistan Airways | 3 | 2026-05-11 |
| UZB251 | Uzbekistan Airways | 3 | 2026-04-24 |
| UZB613 | Uzbekistan Airways | 2 | 2026-06-02 |
| UZB561 | Uzbekistan Airways | 2 | 2026-05-09 |
| UZB257 | Uzbekistan Airways | 2 | 2026-05-17 |
| UZB204 | Uzbekistan Airways | 2 | 2026-05-31 |
| UZB601 | - | 1 | 2026-04-14 |
| UZB553 | Uzbekistan Airways | 1 | 2026-05-11 |
| UZB514 | - | 1 | 2026-05-09 |
| UZB513 | - | 1 | 2026-05-08 |
| UZB512 | - | 1 | 2026-06-02 |
| UZB511 | - | 1 | 2026-06-01 |
| UZB510 | - | 1 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | UZB614 | DME → TAS | Jun 2, 20:05 UTC | Jun 2, 20:20 UTC | 15m |
| 2026-06-02 | UZB613 | TAS → VKO | Jun 2, 16:25 UTC | Jun 2, 16:50 UTC | 25m |
| 2026-06-02 | UZB613 | TAS → VKO | Jun 2, 15:30 UTC | Jun 2, 15:50 UTC | 20m |
| 2026-06-02 | UZB512 | - | Jun 2, 01:25 UTC | Jun 2, 01:40 UTC | 15m |
| 2026-06-01 | UZB511 | - | Jun 1, 22:35 UTC | Jun 1, 23:00 UTC | 25m |
| 2026-05-31 | UZB204 | LHR → TAS | May 31, 18:55 UTC | Jun 1, 10:55 UTC | 16h 0m |
| 2026-05-30 | UZB203 | TAS → LHR | May 30, 22:25 UTC | May 31, 17:00 UTC | 18h 35m |
| 2026-05-30 | UZB203 | TAS → LHR | May 30, 21:05 UTC | May 31, 17:00 UTC | 19h 55m |
| 2026-05-30 | UZB101 | TAS → JFK | May 30, 00:20 UTC | May 30, 18:25 UTC | 18h 5m |
| 2026-05-29 | UZB101 | TAS → JFK | May 29, 22:20 UTC | May 30, 18:25 UTC | 20h 5m |
| 2026-05-29 | UZB101 | TAS → JFK | May 29, 22:00 UTC | May 30, 18:25 UTC | 20h 25m |
| 2026-05-29 | UZB201 | TAS → LHR | May 29, 02:20 UTC | May 29, 20:20 UTC | 18h 0m |
| 2026-05-29 | UZB201 | TAS → LHR | May 29, 00:20 UTC | May 29, 20:20 UTC | 20h 0m |
| 2026-05-28 | UZB102 | JFK → RIX | May 28, 23:05 UTC | May 29, 20:20 UTC | 21h 15m |
| 2026-05-28 | UZB102 | JFK → RIX | May 28, 21:30 UTC | May 29, 20:15 UTC | 22h 45m |
| 2026-05-28 | UZB102 | JFK → RIX | May 28, 18:20 UTC | May 29, 16:50 UTC | 22h 30m |
| 2026-05-28 | UZB102 | JFK → RIX | May 28, 17:10 UTC | May 29, 16:15 UTC | 23h 5m |
| 2026-05-28 | UZB101 | TAS → JFK | May 28, 03:35 UTC | May 28, 13:50 UTC | 10h 15m |
| 2026-05-26 | UZB102 | JFK → RIX | May 26, 17:25 UTC | May 27, 02:39 UTC | 9h 15m |
| 2026-05-26 | UZB101 | TAS → JFK | May 26, 03:25 UTC | May 26, 13:45 UTC | 10h 20m |
| 2026-05-24 | UZB102 | JFK → RIX | May 24, 17:15 UTC | May 24, 23:46 UTC | 6h 31m |
| 2026-05-24 | UZB101 | TAS → JFK | May 24, 04:20 UTC | May 24, 14:05 UTC | 9h 45m |
| 2026-05-19 | UZB506 | - | May 19, 02:10 UTC | May 19, 02:25 UTC | 15m |
| 2026-05-18 | UZB505 | - | May 18, 23:05 UTC | May 18, 23:15 UTC | 10m |
| 2026-05-18 | UZB3224 | AYT → TAS | May 18, 12:05 UTC | May 18, 13:55 UTC | 1h 50m |
| 2026-05-17 | UZB258 | FCO → TAS | May 17, 18:50 UTC | May 18, 09:20 UTC | 14h 30m |
| 2026-05-17 | UZB257 | TAS → FCO | May 17, 01:35 UTC | May 17, 15:55 UTC | 14h 20m |
| 2026-05-16 | UZB257 | TAS → FCO | May 16, 18:20 UTC | May 17, 15:55 UTC | 21h 35m |
| 2026-05-16 | UZB102 | JFK → RIX | May 16, 17:25 UTC | May 17, 14:15 UTC | 20h 50m |
| 2026-05-16 | UZB101 | TAS → JFK | May 16, 12:35 UTC | May 16, 14:01 UTC | 1h 25m |
| 2026-05-15 | UZB202 | LHR → TAS | May 15, 18:20 UTC | May 16, 12:31 UTC | 18h 11m |
| 2026-05-15 | UZB202 | LHR → TAS | May 15, 16:45 UTC | May 16, 12:31 UTC | 19h 46m |
| 2026-05-14 | UZB201 | TAS → LHR | May 14, 23:35 UTC | May 15, 14:45 UTC | 15h 10m |
| 2026-05-14 | UZB201 | TAS → LHR | May 14, 18:20 UTC | May 15, 14:45 UTC | 20h 25m |
| 2026-05-14 | UZB201 | TAS → LHR | May 14, 17:45 UTC | May 15, 14:45 UTC | 21h 0m |
| 2026-05-13 | UZB101 | TAS → JFK | May 13, 20:20 UTC | May 14, 14:25 UTC | 18h 5m |
| 2026-05-13 | UZB101 | TAS → JFK | May 13, 19:30 UTC | May 14, 14:25 UTC | 18h 55m |
| 2026-05-12 | UZB102 | JFK → RIX | May 12, 21:25 UTC | May 13, 15:40 UTC | 18h 15m |
| 2026-05-12 | UZB102 | JFK → RIX | May 12, 18:20 UTC | May 13, 15:40 UTC | 21h 20m |
| 2026-05-12 | UZB102 | JFK → RIX | May 12, 17:20 UTC | May 13, 15:40 UTC | 22h 20m |
| 2026-05-12 | UZB101 | TAS → JFK | May 12, 04:40 UTC | May 12, 14:15 UTC | 9h 35m |
| 2026-05-11 | UZB554 | KUL → TAS | May 11, 08:20 UTC | May 12, 07:20 UTC | 23h 0m |
| 2026-05-11 | UZB554 | KUL → TAS | May 11, 06:50 UTC | May 12, 05:00 UTC | 22h 10m |
| 2026-05-11 | UZB554 | KUL → TAS | May 11, 04:15 UTC | May 11, 09:25 UTC | 5h 10m |
| 2026-05-11 | UZB553 | TAS → KUL | May 11, 01:45 UTC | May 11, 01:55 UTC | 10m |
| 2026-05-10 | UZB562 | CXR → TAS | May 10, 05:25 UTC | May 10, 23:15 UTC | 17h 50m |
| 2026-05-10 | UZB562 | CXR → TAS | May 10, 00:20 UTC | May 10, 23:15 UTC | 22h 55m |
| 2026-05-09 | UZB562 | CXR → TAS | May 9, 23:50 UTC | May 10, 21:49 UTC | 22h 0m |
| 2026-05-09 | UZB561 | TAS → CXR | May 9, 21:05 UTC | May 9, 23:35 UTC | 2h 30m |
| 2026-05-09 | UZB561 | TAS → CXR | May 9, 03:10 UTC | May 9, 23:35 UTC | 20h 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 UK-78706 page for operator, model, and routing details .