sensors Mode-S transponder
507C4C
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-78701 · BOEING 787-8 Dreamliner
- Hex
- 507C4C
- Octal
- 24076114
- Decimal
- 5,274,700
- Country
- UZ
- Tail
- UK-78701
- Type
- B788
- Flights observed
- 76
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 21h ago
Last known position
Country allocation
The ICAO 24-bit address 507C4C 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 |
|---|---|---|---|
| UZB255 | Uzbekistan Airways | 8 | 2026-05-27 |
| UZB527 | Uzbekistan Airways | 7 | 2026-05-28 |
| UZB528 | Uzbekistan Airways | 6 | 2026-05-29 |
| UZB514 | - | 5 | 2026-05-23 |
| UZB256 | Uzbekistan Airways | 5 | 2026-05-27 |
| UZB553 | Uzbekistan Airways | 4 | 2026-05-07 |
| UZB513 | - | 4 | 2026-05-22 |
| UZB273 | Uzbekistan Airways | 4 | 2026-05-16 |
| UZB231 | Uzbekistan Airways | 4 | 2026-04-30 |
| UZB202 | Uzbekistan Airways | 4 | 2026-05-19 |
| UZB511 | - | 3 | 2026-05-26 |
| UZB232 | Uzbekistan Airways | 3 | 2026-04-30 |
| UZB554 | Uzbekistan Airways | 2 | 2026-04-23 |
| UZB281 | Uzbekistan Airways | 2 | 2026-05-18 |
| UZB274 | Uzbekistan Airways | 2 | 2026-05-16 |
| UZB272 | Uzbekistan Airways | 2 | 2026-05-20 |
| UZB201 | Uzbekistan Airways | 2 | 2026-05-04 |
| UZB612 | - | 1 | 2026-04-16 |
| UZB611 | Uzbekistan Airways | 1 | 2026-04-16 |
| UZB515 | - | 1 | 2026-05-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UZB528 | NRT → TAS | May 29, 04:50 UTC | May 29, 08:20 UTC | 3h 30m |
| 2026-05-28 | UZB527 | TAS → NRT | May 28, 23:20 UTC | May 29, 02:10 UTC | 2h 50m |
| 2026-05-27 | UZB256 | MXP → TAS | May 27, 19:20 UTC | May 27, 23:00 UTC | 3h 40m |
| 2026-05-27 | UZB255 | TAS → MXP | May 27, 01:39 UTC | May 27, 17:15 UTC | 15h 36m |
| 2026-05-26 | UZB511 | - | May 26, 22:39 UTC | May 26, 22:59 UTC | 20m |
| 2026-05-26 | UZB528 | NRT → TAS | May 26, 02:29 UTC | May 26, 21:59 UTC | 19h 30m |
| 2026-05-25 | UZB527 | TAS → NRT | May 25, 12:05 UTC | May 26, 00:49 UTC | 12h 45m |
| 2026-05-24 | UZB258 | FCO → TAS | May 24, 19:05 UTC | May 25, 09:45 UTC | 14h 40m |
| 2026-05-23 | UZB257 | TAS → FCO | May 23, 23:40 UTC | May 24, 16:30 UTC | 16h 50m |
| 2026-05-23 | UZB515 | - | May 23, 21:10 UTC | May 23, 21:30 UTC | 20m |
| 2026-05-23 | UZB514 | - | May 23, 01:40 UTC | May 23, 02:05 UTC | 25m |
| 2026-05-22 | UZB513 | - | May 22, 22:55 UTC | May 22, 23:15 UTC | 20m |
| 2026-05-21 | UZB514 | - | May 21, 01:50 UTC | May 21, 17:45 UTC | 15h 55m |
| 2026-05-20 | UZB513 | - | May 20, 23:00 UTC | May 20, 23:20 UTC | 20m |
| 2026-05-20 | UZB272 | IST → TAS | May 20, 10:35 UTC | May 20, 22:15 UTC | 11h 40m |
| 2026-05-20 | UZB271 | TAS → IST | May 20, 07:15 UTC | May 20, 07:30 UTC | 15m |
| 2026-05-19 | UZB202 | LHR → TAS | May 19, 15:50 UTC | May 20, 06:30 UTC | 14h 41m |
| 2026-05-18 | UZB256 | MXP → TAS | May 18, 19:20 UTC | May 19, 13:35 UTC | 18h 15m |
| 2026-05-18 | UZB255 | TAS → MXP | May 18, 03:20 UTC | May 18, 17:40 UTC | 14h 20m |
| 2026-05-18 | UZB281 | TAS → IST | May 18, 01:00 UTC | May 18, 01:10 UTC | 10m |
| 2026-05-17 | UZB281 | TAS → IST | May 17, 05:40 UTC | May 18, 00:20 UTC | 18h 40m |
| 2026-05-16 | UZB274 | IST → TAS | May 16, 20:35 UTC | May 17, 06:00 UTC | 9h 25m |
| 2026-05-16 | UZB273 | TAS → IST | May 16, 01:55 UTC | May 16, 17:35 UTC | 15h 41m |
| 2026-05-15 | UZB513 | - | May 15, 23:55 UTC | May 16, 00:15 UTC | 20m |
| 2026-05-15 | UZB528 | NRT → TAS | May 15, 03:00 UTC | May 15, 04:40 UTC | 1h 40m |
| 2026-05-14 | UZB527 | TAS → NRT | May 14, 22:35 UTC | May 15, 01:00 UTC | 2h 25m |
| 2026-05-14 | UZB514 | - | May 14, 04:45 UTC | May 14, 04:55 UTC | 10m |
| 2026-05-14 | UZB514 | - | May 14, 02:35 UTC | May 14, 03:15 UTC | 40m |
| 2026-05-14 | UZB514 | - | May 14, 01:35 UTC | May 14, 01:50 UTC | 15m |
| 2026-05-13 | UZB513 | - | May 13, 23:15 UTC | May 13, 23:35 UTC | 20m |
| 2026-05-08 | UZB528 | NRT → TAS | May 8, 02:35 UTC | May 8, 05:59 UTC | 3h 25m |
| 2026-05-07 | UZB527 | TAS → NRT | May 7, 06:45 UTC | May 8, 00:09 UTC | 17h 25m |
| 2026-05-07 | UZB553 | TAS → KUL | May 7, 00:55 UTC | May 7, 01:10 UTC | 15m |
| 2026-05-06 | UZB553 | TAS → KUL | May 6, 11:00 UTC | May 6, 22:25 UTC | 11h 24m |
| 2026-05-05 | UZB202 | LHR → TAS | May 5, 15:55 UTC | May 6, 11:00 UTC | 19h 5m |
| 2026-05-04 | UZB201 | TAS → LHR | May 4, 19:35 UTC | May 5, 13:45 UTC | 18h 10m |
| 2026-05-03 | UZB255 | TAS → MXP | May 3, 23:15 UTC | May 4, 17:45 UTC | 18h 30m |
| 2026-05-03 | UZB255 | TAS → MXP | May 3, 17:05 UTC | May 4, 17:00 UTC | 23h 55m |
| 2026-05-02 | UZB101 | TAS → JFK | May 2, 19:15 UTC | May 3, 14:20 UTC | 19h 4m |
| 2026-05-01 | UZB273 | TAS → IST | May 1, 21:05 UTC | May 2, 16:00 UTC | 18h 56m |
| 2026-05-01 | UZB256 | MXP → TAS | May 1, 19:05 UTC | May 2, 16:00 UTC | 20h 55m |
| 2026-05-01 | UZB255 | TAS → MXP | May 1, 01:55 UTC | May 1, 16:55 UTC | 15h 0m |
| 2026-04-30 | UZB505 | - | Apr 30, 23:00 UTC | Apr 30, 23:15 UTC | 15m |
| 2026-04-30 | UZB232 | FRA → TAS | Apr 30, 10:30 UTC | Apr 30, 14:00 UTC | 3h 30m |
| 2026-04-30 | UZB231 | TAS → FRA | Apr 30, 06:00 UTC | Apr 30, 08:05 UTC | 2h 5m |
| 2026-04-29 | UZB231 | TAS → FRA | Apr 29, 09:50 UTC | Apr 30, 08:05 UTC | 22h 14m |
| 2026-04-28 | UZB202 | LHR → TAS | Apr 28, 15:50 UTC | Apr 29, 09:55 UTC | 18h 6m |
| 2026-04-27 | UZB256 | MXP → TAS | Apr 27, 19:25 UTC | Apr 28, 13:35 UTC | 18h 10m |
| 2026-04-27 | UZB255 | TAS → MXP | Apr 27, 01:25 UTC | Apr 27, 17:10 UTC | 15h 45m |
| 2026-04-24 | UZB256 | MXP → TAS | Apr 24, 19:40 UTC | Apr 24, 23:25 UTC | 3h 45m |
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-78701 page for operator, model, and routing details .