sensors Mode-S transponder
89900D
ICAO 24-bit transponder address · allocated to Taiwan
Currently assigned to B-16739 · BOEING 777-300ER
- Hex
- 89900D
- Octal
- 42310015
- Decimal
- 9,015,309
- Country
- TW
- Tail
- B-16739
- Type
- B77W
- Flights observed
- 127
- Distinct callsigns
- 20
- Country
- TW
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 89900D 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 |
|---|---|---|---|
| EVA068 | EVA Air | 21 | 2026-05-27 |
| EVA009 | - | 16 | 2026-05-28 |
| EVA067 | EVA Air | 15 | 2026-05-26 |
| EVA018 | EVA Air | 12 | 2026-05-15 |
| EVA017 | EVA Air | 12 | 2026-05-16 |
| EVA010 | EVA Air | 10 | 2026-05-27 |
| EVA272 | EVA Air | 7 | 2026-05-29 |
| EVA271 | EVA Air | 7 | 2026-05-29 |
| EVA396 | EVA Air | 5 | 2026-05-25 |
| EVA088 | EVA Air | 3 | 2026-05-12 |
| EVA087 | EVA Air | 3 | 2026-05-11 |
| UIA188 | Uni Air | 2 | 2026-05-29 |
| EVA395 | EVA Air | 2 | 2026-05-08 |
| EVA225 | EVA Air | 2 | 2026-05-29 |
| EVA202 | EVA Air | 2 | 2026-05-20 |
| EVA201 | EVA Air | 2 | 2026-05-20 |
| EVA132 | EVA Air | 2 | 2026-05-04 |
| EVA131 | EVA Air | 2 | 2026-05-04 |
| UIA187 | Uni Air | 1 | 2026-05-29 |
| EVA226 | EVA Air | 1 | 2026-05-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | EVA225 | TPE → SIN | May 29, 23:50 UTC | May 30, 00:45 UTC | 55m |
| 2026-05-29 | UIA188 | SZX → TPE | May 29, 13:00 UTC | May 29, 13:30 UTC | 30m |
| 2026-05-29 | UIA188 | SZX → TPE | May 29, 12:10 UTC | May 29, 12:25 UTC | 15m |
| 2026-05-29 | UIA187 | TPE → SZX | May 29, 09:05 UTC | May 29, 10:30 UTC | 1h 25m |
| 2026-05-29 | EVA272 | MNL → TPE | May 29, 05:45 UTC | May 29, 07:25 UTC | 1h 40m |
| 2026-05-29 | EVA271 | TPE → MNL | May 29, 01:50 UTC | May 29, 03:30 UTC | 1h 40m |
| 2026-05-28 | EVA009 | - | May 28, 20:30 UTC | May 28, 21:00 UTC | 30m |
| 2026-05-28 | EVA009 | - | May 28, 09:00 UTC | May 28, 19:10 UTC | 10h 10m |
| 2026-05-27 | EVA010 | TPE → YVR | May 27, 15:55 UTC | May 28, 02:30 UTC | 10h 35m |
| 2026-05-27 | EVA068 | LHR → BKK | May 27, 10:05 UTC | May 27, 13:30 UTC | 3h 25m |
| 2026-05-26 | EVA068 | LHR → BKK | May 26, 21:04 UTC | May 27, 07:50 UTC | 10h 46m |
| 2026-05-26 | EVA067 | BKK → LHR | May 26, 05:54 UTC | May 26, 18:05 UTC | 12h 10m |
| 2026-05-26 | EVA067 | BKK → LHR | May 26, 00:29 UTC | May 26, 03:40 UTC | 3h 10m |
| 2026-05-25 | EVA396 | SGN → TPE | May 25, 11:00 UTC | May 25, 12:15 UTC | 1h 15m |
| 2026-05-24 | EVA009 | - | May 24, 20:15 UTC | May 24, 20:40 UTC | 25m |
| 2026-05-24 | EVA009 | - | May 24, 09:05 UTC | May 24, 19:05 UTC | 10h 0m |
| 2026-05-23 | EVA010 | TPE → YVR | May 23, 16:05 UTC | May 24, 02:10 UTC | 10h 5m |
| 2026-05-22 | EVA009 | - | May 22, 20:25 UTC | May 22, 20:45 UTC | 20m |
| 2026-05-22 | EVA009 | - | May 22, 09:00 UTC | May 22, 19:00 UTC | 10h 0m |
| 2026-05-21 | EVA010 | TPE → YVR | May 21, 17:55 UTC | May 22, 01:50 UTC | 7h 55m |
| 2026-05-21 | EVA010 | TPE → YVR | May 21, 15:55 UTC | May 21, 16:10 UTC | 15m |
| 2026-05-21 | EVA396 | SGN → TPE | May 21, 00:10 UTC | May 21, 12:30 UTC | 12h 20m |
| 2026-05-20 | EVA202 | BKK → TPE | May 20, 08:25 UTC | May 20, 11:35 UTC | 3h 10m |
| 2026-05-20 | EVA201 | TPE → BKK | May 20, 02:55 UTC | May 20, 06:10 UTC | 3h 16m |
| 2026-05-19 | EVA068 | LHR → BKK | May 19, 10:25 UTC | May 19, 13:30 UTC | 3h 5m |
| 2026-05-18 | EVA068 | LHR → BKK | May 18, 20:50 UTC | May 18, 23:40 UTC | 2h 50m |
| 2026-05-18 | EVA067 | BKK → LHR | May 18, 06:25 UTC | May 18, 18:20 UTC | 11h 55m |
| 2026-05-18 | EVA067 | BKK → LHR | May 18, 01:20 UTC | May 18, 04:25 UTC | 3h 5m |
| 2026-05-16 | EVA017 | SFO → TPE | May 16, 21:05 UTC | May 16, 21:30 UTC | 25m |
| 2026-05-16 | EVA017 | SFO → TPE | May 16, 08:41 UTC | May 16, 19:50 UTC | 11h 10m |
| 2026-05-15 | EVA018 | TPE → SFO | May 15, 12:05 UTC | May 15, 22:50 UTC | 10h 44m |
| 2026-05-15 | EVA272 | MNL → TPE | May 15, 05:15 UTC | May 15, 07:00 UTC | 1h 45m |
| 2026-05-15 | EVA271 | TPE → MNL | May 15, 01:50 UTC | May 15, 03:35 UTC | 1h 45m |
| 2026-05-14 | EVA017 | SFO → TPE | May 14, 08:50 UTC | May 14, 21:05 UTC | 12h 15m |
| 2026-05-13 | EVA018 | TPE → SFO | May 13, 12:15 UTC | May 13, 23:00 UTC | 10h 45m |
| 2026-05-13 | EVA272 | MNL → TPE | May 13, 05:50 UTC | May 13, 07:35 UTC | 1h 45m |
| 2026-05-13 | EVA271 | TPE → MNL | May 13, 01:50 UTC | May 13, 03:35 UTC | 1h 45m |
| 2026-05-12 | EVA088 | CDG → TPE | May 12, 10:10 UTC | May 12, 22:31 UTC | 12h 20m |
| 2026-05-11 | EVA087 | TPE → CDG | May 11, 16:05 UTC | May 12, 06:35 UTC | 14h 31m |
| 2026-05-11 | EVA396 | SGN → TPE | May 11, 00:15 UTC | May 11, 11:50 UTC | 11h 35m |
| 2026-05-10 | EVA396 | SGN → TPE | May 10, 00:09 UTC | May 10, 12:10 UTC | 12h 0m |
| 2026-05-09 | EVA009 | YVR → TPE | May 9, 09:15 UTC | May 9, 21:34 UTC | 12h 20m |
| 2026-05-08 | EVA010 | TPE → YVR | May 8, 17:35 UTC | May 9, 01:50 UTC | 8h 15m |
| 2026-05-08 | EVA010 | TPE → YVR | May 8, 15:55 UTC | May 8, 16:05 UTC | 10m |
| 2026-05-08 | EVA395 | TPE → SGN | May 8, 00:05 UTC | May 8, 12:20 UTC | 12h 15m |
| 2026-05-07 | EVA017 | SFO → TPE | May 7, 09:00 UTC | May 7, 21:40 UTC | 12h 40m |
| 2026-05-06 | EVA018 | TPE → SFO | May 6, 14:45 UTC | May 7, 00:15 UTC | 9h 29m |
| 2026-05-06 | EVA018 | TPE → SFO | May 6, 12:50 UTC | May 6, 13:00 UTC | 10m |
| 2026-05-06 | EVA272 | MNL → TPE | May 6, 05:55 UTC | May 6, 07:40 UTC | 1h 45m |
| 2026-05-06 | EVA271 | TPE → MNL | May 6, 02:05 UTC | May 6, 03:50 UTC | 1h 45m |
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-16739 page for operator, model, and routing details .