sensors Mode-S transponder

899126

ICAO 24-bit transponder address · allocated to Taiwan

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

Hex
899126
Octal
42310446
Decimal
9,015,590
Country
TW
Tail
B-58551
Type
A35K
Broadcasting now · callsign SJX803 · 40,000 ft
Flights observed
283
Distinct callsigns
8
Country
TW
Last broadcast
3h ago

Current position

899126 is currently broadcasting. Map zoomed to live position.

Country allocation

The ICAO 24-bit address 899126 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
SJX801 - 76 2026-07-09
SJX800 - 61 2026-07-09
SJX803 - 58 2026-07-13
SJX802 - 51 2026-07-14
SJX823 - 14 2026-07-02
SJX822 - 11 2026-07-02
SJX026 - 6 2026-07-09
SJX025 - 6 2026-07-11

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 SJX802 - Jul 14, 03:00 UTCJul 14, 06:00 UTC3h 0m
2026-07-13 SJX803 - Jul 13, 10:05 UTCJul 13, 10:40 UTC35m
2026-07-13 SJX803 - Jul 13, 07:45 UTCJul 13, 08:55 UTC1h 10m
2026-07-13 SJX802 - Jul 13, 03:10 UTCJul 13, 06:05 UTC2h 55m
2026-07-12 SJX803 NRT → TPE Jul 12, 09:00 UTCJul 12, 11:40 UTC2h 40m
2026-07-12 SJX802 TPE → NRT Jul 12, 03:05 UTCJul 12, 06:10 UTC3h 5m
2026-07-11 SJX025 - Jul 11, 20:15 UTCJul 11, 20:35 UTC20m
2026-07-11 SJX025 - Jul 11, 07:10 UTCJul 11, 19:00 UTC11h 50m
2026-07-09 SJX026 - Jul 9, 14:10 UTCJul 10, 01:10 UTC11h 0m
2026-07-09 SJX026 - Jul 9, 12:45 UTCJul 9, 12:55 UTC10m
2026-07-09 SJX801 - Jul 9, 08:15 UTCJul 9, 08:50 UTC35m
2026-07-09 SJX801 - Jul 9, 05:55 UTCJul 9, 07:10 UTC1h 15m
2026-07-09 SJX800 - Jul 9, 01:15 UTCJul 9, 04:05 UTC2h 50m
2026-07-08 SJX025 - Jul 8, 20:20 UTCJul 8, 20:50 UTC30m
2026-07-08 SJX025 - Jul 8, 07:05 UTCJul 8, 19:10 UTC12h 5m
2026-07-07 SJX026 TPE → PHX Jul 7, 14:05 UTCJul 8, 00:55 UTC10h 50m
2026-07-07 SJX026 TPE → PHX Jul 7, 12:35 UTCJul 7, 12:55 UTC20m
2026-07-06 SJX025 - Jul 6, 20:15 UTCJul 6, 20:35 UTC20m
2026-07-06 SJX025 - Jul 6, 07:10 UTCJul 6, 19:05 UTC11h 55m
2026-07-05 SJX026 TPE → PHX Jul 5, 14:10 UTCJul 6, 00:45 UTC10h 35m
2026-07-05 SJX026 TPE → PHX Jul 5, 12:35 UTCJul 5, 12:55 UTC20m
2026-07-05 SJX801 - Jul 5, 08:25 UTCJul 5, 08:45 UTC20m
2026-07-05 SJX801 - Jul 5, 05:55 UTCJul 5, 07:10 UTC1h 15m
2026-07-05 SJX800 TPE → NRT Jul 5, 01:15 UTCJul 5, 04:05 UTC2h 50m
2026-07-04 SJX801 - Jul 4, 08:15 UTCJul 4, 08:30 UTC15m
2026-07-04 SJX801 - Jul 4, 05:35 UTCJul 4, 06:55 UTC1h 20m
2026-07-04 SJX800 - Jul 4, 02:35 UTCJul 4, 03:45 UTC1h 10m
2026-07-04 SJX800 - Jul 4, 01:05 UTCJul 4, 01:15 UTC10m
2026-07-03 SJX801 - Jul 3, 07:55 UTCJul 3, 08:20 UTC25m
2026-07-03 SJX801 - Jul 3, 05:25 UTCJul 3, 06:45 UTC1h 20m
2026-07-03 SJX800 TPE → NRT Jul 3, 01:00 UTCJul 3, 03:40 UTC2h 40m
2026-07-02 SJX823 - Jul 2, 08:30 UTCJul 2, 09:00 UTC30m
2026-07-02 SJX823 - Jul 2, 06:35 UTCJul 2, 07:10 UTC35m
2026-07-02 SJX822 TPE → KIX Jul 2, 02:45 UTCJul 2, 05:00 UTC2h 15m
2026-07-01 SJX801 - Jul 1, 08:15 UTCJul 1, 08:45 UTC30m
2026-07-01 SJX801 - Jul 1, 05:50 UTCJul 1, 07:00 UTC1h 10m
2026-07-01 SJX800 - Jul 1, 01:15 UTCJul 1, 03:55 UTC2h 40m
2026-06-30 SJX801 - Jun 30, 08:15 UTCJun 30, 08:45 UTC30m
2026-06-30 SJX801 - Jun 30, 05:45 UTCJun 30, 07:00 UTC1h 15m
2026-06-30 SJX800 - Jun 30, 02:45 UTCJun 30, 03:55 UTC1h 10m
2026-06-30 SJX800 - Jun 30, 01:09 UTCJun 30, 01:25 UTC15m
2026-06-29 SJX823 - Jun 29, 06:44 UTCJun 29, 09:10 UTC2h 25m
2026-06-29 SJX822 - Jun 29, 04:25 UTCJun 29, 05:04 UTC40m
2026-06-29 SJX822 - Jun 29, 02:54 UTCJun 29, 03:10 UTC15m
2026-06-28 SJX801 - Jun 28, 08:55 UTCJun 28, 09:20 UTC25m
2026-06-28 SJX801 - Jun 28, 06:05 UTCJun 28, 07:25 UTC1h 20m
2026-06-28 SJX800 TPE → NRT Jun 28, 00:50 UTCJun 28, 03:29 UTC2h 40m
2026-06-27 SJX823 - Jun 27, 09:40 UTCJun 27, 10:10 UTC30m
2026-06-27 SJX823 - Jun 27, 07:39 UTCJun 27, 08:14 UTC35m
2026-06-27 SJX822 - Jun 27, 02:55 UTCJun 27, 05:19 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-58551 page for operator, model, and routing details .

Mode-S 899126 frequently asked

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