sensors Mode-S transponder
507CAC
ICAO 24-bit transponder address · allocated to Uzbekistan
Currently assigned to UK33031 · AIRBUS A-330-300
- Hex
- 507CAC
- Octal
- 24076254
- Decimal
- 5,274,796
- Country
- UZ
- Tail
- UK33031
- Type
- A333
- Flights observed
- 45
- Distinct callsigns
- 20
- Country
- UZ
- Last broadcast
- 18m ago
Current position
Country allocation
The ICAO 24-bit address 507CAC 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 |
|---|---|---|---|
| FAD6105 | - | 5 | 2026-05-03 |
| FAD6102 | - | 4 | 2026-05-04 |
| FAD6346 | - | 3 | 2026-05-05 |
| MFX3029 | - | 2 | 2026-04-15 |
| MFX3016 | - | 2 | 2026-04-15 |
| MFX3015 | - | 2 | 2026-04-15 |
| FAD6360 | - | 2 | 2026-05-10 |
| FAD6027 | - | 2 | 2026-05-17 |
| FAD6024 | - | 2 | 2026-05-16 |
| MFX3312 | - | 1 | 2026-04-14 |
| MFX325 | - | 1 | 2026-04-12 |
| MFX322 | - | 1 | 2026-04-13 |
| MFX3030 | - | 1 | 2026-04-16 |
| FAD7401 | - | 1 | 2026-06-01 |
| FAD7400 | Rog-Air | 1 | 2026-06-01 |
| FAD7302 | - | 1 | 2026-06-02 |
| FAD6354 | - | 1 | 2026-05-08 |
| FAD6350 | - | 1 | 2026-05-06 |
| FAD6243 | - | 1 | 2026-05-18 |
| FAD6138 | - | 1 | 2026-05-15 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | FAD7302 | - | Jun 2, 21:00 UTC | Jun 2, 23:00 UTC | 2h 0m |
| 2026-06-01 | - | - | Jun 1, 20:45 UTC | Jun 1, 21:00 UTC | 15m |
| 2026-06-01 | FAD7401 | - | Jun 1, 09:30 UTC | Jun 1, 17:45 UTC | 8h 15m |
| 2026-06-01 | FAD7400 | JED → YEI | Jun 1, 05:30 UTC | Jun 1, 07:20 UTC | 1h 50m |
| 2026-05-21 | FAD6007 | - | May 21, 20:00 UTC | May 21, 22:30 UTC | 2h 30m |
| 2026-05-21 | FAD6006 | - | May 21, 08:30 UTC | May 21, 11:25 UTC | 2h 55m |
| 2026-05-20 | FAD6017 | SVO → SVO | May 20, 18:50 UTC | May 20, 19:45 UTC | 55m |
| 2026-05-19 | FAD6016 | - | May 19, 20:00 UTC | May 20, 13:20 UTC | 17h 21m |
| 2026-05-18 | FAD6243 | - | May 18, 11:05 UTC | May 18, 18:40 UTC | 7h 34m |
| 2026-05-17 | FAD6027 | - | May 17, 21:35 UTC | May 18, 18:40 UTC | 21h 4m |
| 2026-05-17 | FAD6027 | - | May 17, 14:35 UTC | May 18, 11:05 UTC | 20h 30m |
| 2026-05-17 | FAD6025 | - | May 17, 03:05 UTC | May 17, 21:40 UTC | 18h 35m |
| 2026-05-16 | FAD6024 | - | May 16, 17:40 UTC | May 17, 14:35 UTC | 20h 55m |
| 2026-05-15 | FAD6024 | - | May 15, 21:05 UTC | May 16, 20:30 UTC | 23h 26m |
| 2026-05-15 | FAD6138 | - | May 15, 08:40 UTC | May 15, 21:10 UTC | 12h 29m |
| 2026-05-11 | FAD6130 | - | May 11, 04:45 UTC | May 11, 19:00 UTC | 14h 16m |
| 2026-05-10 | FAD6360 | - | May 10, 12:05 UTC | May 11, 07:25 UTC | 19h 20m |
| 2026-05-09 | FAD6360 | - | May 9, 20:00 UTC | May 10, 12:30 UTC | 16h 30m |
| 2026-05-08 | FAD6354 | - | May 8, 09:04 UTC | May 8, 09:25 UTC | 20m |
| 2026-05-06 | FAD6350 | - | May 6, 20:30 UTC | May 6, 20:55 UTC | 25m |
| 2026-05-05 | FAD6346 | - | May 5, 16:06 UTC | May 5, 19:20 UTC | 3h 15m |
| 2026-05-04 | FAD6346 | - | May 4, 23:05 UTC | May 5, 19:20 UTC | 20h 15m |
| 2026-05-04 | FAD6346 | - | May 4, 21:05 UTC | May 5, 19:20 UTC | 22h 15m |
| 2026-05-04 | FAD6102 | - | May 4, 11:25 UTC | May 4, 23:15 UTC | 11h 51m |
| 2026-05-04 | FAD6102 | - | May 4, 03:40 UTC | May 4, 23:15 UTC | 19h 36m |
| 2026-05-03 | FAD6102 | - | May 3, 18:40 UTC | May 4, 14:15 UTC | 19h 35m |
| 2026-05-03 | FAD6102 | - | May 3, 16:00 UTC | May 4, 14:15 UTC | 22h 15m |
| 2026-05-03 | FAD6106 | - | May 3, 09:25 UTC | May 4, 04:50 UTC | 19h 25m |
| 2026-05-03 | FAD6105 | - | May 3, 08:35 UTC | May 4, 04:50 UTC | 20h 15m |
| 2026-05-03 | FAD6105 | - | May 3, 06:45 UTC | May 4, 04:50 UTC | 22h 5m |
| 2026-05-02 | FAD6105 | - | May 2, 21:30 UTC | May 3, 18:45 UTC | 21h 14m |
| 2026-05-02 | FAD6105 | - | May 2, 15:05 UTC | May 3, 09:50 UTC | 18h 44m |
| 2026-05-02 | FAD6105 | - | May 2, 13:55 UTC | May 3, 09:50 UTC | 19h 54m |
| 2026-05-02 | FAD6117 | - | May 2, 11:55 UTC | May 3, 09:50 UTC | 21h 54m |
| 2026-05-02 | FAD6116 | - | May 2, 03:05 UTC | May 2, 22:35 UTC | 19h 30m |
| 2026-04-16 | MFX3030 | - | Apr 16, 04:04 UTC | Apr 16, 05:05 UTC | 1h 0m |
| 2026-04-15 | MFX3015 | - | Apr 15, 21:05 UTC | Apr 15, 23:00 UTC | 1h 55m |
| 2026-04-15 | MFX3015 | - | Apr 15, 20:05 UTC | Apr 15, 21:00 UTC | 55m |
| 2026-04-15 | MFX3016 | - | Apr 15, 11:10 UTC | Apr 15, 11:25 UTC | 15m |
| 2026-04-15 | MFX3016 | - | Apr 15, 10:15 UTC | Apr 15, 10:45 UTC | 30m |
| 2026-04-15 | MFX3029 | - | Apr 15, 05:00 UTC | Apr 15, 06:15 UTC | 1h 15m |
| 2026-04-15 | MFX3029 | - | Apr 15, 03:00 UTC | Apr 15, 04:50 UTC | 1h 50m |
| 2026-04-14 | MFX3312 | - | Apr 14, 09:25 UTC | Apr 14, 09:40 UTC | 15m |
| 2026-04-13 | MFX322 | - | Apr 13, 02:30 UTC | Apr 13, 03:35 UTC | 1h 5m |
| 2026-04-12 | MFX325 | - | Apr 12, 19:50 UTC | Apr 12, 20:10 UTC | 20m |
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 UK33031 page for operator, model, and routing details .