sensors Mode-S transponder
507C45
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-67004 · BOEING 767-300
- Hex
- 507C45
- Octal
- 24076105
- Decimal
- 5,274,693
- Country
- UZ
- Tail
- UK-67004
- Type
- B763
- Flights observed
- 117
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 21d ago
Last known position
Country allocation
The ICAO 24-bit address 507C45 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 |
|---|---|---|---|
| UZB271 | - | 16 | 2026-06-11 |
| UZB272 | Uzbekistan Airways | 10 | 2026-06-12 |
| UZB273 | Uzbekistan Airways | 7 | 2026-05-31 |
| UZB535 | - | 6 | 2026-05-08 |
| UZB603 | Uzbekistan Airways | 5 | 2026-06-06 |
| UZB601 | Uzbekistan Airways | 5 | 2026-06-13 |
| UZB532 | Uzbekistan Airways | 5 | 2026-05-11 |
| UZB274 | Uzbekistan Airways | 5 | 2026-05-31 |
| UZB211 | - | 5 | 2026-06-17 |
| UZB534 | - | 4 | 2026-05-06 |
| UZB533 | - | 4 | 2026-05-06 |
| UZB302 | Uzbekistan Airways | 4 | 2026-06-15 |
| UZB301 | Uzbekistan Airways | 4 | 2026-06-14 |
| UZB212 | Uzbekistan Airways | 4 | 2026-06-17 |
| UZB634 | Uzbekistan Airways | 3 | 2026-06-03 |
| UZB531 | Uzbekistan Airways | 3 | 2026-04-16 |
| UZB425 | Uzbekistan Airways | 3 | 2026-05-10 |
| UZB423 | Uzbekistan Airways | 3 | 2026-06-10 |
| UZB745 | Uzbekistan Airways | 2 | 2026-04-30 |
| UZB633 | Uzbekistan Airways | 2 | 2026-05-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-23 | UZB3224 | AYT → TAS | Jun 23, 12:05 UTC | Jun 23, 13:55 UTC | 1h 50m |
| 2026-06-23 | UZB3223 | - | Jun 23, 08:04 UTC | Jun 23, 10:35 UTC | 2h 30m |
| 2026-06-21 | UZB709 | - | Jun 21, 20:45 UTC | Jun 22, 07:30 UTC | 10h 45m |
| 2026-06-18 | UZB5302 | - | Jun 18, 11:25 UTC | Jun 19, 05:09 UTC | 17h 44m |
| 2026-06-18 | UZB334 | DXB → TAS | Jun 18, 09:15 UTC | Jun 18, 09:40 UTC | 25m |
| 2026-06-17 | UZB212 | RIX → TAS | Jun 17, 12:05 UTC | Jun 18, 06:15 UTC | 18h 10m |
| 2026-06-17 | UZB211 | - | Jun 17, 08:35 UTC | Jun 17, 08:50 UTC | 15m |
| 2026-06-17 | UZB211 | - | Jun 17, 06:40 UTC | Jun 17, 06:50 UTC | 10m |
| 2026-06-16 | UZB334 | DXB → TAS | Jun 16, 09:00 UTC | Jun 16, 09:25 UTC | 25m |
| 2026-06-15 | UZB302 | TLV → TAS | Jun 15, 11:00 UTC | Jun 16, 03:50 UTC | 16h 50m |
| 2026-06-14 | UZB301 | TAS → TLV | Jun 14, 17:45 UTC | Jun 15, 08:29 UTC | 14h 44m |
| 2026-06-13 | UZB601 | TAS → DME | Jun 13, 19:20 UTC | Jun 14, 18:05 UTC | 22h 46m |
| 2026-06-13 | UZB601 | TAS → DME | Jun 13, 19:00 UTC | Jun 13, 19:40 UTC | 40m |
| 2026-06-12 | UZB601 | TAS → DME | Jun 12, 23:30 UTC | Jun 13, 19:40 UTC | 20h 9m |
| 2026-06-12 | UZB272 | IST → TAS | Jun 12, 09:55 UTC | Jun 12, 19:00 UTC | 9h 5m |
| 2026-06-11 | UZB271 | - | Jun 11, 16:20 UTC | Jun 12, 07:50 UTC | 15h 30m |
| 2026-06-11 | UZB271 | - | Jun 11, 09:20 UTC | Jun 12, 07:50 UTC | 22h 31m |
| 2026-06-11 | UZB271 | - | Jun 11, 08:40 UTC | Jun 12, 07:15 UTC | 22h 36m |
| 2026-06-10 | UZB423 | TAS → DEL | Jun 10, 12:15 UTC | Jun 11, 06:30 UTC | 18h 15m |
| 2026-06-10 | UZB211 | TAS → RIX | Jun 10, 08:30 UTC | Jun 10, 08:50 UTC | 20m |
| 2026-06-09 | UZB272 | IST → TAS | Jun 9, 10:20 UTC | Jun 9, 12:20 UTC | 2h 0m |
| 2026-06-09 | UZB271 | TAS → IST | Jun 9, 05:30 UTC | Jun 9, 08:05 UTC | 2h 35m |
| 2026-06-06 | UZB603 | TAS → DME | Jun 6, 17:10 UTC | Jun 7, 06:40 UTC | 13h 30m |
| 2026-06-06 | UZB282 | IST → TAS | Jun 6, 03:45 UTC | Jun 6, 21:35 UTC | 17h 50m |
| 2026-06-05 | UZB281 | TAS → IST | Jun 5, 10:05 UTC | Jun 6, 01:10 UTC | 15h 5m |
| 2026-06-04 | UZB271 | TAS → IST | Jun 4, 17:45 UTC | Jun 5, 07:45 UTC | 14h 0m |
| 2026-06-04 | UZB271 | TAS → IST | Jun 4, 10:50 UTC | Jun 5, 07:45 UTC | 20h 55m |
| 2026-06-03 | UZB634 | LED → TAS | Jun 3, 10:40 UTC | Jun 3, 11:45 UTC | 1h 5m |
| 2026-06-01 | UZB5302 | - | Jun 1, 22:50 UTC | Jun 2, 11:15 UTC | 12h 25m |
| 2026-06-01 | UZB212 | RIX → TAS | Jun 1, 12:20 UTC | Jun 2, 11:15 UTC | 22h 55m |
| 2026-06-01 | UZB211 | TAS → RIX | Jun 1, 08:15 UTC | Jun 1, 08:30 UTC | 15m |
| 2026-05-31 | UZB274 | IST → TAS | May 31, 19:25 UTC | Jun 1, 06:55 UTC | 11h 30m |
| 2026-05-31 | UZB273 | TAS → IST | May 31, 14:30 UTC | May 31, 17:25 UTC | 2h 55m |
| 2026-05-30 | UZB273 | TAS → IST | May 30, 21:35 UTC | May 31, 17:25 UTC | 19h 50m |
| 2026-05-29 | UZB274 | IST → TAS | May 29, 19:15 UTC | May 29, 21:10 UTC | 1h 55m |
| 2026-05-29 | UZB273 | TAS → IST | May 29, 01:50 UTC | May 29, 17:10 UTC | 15h 20m |
| 2026-05-28 | UZB505 | - | May 28, 22:50 UTC | May 28, 23:05 UTC | 15m |
| 2026-05-28 | UZB272 | IST → TAS | May 28, 10:05 UTC | May 28, 12:10 UTC | 2h 5m |
| 2026-05-27 | UZB271 | TAS → IST | May 27, 19:10 UTC | May 28, 07:50 UTC | 12h 40m |
| 2026-05-27 | UZB273 | TAS → IST | May 27, 14:45 UTC | May 27, 16:10 UTC | 1h 25m |
| 2026-05-25 | UZB274 | IST → TAS | May 25, 22:25 UTC | May 26, 00:24 UTC | 2h 0m |
| 2026-05-25 | UZB273 | TAS → IST | May 25, 20:15 UTC | May 25, 20:24 UTC | 10m |
| 2026-05-25 | UZB273 | TAS → IST | May 25, 09:30 UTC | May 25, 19:25 UTC | 9h 54m |
| 2026-05-25 | UZB423 | TAS → DEL | May 25, 05:35 UTC | May 25, 06:30 UTC | 55m |
| 2026-05-23 | UZB272 | IST → TAS | May 23, 10:10 UTC | May 23, 12:10 UTC | 2h 0m |
| 2026-05-23 | UZB271 | TAS → IST | May 23, 07:30 UTC | May 23, 07:40 UTC | 10m |
| 2026-05-23 | UZB271 | TAS → IST | May 23, 05:30 UTC | May 23, 06:40 UTC | 1h 10m |
| 2026-05-21 | UZB302 | TLV → TAS | May 21, 10:45 UTC | May 21, 13:10 UTC | 2h 25m |
| 2026-05-21 | UZB301 | TAS → TLV | May 21, 05:40 UTC | May 21, 08:10 UTC | 2h 30m |
| 2026-05-20 | UZB301 | TAS → TLV | May 20, 08:40 UTC | May 21, 07:15 UTC | 22h 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-67004 page for operator, model, and routing details .