Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

8991DC

ICAO 24-bit transponder address · allocated to Taiwan

Currently assigned to B-58301 · AIRBUS A-330-900

Hex
8991DC
Octal
42310734
Decimal
9,015,772
Country
TW
Tail
B-58301
Type
A339
Broadcasting now · callsign SJX711 · 38,000 ft
Flights observed
319
Distinct callsigns
20
Country
TW
Last broadcast
48m ago

Current position

8991DC is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 8991DC 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
SJX863 - 36 2026-06-24
SJX862 - 32 2026-06-24
SJX841 - 21 2026-07-06
SJX805 - 21 2026-07-04
SJX804 - 18 2026-07-10
SJX235 - 17 2026-07-09
SJX840 - 15 2026-07-06
SJX236 - 13 2026-07-09
SJX821 - 12 2026-07-09
SJX820 - 12 2026-07-09
SJX233 - 11 2026-07-10
SJX839 STARLUX Airlines 10 2026-06-06
SJX202 - 9 2026-07-13
SJX746 - 8 2026-07-12
SJX745 - 8 2026-07-12
SJX234 - 8 2026-07-10
SJX201 - 8 2026-07-13
SJX847 STARLUX Airlines 7 2026-06-06
SJX838 STARLUX Airlines 7 2026-06-06
SJX711 - 7 2026-07-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 SJX711 - Jul 14, 00:50 UTCJul 14, 01:00 UTC10m
2026-07-13 SJX713 TPE → TPE Jul 13, 06:35 UTCJul 13, 14:45 UTC8h 10m
2026-07-13 SJX202 - Jul 13, 03:20 UTCJul 13, 04:40 UTC1h 20m
2026-07-13 SJX201 - Jul 13, 00:20 UTCJul 13, 01:30 UTC1h 10m
2026-07-12 SJX746 - Jul 12, 13:40 UTCJul 12, 14:45 UTC1h 5m
2026-07-12 SJX746 - Jul 12, 11:15 UTCJul 12, 11:30 UTC15m
2026-07-12 SJX745 - Jul 12, 09:10 UTCJul 12, 09:20 UTC10m
2026-07-12 SJX745 - Jul 12, 06:10 UTCJul 12, 06:55 UTC45m
2026-07-12 SJX3805 NRT → TPE Jul 12, 01:20 UTCJul 12, 04:10 UTC2h 50m
2026-07-10 SJX804 TPE → NRT Jul 10, 07:30 UTCJul 10, 10:25 UTC2h 55m
2026-07-10 SJX234 HKG → TPE Jul 10, 04:25 UTCJul 10, 05:50 UTC1h 25m
2026-07-10 SJX233 TPE → HKG Jul 10, 01:20 UTCJul 10, 02:40 UTC1h 20m
2026-07-09 SJX236 HKG → TPE Jul 9, 13:00 UTCJul 9, 14:45 UTC1h 45m
2026-07-09 SJX235 - Jul 9, 09:20 UTCJul 9, 10:35 UTC1h 15m
2026-07-09 SJX821 KIX → TPE Jul 9, 04:55 UTCJul 9, 07:15 UTC2h 20m
2026-07-09 SJX820 TPE → KIX Jul 9, 01:10 UTCJul 9, 03:30 UTC2h 20m
2026-07-08 SJX712 TPE → TPE Jul 8, 00:10 UTCJul 8, 08:00 UTC7h 50m
2026-07-07 SJX712 TPE → TPE Jul 7, 00:00 UTCJul 7, 08:20 UTC8h 20m
2026-07-06 SJX841 - Jul 6, 07:10 UTCJul 6, 07:35 UTC25m
2026-07-06 SJX841 - Jul 6, 05:45 UTCJul 6, 05:55 UTC10m
2026-07-06 SJX840 - Jul 6, 01:50 UTCJul 6, 03:30 UTC1h 40m
2026-07-05 SJX711 TPE → TPE Jul 5, 00:05 UTCJul 5, 08:05 UTC8h 0m
2026-07-04 SJX805 - Jul 4, 15:05 UTCJul 4, 15:20 UTC15m
2026-07-04 SJX805 - Jul 4, 12:20 UTCJul 4, 13:40 UTC1h 20m
2026-07-04 SJX804 - Jul 4, 08:55 UTCJul 4, 10:15 UTC1h 20m
2026-07-04 SJX804 - Jul 4, 07:20 UTCJul 4, 07:35 UTC15m
2026-07-04 SJX234 HKG → TPE Jul 4, 03:45 UTCJul 4, 05:15 UTC1h 30m
2026-07-04 SJX233 - Jul 4, 01:30 UTCJul 4, 01:50 UTC20m
2026-07-04 SJX233 - Jul 4, 00:30 UTCJul 4, 00:55 UTC25m
2026-07-03 SJX236 - Jul 3, 14:05 UTCJul 3, 14:35 UTC30m
2026-07-03 SJX236 - Jul 3, 13:15 UTCJul 3, 13:35 UTC20m
2026-07-03 SJX235 - Jul 3, 10:15 UTCJul 3, 10:30 UTC15m
2026-07-03 SJX235 - Jul 3, 09:10 UTCJul 3, 09:30 UTC20m
2026-07-03 SJX821 KIX → TPE Jul 3, 04:50 UTCJul 3, 07:20 UTC2h 30m
2026-07-03 SJX820 TPE → KIX Jul 3, 00:45 UTCJul 3, 03:10 UTC2h 25m
2026-07-02 SJX746 - Jul 2, 11:25 UTCJul 2, 14:55 UTC3h 30m
2026-07-02 SJX745 - Jul 2, 06:25 UTCJul 2, 09:30 UTC3h 5m
2026-07-02 SJX202 - Jul 2, 03:40 UTCJul 2, 05:00 UTC1h 20m
2026-07-02 SJX201 - Jul 2, 01:25 UTCJul 2, 02:00 UTC35m
2026-07-02 SJX201 - Jul 2, 00:30 UTCJul 2, 00:55 UTC25m
2026-07-01 SJX746 - Jul 1, 13:50 UTCJul 1, 14:45 UTC55m
2026-07-01 SJX746 - Jul 1, 11:20 UTCJul 1, 11:40 UTC20m
2026-07-01 SJX745 - Jul 1, 09:20 UTCJul 1, 09:30 UTC10m
2026-07-01 SJX745 - Jul 1, 06:20 UTCJul 1, 07:05 UTC45m
2026-07-01 SJX202 - Jul 1, 03:10 UTCJul 1, 04:35 UTC1h 25m
2026-07-01 SJX201 - Jul 1, 00:20 UTCJul 1, 01:30 UTC1h 10m
2026-06-30 SJX236 - Jun 30, 12:40 UTCJun 30, 14:05 UTC1h 25m
2026-06-30 SJX235 - Jun 30, 10:20 UTCJun 30, 10:40 UTC20m
2026-06-30 SJX235 - Jun 30, 09:15 UTCJun 30, 09:50 UTC35m
2026-06-30 SJX821 - Jun 30, 04:50 UTCJun 30, 07:15 UTC2h 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-58301 page for operator, model, and routing details .

Mode-S 8991DC frequently asked

What is Mode-S code 8991DC?
8991DC is an ICAO 24-bit transponder address. Allocated to Taiwan. Assigned to B-58301.
Where is Mode-S 8991DC registered?
Mode-S code 8991DC is allocated to Taiwan (TW). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 8991DC broadcasting right now?
Yes. Mode-S 8991DC is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 8991DC, octal 42310734, decimal 9,015,772.
What flights does 8991DC operate?
Mode-S 8991DC has broadcast 20 distinct callsigns, including SJX863, SJX862, SJX841, SJX805, SJX804.