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
- 170
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 4h 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 |
|---|---|---|---|
| UZB511 | - | 14 | 2026-07-13 |
| UZB273 | Uzbekistan Airways | 13 | 2026-07-12 |
| UZB527 | - | 10 | 2026-06-25 |
| UZB255 | Uzbekistan Airways | 10 | 2026-06-05 |
| UZB528 | - | 9 | 2026-06-26 |
| UZB513 | - | 8 | 2026-07-09 |
| UZB271 | - | 8 | 2026-07-02 |
| UZB202 | Uzbekistan Airways | 8 | 2026-06-23 |
| UZB515 | - | 7 | 2026-07-11 |
| UZB274 | - | 7 | 2026-07-12 |
| UZB256 | Uzbekistan Airways | 7 | 2026-06-05 |
| UZB231 | Uzbekistan Airways | 7 | 2026-06-11 |
| UZB514 | - | 6 | 2026-06-20 |
| UZB512 | - | 6 | 2026-07-14 |
| UZB272 | - | 6 | 2026-07-02 |
| UZB201 | - | 5 | 2026-06-22 |
| UZB553 | Uzbekistan Airways | 4 | 2026-05-07 |
| UZB334 | - | 4 | 2026-07-13 |
| UZB613 | Uzbekistan Airways | 3 | 2026-07-03 |
| UZB232 | Uzbekistan Airways | 3 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UZB512 | - | Jul 14, 01:55 UTC | Jul 14, 03:20 UTC | 1h 25m |
| 2026-07-13 | UZB511 | - | Jul 13, 23:25 UTC | Jul 13, 23:50 UTC | 25m |
| 2026-07-13 | UZB334 | - | Jul 13, 08:45 UTC | Jul 13, 22:40 UTC | 13h 55m |
| 2026-07-12 | UZB274 | - | Jul 12, 19:01 UTC | Jul 13, 06:30 UTC | 11h 30m |
| 2026-07-12 | UZB273 | TAS → IST | Jul 12, 16:30 UTC | Jul 12, 16:50 UTC | 20m |
| 2026-07-11 | UZB273 | TAS → IST | Jul 11, 23:45 UTC | Jul 12, 15:15 UTC | 15h 30m |
| 2026-07-11 | UZB515 | - | Jul 11, 21:10 UTC | Jul 11, 21:25 UTC | 15m |
| 2026-07-11 | UZB515 | - | Jul 11, 19:50 UTC | Jul 11, 20:10 UTC | 20m |
| 2026-07-10 | UZB515 | - | Jul 10, 23:45 UTC | Jul 11, 20:10 UTC | 20h 25m |
| 2026-07-10 | UZB102 | - | Jul 10, 17:30 UTC | Jul 11, 00:00 UTC | 6h 30m |
| 2026-07-09 | UZB101 | - | Jul 9, 19:15 UTC | Jul 10, 14:25 UTC | 19h 10m |
| 2026-07-09 | UZB273 | TAS → IST | Jul 9, 16:40 UTC | Jul 9, 17:00 UTC | 20m |
| 2026-07-09 | UZB273 | TAS → IST | Jul 9, 03:00 UTC | Jul 9, 15:55 UTC | 12h 55m |
| 2026-07-09 | UZB513 | - | Jul 9, 00:05 UTC | Jul 9, 00:25 UTC | 20m |
| 2026-07-08 | UZB513 | - | Jul 8, 22:55 UTC | Jul 8, 23:15 UTC | 20m |
| 2026-07-07 | UZB506 | - | Jul 7, 02:00 UTC | Jul 7, 02:10 UTC | 10m |
| 2026-07-06 | UZB505 | - | Jul 6, 22:40 UTC | Jul 6, 22:55 UTC | 15m |
| 2026-07-06 | UZB334 | - | Jul 6, 08:50 UTC | Jul 6, 09:15 UTC | 25m |
| 2026-07-05 | UZB274 | - | Jul 5, 19:00 UTC | Jul 6, 06:30 UTC | 11h 30m |
| 2026-07-04 | UZB273 | TAS → IST | Jul 4, 23:40 UTC | Jul 5, 16:55 UTC | 17h 15m |
| 2026-07-04 | UZB515 | - | Jul 4, 21:15 UTC | Jul 4, 21:35 UTC | 20m |
| 2026-07-04 | UZB334 | - | Jul 4, 09:25 UTC | Jul 4, 09:55 UTC | 30m |
| 2026-07-03 | UZB613 | TAS → VKO | Jul 3, 15:25 UTC | Jul 4, 06:55 UTC | 15h 30m |
| 2026-07-03 | UZB613 | TAS → VKO | Jul 3, 02:50 UTC | Jul 3, 20:40 UTC | 17h 50m |
| 2026-07-03 | UZB512 | - | Jul 3, 01:35 UTC | Jul 3, 01:50 UTC | 15m |
| 2026-07-02 | UZB511 | - | Jul 2, 22:55 UTC | Jul 2, 23:15 UTC | 20m |
| 2026-07-02 | UZB272 | - | Jul 2, 09:50 UTC | Jul 2, 22:10 UTC | 12h 20m |
| 2026-07-02 | UZB271 | - | Jul 2, 07:25 UTC | Jul 2, 07:45 UTC | 20m |
| 2026-07-02 | UZB271 | - | Jul 2, 05:20 UTC | Jul 2, 06:45 UTC | 1h 25m |
| 2026-07-01 | UZB512 | - | Jul 1, 01:40 UTC | Jul 1, 03:10 UTC | 1h 30m |
| 2026-06-30 | UZB511 | - | Jun 30, 22:50 UTC | Jun 30, 23:10 UTC | 20m |
| 2026-06-30 | UZB511 | - | Jun 30, 03:05 UTC | Jun 30, 22:00 UTC | 18h 55m |
| 2026-06-30 | UZB511 | - | Jun 30, 02:50 UTC | Jun 30, 22:00 UTC | 19h 10m |
| 2026-06-30 | UZB512 | - | Jun 30, 01:40 UTC | Jun 30, 01:55 UTC | 15m |
| 2026-06-29 | UZB511 | - | Jun 29, 23:05 UTC | Jun 29, 23:25 UTC | 20m |
| 2026-06-29 | UZB334 | - | Jun 29, 09:00 UTC | Jun 29, 22:10 UTC | 13h 10m |
| 2026-06-28 | UZB274 | - | Jun 28, 19:40 UTC | Jun 29, 05:54 UTC | 10h 15m |
| 2026-06-27 | UZB273 | TAS → IST | Jun 27, 23:45 UTC | Jun 28, 17:04 UTC | 17h 20m |
| 2026-06-27 | UZB272 | - | Jun 27, 10:10 UTC | Jun 27, 21:44 UTC | 11h 35m |
| 2026-06-27 | UZB271 | - | Jun 27, 08:05 UTC | Jun 27, 08:29 UTC | 25m |
| 2026-06-26 | UZB274 | - | Jun 26, 21:55 UTC | Jun 27, 07:24 UTC | 9h 30m |
| 2026-06-26 | UZB528 | - | Jun 26, 03:39 UTC | Jun 26, 19:30 UTC | 15h 50m |
| 2026-06-25 | UZB527 | - | Jun 25, 10:25 UTC | Jun 25, 23:55 UTC | 13h 30m |
| 2026-06-25 | UZB271 | - | Jun 25, 05:50 UTC | Jun 25, 08:20 UTC | 2h 30m |
| 2026-06-24 | UZB271 | - | Jun 24, 09:05 UTC | Jun 25, 08:20 UTC | 23h 15m |
| 2026-06-24 | UZB333 | - | Jun 24, 05:54 UTC | Jun 24, 06:10 UTC | 15m |
| 2026-06-23 | UZB202 | LHR → TAS | Jun 23, 15:59 UTC | Jun 23, 19:39 UTC | 3h 40m |
| 2026-06-22 | UZB201 | - | Jun 22, 20:30 UTC | Jun 23, 13:59 UTC | 17h 30m |
| 2026-06-22 | UZB201 | - | Jun 22, 15:29 UTC | Jun 23, 13:59 UTC | 22h 30m |
| 2026-06-22 | UZB613 | TAS → VKO | Jun 22, 01:05 UTC | Jun 22, 20:34 UTC | 19h 30m |
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 .