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