sensors Mode-S transponder
507CBA
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK32076 · AIRBUS A-320
- Hex
- 507CBA
- Octal
- 24076272
- Decimal
- 5,274,810
- Country
- UZ
- Tail
- UK32076
- Type
- A320
- Flights observed
- 111
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 507CBA 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 |
|---|---|---|---|
| MFX3134 | - | 9 | 2026-05-15 |
| MFX3138 | - | 8 | 2026-05-17 |
| MFX3154 | - | 7 | 2026-05-19 |
| MFX351 | My Freighter LLC | 6 | 2026-05-27 |
| MFX3156 | - | 6 | 2026-05-20 |
| MFX3147 | - | 6 | 2026-05-17 |
| MFX3130 | - | 6 | 2026-05-14 |
| MFX418 | My Freighter LLC | 5 | 2026-05-28 |
| MFX374 | - | 4 | 2026-05-24 |
| MFX3060 | - | 4 | 2026-05-21 |
| MFX221 | - | 4 | 2026-04-24 |
| MFX417 | My Freighter LLC | 3 | 2026-05-28 |
| MFX373 | - | 3 | 2026-05-24 |
| MFX316 | My Freighter LLC | 3 | 2026-04-28 |
| MFX557 | My Freighter LLC | 2 | 2026-05-25 |
| MFX461 | - | 2 | 2026-04-15 |
| MFX449 | - | 2 | 2026-04-25 |
| MFX410 | My Freighter LLC | 2 | 2026-04-26 |
| MFX409 | - | 2 | 2026-05-24 |
| MFX3150 | - | 2 | 2026-05-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | MFX226 | - | May 29, 20:45 UTC | May 29, 21:35 UTC | 50m |
| 2026-05-29 | MFX225 | - | May 29, 04:35 UTC | May 29, 19:40 UTC | 15h 5m |
| 2026-05-28 | MFX418 | DME → UGC | May 28, 09:25 UTC | May 28, 09:50 UTC | 25m |
| 2026-05-28 | MFX417 | UGC → DME | May 28, 06:20 UTC | May 28, 06:50 UTC | 30m |
| 2026-05-27 | MFX417 | UGC → DME | May 27, 11:25 UTC | May 28, 06:50 UTC | 19h 25m |
| 2026-05-27 | MFX351 | TAS → DXB | May 27, 07:00 UTC | May 27, 07:10 UTC | 10m |
| 2026-05-27 | MFX351 | TAS → DXB | May 27, 04:39 UTC | May 27, 04:49 UTC | 10m |
| 2026-05-26 | MFX558 | - | May 26, 07:10 UTC | May 27, 04:49 UTC | 21h 40m |
| 2026-05-25 | MFX557 | TAS → DEL | May 25, 11:00 UTC | May 26, 04:20 UTC | 17h 19m |
| 2026-05-25 | MFX557 | TAS → DEL | May 25, 07:35 UTC | May 26, 04:20 UTC | 20h 44m |
| 2026-05-24 | MFX409 | - | May 24, 16:50 UTC | May 25, 11:35 UTC | 18h 45m |
| 2026-05-24 | MFX409 | - | May 24, 10:35 UTC | May 25, 08:10 UTC | 21h 35m |
| 2026-05-24 | MFX374 | - | May 24, 08:35 UTC | May 25, 08:10 UTC | 23h 35m |
| 2026-05-24 | MFX373 | - | May 24, 03:50 UTC | May 24, 06:40 UTC | 2h 50m |
| 2026-05-22 | MFX404 | SVO → TAS | May 22, 22:20 UTC | May 22, 22:30 UTC | 10m |
| 2026-05-21 | MFX3060 | - | May 21, 04:30 UTC | May 21, 20:50 UTC | 16h 20m |
| 2026-05-21 | MFX3060 | - | May 21, 00:35 UTC | May 21, 20:50 UTC | 20h 15m |
| 2026-05-20 | MFX3060 | - | May 20, 22:35 UTC | May 21, 20:50 UTC | 22h 15m |
| 2026-05-20 | MFX3060 | - | May 20, 22:15 UTC | May 21, 18:30 UTC | 20h 15m |
| 2026-05-20 | MFX3156 | - | May 20, 10:50 UTC | May 21, 07:35 UTC | 20h 45m |
| 2026-05-20 | MFX3156 | - | May 20, 06:35 UTC | May 21, 06:05 UTC | 23h 30m |
| 2026-05-20 | MFX3156 | - | May 20, 04:45 UTC | May 21, 04:30 UTC | 23h 45m |
| 2026-05-20 | MFX3156 | - | May 20, 04:00 UTC | May 21, 01:00 UTC | 21h 1m |
| 2026-05-20 | MFX3156 | - | May 20, 00:35 UTC | May 21, 00:30 UTC | 23h 56m |
| 2026-05-19 | MFX3156 | - | May 19, 22:35 UTC | May 20, 22:30 UTC | 23h 56m |
| 2026-05-19 | MFX3154 | - | May 19, 18:35 UTC | May 20, 14:30 UTC | 19h 56m |
| 2026-05-19 | MFX3154 | - | May 19, 16:35 UTC | May 20, 14:30 UTC | 21h 56m |
| 2026-05-19 | MFX3154 | - | May 19, 15:25 UTC | May 20, 14:30 UTC | 23h 6m |
| 2026-05-19 | MFX3154 | - | May 19, 10:55 UTC | May 20, 07:00 UTC | 20h 6m |
| 2026-05-19 | MFX3154 | - | May 19, 09:15 UTC | May 20, 07:00 UTC | 21h 46m |
| 2026-05-19 | MFX3154 | - | May 19, 04:35 UTC | May 20, 04:30 UTC | 23h 55m |
| 2026-05-19 | MFX3154 | - | May 19, 03:25 UTC | May 20, 01:40 UTC | 22h 15m |
| 2026-05-19 | MFX3153 | - | May 19, 01:45 UTC | May 20, 00:30 UTC | 22h 45m |
| 2026-05-18 | MFX3150 | - | May 18, 04:40 UTC | May 18, 23:00 UTC | 18h 19m |
| 2026-05-18 | MFX3150 | - | May 18, 02:35 UTC | May 18, 23:00 UTC | 20h 24m |
| 2026-05-17 | MFX3149 | - | May 17, 20:35 UTC | May 18, 20:30 UTC | 23h 54m |
| 2026-05-17 | MFX3147 | - | May 17, 18:35 UTC | May 18, 15:55 UTC | 21h 20m |
| 2026-05-17 | MFX3147 | - | May 17, 16:35 UTC | May 18, 15:55 UTC | 23h 20m |
| 2026-05-17 | MFX3147 | - | May 17, 14:35 UTC | May 18, 14:30 UTC | 23h 55m |
| 2026-05-17 | MFX3147 | - | May 17, 13:45 UTC | May 18, 05:35 UTC | 15h 50m |
| 2026-05-17 | MFX3147 | - | May 17, 06:35 UTC | May 18, 05:35 UTC | 23h 0m |
| 2026-05-17 | MFX3147 | - | May 17, 02:45 UTC | May 17, 22:01 UTC | 19h 15m |
| 2026-05-17 | MFX3138 | - | May 17, 00:55 UTC | May 17, 22:01 UTC | 21h 5m |
| 2026-05-16 | MFX3138 | - | May 16, 18:35 UTC | May 17, 16:40 UTC | 22h 5m |
| 2026-05-16 | MFX3138 | - | May 16, 18:05 UTC | May 17, 16:30 UTC | 22h 25m |
| 2026-05-16 | MFX3138 | - | May 16, 14:41 UTC | May 17, 14:30 UTC | 23h 50m |
| 2026-05-16 | MFX3138 | - | May 16, 12:35 UTC | May 17, 09:35 UTC | 21h 0m |
| 2026-05-16 | MFX3138 | - | May 16, 12:11 UTC | May 17, 09:35 UTC | 21h 25m |
| 2026-05-16 | MFX3138 | - | May 16, 06:50 UTC | May 17, 06:30 UTC | 23h 40m |
| 2026-05-16 | MFX3138 | - | May 16, 05:15 UTC | May 17, 04:10 UTC | 22h 55m |
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 UK32076 page for operator, model, and routing details .