sensors Mode-S transponder
507C4B
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK-67007 · BOEING 767-300
- Hex
- 507C4B
- Octal
- 24076113
- Decimal
- 5,274,699
- Country
- UZ
- Tail
- UK-67007
- Type
- B763
- Flights observed
- 65
- Distinct callsigns
- 15
- Country
- UZ
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 507C4B 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UZB423 | Uzbekistan Airways | 12 | 2026-05-28 |
| UZB422 | Uzbekistan Airways | 10 | 2026-05-29 |
| UZB421 | Uzbekistan Airways | 8 | 2026-05-28 |
| UZB705 | - | 6 | 2026-05-09 |
| UZB706 | - | 5 | 2026-05-23 |
| UZB425 | Uzbekistan Airways | 5 | 2026-05-24 |
| UZB424 | Uzbekistan Airways | 5 | 2026-05-18 |
| UZB271 | Uzbekistan Airways | 4 | 2026-05-17 |
| UZB337 | - | 3 | 2026-04-18 |
| UZB426 | Uzbekistan Airways | 2 | 2026-05-24 |
| UZB708 | - | 1 | 2026-04-12 |
| UZB634 | Uzbekistan Airways | 1 | 2026-04-23 |
| UZB603 | Uzbekistan Airways | 1 | 2026-04-21 |
| UZB338 | - | 1 | 2026-04-16 |
| UZB272 | Uzbekistan Airways | 1 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | UZB422 | DEL → TAS | May 29, 01:30 UTC | May 29, 02:10 UTC | 40m |
| 2026-05-28 | UZB421 | TAS → DEL | May 28, 08:40 UTC | May 28, 23:00 UTC | 14h 20m |
| 2026-05-28 | UZB423 | TAS → DEL | May 28, 05:25 UTC | May 28, 06:30 UTC | 1h 5m |
| 2026-05-27 | UZB423 | TAS → DEL | May 27, 08:50 UTC | May 28, 06:30 UTC | 21h 40m |
| 2026-05-27 | UZB423 | TAS → DEL | May 27, 05:35 UTC | May 27, 06:25 UTC | 50m |
| 2026-05-26 | UZB422 | DEL → TAS | May 26, 01:10 UTC | May 26, 01:49 UTC | 40m |
| 2026-05-25 | UZB421 | TAS → DEL | May 25, 22:25 UTC | May 25, 23:10 UTC | 45m |
| 2026-05-24 | UZB426 | DEL → TAS | May 24, 20:30 UTC | May 24, 21:10 UTC | 40m |
| 2026-05-24 | UZB425 | TAS → DEL | May 24, 06:00 UTC | May 24, 17:45 UTC | 11h 45m |
| 2026-05-23 | UZB425 | TAS → DEL | May 23, 20:50 UTC | May 24, 17:45 UTC | 20h 55m |
| 2026-05-23 | UZB706 | - | May 23, 20:00 UTC | May 24, 17:45 UTC | 21h 45m |
| 2026-05-23 | UZB706 | - | May 23, 07:10 UTC | May 24, 06:40 UTC | 23h 30m |
| 2026-05-22 | UZB422 | DEL → TAS | May 22, 01:40 UTC | May 22, 02:20 UTC | 40m |
| 2026-05-21 | UZB421 | TAS → DEL | May 21, 08:35 UTC | May 21, 23:25 UTC | 14h 50m |
| 2026-05-21 | UZB423 | TAS → DEL | May 21, 05:40 UTC | May 21, 06:35 UTC | 55m |
| 2026-05-19 | UZB422 | DEL → TAS | May 19, 01:25 UTC | May 19, 02:05 UTC | 40m |
| 2026-05-18 | UZB424 | DEL → TAS | May 18, 08:35 UTC | May 18, 23:00 UTC | 14h 24m |
| 2026-05-17 | UZB423 | TAS → DEL | May 17, 21:30 UTC | May 18, 06:50 UTC | 9h 20m |
| 2026-05-17 | UZB271 | TAS → IST | May 17, 05:15 UTC | May 17, 18:35 UTC | 13h 21m |
| 2026-05-16 | UZB271 | TAS → IST | May 16, 20:35 UTC | May 17, 18:35 UTC | 22h 0m |
| 2026-05-16 | UZB271 | TAS → IST | May 16, 08:05 UTC | May 17, 06:40 UTC | 22h 35m |
| 2026-05-15 | UZB422 | DEL → TAS | May 15, 01:25 UTC | May 15, 02:10 UTC | 45m |
| 2026-05-14 | UZB421 | TAS → DEL | May 14, 09:10 UTC | May 14, 23:05 UTC | 13h 55m |
| 2026-05-14 | UZB423 | TAS → DEL | May 14, 05:50 UTC | May 14, 06:40 UTC | 50m |
| 2026-05-11 | UZB424 | DEL → TAS | May 11, 08:55 UTC | May 11, 21:05 UTC | 12h 10m |
| 2026-05-11 | UZB423 | TAS → DEL | May 11, 05:40 UTC | May 11, 07:00 UTC | 1h 20m |
| 2026-05-09 | UZB705 | - | May 9, 07:25 UTC | May 9, 21:14 UTC | 13h 50m |
| 2026-05-07 | UZB424 | DEL → TAS | May 7, 09:35 UTC | May 7, 10:20 UTC | 45m |
| 2026-05-07 | UZB423 | TAS → DEL | May 7, 05:50 UTC | May 7, 06:55 UTC | 1h 5m |
| 2026-05-05 | UZB422 | DEL → TAS | May 5, 01:30 UTC | May 5, 02:15 UTC | 45m |
| 2026-05-04 | UZB424 | DEL → TAS | May 4, 08:40 UTC | May 4, 22:55 UTC | 14h 16m |
| 2026-05-03 | UZB423 | TAS → DEL | May 3, 21:35 UTC | May 4, 06:20 UTC | 8h 45m |
| 2026-05-03 | UZB272 | IST → TAS | May 3, 10:05 UTC | May 3, 19:15 UTC | 9h 10m |
| 2026-05-02 | UZB271 | TAS → IST | May 2, 20:20 UTC | May 3, 07:10 UTC | 10h 49m |
| 2026-05-02 | UZB706 | - | May 2, 07:15 UTC | May 3, 06:45 UTC | 23h 29m |
| 2026-05-01 | UZB422 | DEL → TAS | May 1, 01:20 UTC | May 1, 02:05 UTC | 45m |
| 2026-04-30 | UZB424 | DEL → TAS | Apr 30, 08:50 UTC | Apr 30, 22:50 UTC | 14h 0m |
| 2026-04-29 | UZB423 | TAS → DEL | Apr 29, 16:55 UTC | Apr 30, 06:15 UTC | 13h 19m |
| 2026-04-29 | UZB423 | TAS → DEL | Apr 29, 09:45 UTC | Apr 30, 06:15 UTC | 20h 29m |
| 2026-04-29 | UZB423 | TAS → DEL | Apr 29, 07:05 UTC | Apr 29, 07:40 UTC | 35m |
| 2026-04-28 | UZB422 | DEL → TAS | Apr 28, 01:15 UTC | Apr 28, 01:50 UTC | 35m |
| 2026-04-27 | UZB421 | TAS → DEL | Apr 27, 07:25 UTC | Apr 27, 22:50 UTC | 15h 25m |
| 2026-04-26 | UZB426 | DEL → TAS | Apr 26, 20:10 UTC | Apr 27, 12:10 UTC | 16h 0m |
| 2026-04-26 | UZB425 | TAS → DEL | Apr 26, 16:20 UTC | Apr 26, 17:15 UTC | 55m |
| 2026-04-25 | UZB425 | TAS → DEL | Apr 25, 20:50 UTC | Apr 26, 17:15 UTC | 20h 25m |
| 2026-04-25 | UZB425 | TAS → DEL | Apr 25, 20:30 UTC | Apr 26, 17:15 UTC | 20h 45m |
| 2026-04-25 | UZB705 | - | Apr 25, 08:55 UTC | Apr 25, 21:00 UTC | 12h 5m |
| 2026-04-24 | UZB422 | DEL → TAS | Apr 24, 01:30 UTC | Apr 24, 02:05 UTC | 35m |
| 2026-04-23 | UZB421 | TAS → DEL | Apr 23, 22:20 UTC | Apr 23, 23:00 UTC | 40m |
| 2026-04-23 | UZB634 | LED → TAS | Apr 23, 10:25 UTC | Apr 23, 11:30 UTC | 1h 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-67007 page for operator, model, and routing details .