sensors Mode-S transponder
888090
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A331 · AIRBUS A-321
- Hex
- 888090
- Octal
- 42100220
- Decimal
- 8,945,808
- Country
- VN
- Tail
- VN-A331
- Type
- A321
- Flights observed
- 59
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 888090 falls within the block assigned to Vietnam (VN) by ICAO Annex 10, Volume III. Every aircraft registered in Vietnam 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 |
|---|---|---|---|
| HVN587 | Vietnam Airlines | 4 | 2026-05-27 |
| HVN586 | Vietnam Airlines | 4 | 2026-05-26 |
| HVN655 | Vietnam Airlines | 2 | 2026-04-19 |
| HVN654 | Vietnam Airlines | 2 | 2026-04-19 |
| HVN643 | Vietnam Airlines | 2 | 2026-04-30 |
| HVN631 | Vietnam Airlines | 2 | 2026-04-18 |
| HVN630 | Vietnam Airlines | 2 | 2026-04-18 |
| HVN619 | Vietnam Airlines | 2 | 2026-04-28 |
| HVN618 | Vietnam Airlines | 2 | 2026-04-28 |
| HVN609 | Vietnam Airlines | 2 | 2026-04-18 |
| HVN608 | - | 2 | 2026-04-18 |
| HVN594 | Vietnam Airlines | 2 | 2026-04-17 |
| HVN579 | Vietnam Airlines | 2 | 2026-05-28 |
| HVN578 | Vietnam Airlines | 2 | 2026-05-28 |
| HVN985 | Vietnam Airlines | 1 | 2026-05-03 |
| HVN984 | Vietnam Airlines | 1 | 2026-05-03 |
| HVN7203 | Vietnam Airlines | 1 | 2026-05-29 |
| HVN681 | Vietnam Airlines | 1 | 2026-04-26 |
| HVN680 | Vietnam Airlines | 1 | 2026-04-26 |
| HVN663 | Vietnam Airlines | 1 | 2026-05-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | HVN1233 | HAN → PQC | May 30, 04:35 UTC | May 30, 04:55 UTC | 20m |
| 2026-05-29 | HVN7203 | HAN → SGN | May 29, 09:25 UTC | May 29, 14:05 UTC | 4h 40m |
| 2026-05-29 | HVN1553 | HAN → CXR | May 29, 03:45 UTC | May 29, 07:40 UTC | 3h 55m |
| 2026-05-28 | HVN579 | TPE → HAN | May 28, 23:40 UTC | May 29, 01:35 UTC | 1h 55m |
| 2026-05-28 | HVN578 | HAN → TPE | May 28, 10:40 UTC | May 28, 13:15 UTC | 2h 35m |
| 2026-05-28 | HVN1804 | HAN → DIN | May 28, 07:25 UTC | May 28, 07:45 UTC | 20m |
| 2026-05-28 | HVN166 | DAD → HAN | May 28, 05:20 UTC | May 28, 05:40 UTC | 20m |
| 2026-05-28 | HVN165 | HAN → DAD | May 28, 02:55 UTC | May 28, 03:25 UTC | 30m |
| 2026-05-27 | HVN1541 | HAN → HUI | May 27, 23:00 UTC | May 28, 01:40 UTC | 2h 40m |
| 2026-05-27 | HVN587 | KHH → HAN | May 27, 00:30 UTC | May 27, 12:10 UTC | 11h 40m |
| 2026-05-26 | HVN586 | HAN → KHH | May 26, 08:39 UTC | May 26, 13:34 UTC | 4h 55m |
| 2026-05-25 | HVN614 | BKK → HAN | May 25, 09:20 UTC | May 25, 10:20 UTC | 1h 0m |
| 2026-05-25 | HVN615 | HAN → BKK | May 25, 06:55 UTC | May 25, 07:55 UTC | 1h 0m |
| 2026-05-13 | HVN600 | BKK → SGN | May 13, 04:45 UTC | May 13, 05:20 UTC | 35m |
| 2026-05-13 | HVN601 | SGN → BKK | May 13, 02:30 UTC | May 13, 03:10 UTC | 40m |
| 2026-05-09 | HVN587 | KHH → HAN | May 9, 00:35 UTC | May 9, 01:35 UTC | 1h 0m |
| 2026-05-08 | HVN586 | HAN → KHH | May 8, 05:35 UTC | May 8, 13:40 UTC | 8h 5m |
| 2026-05-05 | HVN662 | SIN → HAN | May 5, 09:15 UTC | May 5, 09:35 UTC | 20m |
| 2026-05-05 | HVN663 | HAN → SIN | May 5, 06:40 UTC | May 5, 06:55 UTC | 15m |
| 2026-05-03 | HVN984 | HYD → HAN | May 3, 21:39 UTC | May 3, 21:54 UTC | 15m |
| 2026-05-03 | HVN985 | HAN → HYD | May 3, 08:30 UTC | May 3, 21:05 UTC | 12h 35m |
| 2026-05-02 | HVN579 | TPE → HAN | May 2, 23:50 UTC | May 3, 01:05 UTC | 1h 15m |
| 2026-05-02 | HVN578 | HAN → TPE | May 2, 05:25 UTC | May 2, 13:10 UTC | 7h 45m |
| 2026-05-01 | HVN634 | CGK → HAN | May 1, 18:25 UTC | May 2, 03:25 UTC | 9h 0m |
| 2026-05-01 | HVN513 | PEK → HAN | May 1, 08:10 UTC | May 1, 08:20 UTC | 10m |
| 2026-05-01 | HVN512 | HAN → PEK | May 1, 06:10 UTC | May 1, 06:20 UTC | 10m |
| 2026-04-30 | HVN643 | HAN → CEB | Apr 30, 05:30 UTC | Apr 30, 22:10 UTC | 16h 40m |
| 2026-04-30 | HVN611 | HAN → BKK | Apr 30, 03:05 UTC | Apr 30, 03:40 UTC | 35m |
| 2026-04-28 | HVN618 | BKK → HAN | Apr 28, 12:25 UTC | Apr 28, 12:50 UTC | 25m |
| 2026-04-28 | HVN619 | HAN → BKK | Apr 28, 10:30 UTC | Apr 28, 11:00 UTC | 30m |
| 2026-04-26 | HVN643 | HAN → CEB | Apr 26, 17:30 UTC | Apr 26, 22:20 UTC | 4h 50m |
| 2026-04-26 | HVN680 | KUL → HAN | Apr 26, 12:20 UTC | Apr 26, 12:30 UTC | 10m |
| 2026-04-26 | HVN681 | HAN → KUL | Apr 26, 10:45 UTC | Apr 26, 10:55 UTC | 10m |
| 2026-04-25 | HVN219 | HAN → SGN | Apr 25, 13:55 UTC | Apr 25, 14:10 UTC | 15m |
| 2026-04-21 | HVN618 | BKK → HAN | Apr 21, 12:35 UTC | Apr 21, 13:30 UTC | 55m |
| 2026-04-21 | HVN619 | HAN → BKK | Apr 21, 09:50 UTC | Apr 21, 10:55 UTC | 1h 5m |
| 2026-04-19 | HVN654 | SIN → SGN | Apr 19, 13:50 UTC | Apr 19, 14:15 UTC | 25m |
| 2026-04-19 | HVN654 | SIN → SGN | Apr 19, 12:45 UTC | Apr 19, 13:00 UTC | 15m |
| 2026-04-19 | HVN655 | SGN → SIN | Apr 19, 09:20 UTC | Apr 19, 09:35 UTC | 15m |
| 2026-04-19 | HVN655 | SGN → SIN | Apr 19, 08:25 UTC | Apr 19, 08:40 UTC | 15m |
| 2026-04-18 | HVN517 | PKX → SGN | Apr 18, 20:35 UTC | Apr 19, 03:35 UTC | 7h 0m |
| 2026-04-18 | HVN608 | - | Apr 18, 15:05 UTC | Apr 18, 15:20 UTC | 15m |
| 2026-04-18 | HVN608 | - | Apr 18, 14:15 UTC | Apr 18, 14:30 UTC | 15m |
| 2026-04-18 | HVN609 | SGN → BKK | Apr 18, 12:30 UTC | Apr 18, 12:50 UTC | 20m |
| 2026-04-18 | HVN609 | SGN → BKK | Apr 18, 11:40 UTC | Apr 18, 11:55 UTC | 15m |
| 2026-04-18 | HVN630 | CGK → SGN | Apr 18, 08:05 UTC | Apr 18, 09:50 UTC | 1h 45m |
| 2026-04-18 | HVN630 | CGK → SGN | Apr 18, 07:00 UTC | Apr 18, 07:15 UTC | 15m |
| 2026-04-18 | HVN631 | SGN → CGK | Apr 18, 05:25 UTC | Apr 18, 05:35 UTC | 10m |
| 2026-04-18 | HVN631 | SGN → CGK | Apr 18, 03:00 UTC | Apr 18, 03:20 UTC | 20m |
| 2026-04-17 | HVN595 | HKG → SGN | Apr 17, 11:10 UTC | Apr 17, 11:15 UTC | 5m |
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 VN-A331 page for operator, model, and routing details .