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
- 207
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- Jul 26, 21:35 UTC
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 | 23 | 2026-07-24 |
| UZB511 | - | 10 | 2026-07-24 |
| UZB333 | - | 10 | 2026-07-12 |
| UZB274 | Uzbekistan Airways | 9 | 2026-07-24 |
| UZB553 | Uzbekistan Airways | 8 | 2026-07-26 |
| UZB513 | - | 7 | 2026-06-26 |
| UZB271 | Uzbekistan Airways | 7 | 2026-07-19 |
| UZB554 | Uzbekistan Airways | 6 | 2026-07-20 |
| UZB334 | - | 5 | 2026-06-28 |
| UZB202 | Uzbekistan Airways | 5 | 2026-07-17 |
| UZB201 | - | 5 | 2026-07-17 |
| UZB562 | Uzbekistan Airways | 4 | 2026-05-17 |
| UZB512 | - | 4 | 2026-07-24 |
| UZB505 | - | 4 | 2026-07-20 |
| UZB3223 | - | 4 | 2026-07-03 |
| 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-26 | UZB553 | TAS → KUL | Jul 26, 00:00 UTC | Jul 26, 21:35 UTC | 21h 36m |
| 2026-07-25 | UZB515 | - | Jul 25, 20:00 UTC | Jul 25, 21:40 UTC | 1h 40m |
| 2026-07-24 | UZB274 | IST → TAS | Jul 24, 20:10 UTC | Jul 25, 20:00 UTC | 23h 50m |
| 2026-07-24 | UZB274 | IST → TAS | Jul 24, 19:25 UTC | Jul 24, 21:15 UTC | 1h 50m |
| 2026-07-24 | UZB273 | TAS → IST | Jul 24, 04:30 UTC | Jul 24, 16:50 UTC | 12h 20m |
| 2026-07-24 | UZB512 | - | Jul 24, 03:20 UTC | Jul 24, 03:40 UTC | 20m |
| 2026-07-24 | UZB511 | - | Jul 24, 00:00 UTC | Jul 24, 00:20 UTC | 20m |
| 2026-07-23 | UZB232 | - | Jul 23, 11:15 UTC | Jul 23, 23:10 UTC | 11h 55m |
| 2026-07-22 | UZB231 | TAS → FRA | Jul 22, 19:50 UTC | Jul 23, 08:25 UTC | 12h 35m |
| 2026-07-22 | UZB273 | TAS → IST | Jul 22, 15:35 UTC | Jul 22, 18:00 UTC | 2h 25m |
| 2026-07-21 | UZB273 | TAS → IST | Jul 21, 20:05 UTC | Jul 22, 18:00 UTC | 21h 55m |
| 2026-07-21 | UZB273 | TAS → IST | Jul 21, 19:05 UTC | Jul 22, 18:00 UTC | 22h 55m |
| 2026-07-21 | UZB273 | TAS → IST | Jul 21, 02:35 UTC | Jul 21, 16:55 UTC | 14h 20m |
| 2026-07-20 | UZB505 | - | Jul 20, 22:55 UTC | Jul 20, 23:10 UTC | 15m |
| 2026-07-20 | UZB554 | KUL → TAS | Jul 20, 04:30 UTC | Jul 20, 09:20 UTC | 4h 50m |
| 2026-07-20 | UZB553 | TAS → KUL | Jul 20, 01:25 UTC | Jul 20, 01:45 UTC | 20m |
| 2026-07-19 | UZB553 | TAS → KUL | Jul 19, 10:00 UTC | Jul 19, 22:55 UTC | 12h 55m |
| 2026-07-19 | UZB271 | TAS → IST | Jul 19, 05:10 UTC | Jul 19, 07:40 UTC | 2h 30m |
| 2026-07-18 | UZB271 | TAS → IST | Jul 18, 08:05 UTC | Jul 19, 07:40 UTC | 23h 35m |
| 2026-07-17 | UZB202 | LHR → TAS | Jul 17, 22:25 UTC | Jul 18, 08:05 UTC | 9h 41m |
| 2026-07-17 | UZB201 | ICN → LHR | Jul 17, 01:49 UTC | Jul 17, 18:25 UTC | 16h 35m |
| 2026-07-16 | UZB554 | - | Jul 16, 04:20 UTC | Jul 16, 23:05 UTC | 18h 45m |
| 2026-07-15 | UZB553 | - | Jul 15, 10:05 UTC | Jul 16, 02:00 UTC | 15h 55m |
| 2026-07-14 | UZB3229 | - | Jul 14, 19:05 UTC | Jul 15, 07:15 UTC | 12h 9m |
| 2026-07-14 | UZB273 | TAS → IST | Jul 14, 16:20 UTC | Jul 14, 16:45 UTC | 25m |
| 2026-07-14 | UZB273 | TAS → IST | Jul 14, 02:00 UTC | Jul 14, 15:40 UTC | 13h 40m |
| 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 |
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 .