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