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
- 194
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 5h 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 | - | 60 | 2026-07-16 |
| UZB102 | - | 46 | 2026-07-16 |
| UZB201 | - | 19 | 2026-07-09 |
| UZB202 | - | 9 | 2026-06-26 |
| UZB273 | Uzbekistan Airways | 6 | 2026-07-17 |
| UZB203 | Uzbekistan Airways | 4 | 2026-05-30 |
| UZB613 | Uzbekistan Airways | 3 | 2026-07-13 |
| UZB562 | Uzbekistan Airways | 3 | 2026-05-10 |
| UZB554 | Uzbekistan Airways | 3 | 2026-05-11 |
| UZB3224 | Uzbekistan Airways | 3 | 2026-06-22 |
| UZB3223 | - | 3 | 2026-06-29 |
| UZB272 | - | 3 | 2026-07-07 |
| UZB271 | - | 3 | 2026-07-07 |
| UZB251 | Uzbekistan Airways | 3 | 2026-04-24 |
| UZB614 | - | 2 | 2026-04-15 |
| UZB561 | Uzbekistan Airways | 2 | 2026-05-09 |
| UZB513 | - | 2 | 2026-06-03 |
| UZB424 | - | 2 | 2026-07-08 |
| UZB423 | - | 2 | 2026-07-13 |
| UZB257 | Uzbekistan Airways | 2 | 2026-05-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | UZB274 | - | Jul 17, 20:04 UTC | Jul 17, 21:44 UTC | 1h 40m |
| 2026-07-17 | UZB273 | TAS → IST | Jul 17, 01:25 UTC | Jul 17, 17:20 UTC | 15h 55m |
| 2026-07-16 | UZB273 | TAS → IST | Jul 16, 18:19 UTC | Jul 17, 17:20 UTC | 23h 0m |
| 2026-07-16 | UZB102 | - | Jul 16, 17:35 UTC | Jul 17, 01:55 UTC | 8h 20m |
| 2026-07-16 | UZB101 | - | Jul 16, 05:05 UTC | Jul 16, 14:29 UTC | 9h 25m |
| 2026-07-15 | UZB101 | - | Jul 15, 14:25 UTC | Jul 16, 14:15 UTC | 23h 50m |
| 2026-07-14 | UZB102 | JFK → AYT | Jul 14, 17:25 UTC | Jul 15, 11:40 UTC | 18h 14m |
| 2026-07-14 | UZB101 | - | Jul 14, 05:10 UTC | Jul 14, 14:45 UTC | 9h 35m |
| 2026-07-13 | UZB101 | - | Jul 13, 16:20 UTC | Jul 14, 14:45 UTC | 22h 25m |
| 2026-07-13 | UZB101 | - | Jul 13, 15:40 UTC | Jul 14, 14:15 UTC | 22h 35m |
| 2026-07-13 | UZB613 | TAS → VKO | Jul 13, 08:35 UTC | Jul 14, 05:50 UTC | 21h 15m |
| 2026-07-13 | UZB423 | - | Jul 13, 05:25 UTC | Jul 13, 06:10 UTC | 45m |
| 2026-07-11 | UZB102 | - | Jul 11, 17:30 UTC | Jul 12, 01:30 UTC | 8h 0m |
| 2026-07-11 | UZB101 | - | Jul 11, 07:35 UTC | Jul 11, 15:00 UTC | 7h 25m |
| 2026-07-10 | UZB101 | - | Jul 10, 18:20 UTC | Jul 11, 15:00 UTC | 20h 41m |
| 2026-07-10 | UZB101 | LHR → JFK | Jul 10, 16:40 UTC | Jul 11, 15:00 UTC | 22h 20m |
| 2026-07-09 | UZB201 | - | Jul 9, 18:20 UTC | Jul 10, 14:00 UTC | 19h 40m |
| 2026-07-09 | UZB201 | JFK → LHR | Jul 9, 17:05 UTC | Jul 10, 14:00 UTC | 20h 55m |
| 2026-07-08 | UZB101 | - | Jul 8, 19:55 UTC | Jul 9, 14:15 UTC | 18h 20m |
| 2026-07-08 | UZB101 | - | Jul 8, 15:30 UTC | Jul 9, 14:15 UTC | 22h 45m |
| 2026-07-08 | UZB424 | - | Jul 8, 08:45 UTC | Jul 9, 05:30 UTC | 20h 45m |
| 2026-07-08 | UZB423 | - | Jul 8, 05:25 UTC | Jul 8, 06:45 UTC | 1h 20m |
| 2026-07-07 | UZB272 | - | Jul 7, 10:20 UTC | Jul 8, 06:45 UTC | 20h 25m |
| 2026-07-07 | UZB272 | - | Jul 7, 10:00 UTC | Jul 8, 06:45 UTC | 20h 45m |
| 2026-07-07 | UZB271 | - | Jul 7, 07:25 UTC | Jul 7, 07:35 UTC | 10m |
| 2026-07-07 | UZB271 | - | Jul 7, 05:05 UTC | Jul 7, 06:30 UTC | 1h 25m |
| 2026-07-04 | UZB102 | - | Jul 4, 17:40 UTC | Jul 5, 02:00 UTC | 8h 20m |
| 2026-07-03 | UZB101 | - | Jul 3, 18:20 UTC | Jul 4, 13:55 UTC | 19h 35m |
| 2026-07-03 | UZB101 | - | Jul 3, 16:25 UTC | Jul 4, 13:55 UTC | 21h 30m |
| 2026-07-02 | UZB201 | - | Jul 2, 23:15 UTC | Jul 3, 14:25 UTC | 15h 10m |
| 2026-07-02 | UZB201 | - | Jul 2, 18:20 UTC | Jul 3, 14:25 UTC | 20h 5m |
| 2026-07-02 | UZB102 | - | Jul 2, 17:15 UTC | Jul 3, 14:25 UTC | 21h 10m |
| 2026-07-01 | UZB101 | - | Jul 1, 19:20 UTC | Jul 2, 13:50 UTC | 18h 30m |
| 2026-07-01 | UZB273 | TAS → IST | Jul 1, 01:10 UTC | Jul 1, 16:50 UTC | 15h 40m |
| 2026-06-30 | UZB273 | TAS → IST | Jun 30, 18:25 UTC | Jul 1, 16:50 UTC | 22h 25m |
| 2026-06-30 | UZB101 | - | Jun 30, 05:05 UTC | Jun 30, 13:35 UTC | 8h 30m |
| 2026-06-29 | UZB101 | - | Jun 29, 12:20 UTC | Jun 30, 12:15 UTC | 23h 56m |
| 2026-06-29 | UZB101 | - | Jun 29, 12:05 UTC | Jun 30, 06:40 UTC | 18h 36m |
| 2026-06-29 | UZB3223 | - | Jun 29, 07:44 UTC | Jun 29, 10:10 UTC | 2h 25m |
| 2026-06-27 | UZB102 | - | Jun 27, 17:09 UTC | Jun 28, 00:55 UTC | 7h 45m |
| 2026-06-26 | UZB101 | - | Jun 26, 18:20 UTC | Jun 27, 13:55 UTC | 19h 35m |
| 2026-06-26 | UZB202 | LHR → JFK | Jun 26, 16:54 UTC | Jun 27, 13:55 UTC | 21h 0m |
| 2026-06-25 | UZB201 | - | Jun 25, 22:59 UTC | Jun 26, 14:44 UTC | 15h 45m |
| 2026-06-25 | UZB201 | - | Jun 25, 18:19 UTC | Jun 26, 14:44 UTC | 20h 25m |
| 2026-06-25 | UZB201 | - | Jun 25, 17:05 UTC | Jun 26, 14:44 UTC | 21h 40m |
| 2026-06-24 | UZB101 | - | Jun 24, 19:34 UTC | Jun 25, 14:04 UTC | 18h 30m |
| 2026-06-23 | UZB102 | - | Jun 23, 23:14 UTC | Jun 24, 16:50 UTC | 17h 35m |
| 2026-06-23 | UZB102 | - | Jun 23, 18:25 UTC | Jun 24, 16:50 UTC | 22h 25m |
| 2026-06-23 | UZB102 | - | Jun 23, 17:15 UTC | Jun 24, 01:24 UTC | 8h 10m |
| 2026-06-23 | UZB101 | - | Jun 23, 05:04 UTC | Jun 23, 14:15 UTC | 9h 10m |
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 .