Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

89912A

ICAO 24-bit transponder address · allocated to Taiwan

Hex
89912A
Octal
42310452
Decimal
9,015,594
Country
TW
Broadcasting now · callsign SJX802 · 11,125 ft
Flights observed
45
Distinct callsigns
8
Country
TW
Last broadcast
Jul 26, 15:45 UTC

Current position

89912A is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 89912A 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 8 distinct

Callsign Airline Flights Last seen
SJX800 STARLUX Airlines 12 2026-07-26
SJX801 STARLUX Airlines 11 2026-07-26
SJX803 STARLUX Airlines 9 2026-07-23
SJX802 STARLUX Airlines 7 2026-07-23
SJX026 STARLUX Airlines 2 2026-07-26
SJX025 - 2 2026-07-15
SJX2351 - 1 2026-07-04
AIB791 - 1 2026-07-04

Recent flights last 45

DateFlightRouteTakeoffLandingDuration
2026-07-26 SJX026 TPE → PHX Jul 26, 12:45 UTCJul 26, 15:45 UTC3h 0m
2026-07-26 SJX801 NRT → TPE Jul 26, 05:40 UTCJul 26, 08:35 UTC2h 56m
2026-07-26 SJX800 TPE → NRT Jul 26, 00:55 UTCJul 26, 03:45 UTC2h 50m
2026-07-25 SJX801 NRT → TPE Jul 25, 08:10 UTCJul 25, 08:25 UTC15m
2026-07-25 SJX801 NRT → TPE Jul 25, 05:35 UTCJul 25, 06:50 UTC1h 15m
2026-07-25 SJX800 TPE → NRT Jul 25, 02:25 UTCJul 25, 03:40 UTC1h 15m
2026-07-25 SJX800 TPE → NRT Jul 25, 00:50 UTCJul 25, 01:10 UTC20m
2026-07-24 SJX801 NRT → TPE Jul 24, 06:00 UTCJul 24, 08:55 UTC2h 55m
2026-07-24 SJX800 TPE → NRT Jul 24, 02:40 UTCJul 24, 04:05 UTC1h 25m
2026-07-24 SJX800 TPE → NRT Jul 24, 01:15 UTCJul 24, 01:25 UTC10m
2026-07-23 SJX803 NRT → TPE Jul 23, 10:25 UTCJul 23, 10:45 UTC20m
2026-07-23 SJX803 NRT → TPE Jul 23, 07:55 UTCJul 23, 09:10 UTC1h 15m
2026-07-23 SJX802 TPE → NRT Jul 23, 04:45 UTCJul 23, 06:10 UTC1h 25m
2026-07-23 SJX802 TPE → NRT Jul 23, 03:10 UTCJul 23, 03:25 UTC15m
2026-07-22 SJX800 TPE → NRT Jul 22, 02:45 UTCJul 22, 04:00 UTC1h 15m
2026-07-22 SJX800 TPE → NRT Jul 22, 01:10 UTCJul 22, 01:25 UTC15m
2026-07-21 SJX803 NRT → TPE Jul 21, 11:00 UTCJul 21, 11:20 UTC20m
2026-07-21 SJX803 NRT → TPE Jul 21, 08:30 UTCJul 21, 09:50 UTC1h 20m
2026-07-21 SJX802 TPE → NRT Jul 21, 04:50 UTCJul 21, 06:20 UTC1h 30m
2026-07-21 SJX802 TPE → NRT Jul 21, 03:20 UTCJul 21, 03:30 UTC10m
2026-07-20 SJX803 NRT → TPE Jul 20, 10:25 UTCJul 20, 10:55 UTC30m
2026-07-20 SJX803 NRT → TPE Jul 20, 08:00 UTCJul 20, 09:20 UTC1h 20m
2026-07-20 SJX802 TPE → NRT Jul 20, 03:15 UTCJul 20, 06:15 UTC3h 0m
2026-07-19 SJX803 NRT → TPE Jul 19, 07:55 UTCJul 19, 10:45 UTC2h 50m
2026-07-19 SJX802 TPE → NRT Jul 19, 03:00 UTCJul 19, 05:55 UTC2h 55m
2026-07-18 SJX803 - Jul 18, 10:35 UTCJul 18, 10:50 UTC15m
2026-07-18 SJX803 - Jul 18, 08:15 UTCJul 18, 09:30 UTC1h 15m
2026-07-18 SJX802 - Jul 18, 03:15 UTCJul 18, 06:25 UTC3h 10m
2026-07-17 SJX801 - Jul 17, 08:00 UTCJul 17, 08:30 UTC30m
2026-07-17 SJX801 - Jul 17, 05:45 UTCJul 17, 07:05 UTC1h 20m
2026-07-17 SJX800 TPE → NRT Jul 17, 00:45 UTCJul 17, 03:50 UTC3h 5m
2026-07-16 SJX801 - Jul 16, 08:15 UTCJul 16, 08:30 UTC15m
2026-07-16 SJX801 - Jul 16, 05:45 UTCJul 16, 07:00 UTC1h 15m
2026-07-16 SJX800 TPE → NRT Jul 16, 01:10 UTCJul 16, 04:05 UTC2h 55m
2026-07-15 SJX025 - Jul 15, 20:10 UTCJul 15, 20:30 UTC20m
2026-07-15 SJX025 - Jul 15, 07:10 UTCJul 15, 19:05 UTC11h 55m
2026-07-14 SJX026 TPE → PHX Jul 14, 12:40 UTCJul 15, 01:30 UTC12h 49m
2026-07-14 SJX801 NRT → TPE Jul 14, 05:55 UTCJul 14, 08:35 UTC2h 40m
2026-07-14 SJX800 - Jul 14, 01:10 UTCJul 14, 04:05 UTC2h 55m
2026-07-13 SJX801 NRT → TPE Jul 13, 05:35 UTCJul 13, 08:25 UTC2h 50m
2026-07-13 SJX800 - Jul 13, 00:55 UTCJul 13, 03:45 UTC2h 50m
2026-07-12 SJX801 NRT → TPE Jul 12, 06:25 UTCJul 12, 09:05 UTC2h 40m
2026-07-12 SJX800 TPE → NRT Jul 12, 00:45 UTCJul 12, 03:45 UTC3h 0m
2026-07-04 SJX2351 TLS → TPE Jul 4, 13:55 UTCJul 5, 03:45 UTC13h 50m
2026-07-04 AIB791 TLS → TLS Jul 4, 07:00 UTCJul 4, 09:40 UTC2h 40m

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.

Mode-S 89912A frequently asked

What is Mode-S code 89912A?
89912A is an ICAO 24-bit transponder address. Allocated to Taiwan.
Where is Mode-S 89912A registered?
Mode-S code 89912A is allocated to Taiwan (TW). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 89912A broadcasting right now?
Yes. Mode-S 89912A is currently airborne.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 89912A, octal 42310452, decimal 9,015,594.
What flights does 89912A operate?
Mode-S 89912A has broadcast 8 distinct callsigns, including SJX800, SJX801, SJX803, SJX802, SJX026.