sensors Mode-S transponder
899122
ICAO 24-bit transponder address · allocated to Taiwan
Currently assigned to B-58510 · AIRBUS A-350-900
- Hex
- 899122
- Octal
- 42310442
- Decimal
- 9,015,586
- Country
- TW
- Tail
- B-58510
- Type
- A359
- Flights observed
- 129
- Distinct callsigns
- 20
- Country
- TW
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 899122 falls within the block assigned to Taiwan (TW) by ICAO Annex 10, Volume III. Every aircraft registered in Taiwan 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 |
|---|---|---|---|
| SJX011 | STARLUX Airlines | 12 | 2026-05-27 |
| SJX851 | STARLUX Airlines | 10 | 2026-05-20 |
| SJX850 | STARLUX Airlines | 10 | 2026-05-20 |
| SJX823 | STARLUX Airlines | 9 | 2026-05-29 |
| SJX001 | - | 9 | 2026-05-21 |
| SJX026 | STARLUX Airlines | 8 | 2026-05-24 |
| SJX025 | STARLUX Airlines | 7 | 2026-05-25 |
| SJX012 | STARLUX Airlines | 7 | 2026-05-26 |
| SJX009 | - | 7 | 2026-05-23 |
| SJX010 | STARLUX Airlines | 6 | 2026-05-22 |
| SJX002 | - | 6 | 2026-05-20 |
| SJX822 | STARLUX Airlines | 4 | 2026-05-29 |
| SJX772 | STARLUX Airlines | 4 | 2026-05-17 |
| SJX771 | STARLUX Airlines | 4 | 2026-05-17 |
| SJX742 | STARLUX Airlines | 4 | 2026-05-24 |
| SJX741 | STARLUX Airlines | 4 | 2026-05-24 |
| SJX821 | STARLUX Airlines | 3 | 2026-04-16 |
| SJX236 | STARLUX Airlines | 3 | 2026-04-16 |
| SJX235 | STARLUX Airlines | 3 | 2026-04-16 |
| SJX820 | STARLUX Airlines | 2 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SJX823 | KIX → TPE | May 29, 06:25 UTC | May 29, 08:45 UTC | 2h 20m |
| 2026-05-29 | SJX822 | TPE → KIX | May 29, 02:35 UTC | May 29, 04:45 UTC | 2h 10m |
| 2026-05-27 | SJX011 | SFO → TPE | May 27, 08:10 UTC | May 27, 20:55 UTC | 12h 45m |
| 2026-05-26 | SJX012 | TPE → SFO | May 26, 16:30 UTC | May 27, 03:39 UTC | 11h 10m |
| 2026-05-26 | SJX711 | TPE → SGN | May 26, 00:14 UTC | May 26, 07:59 UTC | 7h 45m |
| 2026-05-25 | SJX025 | PHX → TPE | May 25, 06:45 UTC | May 25, 20:34 UTC | 13h 50m |
| 2026-05-24 | SJX026 | TPE → PHX | May 24, 12:30 UTC | May 24, 23:46 UTC | 11h 16m |
| 2026-05-24 | SJX742 | BKK → TPE | May 24, 06:30 UTC | May 24, 10:05 UTC | 3h 35m |
| 2026-05-24 | SJX741 | TPE → BKK | May 24, 01:25 UTC | May 24, 04:25 UTC | 3h 0m |
| 2026-05-23 | SJX009 | - | May 23, 19:30 UTC | May 23, 19:55 UTC | 25m |
| 2026-05-23 | SJX009 | - | May 23, 06:30 UTC | May 23, 18:15 UTC | 11h 45m |
| 2026-05-22 | SJX010 | TPE → ONT | May 22, 14:00 UTC | May 22, 23:45 UTC | 9h 45m |
| 2026-05-22 | SJX010 | TPE → ONT | May 22, 12:30 UTC | May 22, 12:50 UTC | 20m |
| 2026-05-22 | SJX823 | KIX → TPE | May 22, 09:10 UTC | May 22, 09:30 UTC | 20m |
| 2026-05-22 | SJX823 | KIX → TPE | May 22, 07:10 UTC | May 22, 07:45 UTC | 35m |
| 2026-05-22 | SJX822 | TPE → KIX | May 22, 02:30 UTC | May 22, 04:45 UTC | 2h 15m |
| 2026-05-21 | SJX001 | - | May 21, 20:50 UTC | May 21, 21:15 UTC | 25m |
| 2026-05-21 | SJX001 | - | May 21, 08:00 UTC | May 21, 08:45 UTC | 45m |
| 2026-05-20 | SJX002 | - | May 20, 16:20 UTC | May 21, 03:40 UTC | 11h 20m |
| 2026-05-20 | SJX851 | CTS → TPE | May 20, 10:50 UTC | May 20, 11:10 UTC | 20m |
| 2026-05-20 | SJX851 | CTS → TPE | May 20, 07:35 UTC | May 20, 10:20 UTC | 2h 45m |
| 2026-05-20 | SJX850 | TPE → CTS | May 20, 02:15 UTC | May 20, 05:35 UTC | 3h 21m |
| 2026-05-19 | SJX712 | SGN → TPE | May 19, 00:05 UTC | May 19, 08:00 UTC | 7h 55m |
| 2026-05-18 | SJX001 | - | May 18, 08:35 UTC | May 18, 22:10 UTC | 13h 34m |
| 2026-05-17 | SJX002 | - | May 17, 16:40 UTC | May 18, 03:50 UTC | 11h 10m |
| 2026-05-17 | SJX772 | SIN → TPE | May 17, 06:25 UTC | May 17, 10:35 UTC | 4h 10m |
| 2026-05-17 | SJX771 | TPE → SIN | May 17, 00:15 UTC | May 17, 01:10 UTC | 55m |
| 2026-05-16 | SJX009 | - | May 16, 19:40 UTC | May 16, 20:05 UTC | 25m |
| 2026-05-16 | SJX009 | - | May 16, 06:31 UTC | May 16, 18:30 UTC | 12h 0m |
| 2026-05-15 | SJX010 | TPE → ONT | May 15, 12:25 UTC | May 15, 23:45 UTC | 11h 19m |
| 2026-05-14 | SJX001 | - | May 14, 07:55 UTC | May 14, 21:00 UTC | 13h 5m |
| 2026-05-13 | SJX002 | - | May 13, 18:10 UTC | May 14, 05:10 UTC | 11h 0m |
| 2026-05-13 | SJX202 | MFM → TPE | May 13, 03:15 UTC | May 13, 04:25 UTC | 1h 10m |
| 2026-05-13 | SJX201 | TPE → MFM | May 13, 00:05 UTC | May 13, 01:20 UTC | 1h 15m |
| 2026-05-12 | SJX031 | SEA → TPE | May 12, 08:30 UTC | May 12, 20:10 UTC | 11h 40m |
| 2026-05-11 | SJX032 | TPE → SEA | May 11, 12:35 UTC | May 11, 22:30 UTC | 9h 56m |
| 2026-05-11 | SJX742 | BKK → TPE | May 11, 06:30 UTC | May 11, 09:45 UTC | 3h 15m |
| 2026-05-11 | SJX741 | TPE → BKK | May 11, 01:20 UTC | May 11, 04:35 UTC | 3h 15m |
| 2026-05-10 | SJX025 | PHX → TPE | May 10, 06:40 UTC | May 10, 20:40 UTC | 14h 0m |
| 2026-05-09 | SJX026 | TPE → PHX | May 9, 14:00 UTC | May 10, 00:09 UTC | 10h 10m |
| 2026-05-09 | SJX026 | TPE → PHX | May 9, 12:40 UTC | May 9, 12:50 UTC | 10m |
| 2026-05-09 | SJX742 | BKK → TPE | May 9, 06:35 UTC | May 9, 09:55 UTC | 3h 20m |
| 2026-05-09 | SJX741 | TPE → BKK | May 9, 01:35 UTC | May 9, 04:50 UTC | 3h 15m |
| 2026-05-08 | SJX772 | SIN → TPE | May 8, 09:19 UTC | May 8, 10:35 UTC | 1h 15m |
| 2026-05-08 | SJX772 | SIN → TPE | May 8, 06:35 UTC | May 8, 06:45 UTC | 10m |
| 2026-05-08 | SJX771 | TPE → SIN | May 8, 00:29 UTC | May 8, 01:35 UTC | 1h 5m |
| 2026-05-07 | SJX011 | SFO → TPE | May 7, 21:05 UTC | May 7, 21:30 UTC | 25m |
| 2026-05-07 | SJX011 | SFO → TPE | May 7, 08:40 UTC | May 7, 20:35 UTC | 11h 55m |
| 2026-05-06 | SJX012 | TPE → SFO | May 6, 16:30 UTC | May 7, 04:10 UTC | 11h 39m |
| 2026-05-06 | SJX711 | TPE → SGN | May 6, 00:01 UTC | May 6, 07:55 UTC | 7h 54m |
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 B-58510 page for operator, model, and routing details .