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
- 145
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 10h ago
Last known 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 | 16 | 2026-06-06 |
| UZB423 | - | 9 | 2026-06-25 |
| UZB272 | Uzbekistan Airways | 8 | 2026-06-06 |
| UZB536 | Uzbekistan Airways | 7 | 2026-05-13 |
| UZB301 | - | 6 | 2026-07-09 |
| UZB601 | Uzbekistan Airways | 5 | 2026-07-01 |
| UZB535 | - | 5 | 2026-05-12 |
| UZB5348 | - | 5 | 2026-06-17 |
| UZB534 | - | 5 | 2026-05-27 |
| UZB302 | - | 5 | 2026-07-09 |
| UZB282 | - | 5 | 2026-07-11 |
| UZB281 | - | 5 | 2026-07-11 |
| UZB273 | Uzbekistan Airways | 5 | 2026-05-28 |
| UZB5349 | - | 4 | 2026-06-08 |
| UZB5345 | - | 4 | 2026-06-11 |
| UZB533 | - | 4 | 2026-05-27 |
| UZB5328 | - | 4 | 2026-06-12 |
| UZB424 | - | 4 | 2026-06-25 |
| UZB576 | - | 3 | 2026-04-27 |
| UZB5369 | - | 3 | 2026-06-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UZB603 | - | Jul 14, 06:05 UTC | Jul 14, 06:20 UTC | 15m |
| 2026-07-12 | UZB613 | TAS → VKO | Jul 12, 15:40 UTC | Jul 12, 15:55 UTC | 15m |
| 2026-07-11 | UZB282 | - | Jul 11, 03:25 UTC | Jul 11, 05:15 UTC | 1h 50m |
| 2026-07-11 | UZB281 | - | Jul 11, 00:55 UTC | Jul 11, 01:15 UTC | 20m |
| 2026-07-10 | UZB281 | - | Jul 10, 12:30 UTC | Jul 11, 00:10 UTC | 11h 40m |
| 2026-07-10 | UZB422 | - | Jul 10, 01:20 UTC | Jul 10, 09:45 UTC | 8h 25m |
| 2026-07-09 | UZB302 | TLV → DEL | Jul 9, 10:45 UTC | Jul 9, 22:45 UTC | 12h 0m |
| 2026-07-09 | UZB301 | - | Jul 9, 05:55 UTC | Jul 9, 08:45 UTC | 2h 50m |
| 2026-07-08 | UZB301 | RIX → TLV | Jul 8, 12:15 UTC | Jul 9, 08:45 UTC | 20h 30m |
| 2026-07-08 | UZB211 | - | Jul 8, 08:50 UTC | Jul 8, 09:10 UTC | 20m |
| 2026-07-07 | UZB282 | - | Jul 7, 03:50 UTC | Jul 7, 05:45 UTC | 1h 55m |
| 2026-07-07 | UZB281 | - | Jul 7, 01:25 UTC | Jul 7, 01:45 UTC | 20m |
| 2026-07-06 | UZB302 | - | Jul 6, 11:00 UTC | Jul 7, 00:30 UTC | 13h 30m |
| 2026-07-06 | UZB301 | - | Jul 6, 05:55 UTC | Jul 6, 08:50 UTC | 2h 55m |
| 2026-07-01 | UZB601 | TAS → DME | Jul 1, 17:05 UTC | Jul 2, 10:40 UTC | 17h 35m |
| 2026-06-25 | UZB424 | - | Jun 25, 09:25 UTC | Jun 25, 10:04 UTC | 40m |
| 2026-06-25 | UZB423 | - | Jun 25, 06:14 UTC | Jun 25, 07:05 UTC | 50m |
| 2026-06-24 | UZB423 | - | Jun 24, 08:45 UTC | Jun 25, 07:05 UTC | 22h 20m |
| 2026-06-23 | UZB423 | - | Jun 23, 21:05 UTC | Jun 24, 06:15 UTC | 9h 10m |
| 2026-06-23 | UZB423 | - | Jun 23, 10:04 UTC | Jun 24, 06:15 UTC | 20h 10m |
| 2026-06-20 | UZB424 | - | Jun 20, 09:05 UTC | Jun 20, 09:44 UTC | 40m |
| 2026-06-20 | UZB423 | - | Jun 20, 06:29 UTC | Jun 20, 07:14 UTC | 45m |
| 2026-06-17 | UZB5329 | - | Jun 17, 20:05 UTC | Jun 18, 13:10 UTC | 17h 5m |
| 2026-06-17 | UZB5329 | - | Jun 17, 15:05 UTC | Jun 18, 13:10 UTC | 22h 5m |
| 2026-06-17 | UZB5329 | - | Jun 17, 12:25 UTC | Jun 18, 07:00 UTC | 18h 35m |
| 2026-06-17 | UZB5348 | - | Jun 17, 07:10 UTC | Jun 18, 06:00 UTC | 22h 50m |
| 2026-06-17 | UZB5348 | - | Jun 17, 04:20 UTC | Jun 18, 04:00 UTC | 23h 40m |
| 2026-06-16 | UZB5366 | - | Jun 16, 15:35 UTC | Jun 17, 12:25 UTC | 20h 51m |
| 2026-06-16 | UZB5366 | - | Jun 16, 12:45 UTC | Jun 17, 07:10 UTC | 18h 26m |
| 2026-06-15 | UZB5324 | - | Jun 15, 21:20 UTC | Jun 16, 15:40 UTC | 18h 20m |
| 2026-06-15 | UZB5324 | - | Jun 15, 04:50 UTC | Jun 15, 21:45 UTC | 16h 55m |
| 2026-06-14 | UZB5370 | - | Jun 14, 09:10 UTC | Jun 15, 05:04 UTC | 19h 55m |
| 2026-06-14 | UZB5369 | - | Jun 14, 00:45 UTC | Jun 14, 10:00 UTC | 9h 15m |
| 2026-06-13 | UZB5369 | - | Jun 13, 13:20 UTC | Jun 14, 10:00 UTC | 20h 40m |
| 2026-06-13 | UZB5369 | - | Jun 13, 05:05 UTC | Jun 14, 03:40 UTC | 22h 35m |
| 2026-06-12 | UZB5328 | - | Jun 12, 21:30 UTC | Jun 13, 13:45 UTC | 16h 14m |
| 2026-06-12 | UZB5328 | - | Jun 12, 13:05 UTC | Jun 13, 05:05 UTC | 15h 59m |
| 2026-06-12 | UZB5328 | - | Jun 12, 05:25 UTC | Jun 12, 22:35 UTC | 17h 10m |
| 2026-06-12 | UZB5328 | - | Jun 12, 00:05 UTC | Jun 12, 22:35 UTC | 22h 31m |
| 2026-06-11 | UZB5345 | - | Jun 11, 23:05 UTC | Jun 12, 21:55 UTC | 22h 51m |
| 2026-06-11 | UZB5345 | - | Jun 11, 21:05 UTC | Jun 12, 13:05 UTC | 16h 1m |
| 2026-06-11 | UZB5345 | - | Jun 11, 12:15 UTC | Jun 12, 05:55 UTC | 17h 41m |
| 2026-06-11 | UZB5345 | - | Jun 11, 09:30 UTC | Jun 12, 05:55 UTC | 20h 26m |
| 2026-06-10 | UZB5304 | - | Jun 10, 13:10 UTC | Jun 11, 09:45 UTC | 20h 35m |
| 2026-06-09 | UZB5304 | - | Jun 9, 21:35 UTC | Jun 10, 13:40 UTC | 16h 5m |
| 2026-06-09 | UZB5304 | - | Jun 9, 15:45 UTC | Jun 10, 13:40 UTC | 21h 55m |
| 2026-06-09 | UZB5322 | - | Jun 9, 05:30 UTC | Jun 9, 21:55 UTC | 16h 25m |
| 2026-06-09 | UZB5322 | - | Jun 9, 00:05 UTC | Jun 9, 21:55 UTC | 21h 50m |
| 2026-06-08 | UZB5349 | - | Jun 8, 23:50 UTC | Jun 9, 21:55 UTC | 22h 5m |
| 2026-06-08 | UZB5349 | - | Jun 8, 21:15 UTC | Jun 9, 15:50 UTC | 18h 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 UK-67005 page for operator, model, and routing details .