sensors Mode-S transponder
885283
ICAO 24-bit transponder address · allocated to Thailand
Currently assigned to HS-TTC · BOEING 777-300ER
- Hex
- 885283
- Octal
- 42051203
- Decimal
- 8,934,019
- Country
- TH
- Tail
- HS-TTC
- Type
- B77W
- Flights observed
- 95
- Distinct callsigns
- 8
- Country
- TH
- Last broadcast
- 47m ago
Current position
Country allocation
The ICAO 24-bit address 885283 falls within the block assigned to Thailand (TH) by ICAO Annex 10, Volume III. Every aircraft registered in Thailand 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 8 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| THA911 | Thai Airways International | 18 | 2026-05-27 |
| THA623 | Thai Airways International | 18 | 2026-05-29 |
| THA910 | Thai Airways International | 16 | 2026-05-29 |
| THA622 | Thai Airways International | 15 | 2026-05-28 |
| THA677 | Thai Airways International | 14 | 2026-05-28 |
| THA676 | Thai Airways International | 12 | 2026-05-28 |
| THA8410 | - | 1 | 2026-05-16 |
| THA8407 | - | 1 | 2026-05-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | THA910 | BKK → LHR | May 29, 17:55 UTC | May 30, 04:45 UTC | 10h 50m |
| 2026-05-29 | THA623 | KIX → BKK | May 29, 03:15 UTC | May 29, 08:50 UTC | 5h 35m |
| 2026-05-28 | THA622 | BKK → KIX | May 28, 17:40 UTC | May 28, 22:40 UTC | 5h 0m |
| 2026-05-28 | THA677 | NRT → BKK | May 28, 08:45 UTC | May 28, 14:25 UTC | 5h 40m |
| 2026-05-28 | THA676 | BKK → NRT | May 28, 01:05 UTC | May 28, 07:10 UTC | 6h 5m |
| 2026-05-27 | THA911 | LHR → BKK | May 27, 11:50 UTC | May 27, 22:30 UTC | 10h 40m |
| 2026-05-26 | THA910 | BKK → LHR | May 26, 17:55 UTC | May 27, 06:20 UTC | 12h 25m |
| 2026-05-26 | THA623 | KIX → BKK | May 26, 02:55 UTC | May 26, 08:15 UTC | 5h 20m |
| 2026-05-25 | THA622 | BKK → KIX | May 25, 18:15 UTC | May 25, 23:24 UTC | 5h 10m |
| 2026-05-25 | THA677 | NRT → BKK | May 25, 08:50 UTC | May 25, 14:35 UTC | 5h 45m |
| 2026-05-24 | THA911 | LHR → BKK | May 24, 12:50 UTC | May 25, 06:50 UTC | 18h 0m |
| 2026-05-24 | THA911 | LHR → BKK | May 24, 11:50 UTC | May 25, 06:50 UTC | 19h 0m |
| 2026-05-23 | THA910 | BKK → LHR | May 23, 17:50 UTC | May 24, 06:00 UTC | 12h 11m |
| 2026-05-23 | THA623 | KIX → BKK | May 23, 03:35 UTC | May 23, 08:45 UTC | 5h 10m |
| 2026-05-22 | THA622 | BKK → KIX | May 22, 17:20 UTC | May 22, 22:15 UTC | 4h 55m |
| 2026-05-22 | THA677 | NRT → BKK | May 22, 09:10 UTC | May 22, 15:05 UTC | 5h 55m |
| 2026-05-22 | THA676 | BKK → NRT | May 22, 01:45 UTC | May 22, 07:20 UTC | 5h 35m |
| 2026-05-21 | THA911 | LHR → BKK | May 21, 11:45 UTC | May 21, 22:00 UTC | 10h 15m |
| 2026-05-20 | THA910 | BKK → LHR | May 20, 18:00 UTC | May 21, 05:50 UTC | 11h 50m |
| 2026-05-20 | THA623 | KIX → BKK | May 20, 03:20 UTC | May 20, 08:30 UTC | 5h 11m |
| 2026-05-19 | THA622 | BKK → KIX | May 19, 17:20 UTC | May 19, 22:25 UTC | 5h 5m |
| 2026-05-19 | THA677 | NRT → BKK | May 19, 08:45 UTC | May 19, 14:25 UTC | 5h 40m |
| 2026-05-19 | THA676 | BKK → NRT | May 19, 01:00 UTC | May 19, 06:45 UTC | 5h 45m |
| 2026-05-18 | THA911 | LHR → BKK | May 18, 11:40 UTC | May 18, 22:50 UTC | 11h 9m |
| 2026-05-17 | THA910 | BKK → LHR | May 17, 18:10 UTC | May 18, 06:10 UTC | 12h 0m |
| 2026-05-17 | THA623 | KIX → BKK | May 17, 03:00 UTC | May 17, 08:05 UTC | 5h 5m |
| 2026-05-16 | THA622 | BKK → KIX | May 16, 17:20 UTC | May 16, 22:30 UTC | 5h 10m |
| 2026-05-16 | THA8410 | - | May 16, 10:11 UTC | May 16, 10:25 UTC | 15m |
| 2026-05-04 | THA8407 | - | May 4, 02:15 UTC | May 4, 02:35 UTC | 20m |
| 2026-05-03 | THA911 | LHR → BKK | May 3, 11:45 UTC | May 3, 22:39 UTC | 10h 55m |
| 2026-05-02 | THA910 | BKK → LHR | May 2, 17:55 UTC | May 3, 06:05 UTC | 12h 9m |
| 2026-05-02 | THA677 | NRT → BKK | May 2, 08:45 UTC | May 2, 14:45 UTC | 6h 0m |
| 2026-05-02 | THA676 | BKK → NRT | May 2, 01:10 UTC | May 2, 06:40 UTC | 5h 30m |
| 2026-05-01 | THA911 | LHR → BKK | May 1, 12:30 UTC | May 1, 22:25 UTC | 9h 55m |
| 2026-05-01 | THA911 | LHR → BKK | May 1, 12:05 UTC | May 1, 12:25 UTC | 20m |
| 2026-04-30 | THA910 | BKK → LHR | Apr 30, 17:55 UTC | May 1, 06:20 UTC | 12h 25m |
| 2026-04-30 | THA677 | NRT → BKK | Apr 30, 08:50 UTC | Apr 30, 15:15 UTC | 6h 25m |
| 2026-04-30 | THA676 | BKK → NRT | Apr 30, 01:05 UTC | Apr 30, 06:25 UTC | 5h 20m |
| 2026-04-29 | THA911 | LHR → BKK | Apr 29, 11:55 UTC | Apr 29, 22:35 UTC | 10h 40m |
| 2026-04-28 | THA910 | BKK → LHR | Apr 28, 17:55 UTC | Apr 29, 06:19 UTC | 12h 25m |
| 2026-04-28 | THA677 | NRT → BKK | Apr 28, 08:40 UTC | Apr 28, 14:50 UTC | 6h 10m |
| 2026-04-28 | THA676 | BKK → NRT | Apr 28, 01:05 UTC | Apr 28, 06:35 UTC | 5h 30m |
| 2026-04-27 | THA911 | LHR → BKK | Apr 27, 12:00 UTC | Apr 27, 22:45 UTC | 10h 45m |
| 2026-04-26 | THA910 | BKK → LHR | Apr 26, 17:55 UTC | Apr 27, 06:05 UTC | 12h 10m |
| 2026-04-26 | THA677 | NRT → BKK | Apr 26, 14:45 UTC | Apr 26, 15:10 UTC | 25m |
| 2026-04-26 | THA677 | NRT → BKK | Apr 26, 08:50 UTC | Apr 26, 12:40 UTC | 3h 50m |
| 2026-04-26 | THA676 | BKK → NRT | Apr 26, 01:05 UTC | Apr 26, 06:20 UTC | 5h 15m |
| 2026-04-25 | THA911 | LHR → BKK | Apr 25, 11:40 UTC | Apr 25, 22:30 UTC | 10h 50m |
| 2026-04-24 | THA910 | BKK → LHR | Apr 24, 18:05 UTC | Apr 25, 06:30 UTC | 12h 25m |
| 2026-04-24 | THA623 | KIX → BKK | Apr 24, 03:35 UTC | Apr 24, 09:05 UTC | 5h 30m |
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 HS-TTC page for operator, model, and routing details .