Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

899129

ICAO 24-bit transponder address · allocated to Taiwan

Currently assigned to B-58552 · AIRBUS A-350-1000

Hex
899129
Octal
42310451
Decimal
9,015,593
Country
TW
Tail
B-58552
Type
A35K
No current signal · last broadcast 47m ago
Flights observed
148
Distinct callsigns
4
Country
TW
Last broadcast
47m ago

Last known position

Most recent position reported by Mode-S 899129.

Country allocation

The ICAO 24-bit address 899129 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 4 distinct

Callsign Airline Flights Last seen
SJX803 STARLUX Airlines 41 2026-05-29
SJX801 STARLUX Airlines 39 2026-05-30
SJX800 STARLUX Airlines 38 2026-05-30
SJX802 STARLUX Airlines 30 2026-05-29

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 SJX801 NRT → TPE May 30, 05:40 UTCMay 30, 08:15 UTC2h 35m
2026-05-30 SJX800 TPE → NRT May 30, 02:25 UTCMay 30, 03:35 UTC1h 10m
2026-05-30 SJX800 TPE → NRT May 30, 01:00 UTCMay 30, 01:10 UTC10m
2026-05-29 SJX803 NRT → TPE May 29, 10:20 UTCMay 29, 10:55 UTC35m
2026-05-29 SJX803 NRT → TPE May 29, 07:45 UTCMay 29, 09:05 UTC1h 20m
2026-05-29 SJX802 TPE → NRT May 29, 03:05 UTCMay 29, 06:00 UTC2h 55m
2026-05-28 SJX801 NRT → TPE May 28, 08:05 UTCMay 28, 08:30 UTC25m
2026-05-28 SJX801 NRT → TPE May 28, 05:35 UTCMay 28, 06:50 UTC1h 15m
2026-05-28 SJX800 TPE → NRT May 28, 01:00 UTCMay 28, 03:55 UTC2h 55m
2026-05-27 SJX803 NRT → TPE May 27, 10:30 UTCMay 27, 10:55 UTC25m
2026-05-27 SJX803 NRT → TPE May 27, 08:10 UTCMay 27, 09:20 UTC1h 10m
2026-05-27 SJX802 TPE → NRT May 27, 03:24 UTCMay 27, 06:25 UTC3h 0m
2026-05-26 SJX801 NRT → TPE May 26, 05:30 UTCMay 26, 08:15 UTC2h 45m
2026-05-26 SJX800 TPE → NRT May 26, 00:49 UTCMay 26, 03:40 UTC2h 50m
2026-05-25 SJX803 NRT → TPE May 25, 08:10 UTCMay 25, 10:55 UTC2h 45m
2026-05-25 SJX802 TPE → NRT May 25, 03:10 UTCMay 25, 06:10 UTC3h 0m
2026-05-24 SJX801 NRT → TPE May 24, 05:40 UTCMay 24, 08:45 UTC3h 5m
2026-05-24 SJX800 TPE → NRT May 24, 02:15 UTCMay 24, 03:40 UTC1h 25m
2026-05-24 SJX800 TPE → NRT May 24, 00:45 UTCMay 24, 01:05 UTC20m
2026-05-23 SJX801 NRT → TPE May 23, 05:50 UTCMay 23, 08:55 UTC3h 5m
2026-05-23 SJX800 TPE → NRT May 23, 01:05 UTCMay 23, 03:45 UTC2h 40m
2026-05-22 SJX801 NRT → TPE May 22, 09:20 UTCMay 22, 09:40 UTC20m
2026-05-22 SJX801 NRT → TPE May 22, 06:35 UTCMay 22, 07:50 UTC1h 15m
2026-05-22 SJX800 TPE → NRT May 22, 02:20 UTCMay 22, 03:45 UTC1h 25m
2026-05-22 SJX800 TPE → NRT May 22, 00:45 UTCMay 22, 01:05 UTC20m
2026-05-21 SJX803 NRT → TPE May 21, 10:30 UTCMay 21, 10:50 UTC20m
2026-05-21 SJX803 NRT → TPE May 21, 07:45 UTCMay 21, 09:10 UTC1h 25m
2026-05-21 SJX802 TPE → NRT May 21, 03:00 UTCMay 21, 05:40 UTC2h 40m
2026-05-20 SJX801 NRT → TPE May 20, 08:10 UTCMay 20, 08:35 UTC25m
2026-05-20 SJX801 NRT → TPE May 20, 05:40 UTCMay 20, 06:50 UTC1h 10m
2026-05-20 SJX800 TPE → NRT May 20, 02:10 UTCMay 20, 03:25 UTC1h 15m
2026-05-20 SJX800 TPE → NRT May 20, 00:40 UTCMay 20, 01:00 UTC20m
2026-05-19 SJX803 NRT → TPE May 19, 10:05 UTCMay 19, 10:40 UTC35m
2026-05-19 SJX803 NRT → TPE May 19, 07:45 UTCMay 19, 08:55 UTC1h 10m
2026-05-19 SJX802 TPE → NRT May 19, 02:45 UTCMay 19, 05:45 UTC3h 0m
2026-05-18 SJX801 NRT → TPE May 18, 05:35 UTCMay 18, 08:20 UTC2h 45m
2026-05-18 SJX800 TPE → NRT May 18, 01:35 UTCMay 18, 03:50 UTC2h 15m
2026-05-18 SJX800 TPE → NRT May 18, 00:50 UTCMay 18, 01:05 UTC15m
2026-05-17 SJX803 NRT → TPE May 17, 07:45 UTCMay 17, 10:30 UTC2h 45m
2026-05-17 SJX802 TPE → NRT May 17, 03:00 UTCMay 17, 05:50 UTC2h 50m
2026-05-16 SJX803 NRT → TPE May 16, 10:11 UTCMay 16, 10:35 UTC25m
2026-05-16 SJX803 NRT → TPE May 16, 07:45 UTCMay 16, 08:51 UTC1h 5m
2026-05-16 SJX802 TPE → NRT May 16, 03:00 UTCMay 16, 05:56 UTC2h 56m
2026-05-15 SJX801 NRT → TPE May 15, 08:00 UTCMay 15, 08:40 UTC40m
2026-05-15 SJX801 NRT → TPE May 15, 05:35 UTCMay 15, 06:35 UTC1h 0m
2026-05-15 SJX800 TPE → NRT May 15, 00:50 UTCMay 15, 03:35 UTC2h 45m
2026-05-14 SJX803 NRT → TPE May 14, 08:00 UTCMay 14, 11:05 UTC3h 5m
2026-05-14 SJX802 TPE → NRT May 14, 03:25 UTCMay 14, 06:10 UTC2h 45m
2026-05-13 SJX801 NRT → TPE May 13, 08:20 UTCMay 13, 08:55 UTC35m
2026-05-13 SJX801 NRT → TPE May 13, 05:45 UTCMay 13, 06:55 UTC1h 10m

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

Mode-S 899129 frequently asked

What is Mode-S code 899129?
899129 is an ICAO 24-bit transponder address. Allocated to Taiwan. Assigned to B-58552.
Where is Mode-S 899129 registered?
Mode-S code 899129 is allocated to Taiwan (TW). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 899129 broadcasting right now?
No active broadcast right now. Last signal was 47m ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 899129, octal 42310451, decimal 9,015,593.
What flights does 899129 operate?
Mode-S 899129 has broadcast 4 distinct callsigns, including SJX803, SJX801, SJX800, SJX802.