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