sensors Mode-S transponder
507C55
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-78705 · BOEING 787-8 Dreamliner
- Hex
- 507C55
- Octal
- 24076125
- Decimal
- 5,274,709
- Country
- UZ
- Tail
- UK-78705
- Type
- B788
- Flights observed
- 101
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 507C55 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 |
|---|---|---|---|
| UZB231 | Uzbekistan Airways | 18 | 2026-05-21 |
| UZB232 | Uzbekistan Airways | 11 | 2026-05-14 |
| UZB273 | Uzbekistan Airways | 9 | 2026-05-22 |
| UZB274 | Uzbekistan Airways | 5 | 2026-05-22 |
| UZB252 | Uzbekistan Airways | 5 | 2026-04-21 |
| UZB566 | - | 4 | 2026-04-26 |
| UZB271 | Uzbekistan Airways | 4 | 2026-05-13 |
| UZB251 | Uzbekistan Airways | 4 | 2026-04-21 |
| UZB102 | Uzbekistan Airways | 4 | 2026-05-17 |
| UZB565 | - | 3 | 2026-04-25 |
| UZB553 | Uzbekistan Airways | 3 | 2026-04-30 |
| UZB528 | Uzbekistan Airways | 3 | 2026-05-22 |
| UZB255 | - | 3 | 2026-04-17 |
| UZB101 | Uzbekistan Airways | 3 | 2026-05-17 |
| UZB554 | Uzbekistan Airways | 2 | 2026-04-30 |
| UZB511 | - | 2 | 2026-04-30 |
| UZB506 | - | 2 | 2026-05-08 |
| UZB334 | Uzbekistan Airways | 2 | 2026-05-23 |
| UZB333 | Uzbekistan Airways | 2 | 2026-05-27 |
| UZB272 | Uzbekistan Airways | 2 | 2026-04-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-27 | UZB333 | TAS → DXB | May 27, 03:50 UTC | May 27, 10:55 UTC | 7h 5m |
| 2026-05-25 | UZB613 | TAS → VKO | May 25, 15:50 UTC | May 25, 20:19 UTC | 4h 30m |
| 2026-05-23 | UZB334 | DXB → TAS | May 23, 09:10 UTC | May 23, 09:20 UTC | 10m |
| 2026-05-23 | UZB333 | TAS → DXB | May 23, 06:15 UTC | May 23, 06:25 UTC | 10m |
| 2026-05-22 | UZB274 | IST → TAS | May 22, 20:00 UTC | May 23, 04:10 UTC | 8h 9m |
| 2026-05-22 | UZB273 | TAS → IST | May 22, 17:45 UTC | May 22, 17:55 UTC | 10m |
| 2026-05-22 | UZB528 | NRT → TAS | May 22, 02:45 UTC | May 22, 16:55 UTC | 14h 10m |
| 2026-05-21 | UZB527 | TAS → NRT | May 21, 10:20 UTC | May 22, 00:55 UTC | 14h 35m |
| 2026-05-21 | UZB231 | TAS → FRA | May 21, 06:10 UTC | May 21, 07:35 UTC | 1h 25m |
| 2026-05-20 | UZB231 | TAS → FRA | May 20, 11:00 UTC | May 21, 07:35 UTC | 20h 35m |
| 2026-05-19 | UZB274 | IST → TAS | May 19, 19:15 UTC | May 20, 11:05 UTC | 15h 51m |
| 2026-05-19 | UZB273 | TAS → IST | May 19, 14:30 UTC | May 19, 15:40 UTC | 1h 10m |
| 2026-05-18 | UZB273 | TAS → IST | May 18, 20:05 UTC | May 19, 15:40 UTC | 19h 35m |
| 2026-05-18 | UZB274 | IST → TAS | May 18, 19:15 UTC | May 18, 19:25 UTC | 10m |
| 2026-05-18 | UZB273 | TAS → IST | May 18, 16:35 UTC | May 18, 16:45 UTC | 10m |
| 2026-05-18 | UZB273 | TAS → IST | May 18, 01:15 UTC | May 18, 15:45 UTC | 14h 30m |
| 2026-05-17 | UZB102 | JFK → RIX | May 17, 17:20 UTC | May 18, 15:45 UTC | 22h 25m |
| 2026-05-17 | UZB102 | JFK → RIX | May 17, 17:10 UTC | May 18, 15:15 UTC | 22h 5m |
| 2026-05-17 | UZB101 | TAS → JFK | May 17, 04:25 UTC | May 17, 14:01 UTC | 9h 35m |
| 2026-05-15 | UZB273 | TAS → IST | May 15, 14:30 UTC | May 15, 21:30 UTC | 6h 59m |
| 2026-05-14 | UZB232 | FRA → TAS | May 14, 10:20 UTC | May 14, 13:50 UTC | 3h 30m |
| 2026-05-14 | UZB231 | TAS → FRA | May 14, 03:55 UTC | May 14, 07:30 UTC | 3h 35m |
| 2026-05-13 | UZB231 | TAS → FRA | May 13, 11:20 UTC | May 14, 07:30 UTC | 20h 10m |
| 2026-05-13 | UZB231 | TAS → FRA | May 13, 10:40 UTC | May 14, 07:30 UTC | 20h 50m |
| 2026-05-13 | UZB271 | TAS → IST | May 13, 05:20 UTC | May 14, 04:35 UTC | 23h 15m |
| 2026-05-12 | UZB274 | IST → TAS | May 12, 19:05 UTC | May 13, 11:55 UTC | 16h 50m |
| 2026-05-12 | UZB273 | TAS → IST | May 12, 14:25 UTC | May 12, 15:45 UTC | 1h 20m |
| 2026-05-10 | UZB102 | JFK → RIX | May 10, 23:00 UTC | May 11, 14:50 UTC | 15h 50m |
| 2026-05-10 | UZB102 | JFK → RIX | May 10, 17:20 UTC | May 11, 14:50 UTC | 21h 30m |
| 2026-05-09 | UZB101 | TAS → JFK | May 9, 20:15 UTC | May 10, 14:54 UTC | 18h 40m |
| 2026-05-09 | UZB101 | TAS → JFK | May 9, 15:20 UTC | May 10, 14:54 UTC | 23h 35m |
| 2026-05-09 | UZB273 | TAS → IST | May 9, 14:40 UTC | May 10, 13:14 UTC | 22h 35m |
| 2026-05-08 | UZB506 | - | May 8, 01:59 UTC | May 8, 02:14 UTC | 15m |
| 2026-05-07 | UZB505 | - | May 7, 23:05 UTC | May 7, 23:19 UTC | 15m |
| 2026-05-07 | UZB232 | FRA → TAS | May 7, 10:10 UTC | May 7, 13:30 UTC | 3h 20m |
| 2026-05-07 | UZB231 | TAS → FRA | May 7, 06:30 UTC | May 7, 07:25 UTC | 55m |
| 2026-05-05 | UZB506 | - | May 5, 01:50 UTC | May 5, 02:01 UTC | 10m |
| 2026-05-04 | UZB3253 | - | May 4, 06:25 UTC | May 4, 23:00 UTC | 16h 36m |
| 2026-05-03 | UZB258 | FCO → TAS | May 3, 19:20 UTC | May 4, 13:20 UTC | 18h 0m |
| 2026-05-03 | UZB258 | FCO → TAS | May 3, 18:55 UTC | May 4, 13:20 UTC | 18h 25m |
| 2026-05-03 | UZB257 | TAS → FCO | May 3, 12:40 UTC | May 3, 16:30 UTC | 3h 50m |
| 2026-05-02 | UZB334 | DXB → TAS | May 2, 08:55 UTC | May 2, 10:55 UTC | 2h 0m |
| 2026-05-01 | UZB274 | IST → TAS | May 1, 19:15 UTC | May 2, 06:45 UTC | 11h 30m |
| 2026-05-01 | UZB273 | TAS → IST | May 1, 01:40 UTC | May 1, 15:40 UTC | 14h 0m |
| 2026-04-30 | UZB511 | - | Apr 30, 22:45 UTC | Apr 30, 23:05 UTC | 20m |
| 2026-04-30 | UZB554 | KUL → TAS | Apr 30, 07:00 UTC | Apr 30, 22:05 UTC | 15h 5m |
| 2026-04-30 | UZB554 | KUL → TAS | Apr 30, 04:30 UTC | Apr 30, 04:40 UTC | 10m |
| 2026-04-30 | UZB553 | TAS → KUL | Apr 30, 01:40 UTC | Apr 30, 02:00 UTC | 20m |
| 2026-04-29 | UZB553 | TAS → KUL | Apr 29, 21:05 UTC | Apr 29, 23:20 UTC | 2h 14m |
| 2026-04-29 | UZB553 | TAS → KUL | Apr 29, 01:35 UTC | Apr 29, 23:20 UTC | 21h 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-78705 page for operator, model, and routing details .