Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

8991DB

ICAO 24-bit transponder address · allocated to Taiwan

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

Hex
8991DB
Octal
42310733
Decimal
9,015,771
Country
TW
Tail
B-58213
Type
A21N
No current signal · last broadcast 1h ago
Flights observed
291
Distinct callsigns
20
Country
TW
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 8991DB.

Country allocation

The ICAO 24-bit address 8991DB 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
SJX303 - 12 2026-07-05
SJX307 - 11 2026-07-03
SJX785 STARLUX Airlines 10 2026-06-04
SJX761 STARLUX Airlines 10 2026-07-08
SJX786 STARLUX Airlines 9 2026-06-05
SJX714 STARLUX Airlines 9 2026-05-31
SJX205 - 8 2026-07-13
SJX835 STARLUX Airlines 7 2026-05-26
SJX315 - 7 2026-07-04
SJX314 - 7 2026-07-04
SJX306 - 7 2026-07-03
SJX718 STARLUX Airlines 6 2026-06-03
SJX711 STARLUX Airlines 6 2026-04-24
SJX332 - 6 2026-07-13
SJX313 - 6 2026-07-03
SJX310 - 6 2026-07-14
SJX309 - 6 2026-07-05
SJX308 STARLUX Airlines 6 2026-07-04
SJX206 - 6 2026-07-09
SJX782 STARLUX Airlines 5 2026-05-15

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 SJX316 - Jul 14, 07:20 UTCJul 14, 07:45 UTC25m
2026-07-14 SJX311 - Jul 14, 03:50 UTCJul 14, 05:45 UTC1h 55m
2026-07-14 SJX310 - Jul 14, 02:05 UTCJul 14, 02:25 UTC20m
2026-07-14 SJX310 - Jul 14, 00:25 UTCJul 14, 00:55 UTC30m
2026-07-13 SJX332 - Jul 13, 11:35 UTCJul 13, 12:55 UTC1h 20m
2026-07-13 SJX205 - Jul 13, 08:25 UTCJul 13, 09:35 UTC1h 10m
2026-07-13 SJX891 - Jul 13, 05:45 UTCJul 13, 06:15 UTC30m
2026-07-13 SJX890 - Jul 13, 03:30 UTCJul 13, 03:55 UTC25m
2026-07-12 SJX726 - Jul 12, 09:55 UTCJul 12, 14:20 UTC4h 25m
2026-07-12 SJX725 - Jul 12, 03:30 UTCJul 12, 07:45 UTC4h 15m
2026-07-11 SJX3704 - Jul 11, 20:50 UTCJul 11, 21:45 UTC55m
2026-07-10 SJX703 - Jul 10, 07:55 UTCJul 10, 08:40 UTC45m
2026-07-09 SJX206 - Jul 9, 13:25 UTCJul 9, 15:05 UTC1h 40m
2026-07-09 SJX205 - Jul 9, 08:20 UTCJul 9, 09:35 UTC1h 15m
2026-07-08 SJX762 - Jul 8, 07:55 UTCJul 8, 11:15 UTC3h 20m
2026-07-08 SJX761 TPE → CGK Jul 8, 04:05 UTCJul 8, 04:20 UTC15m
2026-07-07 SJX761 TPE → CGK Jul 7, 23:25 UTCJul 8, 02:30 UTC3h 5m
2026-07-07 SJX752 CNX → TPE Jul 7, 10:45 UTCJul 7, 14:10 UTC3h 25m
2026-07-07 SJX751 TPE → CNX Jul 7, 05:45 UTCJul 7, 09:05 UTC3h 20m
2026-07-07 SJX790 - Jul 7, 02:20 UTCJul 7, 04:00 UTC1h 40m
2026-07-06 SJX789 - Jul 6, 23:15 UTCJul 7, 00:55 UTC1h 40m
2026-07-06 SJX206 - Jul 6, 13:45 UTCJul 6, 15:05 UTC1h 20m
2026-07-06 SJX331 - Jul 6, 08:30 UTCJul 6, 10:00 UTC1h 30m
2026-07-06 SJX301 - Jul 6, 04:20 UTCJul 6, 06:30 UTC2h 10m
2026-07-06 SJX300 - Jul 6, 00:45 UTCJul 6, 03:00 UTC2h 15m
2026-07-05 SJX303 - Jul 5, 07:45 UTCJul 5, 08:45 UTC1h 0m
2026-07-05 SJX302 - Jul 5, 05:05 UTCJul 5, 05:35 UTC30m
2026-07-05 SJX309 - Jul 5, 01:55 UTCJul 5, 02:20 UTC25m
2026-07-04 SJX308 RMQ → SHI Jul 4, 23:20 UTCJul 4, 23:45 UTC25m
2026-07-04 SJX315 - Jul 4, 07:55 UTCJul 4, 10:50 UTC2h 55m
2026-07-04 SJX314 - Jul 4, 01:30 UTCJul 4, 04:25 UTC2h 55m
2026-07-03 SJX313 - Jul 3, 12:10 UTCJul 3, 12:35 UTC25m
2026-07-03 SJX312 - Jul 3, 09:50 UTCJul 3, 10:00 UTC10m
2026-07-03 SJX312 - Jul 3, 08:50 UTCJul 3, 09:15 UTC25m
2026-07-03 SJX307 - Jul 3, 04:35 UTCJul 3, 07:05 UTC2h 30m
2026-07-03 SJX306 - Jul 3, 00:55 UTCJul 3, 03:15 UTC2h 20m
2026-07-02 SJX313 - Jul 2, 11:20 UTCJul 2, 12:25 UTC1h 5m
2026-07-02 SJX312 - Jul 2, 08:50 UTCJul 2, 09:55 UTC1h 5m
2026-07-02 SJX307 - Jul 2, 06:45 UTCJul 2, 07:20 UTC35m
2026-07-02 SJX307 - Jul 2, 04:45 UTCJul 2, 05:20 UTC35m
2026-07-02 SJX306 - Jul 2, 01:05 UTCJul 2, 03:35 UTC2h 30m
2026-07-01 SJX313 - Jul 1, 08:50 UTCJul 1, 12:35 UTC3h 45m
2026-07-01 SJX307 - Jul 1, 04:45 UTCJul 1, 07:10 UTC2h 25m
2026-07-01 SJX306 - Jul 1, 01:05 UTCJul 1, 03:25 UTC2h 20m
2026-06-30 SJX317 - Jun 30, 07:15 UTCJun 30, 12:15 UTC5h 0m
2026-06-30 SJX311 PUS → RMQ Jun 30, 03:40 UTCJun 30, 05:45 UTC2h 5m
2026-06-30 SJX310 RMQ → PUS Jun 30, 01:50 UTCJun 30, 02:10 UTC20m
2026-06-30 SJX310 RMQ → PUS Jun 30, 00:20 UTCJun 30, 00:49 UTC30m
2026-06-29 SJX315 - Jun 29, 07:05 UTCJun 29, 10:15 UTC3h 10m
2026-06-29 SJX314 RMQ → NRT Jun 29, 01:44 UTCJun 29, 04:50 UTC3h 5m

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

Mode-S 8991DB frequently asked

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