sensors Mode-S transponder

8991DD

ICAO 24-bit transponder address · allocated to Taiwan

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

Hex
8991DD
Octal
42310735
Decimal
9,015,773
Country
TW
Tail
B-58302
Type
A339
No current signal · last broadcast 3h ago
Flights observed
337
Distinct callsigns
20
Country
TW
Last broadcast
3h ago

Last known position

Most recent position reported by Mode-S 8991DD.

Country allocation

The ICAO 24-bit address 8991DD 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 - 28 2026-07-08
SJX841 - 26 2026-07-10
SJX862 - 24 2026-07-08
SJX805 - 23 2026-07-12
SJX840 - 21 2026-07-10
SJX839 - 21 2026-06-15
SJX847 - 15 2026-06-15
SJX838 - 15 2026-06-15
SJX804 - 15 2026-07-12
SJX233 - 15 2026-07-12
SJX821 - 14 2026-07-01
SJX846 STARLUX Airlines 13 2026-06-14
SJX820 - 13 2026-07-01
SJX235 - 13 2026-06-23
SJX234 - 12 2026-07-12
SJX201 - 10 2026-06-18
SJX236 - 9 2026-06-23
SJX205 - 9 2026-07-05
SJX206 - 8 2026-07-05
SJX202 - 7 2026-06-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 SJX714 - Jul 14, 06:50 UTCJul 14, 14:55 UTC8h 5m
2026-07-13 SJX711 - Jul 13, 00:01 UTCJul 13, 07:55 UTC7h 55m
2026-07-12 SJX805 NRT → TPE Jul 12, 12:30 UTCJul 12, 15:30 UTC3h 0m
2026-07-12 SJX804 TPE → NRT Jul 12, 07:10 UTCJul 12, 10:15 UTC3h 5m
2026-07-12 SJX234 - Jul 12, 04:45 UTCJul 12, 05:20 UTC35m
2026-07-12 SJX234 - Jul 12, 03:50 UTCJul 12, 04:10 UTC20m
2026-07-12 SJX233 TPE → HKG Jul 12, 00:45 UTCJul 12, 02:01 UTC1h 15m
2026-07-10 SJX841 - Jul 10, 05:55 UTCJul 10, 08:00 UTC2h 5m
2026-07-10 SJX840 - Jul 10, 01:55 UTCJul 10, 03:35 UTC1h 40m
2026-07-09 SJX841 - Jul 9, 07:00 UTCJul 9, 07:30 UTC30m
2026-07-09 SJX841 - Jul 9, 05:35 UTCJul 9, 05:45 UTC10m
2026-07-09 SJX840 - Jul 9, 03:30 UTCJul 9, 03:55 UTC25m
2026-07-09 SJX840 - Jul 9, 02:10 UTCJul 9, 02:35 UTC25m
2026-07-08 SJX863 - Jul 8, 08:40 UTCJul 8, 11:25 UTC2h 45m
2026-07-08 SJX862 - Jul 8, 03:50 UTCJul 8, 06:35 UTC2h 45m
2026-07-07 SJX863 - Jul 7, 11:15 UTCJul 7, 11:35 UTC20m
2026-07-07 SJX863 - Jul 7, 08:45 UTCJul 7, 10:00 UTC1h 15m
2026-07-07 SJX862 - Jul 7, 05:15 UTCJul 7, 06:20 UTC1h 5m
2026-07-07 SJX862 - Jul 7, 03:40 UTCJul 7, 03:55 UTC15m
2026-07-06 SJX712 TPE → TPE Jul 6, 00:05 UTCJul 6, 08:00 UTC7h 55m
2026-07-05 SJX206 - Jul 5, 13:20 UTCJul 5, 14:40 UTC1h 20m
2026-07-05 SJX205 - Jul 5, 10:00 UTCJul 5, 11:20 UTC1h 20m
2026-07-05 SJX841 - Jul 5, 07:10 UTCJul 5, 07:35 UTC25m
2026-07-05 SJX841 - Jul 5, 05:40 UTCJul 5, 06:05 UTC25m
2026-07-05 SJX840 - Jul 5, 03:30 UTCJul 5, 03:40 UTC10m
2026-07-05 SJX840 - Jul 5, 02:00 UTCJul 5, 02:20 UTC20m
2026-07-04 SJX841 - Jul 4, 07:05 UTCJul 4, 07:20 UTC15m
2026-07-04 SJX841 - Jul 4, 05:35 UTCJul 4, 05:55 UTC20m
2026-07-04 SJX840 - Jul 4, 03:30 UTCJul 4, 03:45 UTC15m
2026-07-04 SJX840 - Jul 4, 02:05 UTCJul 4, 02:20 UTC15m
2026-07-03 SJX712 TPE → TPE Jul 3, 00:15 UTCJul 3, 08:00 UTC7h 45m
2026-07-02 SJX841 - Jul 2, 07:45 UTCJul 2, 08:10 UTC25m
2026-07-02 SJX840 - Jul 2, 03:50 UTCJul 2, 04:00 UTC10m
2026-07-02 SJX840 - Jul 2, 02:25 UTCJul 2, 02:55 UTC30m
2026-07-01 SJX821 - Jul 1, 06:40 UTCJul 1, 07:10 UTC30m
2026-07-01 SJX821 - Jul 1, 04:45 UTCJul 1, 05:20 UTC35m
2026-07-01 SJX820 - Jul 1, 00:55 UTCJul 1, 03:05 UTC2h 10m
2026-06-30 SJX711 - Jun 30, 00:04 UTCJun 30, 08:05 UTC8h 1m
2026-06-29 SJX863 - Jun 29, 09:00 UTCJun 29, 12:05 UTC3h 5m
2026-06-29 SJX862 - Jun 29, 05:15 UTCJun 29, 06:19 UTC1h 5m
2026-06-29 SJX862 - Jun 29, 03:44 UTCJun 29, 04:00 UTC15m
2026-06-27 SJX712 TPE → TPE Jun 27, 23:55 UTCJun 28, 08:00 UTC8h 5m
2026-06-27 SJX863 - Jun 27, 11:50 UTCJun 27, 12:19 UTC30m
2026-06-27 SJX863 - Jun 27, 09:00 UTCJun 27, 10:19 UTC1h 20m
2026-06-27 SJX862 - Jun 27, 03:55 UTCJun 27, 06:30 UTC2h 35m
2026-06-26 265 - Jun 26, 11:34 UTCJun 26, 11:55 UTC20m
2026-06-26 265 - Jun 26, 08:45 UTCJun 26, 10:05 UTC1h 20m
2026-06-26 SJX862 - Jun 26, 05:05 UTCJun 26, 06:29 UTC1h 25m
2026-06-26 SJX862 - Jun 26, 03:54 UTCJun 26, 04:10 UTC15m
2026-06-25 SJX863 - Jun 25, 11:39 UTCJun 25, 11:54 UTC15m

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-58302 page for operator, model, and routing details .

Mode-S 8991DD frequently asked

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