sensors Mode-S transponder
8990C1
ICAO 24-bit transponder address · allocated to Taiwan
Currently assigned to B-58507 · AIRBUS A-350-900
- Hex
- 8990C1
- Octal
- 42310301
- Decimal
- 9,015,489
- Country
- TW
- Tail
- B-58507
- Type
- A359
- Flights observed
- 128
- Distinct callsigns
- 20
- Country
- TW
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 8990C1 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 |
|---|---|---|---|
| SJX025 | STARLUX Airlines | 18 | 2026-05-20 |
| SJX026 | STARLUX Airlines | 15 | 2026-05-19 |
| SJX742 | STARLUX Airlines | 10 | 2026-05-29 |
| SJX741 | STARLUX Airlines | 10 | 2026-05-29 |
| SJX823 | STARLUX Airlines | 8 | 2026-05-19 |
| SJX032 | STARLUX Airlines | 8 | 2026-05-29 |
| SJX001 | - | 8 | 2026-05-22 |
| SJX031 | STARLUX Airlines | 7 | 2026-05-30 |
| SJX771 | STARLUX Airlines | 6 | 2026-05-14 |
| SJX002 | - | 6 | 2026-05-21 |
| SJX772 | STARLUX Airlines | 5 | 2026-05-14 |
| SJX011 | STARLUX Airlines | 4 | 2026-05-28 |
| SJX871 | STARLUX Airlines | 3 | 2026-04-21 |
| SJX822 | STARLUX Airlines | 3 | 2026-05-19 |
| SJX870 | STARLUX Airlines | 2 | 2026-04-21 |
| SJX821 | STARLUX Airlines | 2 | 2026-04-28 |
| SJX803 | STARLUX Airlines | 2 | 2026-05-08 |
| SJX802 | STARLUX Airlines | 2 | 2026-05-08 |
| SJX012 | STARLUX Airlines | 2 | 2026-05-27 |
| SJX820 | STARLUX Airlines | 1 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | SJX031 | SEA → TPE | May 30, 08:25 UTC | May 30, 09:05 UTC | 40m |
| 2026-05-29 | SJX032 | TPE → SEA | May 29, 14:00 UTC | May 29, 23:05 UTC | 9h 5m |
| 2026-05-29 | SJX032 | TPE → SEA | May 29, 12:35 UTC | May 29, 12:55 UTC | 20m |
| 2026-05-29 | SJX742 | BKK → TPE | May 29, 06:30 UTC | May 29, 09:50 UTC | 3h 20m |
| 2026-05-29 | SJX741 | TPE → BKK | May 29, 01:30 UTC | May 29, 04:40 UTC | 3h 10m |
| 2026-05-28 | SJX011 | SFO → TPE | May 28, 08:15 UTC | May 28, 21:10 UTC | 12h 55m |
| 2026-05-27 | SJX012 | TPE → SFO | May 27, 16:25 UTC | May 28, 03:45 UTC | 11h 20m |
| 2026-05-26 | SJX009 | - | May 26, 06:34 UTC | May 26, 20:20 UTC | 13h 45m |
| 2026-05-25 | SJX010 | TPE → ONT | May 25, 12:30 UTC | May 26, 00:04 UTC | 11h 34m |
| 2026-05-24 | SJX031 | SEA → TPE | May 24, 08:35 UTC | May 24, 20:30 UTC | 11h 55m |
| 2026-05-23 | SJX032 | TPE → SEA | May 23, 12:35 UTC | May 23, 22:45 UTC | 10h 11m |
| 2026-05-23 | SJX742 | BKK → TPE | May 23, 06:35 UTC | May 23, 09:55 UTC | 3h 20m |
| 2026-05-23 | SJX741 | TPE → BKK | May 23, 01:35 UTC | May 23, 04:45 UTC | 3h 9m |
| 2026-05-22 | SJX001 | - | May 22, 07:55 UTC | May 22, 21:00 UTC | 13h 5m |
| 2026-05-21 | SJX002 | - | May 21, 18:40 UTC | May 22, 03:55 UTC | 9h 15m |
| 2026-05-21 | SJX002 | - | May 21, 16:45 UTC | May 21, 17:00 UTC | 15m |
| 2026-05-20 | SJX025 | PHX → TPE | May 20, 20:30 UTC | May 20, 20:50 UTC | 20m |
| 2026-05-20 | SJX025 | PHX → TPE | May 20, 06:45 UTC | May 20, 20:00 UTC | 13h 15m |
| 2026-05-19 | SJX026 | TPE → PHX | May 19, 12:25 UTC | May 20, 00:35 UTC | 12h 10m |
| 2026-05-19 | SJX823 | KIX → TPE | May 19, 08:30 UTC | May 19, 08:45 UTC | 15m |
| 2026-05-19 | SJX823 | KIX → TPE | May 19, 06:35 UTC | May 19, 07:10 UTC | 35m |
| 2026-05-19 | SJX822 | TPE → KIX | May 19, 02:35 UTC | May 19, 05:00 UTC | 2h 25m |
| 2026-05-18 | SJX031 | SEA → TPE | May 18, 08:35 UTC | May 18, 20:15 UTC | 11h 39m |
| 2026-05-17 | SJX032 | TPE → SEA | May 17, 14:10 UTC | May 17, 22:55 UTC | 8h 45m |
| 2026-05-17 | SJX032 | TPE → SEA | May 17, 12:35 UTC | May 17, 12:50 UTC | 15m |
| 2026-05-17 | SJX742 | BKK → TPE | May 17, 06:55 UTC | May 17, 10:25 UTC | 3h 30m |
| 2026-05-17 | SJX741 | TPE → BKK | May 17, 02:05 UTC | May 17, 05:15 UTC | 3h 10m |
| 2026-05-16 | SJX001 | - | May 16, 21:05 UTC | May 16, 21:35 UTC | 30m |
| 2026-05-16 | SJX001 | - | May 16, 08:01 UTC | May 16, 19:50 UTC | 11h 50m |
| 2026-05-15 | SJX002 | - | May 15, 16:55 UTC | May 16, 04:10 UTC | 11h 15m |
| 2026-05-15 | SJX823 | KIX → TPE | May 15, 08:20 UTC | May 15, 09:00 UTC | 40m |
| 2026-05-15 | SJX823 | KIX → TPE | May 15, 06:25 UTC | May 15, 06:55 UTC | 30m |
| 2026-05-15 | SJX822 | TPE → KIX | May 15, 02:35 UTC | May 15, 04:50 UTC | 2h 15m |
| 2026-05-14 | SJX772 | SIN → TPE | May 14, 06:30 UTC | May 14, 10:35 UTC | 4h 5m |
| 2026-05-14 | SJX771 | TPE → SIN | May 14, 00:55 UTC | May 14, 01:55 UTC | 1h 0m |
| 2026-05-13 | SJX025 | PHX → TPE | May 13, 06:40 UTC | May 13, 20:10 UTC | 13h 30m |
| 2026-05-12 | SJX026 | TPE → PHX | May 12, 12:25 UTC | May 13, 00:10 UTC | 11h 45m |
| 2026-05-12 | SJX742 | BKK → TPE | May 12, 06:35 UTC | May 12, 09:45 UTC | 3h 10m |
| 2026-05-12 | SJX741 | TPE → BKK | May 12, 03:55 UTC | May 12, 04:35 UTC | 40m |
| 2026-05-11 | SJX025 | PHX → TPE | May 11, 06:40 UTC | May 11, 20:30 UTC | 13h 50m |
| 2026-05-10 | SJX026 | TPE → PHX | May 10, 12:30 UTC | May 11, 00:25 UTC | 11h 55m |
| 2026-05-10 | SJX742 | BKK → TPE | May 10, 06:30 UTC | May 10, 09:40 UTC | 3h 10m |
| 2026-05-10 | SJX741 | TPE → BKK | May 10, 01:20 UTC | May 10, 04:29 UTC | 3h 10m |
| 2026-05-09 | SJX001 | - | May 9, 07:55 UTC | May 9, 21:55 UTC | 14h 0m |
| 2026-05-08 | SJX002 | - | May 8, 16:30 UTC | May 9, 03:35 UTC | 11h 5m |
| 2026-05-08 | SJX803 | NRT → TPE | May 8, 11:05 UTC | May 8, 11:34 UTC | 30m |
| 2026-05-08 | SJX803 | NRT → TPE | May 8, 08:19 UTC | May 8, 09:34 UTC | 1h 15m |
| 2026-05-08 | SJX802 | TPE → NRT | May 8, 04:34 UTC | May 8, 05:49 UTC | 1h 15m |
| 2026-05-08 | SJX802 | TPE → NRT | May 8, 03:09 UTC | May 8, 03:24 UTC | 15m |
| 2026-05-07 | SJX711 | TPE → SGN | May 7, 00:00 UTC | May 7, 07:55 UTC | 7h 55m |
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-58507 page for operator, model, and routing details .