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
- 128
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 2h 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UZB706 | - | 21 | 2026-07-11 |
| UZB423 | - | 16 | 2026-06-28 |
| UZB425 | Uzbekistan Airways | 13 | 2026-07-12 |
| UZB422 | - | 12 | 2026-06-26 |
| UZB705 | - | 11 | 2026-07-11 |
| UZB424 | - | 10 | 2026-06-29 |
| UZB421 | - | 10 | 2026-06-25 |
| UZB426 | - | 5 | 2026-07-12 |
| UZB271 | - | 5 | 2026-07-14 |
| UZB338 | - | 4 | 2026-07-02 |
| UZB337 | - | 3 | 2026-04-18 |
| UZB746 | Uzbekistan Airways | 2 | 2026-06-12 |
| UZB745 | Uzbekistan Airways | 2 | 2026-06-11 |
| UZB613 | Uzbekistan Airways | 2 | 2026-06-08 |
| UZB604 | Uzbekistan Airways | 2 | 2026-06-11 |
| UZB601 | Uzbekistan Airways | 2 | 2026-06-30 |
| UZB708 | - | 1 | 2026-04-12 |
| UZB634 | Uzbekistan Airways | 1 | 2026-04-23 |
| UZB603 | Uzbekistan Airways | 1 | 2026-04-21 |
| UZB3510 | - | 1 | 2026-07-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | UZB271 | - | Jul 14, 05:05 UTC | Jul 14, 07:35 UTC | 2h 30m |
| 2026-07-12 | UZB426 | - | Jul 12, 19:10 UTC | Jul 12, 19:45 UTC | 35m |
| 2026-07-12 | UZB425 | TAS → DEL | Jul 12, 16:01 UTC | Jul 12, 16:55 UTC | 55m |
| 2026-07-11 | UZB706 | - | Jul 11, 20:40 UTC | Jul 12, 16:55 UTC | 20h 15m |
| 2026-07-11 | UZB705 | - | Jul 11, 07:15 UTC | Jul 11, 21:55 UTC | 14h 40m |
| 2026-07-05 | UZB426 | - | Jul 5, 19:05 UTC | Jul 5, 19:45 UTC | 40m |
| 2026-07-05 | UZB425 | TAS → DEL | Jul 5, 16:15 UTC | Jul 5, 16:55 UTC | 40m |
| 2026-07-04 | UZB425 | TAS → DEL | Jul 4, 20:50 UTC | Jul 5, 16:55 UTC | 20h 5m |
| 2026-07-04 | UZB706 | - | Jul 4, 19:40 UTC | Jul 5, 16:55 UTC | 21h 15m |
| 2026-07-04 | UZB706 | - | Jul 4, 07:20 UTC | Jul 4, 21:20 UTC | 14h 0m |
| 2026-07-03 | UZB3510 | - | Jul 3, 14:10 UTC | Jul 4, 08:25 UTC | 18h 15m |
| 2026-07-03 | UZB3509 | - | Jul 3, 10:25 UTC | Jul 3, 11:00 UTC | 35m |
| 2026-07-02 | UZB338 | - | Jul 2, 10:50 UTC | Jul 3, 10:45 UTC | 23h 55m |
| 2026-07-02 | UZB338 | - | Jul 2, 10:40 UTC | Jul 2, 11:40 UTC | 1h 0m |
| 2026-06-30 | UZB601 | TAS → DME | Jun 30, 18:00 UTC | Jun 30, 18:45 UTC | 45m |
| 2026-06-29 | UZB424 | - | Jun 29, 08:50 UTC | Jun 29, 09:25 UTC | 35m |
| 2026-06-28 | UZB423 | - | Jun 28, 19:09 UTC | Jun 29, 06:29 UTC | 11h 20m |
| 2026-06-28 | UZB425 | TAS → DEL | Jun 28, 16:25 UTC | Jun 28, 17:00 UTC | 35m |
| 2026-06-27 | UZB706 | - | Jun 27, 07:10 UTC | Jun 27, 20:59 UTC | 13h 50m |
| 2026-06-26 | UZB705 | - | Jun 26, 16:09 UTC | Jun 27, 08:20 UTC | 16h 10m |
| 2026-06-26 | UZB422 | - | Jun 26, 01:45 UTC | Jun 26, 16:30 UTC | 14h 45m |
| 2026-06-25 | UZB421 | - | Jun 25, 22:59 UTC | Jun 25, 23:09 UTC | 10m |
| 2026-06-25 | UZB338 | - | Jun 25, 02:19 UTC | Jun 25, 13:24 UTC | 11h 5m |
| 2026-06-22 | UZB282 | - | Jun 22, 03:19 UTC | Jun 22, 05:15 UTC | 1h 55m |
| 2026-06-21 | UZB281 | - | Jun 21, 22:54 UTC | Jun 22, 01:25 UTC | 2h 30m |
| 2026-06-20 | UZB705 | - | Jun 20, 07:09 UTC | Jun 20, 20:45 UTC | 13h 35m |
| 2026-06-18 | UZB601 | TAS → DME | Jun 18, 17:21 UTC | Jun 19, 05:59 UTC | 12h 38m |
| 2026-06-17 | UZB424 | - | Jun 17, 08:55 UTC | Jun 17, 16:40 UTC | 7h 45m |
| 2026-06-17 | UZB423 | - | Jun 17, 05:45 UTC | Jun 17, 06:35 UTC | 50m |
| 2026-06-15 | UZB424 | DEL → TAS | Jun 15, 08:29 UTC | Jun 15, 16:24 UTC | 7h 55m |
| 2026-06-14 | UZB423 | - | Jun 14, 22:25 UTC | Jun 15, 06:20 UTC | 7h 55m |
| 2026-06-14 | UZB425 | TAS → DEL | Jun 14, 06:45 UTC | Jun 14, 20:30 UTC | 13h 45m |
| 2026-06-13 | UZB706 | - | Jun 13, 23:00 UTC | Jun 14, 20:30 UTC | 21h 30m |
| 2026-06-13 | UZB706 | - | Jun 13, 10:50 UTC | Jun 14, 07:05 UTC | 20h 15m |
| 2026-06-13 | UZB706 | - | Jun 13, 10:35 UTC | Jun 14, 07:05 UTC | 20h 30m |
| 2026-06-12 | UZB746 | TBS → TAS | Jun 12, 08:10 UTC | Jun 12, 08:35 UTC | 25m |
| 2026-06-11 | UZB745 | TAS → TBS | Jun 11, 10:50 UTC | Jun 12, 06:20 UTC | 19h 31m |
| 2026-06-11 | UZB604 | DME → TAS | Jun 11, 09:40 UTC | Jun 12, 06:20 UTC | 20h 41m |
| 2026-06-10 | UZB706 | - | Jun 10, 20:50 UTC | Jun 11, 06:10 UTC | 9h 20m |
| 2026-06-10 | UZB706 | - | Jun 10, 07:35 UTC | Jun 11, 06:10 UTC | 22h 35m |
| 2026-06-09 | UZB705 | - | Jun 9, 17:30 UTC | Jun 10, 08:45 UTC | 15h 15m |
| 2026-06-09 | UZB604 | DME → TAS | Jun 9, 09:10 UTC | Jun 9, 09:20 UTC | 10m |
| 2026-06-08 | UZB613 | TAS → VKO | Jun 8, 15:40 UTC | Jun 9, 06:00 UTC | 14h 20m |
| 2026-06-08 | UZB424 | DEL → TAS | Jun 8, 08:50 UTC | Jun 9, 06:00 UTC | 21h 10m |
| 2026-06-08 | UZB424 | DEL → TAS | Jun 8, 08:35 UTC | Jun 9, 06:00 UTC | 21h 25m |
| 2026-06-07 | UZB426 | DEL → TAS | Jun 7, 19:15 UTC | Jun 8, 06:20 UTC | 11h 5m |
| 2026-06-06 | UZB425 | TAS → DEL | Jun 6, 22:50 UTC | Jun 7, 16:55 UTC | 18h 5m |
| 2026-06-06 | UZB706 | - | Jun 6, 21:35 UTC | Jun 7, 16:55 UTC | 19h 20m |
| 2026-06-06 | UZB706 | - | Jun 6, 09:55 UTC | Jun 6, 23:00 UTC | 13h 5m |
| 2026-06-05 | UZB705 | - | Jun 5, 16:00 UTC | Jun 6, 11:05 UTC | 19h 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 .