sensors Mode-S transponder
507C85
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK32071 · AIRBUS A-320
- Hex
- 507C85
- Octal
- 24076205
- Decimal
- 5,274,757
- Country
- UZ
- Tail
- UK32071
- Type
- A320
- Flights observed
- 121
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 507C85 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 |
|---|---|---|---|
| MFX3050 | - | 12 | 2026-05-18 |
| MFX3068 | - | 9 | 2026-05-15 |
| MFX3064 | - | 9 | 2026-05-14 |
| MFX456 | - | 8 | 2026-05-03 |
| MFX558 | - | 7 | 2026-05-29 |
| MFX557 | My Freighter LLC | 7 | 2026-05-29 |
| MFX3058 | - | 7 | 2026-05-12 |
| MFX3074 | - | 6 | 2026-05-17 |
| MFX3052 | - | 6 | 2026-05-18 |
| MFX3070 | - | 5 | 2026-05-16 |
| MFX3056 | - | 5 | 2026-05-19 |
| MFX3165 | - | 4 | 2026-06-01 |
| MFX3062 | - | 4 | 2026-05-13 |
| MFX351 | My Freighter LLC | 3 | 2026-05-25 |
| MFX3162 | - | 3 | 2026-06-01 |
| MFX3075 | - | 3 | 2026-05-17 |
| MFX449 | - | 2 | 2026-05-08 |
| MFX445 | - | 2 | 2026-04-17 |
| MFX409 | - | 2 | 2026-04-29 |
| MFX3072 | - | 2 | 2026-05-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | MFX3165 | - | Jun 1, 22:40 UTC | Jun 2, 19:20 UTC | 20h 40m |
| 2026-06-01 | MFX3165 | - | Jun 1, 20:20 UTC | Jun 2, 19:15 UTC | 22h 55m |
| 2026-06-01 | MFX3165 | - | Jun 1, 16:20 UTC | Jun 2, 11:40 UTC | 19h 20m |
| 2026-06-01 | MFX3165 | - | Jun 1, 14:45 UTC | Jun 2, 11:40 UTC | 20h 55m |
| 2026-06-01 | MFX3162 | - | Jun 1, 09:30 UTC | Jun 2, 09:15 UTC | 23h 45m |
| 2026-06-01 | MFX3162 | - | Jun 1, 09:15 UTC | Jun 2, 06:25 UTC | 21h 10m |
| 2026-06-01 | MFX3162 | - | Jun 1, 06:50 UTC | Jun 1, 22:40 UTC | 15h 50m |
| 2026-05-29 | MFX558 | - | May 29, 07:05 UTC | May 29, 07:55 UTC | 50m |
| 2026-05-29 | MFX557 | TAS → DEL | May 29, 03:45 UTC | May 29, 04:30 UTC | 45m |
| 2026-05-26 | MFX372 | - | May 26, 21:14 UTC | May 26, 23:39 UTC | 2h 25m |
| 2026-05-26 | MFX371 | - | May 26, 17:04 UTC | May 26, 19:40 UTC | 2h 35m |
| 2026-05-25 | MFX351 | TAS → DXB | May 25, 04:30 UTC | May 25, 11:35 UTC | 7h 5m |
| 2026-05-23 | MFX316 | IST → FEG | May 23, 15:15 UTC | May 23, 16:25 UTC | 1h 10m |
| 2026-05-23 | MFX315 | FEG → IST | May 23, 11:20 UTC | May 23, 11:35 UTC | 15m |
| 2026-05-22 | MFX226 | - | May 22, 20:20 UTC | May 22, 21:10 UTC | 50m |
| 2026-05-22 | MFX225 | - | May 22, 04:25 UTC | May 22, 19:10 UTC | 14h 45m |
| 2026-05-19 | MFX3056 | - | May 19, 23:05 UTC | May 20, 16:35 UTC | 17h 31m |
| 2026-05-18 | MFX3052 | - | May 18, 23:20 UTC | May 19, 23:15 UTC | 23h 55m |
| 2026-05-18 | MFX3050 | - | May 18, 06:55 UTC | May 18, 23:40 UTC | 16h 44m |
| 2026-05-18 | MFX3050 | - | May 18, 01:45 UTC | May 18, 23:40 UTC | 21h 54m |
| 2026-05-18 | MFX3050 | - | May 18, 00:40 UTC | May 18, 21:15 UTC | 20h 34m |
| 2026-05-17 | MFX3050 | - | May 17, 19:50 UTC | May 18, 16:15 UTC | 20h 25m |
| 2026-05-17 | MFX3050 | - | May 17, 18:01 UTC | May 18, 16:15 UTC | 22h 15m |
| 2026-05-17 | MFX3050 | - | May 17, 13:20 UTC | May 18, 13:15 UTC | 23h 55m |
| 2026-05-17 | MFX3050 | - | May 17, 11:20 UTC | May 18, 10:15 UTC | 22h 55m |
| 2026-05-17 | MFX3075 | - | May 17, 10:45 UTC | May 18, 09:05 UTC | 22h 20m |
| 2026-05-17 | MFX3075 | - | May 17, 07:20 UTC | May 18, 07:15 UTC | 23h 55m |
| 2026-05-17 | MFX3075 | - | May 17, 05:20 UTC | May 18, 03:05 UTC | 21h 45m |
| 2026-05-17 | MFX3074 | - | May 17, 03:55 UTC | May 18, 03:05 UTC | 23h 10m |
| 2026-05-16 | MFX3074 | - | May 16, 23:20 UTC | May 17, 20:45 UTC | 21h 25m |
| 2026-05-16 | MFX3074 | - | May 16, 21:20 UTC | May 17, 20:45 UTC | 23h 25m |
| 2026-05-16 | MFX3074 | - | May 16, 17:20 UTC | May 17, 13:45 UTC | 20h 25m |
| 2026-05-16 | MFX3074 | - | May 16, 15:20 UTC | May 17, 13:45 UTC | 22h 25m |
| 2026-05-16 | MFX3074 | - | May 16, 09:21 UTC | May 17, 07:30 UTC | 22h 10m |
| 2026-05-16 | MFX3072 | - | May 16, 07:41 UTC | May 17, 07:15 UTC | 23h 35m |
| 2026-05-16 | MFX3072 | - | May 16, 04:00 UTC | May 16, 23:55 UTC | 19h 56m |
| 2026-05-16 | MFX3070 | - | May 16, 01:30 UTC | May 16, 23:55 UTC | 22h 26m |
| 2026-05-15 | MFX3070 | - | May 15, 21:20 UTC | May 16, 18:30 UTC | 21h 11m |
| 2026-05-15 | MFX3070 | - | May 15, 20:50 UTC | May 16, 18:30 UTC | 21h 41m |
| 2026-05-15 | MFX3070 | - | May 15, 15:20 UTC | May 16, 15:16 UTC | 23h 56m |
| 2026-05-15 | MFX3070 | - | May 15, 13:50 UTC | May 16, 10:25 UTC | 20h 35m |
| 2026-05-15 | MFX3068 | - | May 15, 11:35 UTC | May 16, 10:25 UTC | 22h 50m |
| 2026-05-15 | MFX3068 | - | May 15, 07:20 UTC | May 16, 05:15 UTC | 21h 54m |
| 2026-05-15 | MFX3068 | - | May 15, 06:15 UTC | May 16, 05:15 UTC | 22h 59m |
| 2026-05-15 | MFX3068 | - | May 15, 04:40 UTC | May 16, 03:15 UTC | 22h 34m |
| 2026-05-15 | MFX3068 | - | May 15, 01:20 UTC | May 15, 21:55 UTC | 20h 34m |
| 2026-05-14 | MFX3068 | - | May 14, 23:20 UTC | May 15, 21:55 UTC | 22h 34m |
| 2026-05-14 | MFX3068 | - | May 14, 22:35 UTC | May 15, 21:15 UTC | 22h 39m |
| 2026-05-14 | MFX3068 | - | May 14, 17:35 UTC | May 15, 15:20 UTC | 21h 44m |
| 2026-05-14 | MFX3068 | - | May 14, 15:45 UTC | May 15, 15:15 UTC | 23h 29m |
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 UK32071 page for operator, model, and routing details .