sensors Mode-S transponder
601834
ICAO 24-bit transponder address · allocated to Turkmenistan
Currently assigned to EZ-A018 · BOEING 737-800
- Hex
- 601834
- Octal
- 30014064
- Decimal
- 6,297,652
- Country
- TM
- Tail
- EZ-A018
- Type
- B738
- Flights observed
- 113
- Distinct callsigns
- 17
- Country
- TM
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 601834 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TUA921 | Turkmenistan Airlines | 20 | 2026-07-12 |
| TUA922 | - | 12 | 2026-07-12 |
| TUA445 | - | 11 | 2026-07-08 |
| TUA446 | Turkmenistan Airlines | 10 | 2026-07-08 |
| TUA444 | Turkmenistan Airlines | 9 | 2026-07-11 |
| TUA443 | - | 9 | 2026-07-11 |
| TUA985 | Turkmenistan Airlines | 7 | 2026-06-20 |
| TUA531 | - | 7 | 2026-07-07 |
| TUA901 | - | 6 | 2026-07-05 |
| TUA535 | Turkmenistan Airlines | 6 | 2026-06-19 |
| TUA986 | Turkmenistan Airlines | 4 | 2026-06-20 |
| TUA534 | Turkmenistan Airlines | 4 | 2026-06-11 |
| TUA912 | Turkmenistan Airlines | 2 | 2026-04-17 |
| TUA911 | Turkmenistan Airlines | 2 | 2026-05-05 |
| TUA902 | - | 2 | 2026-07-05 |
| TUA536 | Turkmenistan Airlines | 1 | 2026-06-06 |
| TUA533 | Turkmenistan Airlines | 1 | 2026-04-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | TUA922 | - | Jul 12, 19:35 UTC | Jul 12, 21:25 UTC | 1h 50m |
| 2026-07-12 | TUA921 | ASB → IST | Jul 12, 15:01 UTC | Jul 12, 16:30 UTC | 1h 30m |
| 2026-07-11 | TUA921 | ASB → IST | Jul 11, 19:05 UTC | Jul 12, 16:30 UTC | 21h 25m |
| 2026-07-11 | TUA444 | MXP → ASB | Jul 11, 17:15 UTC | Jul 12, 16:30 UTC | 23h 15m |
| 2026-07-11 | TUA443 | - | Jul 11, 07:40 UTC | Jul 11, 12:20 UTC | 4h 40m |
| 2026-07-09 | TUA922 | - | Jul 9, 19:25 UTC | Jul 9, 21:25 UTC | 2h 0m |
| 2026-07-09 | TUA921 | ASB → IST | Jul 9, 07:00 UTC | Jul 9, 17:15 UTC | 10h 15m |
| 2026-07-08 | TUA446 | MXP → ASB | Jul 8, 17:40 UTC | Jul 9, 04:55 UTC | 11h 15m |
| 2026-07-08 | TUA445 | - | Jul 8, 01:30 UTC | Jul 8, 14:45 UTC | 13h 15m |
| 2026-07-07 | TUA531 | - | Jul 7, 22:50 UTC | Jul 7, 23:55 UTC | 1h 5m |
| 2026-07-06 | TUA922 | - | Jul 6, 19:20 UTC | Jul 6, 21:15 UTC | 1h 55m |
| 2026-07-06 | TUA921 | ASB → IST | Jul 6, 17:15 UTC | Jul 6, 17:40 UTC | 25m |
| 2026-07-05 | TUA921 | ASB → IST | Jul 5, 21:05 UTC | Jul 6, 16:35 UTC | 19h 30m |
| 2026-07-05 | TUA921 | ASB → IST | Jul 5, 19:20 UTC | Jul 6, 16:35 UTC | 21h 15m |
| 2026-07-05 | TUA921 | ASB → IST | Jul 5, 17:10 UTC | Jul 5, 17:30 UTC | 20m |
| 2026-07-05 | TUA902 | - | Jul 5, 06:55 UTC | Jul 5, 16:30 UTC | 9h 35m |
| 2026-07-05 | TUA901 | - | Jul 5, 04:40 UTC | Jul 5, 05:00 UTC | 20m |
| 2026-07-04 | TUA444 | MXP → ASB | Jul 4, 15:15 UTC | Jul 5, 04:05 UTC | 12h 50m |
| 2026-07-04 | TUA443 | - | Jul 4, 07:45 UTC | Jul 4, 12:25 UTC | 4h 40m |
| 2026-07-02 | TUA922 | - | Jul 2, 20:45 UTC | Jul 2, 21:15 UTC | 30m |
| 2026-07-02 | TUA922 | - | Jul 2, 19:25 UTC | Jul 2, 19:55 UTC | 30m |
| 2026-07-02 | TUA921 | ASB → IST | Jul 2, 07:00 UTC | Jul 2, 17:35 UTC | 10h 35m |
| 2026-07-02 | TUA901 | - | Jul 2, 04:40 UTC | Jul 2, 05:00 UTC | 20m |
| 2026-07-01 | TUA446 | MXP → ASB | Jul 1, 18:05 UTC | Jul 2, 04:05 UTC | 10h 0m |
| 2026-07-01 | TUA445 | - | Jul 1, 01:55 UTC | Jul 1, 15:00 UTC | 13h 5m |
| 2026-06-30 | TUA531 | - | Jun 30, 23:25 UTC | Jul 1, 00:20 UTC | 55m |
| 2026-06-20 | TUA986 | IST → ASB | Jun 20, 14:59 UTC | Jun 20, 16:55 UTC | 1h 55m |
| 2026-06-20 | TUA985 | ASB → IST | Jun 20, 02:04 UTC | Jun 20, 13:04 UTC | 11h 0m |
| 2026-06-19 | TUA535 | ASB → DEL | Jun 19, 23:04 UTC | Jun 20, 00:04 UTC | 1h 0m |
| 2026-06-13 | TUA444 | MXP → ASB | Jun 13, 15:45 UTC | Jun 13, 19:40 UTC | 3h 55m |
| 2026-06-12 | TUA443 | ASB → MXP | Jun 12, 19:20 UTC | Jun 13, 12:20 UTC | 16h 59m |
| 2026-06-12 | TUA921 | ASB → IST | Jun 12, 14:55 UTC | Jun 12, 17:20 UTC | 2h 25m |
| 2026-06-11 | TUA534 | ATQ → ASB | Jun 11, 07:20 UTC | Jun 11, 08:20 UTC | 1h 0m |
| 2026-06-10 | TUA446 | MXP → ASB | Jun 10, 17:10 UTC | Jun 11, 05:10 UTC | 12h 0m |
| 2026-06-10 | TUA445 | ASB → MXP | Jun 10, 01:40 UTC | Jun 10, 15:10 UTC | 13h 30m |
| 2026-06-09 | TUA531 | ASB → DEL | Jun 9, 23:05 UTC | Jun 10, 00:10 UTC | 1h 5m |
| 2026-06-08 | TUA922 | IST → ASB | Jun 8, 19:25 UTC | Jun 8, 21:25 UTC | 2h 0m |
| 2026-06-08 | TUA921 | ASB → IST | Jun 8, 15:00 UTC | Jun 8, 16:25 UTC | 1h 25m |
| 2026-06-06 | TUA444 | MXP → ASB | Jun 6, 17:05 UTC | Jun 7, 11:50 UTC | 18h 45m |
| 2026-06-06 | TUA444 | MXP → ASB | Jun 6, 15:05 UTC | Jun 7, 11:50 UTC | 20h 45m |
| 2026-06-06 | TUA444 | MXP → ASB | Jun 6, 14:45 UTC | Jun 7, 11:50 UTC | 21h 5m |
| 2026-06-06 | TUA443 | ASB → MXP | Jun 6, 02:40 UTC | Jun 6, 12:40 UTC | 10h 0m |
| 2026-06-06 | TUA536 | DEL → ASB | Jun 6, 01:45 UTC | Jun 6, 02:00 UTC | 15m |
| 2026-06-05 | TUA535 | ASB → DEL | Jun 5, 23:35 UTC | Jun 5, 23:55 UTC | 20m |
| 2026-06-05 | TUA535 | ASB → DEL | Jun 5, 22:55 UTC | Jun 5, 23:05 UTC | 10m |
| 2026-06-04 | TUA534 | ATQ → ASB | Jun 4, 07:10 UTC | Jun 4, 08:25 UTC | 1h 15m |
| 2026-06-03 | TUA446 | MXP → ASB | Jun 3, 17:35 UTC | Jun 4, 05:30 UTC | 11h 55m |
| 2026-06-03 | TUA445 | ASB → MXP | Jun 3, 01:25 UTC | Jun 3, 14:50 UTC | 13h 25m |
| 2026-05-30 | TUA986 | IST → ASB | May 30, 15:05 UTC | May 31, 10:55 UTC | 19h 50m |
| 2026-05-30 | TUA985 | ASB → IST | May 30, 12:50 UTC | May 30, 13:05 UTC | 15m |
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-A018 page for operator, model, and routing details .