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
- 83
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 13h 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 | Uzbekistan Airways | 10 | 2026-05-27 |
| UZB272 | Uzbekistan Airways | 8 | 2026-05-28 |
| UZB535 | - | 6 | 2026-05-08 |
| UZB532 | Uzbekistan Airways | 5 | 2026-05-11 |
| UZB273 | Uzbekistan Airways | 5 | 2026-05-29 |
| UZB603 | Uzbekistan Airways | 4 | 2026-05-18 |
| UZB534 | - | 4 | 2026-05-06 |
| UZB533 | - | 4 | 2026-05-06 |
| UZB274 | Uzbekistan Airways | 4 | 2026-05-29 |
| UZB531 | Uzbekistan Airways | 3 | 2026-04-16 |
| UZB425 | Uzbekistan Airways | 3 | 2026-05-10 |
| UZB302 | Uzbekistan Airways | 3 | 2026-05-21 |
| UZB301 | Uzbekistan Airways | 3 | 2026-05-21 |
| UZB745 | Uzbekistan Airways | 2 | 2026-04-30 |
| UZB634 | - | 2 | 2026-04-21 |
| UZB633 | Uzbekistan Airways | 2 | 2026-05-17 |
| UZB601 | Uzbekistan Airways | 2 | 2026-05-15 |
| UZB536 | Uzbekistan Airways | 2 | 2026-04-15 |
| UZB505 | - | 2 | 2026-05-28 |
| UZB426 | Uzbekistan Airways | 2 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 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 |
| 2026-05-19 | UZB423 | TAS → DEL | May 19, 11:20 UTC | May 20, 06:25 UTC | 19h 6m |
| 2026-05-19 | UZB272 | IST → TAS | May 19, 10:50 UTC | May 20, 06:25 UTC | 19h 36m |
| 2026-05-19 | UZB271 | TAS → IST | May 19, 07:20 UTC | May 19, 07:30 UTC | 10m |
| 2026-05-19 | UZB271 | TAS → IST | May 19, 05:10 UTC | May 19, 06:20 UTC | 1h 10m |
| 2026-05-18 | UZB603 | TAS → DME | May 18, 06:05 UTC | May 19, 05:15 UTC | 23h 9m |
| 2026-05-17 | UZB633 | TAS → LED | May 17, 06:25 UTC | May 17, 07:05 UTC | 40m |
| 2026-05-15 | UZB601 | TAS → DME | May 15, 17:15 UTC | May 16, 06:16 UTC | 13h 1m |
| 2026-05-15 | UZB603 | TAS → DME | May 15, 06:05 UTC | May 15, 17:35 UTC | 11h 29m |
| 2026-05-14 | UZB274 | IST → TAS | May 14, 20:00 UTC | May 15, 17:35 UTC | 21h 34m |
| 2026-05-14 | UZB274 | IST → TAS | May 14, 19:10 UTC | May 14, 19:20 UTC | 10m |
| 2026-05-14 | UZB273 | TAS → IST | May 14, 14:30 UTC | May 14, 15:55 UTC | 1h 25m |
| 2026-05-13 | UZB212 | RIX → TAS | May 13, 12:20 UTC | May 13, 13:05 UTC | 45m |
| 2026-05-13 | UZB211 | TAS → RIX | May 13, 08:50 UTC | May 13, 09:15 UTC | 25m |
| 2026-05-11 | UZB532 | BKK → TAS | May 11, 11:20 UTC | May 12, 06:15 UTC | 18h 55m |
| 2026-05-11 | UZB532 | BKK → TAS | May 11, 10:00 UTC | May 12, 06:15 UTC | 20h 15m |
| 2026-05-10 | UZB271 | TAS → IST | May 10, 20:30 UTC | May 11, 06:30 UTC | 10h 0m |
| 2026-05-10 | UZB425 | TAS → DEL | May 10, 16:50 UTC | May 10, 17:55 UTC | 1h 5m |
| 2026-05-08 | UZB535 | - | May 8, 21:30 UTC | May 9, 08:00 UTC | 10h 30m |
| 2026-05-08 | UZB535 | - | May 8, 09:19 UTC | May 9, 08:00 UTC | 22h 40m |
| 2026-05-08 | UZB535 | - | May 8, 09:14 UTC | May 9, 07:15 UTC | 22h 0m |
| 2026-05-08 | UZB535 | - | May 8, 01:55 UTC | May 8, 23:45 UTC | 21h 50m |
| 2026-05-07 | UZB302 | TLV → TAS | May 7, 10:40 UTC | May 7, 23:05 UTC | 12h 25m |
| 2026-05-06 | UZB534 | BKK → TLV | May 6, 16:25 UTC | May 7, 08:25 UTC | 16h 0m |
| 2026-05-06 | UZB533 | - | May 6, 10:05 UTC | May 6, 14:00 UTC | 3h 55m |
| 2026-05-04 | UZB272 | IST → TAS | May 4, 10:00 UTC | May 4, 11:55 UTC | 1h 55m |
| 2026-05-04 | UZB271 | TAS → IST | May 4, 05:20 UTC | May 4, 06:40 UTC | 1h 20m |
| 2026-05-03 | UZB603 | TAS → DME | May 3, 05:50 UTC | May 3, 06:55 UTC | 1h 5m |
| 2026-05-01 | UZB746 | TBS → TAS | May 1, 08:25 UTC | May 1, 20:00 UTC | 11h 35m |
| 2026-04-30 | UZB745 | TAS → TBS | Apr 30, 17:00 UTC | May 1, 06:15 UTC | 13h 15m |
| 2026-04-30 | UZB745 | TAS → TBS | Apr 30, 10:05 UTC | May 1, 06:15 UTC | 20h 10m |
| 2026-04-29 | UZB534 | - | Apr 29, 19:55 UTC | Apr 30, 17:35 UTC | 21h 40m |
| 2026-04-29 | UZB534 | - | Apr 29, 17:20 UTC | Apr 30, 17:15 UTC | 23h 55m |
| 2026-04-29 | UZB534 | - | Apr 29, 16:20 UTC | Apr 30, 10:10 UTC | 17h 49m |
| 2026-04-29 | UZB533 | - | Apr 29, 10:15 UTC | Apr 29, 14:10 UTC | 3h 55m |
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 .