sensors Mode-S transponder
507C50
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-78703 · BOEING 787-8 Dreamliner
- Hex
- 507C50
- Octal
- 24076120
- Decimal
- 5,274,704
- Country
- UZ
- Tail
- UK-78703
- Type
- B788
- Flights observed
- 182
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 507C50 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 |
|---|---|---|---|
| UZB102 | Uzbekistan Airways | 33 | 2026-06-14 |
| UZB101 | Uzbekistan Airways | 28 | 2026-06-13 |
| UZB273 | Uzbekistan Airways | 16 | 2026-07-10 |
| UZB333 | - | 10 | 2026-07-12 |
| UZB511 | - | 9 | 2026-07-09 |
| UZB513 | - | 7 | 2026-06-26 |
| UZB274 | - | 7 | 2026-07-10 |
| UZB334 | - | 5 | 2026-06-28 |
| UZB271 | - | 5 | 2026-07-04 |
| UZB562 | Uzbekistan Airways | 4 | 2026-05-17 |
| UZB554 | - | 4 | 2026-07-13 |
| UZB553 | - | 4 | 2026-07-12 |
| UZB3223 | - | 4 | 2026-07-03 |
| UZB202 | - | 4 | 2026-07-07 |
| UZB201 | - | 4 | 2026-07-07 |
| UZB512 | - | 3 | 2026-06-29 |
| UZB505 | - | 3 | 2026-07-13 |
| UZB3224 | Uzbekistan Airways | 3 | 2026-06-08 |
| UZB282 | Uzbekistan Airways | 3 | 2026-05-16 |
| UZB272 | Uzbekistan Airways | 3 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UZB506 | - | Jul 14, 02:00 UTC | Jul 14, 02:15 UTC | 15m |
| 2026-07-13 | UZB505 | - | Jul 13, 22:45 UTC | Jul 13, 23:00 UTC | 15m |
| 2026-07-13 | UZB554 | - | Jul 13, 04:15 UTC | Jul 13, 09:15 UTC | 5h 0m |
| 2026-07-12 | UZB553 | - | Jul 12, 08:45 UTC | Jul 13, 01:30 UTC | 16h 45m |
| 2026-07-12 | UZB333 | - | Jul 12, 04:15 UTC | Jul 12, 06:25 UTC | 2h 10m |
| 2026-07-11 | UZB424 | - | Jul 11, 08:30 UTC | Jul 12, 06:25 UTC | 21h 55m |
| 2026-07-10 | UZB274 | - | Jul 10, 19:15 UTC | Jul 11, 06:10 UTC | 10h 56m |
| 2026-07-10 | UZB273 | TAS → IST | Jul 10, 01:40 UTC | Jul 10, 17:05 UTC | 15h 25m |
| 2026-07-09 | UZB511 | - | Jul 9, 22:45 UTC | Jul 9, 23:05 UTC | 20m |
| 2026-07-09 | UZB338 | - | Jul 9, 04:10 UTC | Jul 9, 22:00 UTC | 17h 50m |
| 2026-07-08 | UZB3230 | - | Jul 8, 10:05 UTC | Jul 9, 04:30 UTC | 18h 25m |
| 2026-07-08 | UZB3230 | - | Jul 8, 09:45 UTC | Jul 9, 04:30 UTC | 18h 45m |
| 2026-07-07 | UZB202 | - | Jul 7, 16:00 UTC | Jul 8, 07:35 UTC | 15h 35m |
| 2026-07-07 | UZB201 | DEL → LHR | Jul 7, 01:20 UTC | Jul 7, 14:05 UTC | 12h 45m |
| 2026-07-06 | UZB554 | - | Jul 6, 04:10 UTC | Jul 6, 23:10 UTC | 19h 0m |
| 2026-07-05 | UZB553 | - | Jul 5, 09:55 UTC | Jul 6, 02:00 UTC | 16h 5m |
| 2026-07-04 | UZB271 | - | Jul 4, 10:05 UTC | Jul 5, 07:55 UTC | 21h 50m |
| 2026-07-03 | UZB271 | - | Jul 3, 21:05 UTC | Jul 4, 07:40 UTC | 10h 35m |
| 2026-07-03 | UZB3223 | - | Jul 3, 08:40 UTC | Jul 3, 18:50 UTC | 10h 10m |
| 2026-07-03 | UZB333 | - | Jul 3, 04:25 UTC | Jul 3, 06:45 UTC | 2h 20m |
| 2026-07-01 | UZB424 | - | Jul 1, 08:40 UTC | Jul 1, 09:20 UTC | 40m |
| 2026-06-30 | UZB274 | - | Jun 30, 19:20 UTC | Jul 1, 06:10 UTC | 10h 50m |
| 2026-06-30 | UZB273 | TAS → IST | Jun 30, 02:05 UTC | Jun 30, 17:20 UTC | 15h 15m |
| 2026-06-29 | UZB505 | - | Jun 29, 22:59 UTC | Jun 29, 23:14 UTC | 15m |
| 2026-06-29 | UZB512 | - | Jun 29, 01:20 UTC | Jun 29, 02:59 UTC | 1h 40m |
| 2026-06-28 | UZB511 | - | Jun 28, 22:49 UTC | Jun 28, 23:14 UTC | 25m |
| 2026-06-28 | UZB334 | - | Jun 28, 09:05 UTC | Jun 28, 21:59 UTC | 12h 55m |
| 2026-06-28 | UZB333 | - | Jun 28, 05:34 UTC | Jun 28, 06:00 UTC | 25m |
| 2026-06-27 | UZB514 | - | Jun 27, 01:54 UTC | Jun 27, 03:20 UTC | 1h 25m |
| 2026-06-26 | UZB513 | - | Jun 26, 23:04 UTC | Jun 26, 23:34 UTC | 30m |
| 2026-06-26 | UZB513 | - | Jun 26, 08:50 UTC | Jun 26, 22:25 UTC | 13h 35m |
| 2026-06-26 | UZB333 | - | Jun 26, 05:44 UTC | Jun 26, 06:15 UTC | 30m |
| 2026-06-24 | UZB512 | - | Jun 24, 01:44 UTC | Jun 24, 03:19 UTC | 1h 35m |
| 2026-06-23 | UZB511 | - | Jun 23, 23:14 UTC | Jun 23, 23:39 UTC | 25m |
| 2026-06-23 | UZB334 | - | Jun 23, 08:59 UTC | Jun 23, 22:34 UTC | 13h 35m |
| 2026-06-23 | UZB333 | - | Jun 23, 05:59 UTC | Jun 23, 06:19 UTC | 20m |
| 2026-06-22 | UZB274 | - | Jun 22, 19:24 UTC | Jun 22, 21:19 UTC | 1h 55m |
| 2026-06-22 | UZB273 | TAS → IST | Jun 22, 01:29 UTC | Jun 22, 17:04 UTC | 15h 35m |
| 2026-06-21 | UZB511 | - | Jun 21, 23:05 UTC | Jun 21, 23:34 UTC | 30m |
| 2026-06-21 | UZB511 | - | Jun 21, 10:54 UTC | Jun 21, 22:29 UTC | 11h 35m |
| 2026-06-21 | UZB334 | - | Jun 21, 08:49 UTC | Jun 21, 09:15 UTC | 25m |
| 2026-06-21 | UZB333 | - | Jun 21, 06:10 UTC | Jun 21, 06:19 UTC | 10m |
| 2026-06-14 | UZB102 | JFK → RIX | Jun 14, 16:55 UTC | Jun 15, 01:25 UTC | 8h 29m |
| 2026-06-13 | UZB101 | TAS → JFK | Jun 13, 20:15 UTC | Jun 14, 13:55 UTC | 17h 40m |
| 2026-06-13 | UZB101 | TAS → JFK | Jun 13, 16:05 UTC | Jun 14, 13:55 UTC | 21h 50m |
| 2026-06-13 | UZB101 | TAS → JFK | Jun 13, 15:30 UTC | Jun 14, 13:55 UTC | 22h 25m |
| 2026-06-13 | UZB613 | TAS → VKO | Jun 13, 02:05 UTC | Jun 13, 20:25 UTC | 18h 19m |
| 2026-06-13 | UZB102 | JFK → RIX | Jun 13, 00:05 UTC | Jun 13, 20:25 UTC | 20h 19m |
| 2026-06-12 | UZB102 | JFK → RIX | Jun 12, 23:40 UTC | Jun 13, 20:25 UTC | 20h 44m |
| 2026-06-12 | UZB102 | JFK → RIX | Jun 12, 17:25 UTC | Jun 13, 16:00 UTC | 22h 34m |
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-78703 page for operator, model, and routing details .