sensors Mode-S transponder
8990D5
ICAO 24-bit transponder address · allocated to Taiwan
Currently assigned to B-16706 · BOEING 777-300ER
- Hex
- 8990D5
- Octal
- 42310325
- Decimal
- 9,015,509
- Country
- TW
- Tail
- B-16706
- Type
- B77W
- Flights observed
- 121
- Distinct callsigns
- 20
- Country
- TW
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address 8990D5 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 |
|---|---|---|---|
| EVA006 | - | 8 | 2026-04-21 |
| EVA707 | EVA Air | 6 | 2026-05-24 |
| EVA218 | EVA Air | 6 | 2026-05-29 |
| EVA027 | EVA Air | 6 | 2026-05-14 |
| EVA012 | EVA Air | 6 | 2026-05-25 |
| EVA011 | EVA Air | 6 | 2026-05-26 |
| EVA005 | - | 6 | 2026-04-22 |
| UIA187 | Uni Air | 5 | 2026-05-24 |
| EVA711 | EVA Air | 5 | 2026-05-20 |
| EVA262 | EVA Air | 5 | 2026-04-22 |
| EVA261 | EVA Air | 5 | 2026-04-22 |
| EVA217 | EVA Air | 5 | 2026-05-28 |
| UIA188 | Uni Air | 4 | 2026-05-24 |
| EVA159 | EVA Air | 4 | 2026-05-06 |
| EVA028 | EVA Air | 4 | 2026-05-13 |
| EVA015 | EVA Air | 4 | 2026-05-23 |
| EVA708 | EVA Air | 3 | 2026-05-24 |
| EVA212 | EVA Air | 3 | 2026-05-27 |
| EVA211 | EVA Air | 3 | 2026-05-27 |
| EVA160 | EVA Air | 3 | 2026-05-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | EVA201 | TPE → BKK | May 30, 02:35 UTC | May 30, 05:50 UTC | 3h 15m |
| 2026-05-29 | EVA218 | KUL → TPE | May 29, 05:05 UTC | May 29, 09:05 UTC | 4h 0m |
| 2026-05-28 | EVA217 | TPE → KUL | May 28, 22:55 UTC | May 29, 03:05 UTC | 4h 10m |
| 2026-05-28 | EVA228 | KUL → TPE | May 28, 07:45 UTC | May 28, 12:05 UTC | 4h 20m |
| 2026-05-28 | EVA227 | TPE → KUL | May 28, 01:50 UTC | May 28, 05:55 UTC | 4h 5m |
| 2026-05-27 | EVA212 | BKK → TPE | May 27, 05:49 UTC | May 27, 09:20 UTC | 3h 30m |
| 2026-05-27 | EVA211 | TPE → BKK | May 27, 00:49 UTC | May 27, 03:54 UTC | 3h 5m |
| 2026-05-26 | EVA011 | LAX → TPE | May 26, 07:29 UTC | May 26, 21:04 UTC | 13h 35m |
| 2026-05-25 | EVA012 | TPE → LAX | May 25, 12:05 UTC | May 25, 23:35 UTC | 11h 30m |
| 2026-05-25 | EVA212 | BKK → TPE | May 25, 05:45 UTC | May 25, 09:05 UTC | 3h 20m |
| 2026-05-25 | EVA211 | TPE → BKK | May 25, 03:15 UTC | May 25, 03:55 UTC | 40m |
| 2026-05-24 | UIA188 | SZX → TPE | May 24, 13:50 UTC | May 24, 14:30 UTC | 40m |
| 2026-05-24 | UIA187 | TPE → SZX | May 24, 10:35 UTC | May 24, 10:55 UTC | 20m |
| 2026-05-24 | UIA187 | TPE → SZX | May 24, 09:35 UTC | May 24, 10:05 UTC | 30m |
| 2026-05-24 | EVA708 | CAN → TPE | May 24, 06:05 UTC | May 24, 07:50 UTC | 1h 45m |
| 2026-05-24 | EVA707 | TPE → CAN | May 24, 03:35 UTC | May 24, 03:45 UTC | 10m |
| 2026-05-24 | EVA707 | TPE → CAN | May 24, 02:40 UTC | May 24, 03:05 UTC | 25m |
| 2026-05-23 | EVA015 | LAX → TPE | May 23, 08:15 UTC | May 23, 21:45 UTC | 13h 31m |
| 2026-05-22 | EVA016 | TPE → LAX | May 22, 16:20 UTC | May 23, 03:40 UTC | 11h 19m |
| 2026-05-21 | EVA011 | LAX → TPE | May 21, 20:50 UTC | May 21, 21:25 UTC | 35m |
| 2026-05-21 | EVA011 | LAX → TPE | May 21, 07:55 UTC | May 21, 08:40 UTC | 45m |
| 2026-05-20 | EVA012 | TPE → LAX | May 20, 11:55 UTC | May 20, 23:05 UTC | 11h 10m |
| 2026-05-20 | EVA711 | PVG → TPE | May 20, 06:20 UTC | May 20, 06:45 UTC | 25m |
| 2026-05-20 | EVA712 | TPE → PVG | May 20, 02:20 UTC | May 20, 02:45 UTC | 25m |
| 2026-05-19 | EVA015 | LAX → TPE | May 19, 08:10 UTC | May 19, 21:30 UTC | 13h 20m |
| 2026-05-18 | EVA016 | TPE → LAX | May 18, 16:15 UTC | May 19, 03:55 UTC | 11h 39m |
| 2026-05-18 | EVA216 | SIN → TPE | May 18, 08:10 UTC | May 18, 12:15 UTC | 4h 5m |
| 2026-05-18 | EVA215 | TPE → SIN | May 18, 02:25 UTC | May 18, 03:20 UTC | 55m |
| 2026-05-17 | EVA011 | LAX → TPE | May 17, 07:35 UTC | May 17, 20:50 UTC | 13h 15m |
| 2026-05-16 | EVA012 | TPE → LAX | May 16, 12:05 UTC | May 16, 23:30 UTC | 11h 25m |
| 2026-05-16 | EVA212 | BKK → TPE | May 16, 05:56 UTC | May 16, 09:16 UTC | 3h 20m |
| 2026-05-16 | EVA211 | TPE → BKK | May 16, 00:50 UTC | May 16, 04:05 UTC | 3h 15m |
| 2026-05-15 | UIA188 | SZX → TPE | May 15, 12:50 UTC | May 15, 13:20 UTC | 30m |
| 2026-05-15 | UIA188 | SZX → TPE | May 15, 12:05 UTC | May 15, 12:15 UTC | 10m |
| 2026-05-15 | UIA187 | TPE → SZX | May 15, 09:05 UTC | May 15, 09:30 UTC | 25m |
| 2026-05-15 | EVA711 | PVG → TPE | May 15, 02:15 UTC | May 15, 06:55 UTC | 4h 40m |
| 2026-05-14 | EVA027 | SFO → TPE | May 14, 08:25 UTC | May 14, 20:50 UTC | 12h 25m |
| 2026-05-13 | EVA028 | TPE → SFO | May 13, 16:10 UTC | May 14, 02:40 UTC | 10h 30m |
| 2026-05-13 | EVA218 | KUL → TPE | May 13, 05:15 UTC | May 13, 09:20 UTC | 4h 5m |
| 2026-05-12 | EVA217 | TPE → KUL | May 12, 22:50 UTC | May 13, 02:55 UTC | 4h 5m |
| 2026-05-11 | EVA708 | CAN → TPE | May 11, 06:25 UTC | May 11, 07:40 UTC | 1h 15m |
| 2026-05-11 | EVA707 | TPE → CAN | May 11, 03:45 UTC | May 11, 03:55 UTC | 10m |
| 2026-05-11 | EVA707 | TPE → CAN | May 11, 02:45 UTC | May 11, 03:15 UTC | 30m |
| 2026-05-10 | EVA011 | LAX → TPE | May 10, 07:45 UTC | May 10, 21:10 UTC | 13h 25m |
| 2026-05-09 | EVA012 | TPE → LAX | May 9, 13:55 UTC | May 9, 23:15 UTC | 9h 20m |
| 2026-05-09 | EVA012 | TPE → LAX | May 9, 12:15 UTC | May 9, 12:25 UTC | 10m |
| 2026-05-08 | UIA188 | SZX → TPE | May 8, 11:44 UTC | May 8, 13:10 UTC | 1h 25m |
| 2026-05-08 | UIA187 | TPE → SZX | May 8, 09:44 UTC | May 8, 10:04 UTC | 20m |
| 2026-05-08 | UIA187 | TPE → SZX | May 8, 08:40 UTC | May 8, 09:09 UTC | 30m |
| 2026-05-08 | EVA711 | PVG → TPE | May 8, 02:14 UTC | May 8, 06:54 UTC | 4h 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.
Prefer a tail-number view? See the B-16706 page for operator, model, and routing details .