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