sensors Mode-S transponder
60183A
ICAO 24-bit transponder address · allocated to Turkmenistan
Currently assigned to EZ-A778 · BOEING 777-200
- Hex
- 60183A
- Octal
- 30014072
- Decimal
- 6,297,658
- Country
- TM
- Tail
- EZ-A778
- Type
- B772
- Flights observed
- 118
- Distinct callsigns
- 20
- Country
- TM
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 60183A 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 |
|---|---|---|---|
| TUA641 | Turkmenistan Airlines | 14 | 2026-07-24 |
| TUA801 | Turkmenistan Airlines | 11 | 2026-07-21 |
| TUA804 | Turkmenistan Airlines | 9 | 2026-07-23 |
| TUA423 | - | 9 | 2026-07-14 |
| TUA424 | Turkmenistan Airlines | 8 | 2026-06-24 |
| TUA427 | Turkmenistan Airlines | 7 | 2026-07-24 |
| TUA803 | Turkmenistan Airlines | 6 | 2026-07-22 |
| TUA678 | Turkmenistan Airlines | 6 | 2026-07-20 |
| TUA677 | - | 5 | 2026-07-20 |
| TUA648 | - | 5 | 2026-07-12 |
| TUA647 | - | 5 | 2026-07-11 |
| TUA428 | Turkmenistan Airlines | 5 | 2026-07-25 |
| TUA911 | - | 4 | 2026-06-29 |
| TUA652 | Turkmenistan Airlines | 4 | 2026-05-19 |
| TUA642 | - | 4 | 2026-07-03 |
| TUA902 | Turkmenistan Airlines | 3 | 2026-07-26 |
| TUA901 | - | 3 | 2026-06-29 |
| TUA912 | - | 2 | 2026-06-30 |
| TUA928 | Turkmenistan Airlines | 1 | 2026-05-03 |
| TUA927 | Turkmenistan Airlines | 1 | 2026-05-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | TUA902 | IST → ASB | Jul 26, 07:00 UTC | Jul 26, 07:25 UTC | 25m |
| 2026-07-25 | TUA428 | LHR → ASB | Jul 25, 16:20 UTC | Jul 26, 04:00 UTC | 11h 40m |
| 2026-07-24 | TUA427 | ASB → LHR | Jul 24, 22:05 UTC | Jul 25, 14:10 UTC | 16h 5m |
| 2026-07-24 | TUA641 | ASB → BKK | Jul 24, 16:00 UTC | Jul 24, 20:15 UTC | 4h 15m |
| 2026-07-23 | TUA804 | KUL → ASB | Jul 23, 16:35 UTC | Jul 24, 16:30 UTC | 23h 55m |
| 2026-07-23 | TUA804 | KUL → ASB | Jul 23, 12:05 UTC | Jul 23, 17:10 UTC | 5h 5m |
| 2026-07-22 | TUA803 | ASB → KUL | Jul 22, 16:30 UTC | Jul 23, 09:15 UTC | 16h 45m |
| 2026-07-21 | TUA802 | KUL → ASB | Jul 21, 21:15 UTC | Jul 22, 14:05 UTC | 16h 50m |
| 2026-07-21 | TUA801 | ASB → KUL | Jul 21, 12:55 UTC | Jul 21, 18:15 UTC | 5h 20m |
| 2026-07-20 | TUA801 | ASB → KUL | Jul 20, 14:35 UTC | Jul 21, 14:00 UTC | 23h 25m |
| 2026-07-20 | TUA678 | ICN → ASB | Jul 20, 14:25 UTC | Jul 20, 14:55 UTC | 30m |
| 2026-07-20 | TUA677 | - | Jul 20, 11:25 UTC | Jul 20, 11:45 UTC | 20m |
| 2026-07-20 | TUA677 | - | Jul 20, 10:15 UTC | Jul 20, 10:35 UTC | 20m |
| 2026-07-18 | TUA428 | - | Jul 18, 17:00 UTC | Jul 18, 21:10 UTC | 4h 10m |
| 2026-07-17 | TUA427 | ASB → LHR | Jul 17, 22:00 UTC | Jul 18, 14:25 UTC | 16h 26m |
| 2026-07-17 | TUA641 | ASB → BKK | Jul 17, 15:44 UTC | Jul 17, 20:00 UTC | 4h 15m |
| 2026-07-16 | TUA641 | ASB → BKK | Jul 16, 16:35 UTC | Jul 17, 16:29 UTC | 23h 55m |
| 2026-07-16 | TUA804 | KUL → ASB | Jul 16, 12:05 UTC | Jul 16, 17:14 UTC | 5h 10m |
| 2026-07-15 | TUA803 | - | Jul 15, 17:10 UTC | Jul 16, 09:20 UTC | 16h 10m |
| 2026-07-14 | TUA423 | - | Jul 14, 21:20 UTC | Jul 15, 14:10 UTC | 16h 49m |
| 2026-07-14 | TUA801 | ASB → KUL | Jul 14, 13:05 UTC | Jul 14, 18:20 UTC | 5h 15m |
| 2026-07-12 | TUA648 | - | Jul 12, 08:50 UTC | Jul 12, 12:55 UTC | 4h 5m |
| 2026-07-11 | TUA647 | - | Jul 11, 16:35 UTC | Jul 12, 06:01 UTC | 13h 25m |
| 2026-07-10 | TUA427 | - | Jul 10, 21:55 UTC | Jul 11, 14:25 UTC | 16h 30m |
| 2026-07-10 | TUA641 | ASB → BKK | Jul 10, 15:50 UTC | Jul 10, 20:05 UTC | 4h 15m |
| 2026-07-09 | TUA641 | ASB → BKK | Jul 9, 16:35 UTC | Jul 10, 16:30 UTC | 23h 55m |
| 2026-07-09 | TUA804 | KUL → ASB | Jul 9, 11:45 UTC | Jul 9, 16:45 UTC | 5h 0m |
| 2026-07-08 | TUA803 | - | Jul 8, 16:15 UTC | Jul 9, 09:00 UTC | 16h 45m |
| 2026-07-07 | TUA423 | - | Jul 7, 21:10 UTC | Jul 8, 14:10 UTC | 17h 0m |
| 2026-07-07 | TUA801 | ASB → KUL | Jul 7, 13:05 UTC | Jul 7, 18:25 UTC | 5h 20m |
| 2026-07-06 | TUA678 | ICN → ASB | Jul 6, 14:00 UTC | Jul 6, 14:25 UTC | 25m |
| 2026-07-06 | TUA677 | - | Jul 6, 11:45 UTC | Jul 6, 12:05 UTC | 20m |
| 2026-07-05 | TUA648 | - | Jul 5, 08:30 UTC | Jul 5, 12:40 UTC | 4h 10m |
| 2026-07-04 | TUA647 | - | Jul 4, 16:45 UTC | Jul 5, 05:55 UTC | 13h 10m |
| 2026-07-03 | TUA642 | BKK → LGW | Jul 3, 21:40 UTC | Jul 4, 14:30 UTC | 16h 50m |
| 2026-07-03 | TUA641 | ASB → BKK | Jul 3, 15:50 UTC | Jul 3, 20:05 UTC | 4h 15m |
| 2026-07-02 | TUA641 | ASB → BKK | Jul 2, 16:35 UTC | Jul 3, 16:30 UTC | 23h 55m |
| 2026-07-02 | TUA804 | KUL → ASB | Jul 2, 11:40 UTC | Jul 2, 17:00 UTC | 5h 20m |
| 2026-07-01 | TUA803 | - | Jul 1, 16:40 UTC | Jul 2, 09:10 UTC | 16h 30m |
| 2026-07-01 | TUA423 | - | Jul 1, 08:35 UTC | Jul 1, 13:50 UTC | 5h 15m |
| 2026-06-30 | TUA912 | - | Jun 30, 05:50 UTC | Jun 30, 07:35 UTC | 1h 45m |
| 2026-06-29 | TUA911 | - | Jun 29, 08:35 UTC | Jun 30, 02:35 UTC | 18h 1m |
| 2026-06-29 | TUA902 | - | Jun 29, 06:54 UTC | Jun 30, 02:35 UTC | 19h 41m |
| 2026-06-29 | TUA901 | - | Jun 29, 04:39 UTC | Jun 29, 05:00 UTC | 20m |
| 2026-06-28 | TUA648 | - | Jun 28, 08:55 UTC | Jun 29, 04:04 UTC | 19h 10m |
| 2026-06-27 | TUA647 | LGW → BKK | Jun 27, 17:49 UTC | Jun 28, 06:59 UTC | 13h 10m |
| 2026-06-26 | TUA642 | - | Jun 26, 22:10 UTC | Jun 27, 14:25 UTC | 16h 15m |
| 2026-06-26 | TUA641 | ASB → BKK | Jun 26, 15:39 UTC | Jun 26, 19:45 UTC | 4h 5m |
| 2026-06-25 | TUA641 | ASB → BKK | Jun 25, 16:35 UTC | Jun 26, 16:30 UTC | 23h 55m |
| 2026-06-25 | TUA804 | KUL → ASB | Jun 25, 11:44 UTC | Jun 25, 16:50 UTC | 5h 5m |
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-A778 page for operator, model, and routing details .