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
- 186
- 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 |
| MFX557 | - | 11 | 2026-07-13 |
| MFX558 | - | 10 | 2026-07-14 |
| MFX456 | - | 9 | 2026-06-25 |
| MFX3068 | - | 9 | 2026-05-15 |
| MFX3064 | - | 9 | 2026-05-14 |
| MFX3174 | - | 7 | 2026-06-04 |
| MFX3165 | - | 7 | 2026-06-02 |
| MFX3058 | - | 7 | 2026-05-12 |
| MFX445 | - | 6 | 2026-07-10 |
| MFX351 | - | 6 | 2026-07-16 |
| MFX3169 | - | 6 | 2026-06-03 |
| MFX3074 | - | 6 | 2026-05-17 |
| MFX3052 | - | 6 | 2026-05-18 |
| MFX3185 | - | 5 | 2026-06-07 |
| MFX3070 | - | 5 | 2026-05-16 |
| MFX3056 | - | 5 | 2026-05-19 |
| MFX3179 | - | 4 | 2026-06-06 |
| MFX3062 | - | 4 | 2026-05-13 |
| MFX446 | - | 3 | 2026-07-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | MFX222 | - | Jul 17, 22:45 UTC | Jul 17, 23:14 UTC | 30m |
| 2026-07-17 | MFX221 | - | Jul 17, 20:44 UTC | Jul 17, 21:20 UTC | 35m |
| 2026-07-16 | MFX352 | - | Jul 16, 09:20 UTC | Jul 16, 11:30 UTC | 2h 10m |
| 2026-07-16 | MFX351 | - | Jul 16, 06:40 UTC | Jul 16, 07:10 UTC | 30m |
| 2026-07-14 | MFX558 | - | Jul 14, 06:45 UTC | Jul 14, 07:25 UTC | 40m |
| 2026-07-13 | MFX557 | - | Jul 13, 11:10 UTC | Jul 14, 04:20 UTC | 17h 10m |
| 2026-07-13 | MFX557 | - | Jul 13, 07:20 UTC | Jul 14, 04:20 UTC | 21h 0m |
| 2026-07-10 | MFX445 | - | Jul 10, 14:55 UTC | Jul 10, 19:05 UTC | 4h 10m |
| 2026-07-09 | MFX455 | - | Jul 9, 07:55 UTC | Jul 9, 14:00 UTC | 6h 5m |
| 2026-07-07 | MFX558 | - | Jul 7, 07:00 UTC | Jul 7, 17:50 UTC | 10h 50m |
| 2026-07-06 | MFX557 | - | Jul 6, 10:35 UTC | Jul 7, 04:30 UTC | 17h 55m |
| 2026-07-06 | MFX445 | - | Jul 6, 07:20 UTC | Jul 6, 07:45 UTC | 25m |
| 2026-07-03 | MFX446 | - | Jul 3, 14:45 UTC | Jul 3, 19:35 UTC | 4h 50m |
| 2026-07-02 | MFX352 | - | Jul 2, 10:10 UTC | Jul 2, 12:30 UTC | 2h 20m |
| 2026-07-02 | MFX351 | - | Jul 2, 04:55 UTC | Jul 2, 07:10 UTC | 2h 15m |
| 2026-06-28 | MFX417 | - | Jun 28, 06:10 UTC | Jun 28, 06:44 UTC | 35m |
| 2026-06-25 | MFX456 | - | Jun 25, 12:44 UTC | Jun 25, 14:09 UTC | 1h 25m |
| 2026-06-25 | MFX455 | - | Jun 25, 08:40 UTC | Jun 25, 09:25 UTC | 45m |
| 2026-06-24 | MFX374 | - | Jun 24, 06:35 UTC | Jun 24, 08:49 UTC | 2h 15m |
| 2026-06-24 | MFX373 | - | Jun 24, 01:19 UTC | Jun 24, 04:05 UTC | 2h 45m |
| 2026-06-19 | MFX445 | - | Jun 19, 15:19 UTC | Jun 19, 19:14 UTC | 3h 55m |
| 2026-06-18 | MFX558 | - | Jun 18, 06:55 UTC | Jun 18, 07:30 UTC | 35m |
| 2026-06-18 | MFX557 | - | Jun 18, 03:40 UTC | Jun 18, 04:25 UTC | 45m |
| 2026-06-15 | MFX453 | - | Jun 15, 19:35 UTC | Jun 15, 19:55 UTC | 20m |
| 2026-06-15 | MFX446 | - | Jun 15, 08:15 UTC | Jun 15, 12:25 UTC | 4h 10m |
| 2026-06-14 | MFX445 | - | Jun 14, 11:35 UTC | Jun 15, 08:45 UTC | 21h 9m |
| 2026-06-14 | MFX351 | TAS → DXB | Jun 14, 06:40 UTC | Jun 14, 06:50 UTC | 10m |
| 2026-06-11 | MFX418 | DME → UGC | Jun 11, 09:35 UTC | Jun 11, 09:45 UTC | 10m |
| 2026-06-10 | MFX461 | - | Jun 10, 09:00 UTC | Jun 10, 16:40 UTC | 7h 40m |
| 2026-06-07 | MFX3185 | - | Jun 7, 19:20 UTC | Jun 8, 13:35 UTC | 18h 15m |
| 2026-06-07 | MFX3185 | - | Jun 7, 17:20 UTC | Jun 8, 13:35 UTC | 20h 15m |
| 2026-06-07 | MFX3185 | - | Jun 7, 11:35 UTC | Jun 8, 11:15 UTC | 23h 40m |
| 2026-06-07 | MFX3185 | - | Jun 7, 09:30 UTC | Jun 8, 05:20 UTC | 19h 50m |
| 2026-06-07 | MFX3185 | - | Jun 7, 05:20 UTC | Jun 8, 05:15 UTC | 23h 55m |
| 2026-06-07 | MFX3184 | - | Jun 7, 03:45 UTC | Jun 8, 03:15 UTC | 23h 30m |
| 2026-06-06 | MFX3182 | - | Jun 6, 20:25 UTC | Jun 7, 19:15 UTC | 22h 50m |
| 2026-06-06 | MFX3182 | - | Jun 6, 17:19 UTC | Jun 7, 17:15 UTC | 23h 55m |
| 2026-06-06 | MFX3180 | - | Jun 6, 15:19 UTC | Jun 7, 11:45 UTC | 20h 25m |
| 2026-06-06 | MFX3180 | - | Jun 6, 07:20 UTC | Jun 7, 06:00 UTC | 22h 40m |
| 2026-06-06 | MFX3179 | - | Jun 6, 06:45 UTC | Jun 7, 05:15 UTC | 22h 30m |
| 2026-06-06 | MFX3179 | - | Jun 6, 01:35 UTC | Jun 6, 20:49 UTC | 19h 15m |
| 2026-06-05 | MFX3179 | - | Jun 5, 13:20 UTC | Jun 6, 09:09 UTC | 19h 50m |
| 2026-06-05 | MFX3179 | - | Jun 5, 11:40 UTC | Jun 6, 09:09 UTC | 21h 30m |
| 2026-06-05 | MFX3178 | - | Jun 5, 06:05 UTC | Jun 6, 03:35 UTC | 21h 30m |
| 2026-06-05 | MFX3175 | - | Jun 5, 04:10 UTC | Jun 6, 03:15 UTC | 23h 5m |
| 2026-06-04 | MFX3174 | - | Jun 4, 22:30 UTC | Jun 5, 13:45 UTC | 15h 15m |
| 2026-06-04 | MFX3174 | - | Jun 4, 15:20 UTC | Jun 5, 13:45 UTC | 22h 25m |
| 2026-06-04 | MFX3174 | - | Jun 4, 14:40 UTC | Jun 5, 13:15 UTC | 22h 35m |
| 2026-06-04 | MFX3174 | - | Jun 4, 11:20 UTC | Jun 5, 06:15 UTC | 18h 55m |
| 2026-06-04 | MFX3174 | - | Jun 4, 10:40 UTC | Jun 5, 06:15 UTC | 19h 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 UK32071 page for operator, model, and routing details .