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