sensors Mode-S transponder
507C70
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK32105 · AIRBUS A-321neo
- Hex
- 507C70
- Octal
- 24076160
- Decimal
- 5,274,736
- Country
- UZ
- Tail
- UK32105
- Type
- A21N
- Flights observed
- 75
- Distinct callsigns
- 12
- Country
- UZ
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 507C70 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 12 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UZB3223 | - | 13 | 2026-05-12 |
| UZB211 | Uzbekistan Airways | 13 | 2026-05-29 |
| UZB212 | Uzbekistan Airways | 11 | 2026-05-29 |
| UZB3224 | Uzbekistan Airways | 9 | 2026-05-13 |
| UZB614 | Uzbekistan Airways | 6 | 2026-05-23 |
| UZB612 | Uzbekistan Airways | 5 | 2026-05-02 |
| UZB341 | - | 5 | 2026-04-25 |
| UZB342 | Uzbekistan Airways | 4 | 2026-04-22 |
| UZB282 | Uzbekistan Airways | 3 | 2026-05-23 |
| UZB281 | Uzbekistan Airways | 3 | 2026-05-23 |
| UZB634 | Uzbekistan Airways | 2 | 2026-04-27 |
| UZB632 | Uzbekistan Airways | 1 | 2026-05-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UZB212 | RIX → TAS | May 29, 12:05 UTC | May 29, 14:25 UTC | 2h 20m |
| 2026-05-29 | UZB211 | TAS → RIX | May 29, 08:40 UTC | May 29, 09:00 UTC | 20m |
| 2026-05-28 | UZB212 | RIX → TAS | May 28, 12:05 UTC | May 28, 14:15 UTC | 2h 10m |
| 2026-05-27 | UZB211 | TAS → RIX | May 27, 14:10 UTC | May 28, 09:00 UTC | 18h 50m |
| 2026-05-27 | UZB212 | RIX → TAS | May 27, 12:10 UTC | May 28, 09:00 UTC | 20h 50m |
| 2026-05-27 | UZB211 | TAS → RIX | May 27, 08:25 UTC | May 27, 08:45 UTC | 20m |
| 2026-05-26 | UZB211 | TAS → RIX | May 26, 12:24 UTC | May 27, 07:40 UTC | 19h 15m |
| 2026-05-23 | UZB614 | DME → TAS | May 23, 21:30 UTC | May 23, 21:55 UTC | 25m |
| 2026-05-23 | UZB282 | IST → TAS | May 23, 03:40 UTC | May 23, 05:40 UTC | 2h 0m |
| 2026-05-23 | UZB281 | TAS → IST | May 23, 01:15 UTC | May 23, 01:25 UTC | 10m |
| 2026-05-22 | UZB281 | TAS → IST | May 22, 23:20 UTC | May 23, 00:25 UTC | 1h 5m |
| 2026-05-17 | UZB632 | LED → TAS | May 17, 22:35 UTC | May 18, 06:55 UTC | 8h 20m |
| 2026-05-16 | UZB614 | DME → TAS | May 16, 19:50 UTC | May 16, 20:35 UTC | 45m |
| 2026-05-14 | UZB212 | RIX → TAS | May 14, 12:15 UTC | May 14, 14:35 UTC | 2h 20m |
| 2026-05-14 | UZB211 | TAS → RIX | May 14, 07:40 UTC | May 14, 08:40 UTC | 1h 0m |
| 2026-05-13 | UZB3224 | AYT → TAS | May 13, 12:05 UTC | May 14, 08:40 UTC | 20h 35m |
| 2026-05-12 | UZB3223 | - | May 12, 20:10 UTC | May 13, 09:45 UTC | 13h 35m |
| 2026-05-11 | UZB3224 | AYT → TAS | May 11, 12:20 UTC | May 11, 14:15 UTC | 1h 55m |
| 2026-05-10 | UZB3223 | - | May 10, 22:20 UTC | May 11, 09:45 UTC | 11h 25m |
| 2026-05-10 | UZB3223 | - | May 10, 08:35 UTC | May 11, 08:00 UTC | 23h 26m |
| 2026-05-09 | UZB614 | DME → TAS | May 9, 19:55 UTC | May 10, 08:40 UTC | 12h 45m |
| 2026-05-09 | UZB282 | IST → TAS | May 9, 03:55 UTC | May 9, 20:10 UTC | 16h 15m |
| 2026-05-08 | UZB3224 | AYT → TAS | May 8, 12:14 UTC | May 9, 00:30 UTC | 12h 15m |
| 2026-05-08 | UZB3223 | - | May 8, 08:05 UTC | May 8, 10:09 UTC | 2h 5m |
| 2026-05-07 | UZB3223 | - | May 7, 14:05 UTC | May 8, 10:09 UTC | 20h 5m |
| 2026-05-07 | UZB3223 | - | May 7, 12:05 UTC | May 8, 10:09 UTC | 22h 5m |
| 2026-05-06 | UZB211 | TAS → RIX | May 6, 14:05 UTC | May 7, 08:45 UTC | 18h 40m |
| 2026-05-06 | UZB3224 | AYT → TAS | May 6, 12:05 UTC | May 7, 08:45 UTC | 20h 40m |
| 2026-05-06 | UZB3223 | - | May 6, 07:25 UTC | May 6, 09:40 UTC | 2h 15m |
| 2026-05-05 | UZB614 | DME → TAS | May 5, 19:20 UTC | May 5, 19:35 UTC | 15m |
| 2026-05-04 | UZB3224 | AYT → TAS | May 4, 14:05 UTC | May 5, 08:50 UTC | 18h 46m |
| 2026-05-04 | UZB3224 | AYT → TAS | May 4, 13:10 UTC | May 5, 08:50 UTC | 19h 41m |
| 2026-05-04 | UZB3223 | - | May 4, 08:35 UTC | May 4, 11:00 UTC | 2h 25m |
| 2026-05-03 | UZB3223 | - | May 3, 12:40 UTC | May 4, 11:00 UTC | 22h 20m |
| 2026-05-02 | UZB612 | DME → SKD | May 2, 20:00 UTC | May 3, 12:50 UTC | 16h 49m |
| 2026-05-02 | UZB282 | IST → TAS | May 2, 03:40 UTC | May 2, 20:05 UTC | 16h 25m |
| 2026-05-01 | UZB281 | TAS → IST | May 1, 23:00 UTC | May 2, 00:25 UTC | 1h 25m |
| 2026-04-30 | UZB212 | RIX → TAS | Apr 30, 12:10 UTC | Apr 30, 14:25 UTC | 2h 15m |
| 2026-04-29 | UZB211 | TAS → RIX | Apr 29, 14:10 UTC | Apr 30, 08:40 UTC | 18h 29m |
| 2026-04-29 | UZB3224 | AYT → TAS | Apr 29, 12:10 UTC | Apr 30, 08:40 UTC | 20h 29m |
| 2026-04-29 | UZB3223 | - | Apr 29, 09:30 UTC | Apr 29, 09:50 UTC | 20m |
| 2026-04-28 | UZB3223 | - | Apr 28, 21:10 UTC | Apr 29, 08:50 UTC | 11h 40m |
| 2026-04-27 | UZB634 | LED → TAS | Apr 27, 12:10 UTC | Apr 27, 12:25 UTC | 15m |
| 2026-04-26 | UZB634 | LED → TAS | Apr 26, 11:00 UTC | Apr 26, 12:50 UTC | 1h 50m |
| 2026-04-25 | UZB341 | - | Apr 25, 07:10 UTC | Apr 25, 16:10 UTC | 9h 0m |
| 2026-04-24 | UZB341 | - | Apr 24, 12:30 UTC | Apr 25, 10:45 UTC | 22h 15m |
| 2026-04-24 | UZB211 | TAS → RIX | Apr 24, 08:40 UTC | Apr 24, 09:05 UTC | 25m |
| 2026-04-23 | UZB612 | DME → SKD | Apr 23, 07:45 UTC | Apr 23, 08:15 UTC | 30m |
| 2026-04-22 | UZB342 | SSH → TAS | Apr 22, 06:50 UTC | Apr 22, 15:45 UTC | 8h 55m |
| 2026-04-21 | UZB614 | DME → TAS | Apr 21, 19:35 UTC | Apr 21, 20:10 UTC | 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 UK32105 page for operator, model, and routing details .