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
- 97
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 2h ago
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 | 8 | 2026-05-24 |
| UZB255 | Uzbekistan Airways | 8 | 2026-05-29 |
| UZB274 | Uzbekistan Airways | 6 | 2026-05-08 |
| UZB256 | Uzbekistan Airways | 6 | 2026-05-29 |
| UZB515 | - | 5 | 2026-05-09 |
| UZB553 | Uzbekistan Airways | 4 | 2026-05-04 |
| UZB514 | - | 4 | 2026-05-28 |
| UZB334 | Uzbekistan Airways | 4 | 2026-05-15 |
| UZB3212 | - | 4 | 2026-05-03 |
| UZB202 | Uzbekistan Airways | 4 | 2026-05-22 |
| UZB201 | Uzbekistan Airways | 4 | 2026-05-22 |
| UZB554 | Uzbekistan Airways | 3 | 2026-05-04 |
| UZB528 | Uzbekistan Airways | 3 | 2026-05-19 |
| UZB527 | Uzbekistan Airways | 3 | 2026-05-18 |
| UZB516 | - | 3 | 2026-05-10 |
| UZB511 | - | 3 | 2026-05-28 |
| UZB510 | - | 3 | 2026-04-21 |
| UZB251 | - | 3 | 2026-04-17 |
| UZB633 | Uzbekistan Airways | 2 | 2026-05-27 |
| UZB512 | - | 2 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UZB256 | MXP → TAS | May 29, 20:50 UTC | May 29, 23:00 UTC | 2h 10m |
| 2026-05-29 | UZB255 | TAS → MXP | May 29, 03:10 UTC | May 29, 18:40 UTC | 15h 30m |
| 2026-05-29 | UZB512 | - | May 29, 01:50 UTC | May 29, 02:05 UTC | 15m |
| 2026-05-28 | UZB511 | - | May 28, 22:40 UTC | May 28, 23:05 UTC | 25m |
| 2026-05-28 | UZB514 | - | May 28, 03:10 UTC | May 28, 22:00 UTC | 18h 50m |
| 2026-05-28 | UZB514 | - | May 28, 01:55 UTC | May 28, 22:00 UTC | 20h 5m |
| 2026-05-27 | UZB513 | - | May 27, 23:10 UTC | May 27, 23:30 UTC | 20m |
| 2026-05-27 | UZB633 | TAS → LED | May 27, 05:59 UTC | May 27, 22:25 UTC | 16h 25m |
| 2026-05-26 | UZB633 | TAS → LED | May 26, 11:05 UTC | May 27, 07:50 UTC | 20h 46m |
| 2026-05-26 | UZB272 | IST → TAS | May 26, 09:59 UTC | May 27, 07:50 UTC | 21h 51m |
| 2026-05-25 | UZB232 | FRA → TAS | May 25, 11:05 UTC | May 26, 06:39 UTC | 19h 35m |
| 2026-05-25 | UZB232 | FRA → TAS | May 25, 09:55 UTC | May 26, 06:39 UTC | 20h 44m |
| 2026-05-24 | UZB231 | TAS → FRA | May 24, 19:15 UTC | May 25, 07:20 UTC | 12h 5m |
| 2026-05-24 | UZB273 | TAS → IST | May 24, 16:55 UTC | May 24, 17:05 UTC | 10m |
| 2026-05-24 | UZB273 | TAS → IST | May 24, 14:55 UTC | May 24, 16:10 UTC | 1h 15m |
| 2026-05-22 | UZB202 | LHR → TAS | May 22, 16:10 UTC | May 22, 20:10 UTC | 4h 0m |
| 2026-05-22 | UZB201 | TAS → LHR | May 22, 09:20 UTC | May 22, 13:30 UTC | 4h 10m |
| 2026-05-20 | UZB256 | MXP → TAS | May 20, 19:15 UTC | May 20, 23:00 UTC | 3h 45m |
| 2026-05-20 | UZB255 | TAS → MXP | May 20, 12:55 UTC | May 20, 17:00 UTC | 4h 5m |
| 2026-05-19 | UZB528 | NRT → TAS | May 19, 02:30 UTC | May 19, 05:35 UTC | 3h 5m |
| 2026-05-18 | UZB527 | TAS → NRT | May 18, 21:25 UTC | May 19, 00:30 UTC | 3h 5m |
| 2026-05-18 | UZB527 | TAS → NRT | May 18, 01:30 UTC | May 19, 00:30 UTC | 22h 59m |
| 2026-05-17 | UZB511 | - | May 17, 22:50 UTC | May 17, 23:10 UTC | 20m |
| 2026-05-17 | UZB236 | MUC → TAS | May 17, 09:30 UTC | May 17, 22:10 UTC | 12h 40m |
| 2026-05-17 | UZB235 | TAS → MUC | May 17, 03:40 UTC | May 17, 07:20 UTC | 3h 40m |
| 2026-05-15 | UZB334 | DXB → TAS | May 15, 09:30 UTC | May 16, 04:05 UTC | 18h 34m |
| 2026-05-13 | UZB256 | MXP → TAS | May 13, 19:50 UTC | May 13, 23:20 UTC | 3h 30m |
| 2026-05-13 | UZB255 | TAS → MXP | May 13, 12:30 UTC | May 13, 16:40 UTC | 4h 10m |
| 2026-05-11 | UZB528 | NRT → TAS | May 11, 10:35 UTC | May 12, 04:25 UTC | 17h 50m |
| 2026-05-10 | UZB516 | - | May 10, 01:04 UTC | May 10, 01:14 UTC | 10m |
| 2026-05-09 | UZB516 | - | May 9, 23:50 UTC | May 10, 00:05 UTC | 15m |
| 2026-05-09 | UZB515 | - | May 9, 21:34 UTC | May 9, 21:50 UTC | 15m |
| 2026-05-09 | UZB515 | - | May 9, 11:05 UTC | May 9, 20:49 UTC | 9h 45m |
| 2026-05-08 | UZB515 | - | May 8, 21:05 UTC | May 9, 20:49 UTC | 23h 45m |
| 2026-05-08 | UZB274 | IST → TAS | May 8, 19:55 UTC | May 9, 11:05 UTC | 15h 10m |
| 2026-05-08 | UZB274 | IST → TAS | May 8, 15:05 UTC | May 9, 11:05 UTC | 20h 0m |
| 2026-05-08 | UZB273 | TAS → IST | May 8, 14:45 UTC | May 9, 11:05 UTC | 20h 20m |
| 2026-05-08 | UZB273 | TAS → IST | May 8, 03:04 UTC | May 8, 21:10 UTC | 18h 5m |
| 2026-05-07 | UZB511 | - | May 7, 03:05 UTC | May 7, 22:35 UTC | 19h 30m |
| 2026-05-07 | UZB514 | - | May 7, 01:45 UTC | May 7, 01:55 UTC | 10m |
| 2026-05-06 | UZB272 | IST → TAS | May 6, 05:25 UTC | May 6, 22:30 UTC | 17h 4m |
| 2026-05-05 | UZB274 | IST → TAS | May 5, 19:05 UTC | May 6, 11:55 UTC | 16h 49m |
| 2026-05-05 | UZB273 | TAS → IST | May 5, 01:30 UTC | May 5, 16:15 UTC | 14h 45m |
| 2026-05-04 | UZB554 | KUL → TAS | May 4, 07:05 UTC | May 4, 22:05 UTC | 15h 1m |
| 2026-05-04 | UZB554 | KUL → TAS | May 4, 04:20 UTC | May 4, 04:34 UTC | 15m |
| 2026-05-04 | UZB553 | TAS → KUL | May 4, 01:35 UTC | May 4, 01:55 UTC | 20m |
| 2026-05-03 | UZB553 | TAS → KUL | May 3, 22:25 UTC | May 3, 23:10 UTC | 45m |
| 2026-05-03 | UZB3212 | - | May 3, 07:05 UTC | May 3, 22:15 UTC | 15h 10m |
| 2026-05-02 | UZB3212 | - | May 2, 23:05 UTC | May 3, 22:15 UTC | 23h 9m |
| 2026-05-02 | UZB3212 | - | May 2, 21:05 UTC | May 3, 21:00 UTC | 23h 54m |
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 .