sensors Mode-S transponder
601828
ICAO 24-bit transponder address · allocated to Turkmenistan
Currently assigned to EZ-A781 · BOEING 777-300ER
- Hex
- 601828
- Octal
- 30014050
- Decimal
- 6,297,640
- Country
- TM
- Tail
- EZ-A781
- Type
- B77W
- Flights observed
- 108
- Distinct callsigns
- 20
- Country
- TM
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 601828 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 |
|---|---|---|---|
| TUA652 | Turkmenistan Airlines | 15 | 2026-06-16 |
| TUA654 | Turkmenistan Airlines | 12 | 2026-07-09 |
| TUA651 | Turkmenistan Airlines | 10 | 2026-07-07 |
| TUA653 | Turkmenistan Airlines | 5 | 2026-05-06 |
| TUA608 | - | 5 | 2026-07-10 |
| TUA607 | Turkmenistan Airlines | 5 | 2026-07-10 |
| TUA605 | - | 5 | 2026-07-12 |
| TUA464 | Turkmenistan Airlines | 5 | 2026-06-27 |
| TUA463 | - | 5 | 2026-06-27 |
| TUA462 | Turkmenistan Airlines | 5 | 2026-06-10 |
| TUA801 | Turkmenistan Airlines | 4 | 2026-06-30 |
| TUA461 | Turkmenistan Airlines | 4 | 2026-06-30 |
| TUA606 | - | 3 | 2026-07-12 |
| TUA928 | - | 2 | 2026-07-06 |
| TUA927 | - | 2 | 2026-07-05 |
| TUA921 | Turkmenistan Airlines | 2 | 2026-06-04 |
| TUA902 | - | 2 | 2026-07-13 |
| TUA804 | Turkmenistan Airlines | 2 | 2026-06-11 |
| TUA803 | Turkmenistan Airlines | 2 | 2026-04-23 |
| TUA802 | Turkmenistan Airlines | 2 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | TUA912 | - | Jul 14, 06:05 UTC | Jul 14, 07:55 UTC | 1h 50m |
| 2026-07-14 | - | - | Jul 14, 03:25 UTC | Jul 14, 03:50 UTC | 25m |
| 2026-07-13 | TUA902 | - | Jul 13, 08:15 UTC | Jul 14, 02:20 UTC | 18h 5m |
| 2026-07-13 | TUA902 | - | Jul 13, 07:05 UTC | Jul 14, 02:20 UTC | 19h 15m |
| 2026-07-13 | TUA901 | - | Jul 13, 02:40 UTC | Jul 13, 05:05 UTC | 2h 25m |
| 2026-07-12 | TUA606 | - | Jul 12, 07:55 UTC | Jul 12, 08:05 UTC | 10m |
| 2026-07-12 | TUA605 | - | Jul 12, 04:25 UTC | Jul 12, 04:50 UTC | 25m |
| 2026-07-10 | TUA608 | - | Jul 10, 22:00 UTC | Jul 10, 22:15 UTC | 15m |
| 2026-07-10 | TUA607 | ASB → PEK | Jul 10, 18:55 UTC | Jul 10, 19:20 UTC | 25m |
| 2026-07-09 | TUA654 | SGN → ASB | Jul 9, 16:05 UTC | Jul 10, 15:55 UTC | 23h 50m |
| 2026-07-09 | TUA654 | SGN → ASB | Jul 9, 08:15 UTC | Jul 9, 18:00 UTC | 9h 45m |
| 2026-07-07 | TUA651 | ASB → SGN | Jul 7, 13:20 UTC | Jul 8, 01:25 UTC | 12h 5m |
| 2026-07-06 | TUA928 | - | Jul 6, 01:40 UTC | Jul 6, 03:25 UTC | 1h 45m |
| 2026-07-05 | TUA927 | - | Jul 5, 07:15 UTC | Jul 5, 23:35 UTC | 16h 20m |
| 2026-07-05 | TUA605 | ASB → PEK | Jul 5, 04:10 UTC | Jul 5, 04:30 UTC | 20m |
| 2026-07-03 | TUA608 | - | Jul 3, 21:55 UTC | Jul 3, 22:10 UTC | 15m |
| 2026-07-03 | TUA607 | ASB → PEK | Jul 3, 19:05 UTC | Jul 3, 19:25 UTC | 20m |
| 2026-07-01 | TUA654 | SGN → ASB | Jul 1, 22:05 UTC | Jul 2, 17:25 UTC | 19h 20m |
| 2026-07-01 | TUA654 | SGN → ASB | Jul 1, 20:05 UTC | Jul 2, 17:25 UTC | 21h 20m |
| 2026-07-01 | TUA654 | SGN → ASB | Jul 1, 18:25 UTC | Jul 2, 17:25 UTC | 23h 0m |
| 2026-06-30 | TUA461 | ASB → FRA | Jun 30, 21:15 UTC | Jul 1, 14:25 UTC | 17h 10m |
| 2026-06-30 | TUA801 | ASB → KUL | Jun 30, 12:55 UTC | Jun 30, 18:30 UTC | 5h 35m |
| 2026-06-28 | TUA928 | - | Jun 28, 23:34 UTC | Jun 29, 01:25 UTC | 1h 50m |
| 2026-06-28 | TUA927 | - | Jun 28, 19:09 UTC | Jun 28, 21:20 UTC | 2h 10m |
| 2026-06-27 | TUA464 | FRA → ASB | Jun 27, 17:20 UTC | Jun 27, 19:34 UTC | 2h 15m |
| 2026-06-27 | TUA463 | - | Jun 27, 09:04 UTC | Jun 27, 13:15 UTC | 4h 10m |
| 2026-06-21 | TUA606 | PEK → ASB | Jun 21, 07:29 UTC | Jun 21, 07:45 UTC | 15m |
| 2026-06-21 | TUA605 | ASB → PEK | Jun 21, 04:20 UTC | Jun 21, 04:34 UTC | 15m |
| 2026-06-19 | TUA608 | PEK → ASB | Jun 19, 21:14 UTC | Jun 19, 21:30 UTC | 15m |
| 2026-06-19 | TUA607 | ASB → PEK | Jun 19, 18:44 UTC | Jun 19, 19:04 UTC | 20m |
| 2026-06-18 | TUA654 | SGN → ASB | Jun 18, 05:00 UTC | Jun 18, 17:10 UTC | 12h 10m |
| 2026-06-16 | TUA652 | SGN → ASB | Jun 16, 13:30 UTC | Jun 17, 01:40 UTC | 12h 11m |
| 2026-06-15 | TUA651 | ASB → SGN | Jun 15, 20:04 UTC | Jun 16, 17:49 UTC | 21h 45m |
| 2026-06-15 | TUA651 | ASB → SGN | Jun 15, 19:39 UTC | Jun 16, 17:49 UTC | 22h 10m |
| 2026-06-15 | - | - | Jun 15, 17:15 UTC | Jun 15, 17:25 UTC | 10m |
| 2026-06-15 | - | - | Jun 15, 15:15 UTC | Jun 15, 15:55 UTC | 40m |
| 2026-06-13 | TUA464 | FRA → ASB | Jun 13, 16:25 UTC | Jun 13, 20:05 UTC | 3h 40m |
| 2026-06-13 | TUA463 | ASB → FRA | Jun 13, 08:25 UTC | Jun 13, 12:55 UTC | 4h 30m |
| 2026-06-11 | TUA804 | KUL → ASB | Jun 11, 11:25 UTC | Jun 11, 16:50 UTC | 5h 25m |
| 2026-06-10 | TUA462 | FRA → EVN | Jun 10, 17:25 UTC | Jun 11, 09:25 UTC | 16h 0m |
| 2026-06-09 | TUA652 | SGN → ASB | Jun 9, 21:15 UTC | Jun 10, 14:05 UTC | 16h 50m |
| 2026-06-09 | TUA652 | SGN → ASB | Jun 9, 16:45 UTC | Jun 10, 14:05 UTC | 21h 20m |
| 2026-06-09 | TUA652 | SGN → ASB | Jun 9, 14:05 UTC | Jun 10, 14:00 UTC | 23h 55m |
| 2026-06-09 | TUA652 | SGN → ASB | Jun 9, 13:10 UTC | Jun 10, 11:10 UTC | 22h 0m |
| 2026-06-09 | TUA651 | ASB → SGN | Jun 9, 00:05 UTC | Jun 10, 00:00 UTC | 23h 55m |
| 2026-06-08 | TUA651 | ASB → SGN | Jun 8, 22:05 UTC | Jun 9, 21:55 UTC | 23h 50m |
| 2026-06-08 | TUA651 | ASB → SGN | Jun 8, 21:30 UTC | Jun 9, 17:20 UTC | 19h 50m |
| 2026-06-08 | TUA651 | ASB → SGN | Jun 8, 16:05 UTC | Jun 9, 15:45 UTC | 23h 40m |
| 2026-06-08 | TUA3827 | ASB → MED | Jun 8, 14:05 UTC | Jun 9, 14:00 UTC | 23h 55m |
| 2026-06-08 | TUA3827 | ASB → MED | Jun 8, 13:40 UTC | Jun 9, 00:05 UTC | 10h 25m |
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-A781 page for operator, model, and routing details .