sensors Mode-S transponder

8991D6

ICAO 24-bit transponder address · allocated to Taiwan

Currently assigned to B-58208 · AIRBUS A-321neo

Hex
8991D6
Octal
42310726
Decimal
9,015,766
Country
TW
Tail
B-58208
Type
A21N
No current signal · last broadcast 5h ago
Flights observed
307
Distinct callsigns
20
Country
TW
Last broadcast
5h ago

Last known position

Most recent position reported by Mode-S 8991D6.

Country allocation

The ICAO 24-bit address 8991D6 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
SJX331 - 15 2026-06-25
SJX726 - 14 2026-06-29
SJX332 - 14 2026-06-24
SJX861 - 13 2026-07-08
SJX303 - 13 2026-07-14
SJX860 - 12 2026-07-08
SJX301 - 12 2026-06-25
SJX725 - 11 2026-06-29
SJX302 - 11 2026-07-14
SJX300 - 11 2026-06-25
SJX315 - 9 2026-06-18
SJX313 - 9 2026-07-12
SJX307 - 9 2026-06-23
SJX835 STARLUX Airlines 8 2026-06-09
SJX314 - 8 2026-06-18
SJX306 - 8 2026-06-23
SJX715 - 6 2026-06-26
SJX309 - 6 2026-07-12
SJX308 - 6 2026-07-11
SJX834 STARLUX Airlines 5 2026-06-09

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 SJX303 - Jul 14, 08:05 UTCJul 14, 09:05 UTC1h 0m
2026-07-14 SJX302 - Jul 14, 05:25 UTCJul 14, 05:55 UTC30m
2026-07-13 SJX317 - Jul 13, 10:35 UTCJul 13, 12:35 UTC2h 0m
2026-07-13 SJX316 - Jul 13, 07:15 UTCJul 13, 07:50 UTC35m
2026-07-13 SJX330 - Jul 13, 03:40 UTCJul 13, 04:50 UTC1h 10m
2026-07-13 SJX329 - Jul 13, 00:50 UTCJul 13, 01:50 UTC1h 0m
2026-07-12 SJX313 - Jul 12, 12:25 UTCJul 12, 13:25 UTC1h 0m
2026-07-12 SJX312 - Jul 12, 09:45 UTCJul 12, 10:55 UTC1h 10m
2026-07-12 SJX303 - Jul 12, 07:10 UTCJul 12, 08:10 UTC1h 0m
2026-07-12 SJX302 - Jul 12, 04:30 UTCJul 12, 05:35 UTC1h 5m
2026-07-12 SJX309 - Jul 12, 01:50 UTCJul 12, 02:25 UTC35m
2026-07-11 SJX308 - Jul 11, 23:25 UTCJul 11, 23:50 UTC25m
2026-07-09 SJX313 - Jul 9, 09:10 UTCJul 9, 10:10 UTC1h 0m
2026-07-09 SJX312 - Jul 9, 06:20 UTCJul 9, 06:45 UTC25m
2026-07-09 SJX2523 - Jul 9, 03:55 UTCJul 9, 04:15 UTC20m
2026-07-08 SJX861 - Jul 8, 11:50 UTCJul 8, 12:20 UTC30m
2026-07-08 SJX861 - Jul 8, 08:55 UTCJul 8, 10:40 UTC1h 45m
2026-07-08 SJX860 - Jul 8, 05:55 UTCJul 8, 07:40 UTC1h 45m
2026-07-08 SJX860 - Jul 8, 04:20 UTCJul 8, 04:40 UTC20m
2026-07-07 SJX704 TPE → TPE Jul 7, 08:10 UTCJul 7, 14:55 UTC6h 45m
2026-07-06 SJX792 - Jul 6, 13:00 UTCJul 6, 14:35 UTC1h 35m
2026-07-06 SJX791 - Jul 6, 09:55 UTCJul 6, 11:30 UTC1h 35m
2026-07-06 SJX1901 PUS → TPE Jul 6, 06:40 UTCJul 6, 08:35 UTC1h 55m
2026-07-06 SJX1900 - Jul 6, 04:50 UTCJul 6, 05:15 UTC25m
2026-07-06 SJX1900 - Jul 6, 03:25 UTCJul 6, 03:50 UTC25m
2026-07-05 SJX792 - Jul 5, 13:05 UTCJul 5, 14:50 UTC1h 45m
2026-07-05 SJX791 TPE → CRK Jul 5, 09:35 UTCJul 5, 11:10 UTC1h 35m
2026-07-05 SJX901 PUS → TPE Jul 5, 06:10 UTCJul 5, 08:10 UTC2h 0m
2026-07-05 SJX900 TPE → PUS Jul 5, 03:00 UTCJul 5, 04:45 UTC1h 45m
2026-07-04 SJX762 - Jul 4, 07:55 UTCJul 4, 11:20 UTC3h 25m
2026-07-04 SJX761 TPE → CGK Jul 4, 04:10 UTCJul 4, 04:30 UTC20m
2026-07-03 SJX761 TPE → CGK Jul 3, 23:35 UTCJul 4, 02:45 UTC3h 10m
2026-07-03 SJX703 TPE → TPE Jul 3, 08:15 UTCJul 3, 14:40 UTC6h 25m
2026-07-02 SJX752 - Jul 2, 10:20 UTCJul 2, 13:45 UTC3h 25m
2026-07-02 SJX751 - Jul 2, 05:40 UTCJul 2, 08:45 UTC3h 5m
2026-07-01 SJX861 - Jul 1, 12:15 UTCJul 1, 12:40 UTC25m
2026-07-01 SJX861 - Jul 1, 09:15 UTCJul 1, 10:50 UTC1h 35m
2026-07-01 SJX860 - Jul 1, 04:40 UTCJul 1, 07:50 UTC3h 10m
2026-06-30 SJX861 - Jun 30, 08:55 UTCJun 30, 12:25 UTC3h 30m
2026-06-30 SJX860 - Jun 30, 06:00 UTCJun 30, 07:40 UTC1h 40m
2026-06-30 SJX860 - Jun 30, 04:30 UTCJun 30, 04:40 UTC10m
2026-06-29 SJX726 - Jun 29, 10:04 UTCJun 29, 14:29 UTC4h 25m
2026-06-29 SJX725 - Jun 29, 07:15 UTCJun 29, 07:59 UTC45m
2026-06-29 SJX725 - Jun 29, 03:39 UTCJun 29, 04:34 UTC55m
2026-06-28 SJX714 TPE → TPE Jun 28, 06:30 UTCJun 28, 14:34 UTC8h 5m
2026-06-27 SJX726 - Jun 27, 12:45 UTCJun 27, 14:14 UTC1h 30m
2026-06-27 SJX726 - Jun 27, 09:34 UTCJun 27, 09:44 UTC10m
2026-06-27 SJX725 - Jun 27, 03:34 UTCJun 27, 07:45 UTC4h 10m
2026-06-26 SJX716 - Jun 26, 06:39 UTCJun 26, 07:05 UTC25m
2026-06-26 SJX716 - Jun 26, 04:39 UTCJun 26, 06:04 UTC1h 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 B-58208 page for operator, model, and routing details .

Mode-S 8991D6 frequently asked

What is Mode-S code 8991D6?
8991D6 is an ICAO 24-bit transponder address. Allocated to Taiwan. Assigned to B-58208.
Where is Mode-S 8991D6 registered?
Mode-S code 8991D6 is allocated to Taiwan (TW). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 8991D6 broadcasting right now?
No active broadcast right now. Last signal was 5h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 8991D6, octal 42310726, decimal 9,015,766.
What flights does 8991D6 operate?
Mode-S 8991D6 has broadcast 20 distinct callsigns, including SJX331, SJX726, SJX332, SJX861, SJX303.