sensors Mode-S transponder
507C48
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-67005 · BOEING 767-300
- Hex
- 507C48
- Octal
- 24076110
- Decimal
- 5,274,696
- Country
- UZ
- Tail
- UK-67005
- Type
- B763
- Flights observed
- 76
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 20h ago
Current position
Country allocation
The ICAO 24-bit address 507C48 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-25 |
| UZB536 | Uzbekistan Airways | 7 | 2026-05-13 |
| UZB272 | Uzbekistan Airways | 6 | 2026-05-18 |
| UZB535 | - | 5 | 2026-05-12 |
| UZB534 | - | 5 | 2026-05-27 |
| UZB273 | Uzbekistan Airways | 5 | 2026-05-28 |
| UZB533 | - | 4 | 2026-05-27 |
| UZB423 | Uzbekistan Airways | 4 | 2026-05-23 |
| UZB601 | Uzbekistan Airways | 3 | 2026-05-11 |
| UZB576 | - | 3 | 2026-04-27 |
| UZB532 | Uzbekistan Airways | 3 | 2026-05-26 |
| UZB531 | Uzbekistan Airways | 3 | 2026-05-25 |
| UZB282 | Uzbekistan Airways | 3 | 2026-04-18 |
| UZB274 | Uzbekistan Airways | 3 | 2026-05-28 |
| UZB424 | Uzbekistan Airways | 2 | 2026-05-23 |
| UZB301 | Uzbekistan Airways | 2 | 2026-04-16 |
| UZB281 | Uzbekistan Airways | 2 | 2026-04-17 |
| UZB746 | Uzbekistan Airways | 1 | 2026-05-29 |
| UZB745 | Uzbekistan Airways | 1 | 2026-05-22 |
| UZB633 | Uzbekistan Airways | 1 | 2026-04-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UZB746 | TBS → TAS | May 29, 08:40 UTC | May 29, 09:00 UTC | 20m |
| 2026-05-28 | UZB274 | IST → TAS | May 28, 19:20 UTC | May 29, 06:20 UTC | 11h 0m |
| 2026-05-28 | UZB273 | TAS → IST | May 28, 15:10 UTC | May 28, 17:40 UTC | 2h 30m |
| 2026-05-27 | UZB273 | TAS → IST | May 27, 20:05 UTC | May 28, 17:40 UTC | 21h 35m |
| 2026-05-27 | UZB534 | - | May 27, 18:05 UTC | May 28, 17:40 UTC | 23h 35m |
| 2026-05-27 | UZB534 | - | May 27, 16:20 UTC | May 28, 15:55 UTC | 23h 35m |
| 2026-05-27 | UZB533 | - | May 27, 10:00 UTC | May 27, 14:15 UTC | 4h 15m |
| 2026-05-26 | UZB532 | BKK → TAS | May 26, 02:00 UTC | May 26, 06:14 UTC | 4h 15m |
| 2026-05-25 | UZB531 | TAS → BKK | May 25, 09:55 UTC | May 25, 23:54 UTC | 13h 59m |
| 2026-05-25 | UZB271 | TAS → IST | May 25, 07:30 UTC | May 25, 07:40 UTC | 10m |
| 2026-05-25 | UZB271 | TAS → IST | May 25, 05:20 UTC | May 25, 06:30 UTC | 1h 10m |
| 2026-05-23 | UZB424 | DEL → TAS | May 23, 08:30 UTC | May 23, 09:10 UTC | 40m |
| 2026-05-23 | UZB423 | TAS → DEL | May 23, 05:30 UTC | May 23, 06:20 UTC | 50m |
| 2026-05-22 | UZB423 | TAS → DEL | May 22, 08:20 UTC | May 23, 06:20 UTC | 21h 59m |
| 2026-05-22 | UZB745 | TAS → TBS | May 22, 05:40 UTC | May 22, 06:15 UTC | 35m |
| 2026-05-18 | UZB272 | IST → TAS | May 18, 10:15 UTC | May 18, 12:10 UTC | 1h 55m |
| 2026-05-18 | UZB271 | TAS → IST | May 18, 07:40 UTC | May 18, 07:50 UTC | 10m |
| 2026-05-18 | UZB271 | TAS → IST | May 18, 05:30 UTC | May 18, 06:45 UTC | 1h 15m |
| 2026-05-14 | UZB272 | IST → TAS | May 14, 10:05 UTC | May 14, 11:55 UTC | 1h 50m |
| 2026-05-13 | UZB271 | TAS → IST | May 13, 16:10 UTC | May 14, 06:20 UTC | 14h 10m |
| 2026-05-13 | UZB536 | HKT → TAS | May 13, 08:05 UTC | May 14, 06:20 UTC | 22h 15m |
| 2026-05-13 | UZB536 | HKT → TAS | May 13, 06:30 UTC | May 14, 05:55 UTC | 23h 25m |
| 2026-05-13 | UZB536 | HKT → TAS | May 13, 00:05 UTC | May 13, 20:35 UTC | 20h 30m |
| 2026-05-12 | UZB536 | HKT → TAS | May 12, 22:15 UTC | May 13, 20:35 UTC | 22h 20m |
| 2026-05-12 | UZB535 | - | May 12, 08:05 UTC | May 13, 07:10 UTC | 23h 5m |
| 2026-05-12 | UZB535 | - | May 12, 07:30 UTC | May 13, 00:35 UTC | 17h 5m |
| 2026-05-11 | UZB601 | TAS → DME | May 11, 17:10 UTC | May 12, 08:15 UTC | 15h 5m |
| 2026-05-09 | UZB603 | TAS → DME | May 9, 06:20 UTC | May 9, 18:40 UTC | 12h 20m |
| 2026-05-08 | UZB532 | BKK → TAS | May 8, 01:14 UTC | May 8, 05:35 UTC | 4h 20m |
| 2026-05-07 | UZB531 | TAS → BKK | May 7, 09:55 UTC | May 7, 23:24 UTC | 13h 29m |
| 2026-05-06 | UZB271 | TAS → IST | May 6, 17:00 UTC | May 7, 06:40 UTC | 13h 39m |
| 2026-05-06 | UZB271 | TAS → IST | May 6, 08:45 UTC | May 7, 06:40 UTC | 21h 54m |
| 2026-05-06 | UZB536 | HKT → TAS | May 6, 07:15 UTC | May 7, 06:00 UTC | 22h 44m |
| 2026-05-05 | UZB536 | HKT → TAS | May 5, 22:45 UTC | May 6, 17:35 UTC | 18h 49m |
| 2026-05-05 | UZB536 | HKT → TAS | May 5, 12:20 UTC | May 6, 09:55 UTC | 21h 35m |
| 2026-05-04 | UZB601 | TAS → DME | May 4, 17:10 UTC | May 5, 12:25 UTC | 19h 16m |
| 2026-05-02 | UZB424 | DEL → TAS | May 2, 08:50 UTC | May 2, 17:40 UTC | 8h 50m |
| 2026-05-02 | UZB423 | TAS → DEL | May 2, 05:40 UTC | May 2, 06:15 UTC | 35m |
| 2026-05-01 | UZB532 | BKK → TAS | May 1, 01:30 UTC | May 1, 05:55 UTC | 4h 25m |
| 2026-04-30 | UZB531 | TAS → BKK | Apr 30, 10:55 UTC | Apr 30, 23:35 UTC | 12h 40m |
| 2026-04-29 | UZB271 | TAS → IST | Apr 29, 12:15 UTC | Apr 30, 06:35 UTC | 18h 19m |
| 2026-04-29 | UZB211 | TAS → RIX | Apr 29, 08:25 UTC | Apr 29, 08:40 UTC | 15m |
| 2026-04-27 | UZB601 | TAS → DME | Apr 27, 18:15 UTC | Apr 27, 18:25 UTC | 10m |
| 2026-04-27 | UZB576 | - | Apr 27, 02:25 UTC | Apr 27, 02:40 UTC | 15m |
| 2026-04-25 | UZB274 | IST → TAS | Apr 25, 20:20 UTC | Apr 26, 06:35 UTC | 10h 15m |
| 2026-04-25 | UZB273 | TAS → IST | Apr 25, 08:55 UTC | Apr 25, 17:30 UTC | 8h 35m |
| 2026-04-25 | UZB423 | TAS → DEL | Apr 25, 06:05 UTC | Apr 25, 06:40 UTC | 35m |
| 2026-04-21 | UZB535 | - | Apr 21, 22:45 UTC | Apr 22, 09:35 UTC | 10h 50m |
| 2026-04-21 | UZB535 | - | Apr 21, 12:05 UTC | Apr 22, 09:35 UTC | 21h 30m |
| 2026-04-21 | UZB535 | - | Apr 21, 10:30 UTC | Apr 22, 09:35 UTC | 23h 5m |
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-67005 page for operator, model, and routing details .