sensors Mode-S transponder
89901B
ICAO 24-bit transponder address · allocated to Taiwan
Currently assigned to B-18001 · BOEING 777-300ER
- Hex
- 89901B
- Octal
- 42310033
- Decimal
- 9,015,323
- Country
- TW
- Tail
- B-18001
- Type
- B77W
- Flights observed
- 100
- Distinct callsigns
- 20
- Country
- TW
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 89901B 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 |
|---|---|---|---|
| CAL023 | China Airlines | 11 | 2026-05-12 |
| CAL024 | China Airlines | 10 | 2026-05-11 |
| CAL032 | China Airlines | 9 | 2026-05-27 |
| CAL004 | - | 9 | 2026-05-29 |
| CAL003 | - | 9 | 2026-05-18 |
| CAL031 | China Airlines | 8 | 2026-05-28 |
| CAL784 | China Airlines | 7 | 2026-05-29 |
| CAL722 | China Airlines | 5 | 2026-05-13 |
| CAL721 | China Airlines | 4 | 2026-05-13 |
| CAL007 | - | 4 | 2026-04-22 |
| CAL923 | China Airlines | 2 | 2026-05-24 |
| CAL782 | China Airlines | 2 | 2026-04-30 |
| CAL772 | China Airlines | 2 | 2026-05-03 |
| CAL012 | China Airlines | 2 | 2026-04-23 |
| CAL011 | China Airlines | 2 | 2026-04-24 |
| CAL008 | - | 2 | 2026-04-21 |
| CAL924 | China Airlines | 1 | 2026-05-24 |
| CAL783 | China Airlines | 1 | 2026-04-17 |
| CAL781 | China Airlines | 1 | 2026-04-22 |
| CAL771 | China Airlines | 1 | 2026-05-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | CAL004 | - | May 29, 15:55 UTC | May 29, 18:25 UTC | 2h 30m |
| 2026-05-29 | CAL784 | SGN → TPE | May 29, 06:10 UTC | May 29, 13:45 UTC | 7h 35m |
| 2026-05-28 | CAL031 | YVR → TPE | May 28, 09:10 UTC | May 28, 21:15 UTC | 12h 5m |
| 2026-05-27 | CAL032 | TPE → YVR | May 27, 16:05 UTC | May 28, 02:35 UTC | 10h 30m |
| 2026-05-27 | CAL771 | TPE → DPS | May 27, 01:49 UTC | May 27, 13:00 UTC | 11h 11m |
| 2026-05-26 | CAL031 | YVR → TPE | May 26, 20:50 UTC | May 26, 21:14 UTC | 25m |
| 2026-05-26 | CAL031 | YVR → TPE | May 26, 09:15 UTC | May 26, 19:34 UTC | 10h 20m |
| 2026-05-26 | CAL032 | TPE → YVR | May 26, 01:44 UTC | May 26, 02:24 UTC | 40m |
| 2026-05-25 | CAL032 | TPE → YVR | May 25, 16:05 UTC | May 25, 16:25 UTC | 20m |
| 2026-05-24 | CAL924 | HKG → TPE | May 24, 13:45 UTC | May 24, 15:00 UTC | 1h 15m |
| 2026-05-24 | CAL923 | TPE → HKG | May 24, 11:35 UTC | May 24, 11:50 UTC | 15m |
| 2026-05-24 | CAL923 | TPE → HKG | May 24, 10:35 UTC | May 24, 11:00 UTC | 25m |
| 2026-05-18 | CAL003 | - | May 18, 21:00 UTC | May 18, 21:30 UTC | 30m |
| 2026-05-18 | CAL003 | - | May 18, 08:25 UTC | May 18, 19:45 UTC | 11h 19m |
| 2026-05-17 | CAL004 | - | May 17, 16:01 UTC | May 18, 02:40 UTC | 10h 40m |
| 2026-05-16 | CAL003 | - | May 16, 21:15 UTC | May 16, 21:35 UTC | 20m |
| 2026-05-16 | CAL003 | - | May 16, 08:36 UTC | May 16, 19:55 UTC | 11h 20m |
| 2026-05-15 | CAL004 | - | May 15, 16:10 UTC | May 16, 03:00 UTC | 10h 50m |
| 2026-05-15 | CAL784 | SGN → TPE | May 15, 06:00 UTC | May 15, 13:45 UTC | 7h 45m |
| 2026-05-14 | CAL031 | YVR → TPE | May 14, 09:10 UTC | May 14, 20:10 UTC | 11h 0m |
| 2026-05-13 | CAL032 | TPE → YVR | May 13, 17:00 UTC | May 14, 02:35 UTC | 9h 35m |
| 2026-05-13 | CAL032 | TPE → YVR | May 13, 16:20 UTC | May 13, 16:30 UTC | 10m |
| 2026-05-13 | CAL722 | KUL → TPE | May 13, 07:00 UTC | May 13, 11:05 UTC | 4h 5m |
| 2026-05-13 | CAL721 | TPE → KUL | May 13, 01:10 UTC | May 13, 05:15 UTC | 4h 5m |
| 2026-05-12 | CAL023 | ONT → TPE | May 12, 20:10 UTC | May 12, 20:40 UTC | 30m |
| 2026-05-12 | CAL023 | ONT → TPE | May 12, 07:25 UTC | May 12, 19:00 UTC | 11h 35m |
| 2026-05-11 | CAL024 | TPE → ONT | May 11, 13:35 UTC | May 11, 14:35 UTC | 1h 0m |
| 2026-05-09 | CAL031 | YVR → TPE | May 9, 20:55 UTC | May 9, 21:19 UTC | 25m |
| 2026-05-09 | CAL031 | YVR → TPE | May 9, 09:05 UTC | May 9, 19:35 UTC | 10h 30m |
| 2026-05-08 | CAL032 | TPE → YVR | May 8, 17:35 UTC | May 9, 01:55 UTC | 8h 20m |
| 2026-05-08 | CAL032 | TPE → YVR | May 8, 16:00 UTC | May 8, 16:10 UTC | 10m |
| 2026-05-08 | CAL784 | SGN → TPE | May 8, 06:09 UTC | May 8, 14:05 UTC | 7h 55m |
| 2026-05-07 | CAL003 | - | May 7, 20:50 UTC | May 7, 21:15 UTC | 25m |
| 2026-05-07 | CAL003 | - | May 7, 08:30 UTC | May 7, 19:20 UTC | 10h 50m |
| 2026-05-06 | CAL004 | - | May 6, 15:55 UTC | May 7, 04:05 UTC | 12h 9m |
| 2026-05-06 | CAL784 | SGN → TPE | May 6, 06:15 UTC | May 6, 13:35 UTC | 7h 20m |
| 2026-05-05 | CAL722 | KUL → TPE | May 5, 07:10 UTC | May 5, 11:20 UTC | 4h 10m |
| 2026-05-05 | CAL721 | TPE → KUL | May 5, 01:30 UTC | May 5, 05:30 UTC | 4h 0m |
| 2026-05-04 | CAL031 | YVR → TPE | May 4, 09:00 UTC | May 4, 21:05 UTC | 12h 6m |
| 2026-05-03 | CAL032 | TPE → YVR | May 3, 18:14 UTC | May 4, 02:50 UTC | 8h 35m |
| 2026-05-03 | CAL772 | DPS → TPE | May 3, 01:30 UTC | May 3, 13:00 UTC | 11h 29m |
| 2026-05-02 | CAL023 | ONT → TPE | May 2, 07:20 UTC | May 2, 21:05 UTC | 13h 45m |
| 2026-05-01 | CAL024 | TPE → ONT | May 1, 15:40 UTC | May 2, 01:15 UTC | 9h 35m |
| 2026-05-01 | CAL024 | TPE → ONT | May 1, 13:45 UTC | May 1, 13:55 UTC | 10m |
| 2026-04-30 | CAL782 | SGN → TPE | Apr 30, 23:50 UTC | May 1, 07:40 UTC | 7h 50m |
| 2026-04-30 | CAL031 | YVR → TPE | Apr 30, 09:20 UTC | Apr 30, 21:50 UTC | 12h 30m |
| 2026-04-29 | CAL032 | TPE → YVR | Apr 29, 16:45 UTC | Apr 30, 02:00 UTC | 9h 14m |
| 2026-04-29 | CAL504 | PVG → TPE | Apr 29, 08:55 UTC | Apr 29, 14:15 UTC | 5h 21m |
| 2026-04-29 | CAL502 | PVG → TPE | Apr 29, 01:10 UTC | Apr 29, 06:00 UTC | 4h 50m |
| 2026-04-28 | CAL023 | ONT → TPE | Apr 28, 21:05 UTC | Apr 28, 21:30 UTC | 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-18001 page for operator, model, and routing details .