sensors Mode-S transponder
60182A
ICAO 24-bit transponder address · allocated to Turkmenistan
Currently assigned to EZ-F430 · AIRBUS A-330-200
- Hex
- 60182A
- Octal
- 30014052
- Decimal
- 6,297,642
- Country
- TM
- Tail
- EZ-F430
- Type
- A332
- Flights observed
- 155
- Distinct callsigns
- 20
- Country
- TM
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 60182A falls within the block assigned to Turkmenistan (TM) by ICAO Annex 10, Volume III. Every aircraft registered in Turkmenistan 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 |
|---|---|---|---|
| TUA698 | Turkmenistan Airlines | 13 | 2026-07-02 |
| TUA475 | - | 10 | 2026-07-12 |
| TUA477 | - | 9 | 2026-06-26 |
| TUA697 | - | 8 | 2026-07-02 |
| TUA696 | Turkmenistan Airlines | 8 | 2026-07-12 |
| TUA683 | Turkmenistan Airlines | 8 | 2026-06-19 |
| TUA616 | Turkmenistan Airlines | 8 | 2026-06-30 |
| TUA447 | Turkmenistan Airlines | 8 | 2026-07-01 |
| TUA455 | - | 7 | 2026-07-09 |
| TUA620 | - | 6 | 2026-06-14 |
| TUA476 | Turkmenistan Airlines | 6 | 2026-07-13 |
| TUA456 | Turkmenistan Airlines | 6 | 2026-07-10 |
| TUA449 | Turkmenistan Airlines | 6 | 2026-07-05 |
| TUA694 | - | 5 | 2026-07-09 |
| TUA618 | - | 5 | 2026-07-04 |
| TUA617 | Turkmenistan Airlines | 5 | 2026-07-04 |
| TUA478 | Turkmenistan Airlines | 5 | 2026-06-20 |
| TUA450 | - | 5 | 2026-07-05 |
| TUA448 | Turkmenistan Airlines | 4 | 2026-07-01 |
| TUA695 | - | 3 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | TUA476 | FRA → ASB | Jul 13, 16:45 UTC | Jul 13, 20:35 UTC | 3h 50m |
| 2026-07-12 | TUA475 | - | Jul 12, 16:35 UTC | Jul 13, 14:25 UTC | 21h 50m |
| 2026-07-12 | TUA475 | - | Jul 12, 14:35 UTC | Jul 13, 14:25 UTC | 23h 50m |
| 2026-07-12 | TUA696 | HAN → ASB | Jul 12, 12:35 UTC | Jul 13, 12:30 UTC | 23h 55m |
| 2026-07-12 | TUA695 | - | Jul 12, 04:45 UTC | Jul 12, 08:50 UTC | 4h 5m |
| 2026-07-10 | TUA456 | MXP → ASB | Jul 10, 19:00 UTC | Jul 10, 21:20 UTC | 2h 21m |
| 2026-07-09 | TUA455 | - | Jul 9, 21:40 UTC | Jul 10, 14:35 UTC | 16h 55m |
| 2026-07-09 | TUA455 | - | Jul 9, 16:55 UTC | Jul 10, 14:35 UTC | 21h 40m |
| 2026-07-09 | TUA694 | - | Jul 9, 15:10 UTC | Jul 10, 14:30 UTC | 23h 20m |
| 2026-07-09 | TUA694 | - | Jul 9, 13:25 UTC | Jul 10, 12:30 UTC | 23h 5m |
| 2026-07-05 | TUA450 | - | Jul 5, 17:25 UTC | Jul 5, 21:05 UTC | 3h 40m |
| 2026-07-05 | TUA449 | ASB → MXP | Jul 5, 10:20 UTC | Jul 5, 14:55 UTC | 4h 35m |
| 2026-07-04 | TUA618 | - | Jul 4, 22:25 UTC | Jul 4, 22:35 UTC | 10m |
| 2026-07-04 | TUA617 | ASB → SZX | Jul 4, 18:50 UTC | Jul 4, 19:00 UTC | 10m |
| 2026-07-02 | TUA698 | HAN → ASB | Jul 2, 12:10 UTC | Jul 2, 16:35 UTC | 4h 25m |
| 2026-07-02 | TUA697 | - | Jul 2, 08:55 UTC | Jul 2, 09:05 UTC | 10m |
| 2026-07-01 | TUA448 | MXP → ASB | Jul 1, 17:10 UTC | Jul 2, 08:10 UTC | 15h 0m |
| 2026-07-01 | TUA447 | ASB → MXP | Jul 1, 10:20 UTC | Jul 1, 14:40 UTC | 4h 20m |
| 2026-06-30 | TUA616 | SZX → ASB | Jun 30, 22:00 UTC | Jun 30, 22:15 UTC | 15m |
| 2026-06-30 | TUA615 | - | Jun 30, 19:10 UTC | Jun 30, 19:20 UTC | 10m |
| 2026-06-28 | TUA696 | HAN → ASB | Jun 28, 13:19 UTC | Jun 28, 17:44 UTC | 4h 25m |
| 2026-06-28 | TUA695 | - | Jun 28, 09:39 UTC | Jun 28, 09:55 UTC | 15m |
| 2026-06-27 | TUA695 | - | Jun 27, 16:55 UTC | Jun 28, 08:59 UTC | 16h 5m |
| 2026-06-26 | TUA477 | MLA → FRA | Jun 26, 19:14 UTC | Jun 27, 14:29 UTC | 19h 15m |
| 2026-06-25 | TUA3245 | - | Jun 25, 12:44 UTC | Jun 26, 06:39 UTC | 17h 55m |
| 2026-06-25 | TUA3245 | - | Jun 25, 11:10 UTC | Jun 26, 06:39 UTC | 19h 30m |
| 2026-06-25 | TUA697 | - | Jun 25, 08:30 UTC | Jun 25, 08:40 UTC | 10m |
| 2026-06-24 | TUA697 | - | Jun 24, 17:14 UTC | Jun 25, 07:59 UTC | 14h 45m |
| 2026-06-24 | TUA447 | ASB → MXP | Jun 24, 10:25 UTC | Jun 24, 14:39 UTC | 4h 15m |
| 2026-06-23 | TUA616 | SZX → ASB | Jun 23, 22:40 UTC | Jun 23, 22:55 UTC | 15m |
| 2026-06-22 | TUA488 | - | Jun 22, 15:54 UTC | Jun 22, 17:50 UTC | 1h 55m |
| 2026-06-21 | TUA696 | HAN → ASB | Jun 21, 14:15 UTC | Jun 22, 04:49 UTC | 14h 35m |
| 2026-06-20 | TUA478 | FRA → ASB | Jun 20, 20:45 UTC | Jun 21, 09:59 UTC | 13h 15m |
| 2026-06-20 | TUA477 | ASB → FRA | Jun 20, 09:59 UTC | Jun 20, 14:29 UTC | 4h 30m |
| 2026-06-19 | TUA477 | ASB → FRA | Jun 19, 14:44 UTC | Jun 20, 14:29 UTC | 23h 45m |
| 2026-06-19 | TUA683 | ASB → ICN | Jun 19, 11:59 UTC | Jun 19, 12:25 UTC | 25m |
| 2026-06-19 | TUA683 | ASB → ICN | Jun 19, 10:44 UTC | Jun 19, 11:14 UTC | 30m |
| 2026-06-18 | TUA698 | HAN → ASB | Jun 18, 14:35 UTC | Jun 19, 11:14 UTC | 20h 39m |
| 2026-06-18 | TUA698 | HAN → ASB | Jun 18, 12:35 UTC | Jun 19, 11:14 UTC | 22h 39m |
| 2026-06-18 | TUA698 | HAN → ASB | Jun 18, 11:25 UTC | Jun 18, 15:55 UTC | 4h 30m |
| 2026-06-17 | TUA697 | ASB → HAN | Jun 17, 17:05 UTC | Jun 18, 07:55 UTC | 14h 50m |
| 2026-06-17 | TUA447 | ASB → MXP | Jun 17, 10:25 UTC | Jun 17, 14:45 UTC | 4h 20m |
| 2026-06-16 | TUA616 | SZX → ASB | Jun 16, 21:35 UTC | Jun 16, 21:45 UTC | 10m |
| 2026-06-15 | TUA458 | - | Jun 15, 16:59 UTC | Jun 15, 20:54 UTC | 3h 55m |
| 2026-06-15 | TUA457 | - | Jun 15, 10:30 UTC | Jun 15, 14:50 UTC | 4h 20m |
| 2026-06-14 | TUA620 | - | Jun 14, 22:05 UTC | Jun 14, 22:20 UTC | 15m |
| 2026-06-14 | TUA619 | ASB → SZX | Jun 14, 18:50 UTC | Jun 14, 19:05 UTC | 15m |
| 2026-06-13 | TUA478 | FRA → ASB | Jun 13, 19:10 UTC | Jun 13, 23:00 UTC | 3h 50m |
| 2026-06-12 | TUA477 | ASB → FRA | Jun 12, 20:40 UTC | Jun 13, 16:20 UTC | 19h 39m |
| 2026-06-12 | TUA477 | ASB → FRA | Jun 12, 18:35 UTC | Jun 13, 16:20 UTC | 21h 44m |
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 EZ-F430 page for operator, model, and routing details .