sensors Mode-S transponder

507C41

ICAO 24-bit transponder address · allocated to Uzbekistan

Currently assigned to UK-32018 · AIRBUS A-320

Hex
507C41
Octal
24076101
Decimal
5,274,689
Country
UZ
Tail
UK-32018
Type
A320
No current signal · last broadcast 4h ago
Flights observed
101
Distinct callsigns
20
Country
UZ
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S 507C41.

Country allocation

The ICAO 24-bit address 507C41 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
UZB301 - 15 2026-07-12
UZB710 - 12 2026-07-11
UZB302 - 10 2026-07-12
UZB281 Uzbekistan Airways 8 2026-06-09
UZB746 - 7 2026-07-14
UZB745 - 7 2026-07-14
UZB282 - 6 2026-06-15
UZB304 Uzbekistan Airways 5 2026-06-23
UZB303 Uzbekistan Airways 4 2026-06-23
UZB291 - 4 2026-07-09
UZB747 - 3 2026-06-17
UZB428 - 3 2026-06-19
UZB427 - 3 2026-06-22
UZB748 Uzbekistan Airways 2 2026-06-10
UZB709 - 2 2026-07-02
UZB645 Uzbekistan Airways 2 2026-06-24
UZB280 Uzbekistan Airways 2 2026-05-22
UZB279 Uzbekistan Airways 2 2026-05-22
UZB9684 - 1 2026-05-09
UZB3210 - 1 2026-07-06

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 UZB746 - Jul 14, 08:15 UTCJul 14, 08:40 UTC25m
2026-07-14 UZB745 - Jul 14, 05:35 UTCJul 14, 06:10 UTC35m
2026-07-12 UZB302 - Jul 12, 10:45 UTCJul 12, 12:55 UTC2h 10m
2026-07-12 UZB301 - Jul 12, 05:35 UTCJul 12, 08:20 UTC2h 45m
2026-07-11 UZB710 - Jul 11, 18:40 UTCJul 11, 18:50 UTC10m
2026-07-09 UZB291 - Jul 9, 04:55 UTCJul 9, 10:25 UTC5h 30m
2026-07-07 UZB746 - Jul 7, 08:15 UTCJul 7, 08:45 UTC30m
2026-07-07 UZB745 - Jul 7, 05:35 UTCJul 7, 06:05 UTC30m
2026-07-06 UZB3210 - Jul 6, 18:20 UTCJul 6, 18:35 UTC15m
2026-07-05 UZB302 - Jul 5, 10:35 UTCJul 5, 12:45 UTC2h 10m
2026-07-05 UZB301 - Jul 5, 05:55 UTCJul 5, 08:40 UTC2h 45m
2026-07-04 UZB710 - Jul 4, 18:35 UTCJul 4, 18:45 UTC10m
2026-07-03 UZB746 - Jul 3, 08:10 UTCJul 3, 08:35 UTC25m
2026-07-03 UZB745 - Jul 3, 05:35 UTCJul 3, 06:00 UTC25m
2026-07-02 UZB710 - Jul 2, 11:05 UTCJul 2, 11:25 UTC20m
2026-07-02 UZB709 - Jul 2, 09:10 UTCJul 2, 09:20 UTC10m
2026-06-30 UZB746 - Jun 30, 08:00 UTCJun 30, 08:25 UTC25m
2026-06-30 UZB745 - Jun 30, 05:55 UTCJun 30, 06:25 UTC30m
2026-06-29 UZB710 - Jun 29, 11:04 UTCJun 29, 11:14 UTC10m
2026-06-29 UZB709 - Jun 29, 08:54 UTCJun 29, 09:05 UTC10m
2026-06-28 UZB302 - Jun 28, 10:55 UTCJun 28, 13:10 UTC2h 15m
2026-06-28 UZB301 - Jun 28, 05:49 UTCJun 28, 08:29 UTC2h 40m
2026-06-26 UZB746 - Jun 26, 08:10 UTCJun 26, 08:34 UTC25m
2026-06-26 UZB745 - Jun 26, 05:44 UTCJun 26, 06:15 UTC30m
2026-06-25 UZB710 - Jun 25, 10:59 UTCJun 25, 11:10 UTC10m
2026-06-24 UZB645 TAS → MRV Jun 24, 16:19 UTCJun 24, 16:34 UTC15m
2026-06-23 UZB645 TAS → MRV Jun 23, 20:19 UTCJun 24, 16:34 UTC20h 15m
2026-06-23 UZB304 TLV → TAS Jun 23, 18:20 UTCJun 24, 16:34 UTC22h 15m
2026-06-23 UZB304 TLV → TAS Jun 23, 17:54 UTCJun 23, 20:19 UTC2h 25m
2026-06-23 UZB303 TAS → TLV Jun 23, 00:24 UTCJun 23, 16:20 UTC15h 55m
2026-06-22 UZB427 - Jun 22, 20:24 UTCJun 22, 22:44 UTC2h 20m
2026-06-21 UZB302 TLV → TAS Jun 21, 10:49 UTCJun 21, 12:55 UTC2h 5m
2026-06-21 UZB301 - Jun 21, 05:44 UTCJun 21, 08:49 UTC3h 5m
2026-06-19 UZB428 - Jun 19, 01:04 UTCJun 19, 02:54 UTC1h 50m
2026-06-18 UZB302 TLV → TAS Jun 18, 10:35 UTCJun 18, 22:45 UTC12h 10m
2026-06-17 UZB301 - Jun 17, 16:55 UTCJun 18, 08:45 UTC15h 50m
2026-06-17 UZB301 - Jun 17, 10:20 UTCJun 18, 08:45 UTC22h 25m
2026-06-17 UZB747 - Jun 17, 07:45 UTCJun 17, 08:45 UTC1h 0m
2026-06-15 UZB282 - Jun 15, 03:15 UTCJun 15, 05:20 UTC2h 5m
2026-06-14 UZB302 TLV → TAS Jun 14, 10:35 UTCJun 15, 01:15 UTC14h 39m
2026-06-13 UZB301 TAS → TLV Jun 13, 16:55 UTCJun 14, 08:25 UTC15h 30m
2026-06-13 UZB301 TAS → TLV Jun 13, 10:20 UTCJun 14, 08:25 UTC22h 6m
2026-06-13 UZB301 TAS → TLV Jun 13, 09:10 UTCJun 14, 08:15 UTC23h 5m
2026-06-13 UZB291 - Jun 13, 04:45 UTCJun 13, 19:50 UTC15h 5m
2026-06-12 UZB291 - Jun 12, 12:20 UTCJun 13, 10:20 UTC21h 59m
2026-06-12 UZB291 - Jun 12, 12:10 UTCJun 13, 10:15 UTC22h 4m
2026-06-12 UZB211 - Jun 12, 08:45 UTCJun 12, 09:00 UTC15m
2026-06-11 UZB710 MSQ → TAS Jun 11, 11:10 UTCJun 11, 11:25 UTC15m
2026-06-10 UZB748 SIP → TAS Jun 10, 10:25 UTCJun 10, 20:40 UTC10h 15m
2026-06-10 UZB747 - Jun 10, 08:10 UTCJun 10, 09:00 UTC50m

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-32018 page for operator, model, and routing details .

Mode-S 507C41 frequently asked

What is Mode-S code 507C41?
507C41 is an ICAO 24-bit transponder address. Allocated to Uzbekistan. Assigned to UK-32018.
Where is Mode-S 507C41 registered?
Mode-S code 507C41 is allocated to Uzbekistan (UZ). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 507C41 broadcasting right now?
No active broadcast right now. Last signal was 4h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 507C41, octal 24076101, decimal 5,274,689.
What flights does 507C41 operate?
Mode-S 507C41 has broadcast 20 distinct callsigns, including UZB301, UZB710, UZB302, UZB281, UZB746.