sensors Mode-S transponder
8880AE
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A603 · AIRBUS A-321
- Hex
- 8880AE
- Octal
- 42100256
- Decimal
- 8,945,838
- Country
- VN
- Tail
- VN-A603
- Type
- A321
- Flights observed
- 69
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 8880AE 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 |
|---|---|---|---|
| HVN640 | Vietnam Airlines | 5 | 2026-05-21 |
| HVN630 | Vietnam Airlines | 4 | 2026-05-15 |
| HVN586 | Vietnam Airlines | 4 | 2026-05-01 |
| HVN650 | Vietnam Airlines | 3 | 2026-05-28 |
| HVN647 | Vietnam Airlines | 3 | 2026-04-29 |
| HVN587 | Vietnam Airlines | 3 | 2026-05-02 |
| HVN581 | Vietnam Airlines | 3 | 2026-05-25 |
| HVN580 | Vietnam Airlines | 3 | 2026-05-25 |
| HVN681 | Vietnam Airlines | 2 | 2026-05-08 |
| HVN680 | Vietnam Airlines | 2 | 2026-05-08 |
| HVN631 | Vietnam Airlines | 2 | 2026-05-13 |
| HVN609 | Vietnam Airlines | 2 | 2026-05-29 |
| HVN608 | Vietnam Airlines | 2 | 2026-05-29 |
| HVN571 | Vietnam Airlines | 2 | 2026-05-20 |
| HVN570 | Vietnam Airlines | 2 | 2026-05-19 |
| HVN1822 | Vietnam Airlines | 2 | 2026-04-25 |
| HVN1350 | - | 2 | 2026-04-19 |
| HVN813 | Vietnam Airlines | 1 | 2026-04-22 |
| HVN812 | Vietnam Airlines | 1 | 2026-04-22 |
| HVN678 | Vietnam Airlines | 1 | 2026-05-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | HVN608 | BKK → SGN | May 29, 14:20 UTC | May 29, 14:50 UTC | 30m |
| 2026-05-29 | HVN609 | SGN → BKK | May 29, 12:40 UTC | May 29, 13:05 UTC | 25m |
| 2026-05-28 | HVN650 | SIN → SGN | May 28, 05:30 UTC | May 28, 06:00 UTC | 30m |
| 2026-05-27 | HVN608 | BKK → SGN | May 27, 14:15 UTC | May 28, 03:45 UTC | 13h 30m |
| 2026-05-27 | HVN609 | SGN → BKK | May 27, 12:05 UTC | May 27, 12:55 UTC | 50m |
| 2026-05-27 | HVN502 | SGN → CAN | May 27, 05:14 UTC | May 27, 05:35 UTC | 20m |
| 2026-05-25 | HVN581 | KHH → SGN | May 25, 23:24 UTC | May 26, 00:04 UTC | 40m |
| 2026-05-25 | HVN580 | SGN → KHH | May 25, 13:05 UTC | May 25, 13:50 UTC | 45m |
| 2026-05-24 | HVN650 | SIN → SGN | May 24, 05:30 UTC | May 24, 05:50 UTC | 20m |
| 2026-05-24 | HVN651 | SGN → SIN | May 24, 03:25 UTC | May 24, 04:00 UTC | 35m |
| 2026-05-22 | HVN678 | KUL → SGN | May 22, 11:35 UTC | May 22, 11:45 UTC | 10m |
| 2026-05-22 | HVN650 | SIN → SGN | May 22, 05:25 UTC | May 22, 10:05 UTC | 4h 40m |
| 2026-05-21 | HVN640 | DPS → SGN | May 21, 10:00 UTC | May 22, 03:35 UTC | 17h 35m |
| 2026-05-20 | HVN606 | BKK → SGN | May 20, 12:30 UTC | May 21, 10:20 UTC | 21h 50m |
| 2026-05-20 | HVN571 | TPE → SGN | May 20, 00:10 UTC | May 20, 11:15 UTC | 11h 6m |
| 2026-05-19 | HVN570 | SGN → TPE | May 19, 11:45 UTC | May 19, 12:50 UTC | 1h 5m |
| 2026-05-17 | HVN654 | SIN → SGN | May 17, 11:10 UTC | May 17, 11:40 UTC | 30m |
| 2026-05-17 | HVN600 | BKK → SGN | May 17, 04:30 UTC | May 17, 08:55 UTC | 4h 25m |
| 2026-05-17 | HVN601 | SGN → BKK | May 17, 02:20 UTC | May 17, 03:00 UTC | 40m |
| 2026-05-15 | HVN581 | KHH → SGN | May 15, 23:35 UTC | May 16, 00:10 UTC | 35m |
| 2026-05-15 | HVN630 | CGK → SGN | May 15, 07:00 UTC | May 15, 14:05 UTC | 7h 5m |
| 2026-05-14 | HVN640 | DPS → SGN | May 14, 09:55 UTC | May 14, 10:20 UTC | 25m |
| 2026-05-13 | HVN630 | CGK → SGN | May 13, 07:15 UTC | May 13, 08:40 UTC | 1h 25m |
| 2026-05-13 | HVN631 | SGN → CGK | May 13, 05:20 UTC | May 13, 05:40 UTC | 20m |
| 2026-05-12 | HVN640 | DPS → SGN | May 12, 09:50 UTC | May 12, 10:15 UTC | 25m |
| 2026-05-08 | HVN680 | KUL → HAN | May 8, 12:14 UTC | May 8, 12:30 UTC | 15m |
| 2026-05-08 | HVN681 | HAN → KUL | May 8, 10:19 UTC | May 8, 10:44 UTC | 25m |
| 2026-05-05 | HVN571 | TPE → SGN | May 5, 00:10 UTC | May 5, 01:15 UTC | 1h 5m |
| 2026-05-04 | HVN570 | SGN → TPE | May 4, 11:45 UTC | May 4, 12:45 UTC | 1h 0m |
| 2026-05-03 | HVN680 | KUL → HAN | May 3, 12:25 UTC | May 3, 12:35 UTC | 10m |
| 2026-05-03 | HVN681 | HAN → KUL | May 3, 10:30 UTC | May 3, 10:50 UTC | 20m |
| 2026-05-03 | HVN610 | BKK → HAN | May 3, 05:15 UTC | May 3, 05:35 UTC | 20m |
| 2026-05-03 | HVN611 | HAN → BKK | May 3, 03:20 UTC | May 3, 03:55 UTC | 34m |
| 2026-05-02 | HVN587 | KHH → HAN | May 2, 00:35 UTC | May 2, 01:30 UTC | 55m |
| 2026-05-01 | HVN586 | HAN → KHH | May 1, 08:45 UTC | May 1, 14:00 UTC | 5h 15m |
| 2026-05-01 | HVN587 | KHH → HAN | May 1, 00:40 UTC | May 1, 01:40 UTC | 1h 0m |
| 2026-04-29 | HVN586 | HAN → KHH | Apr 29, 21:25 UTC | Apr 30, 13:15 UTC | 15h 49m |
| 2026-04-29 | HVN647 | HAN → MNL | Apr 29, 03:49 UTC | Apr 29, 20:05 UTC | 16h 16m |
| 2026-04-27 | HVN647 | HAN → MNL | Apr 27, 01:35 UTC | Apr 27, 20:00 UTC | 18h 25m |
| 2026-04-27 | HVN647 | HAN → MNL | Apr 27, 00:30 UTC | Apr 27, 20:00 UTC | 19h 30m |
| 2026-04-26 | HVN586 | HAN → KHH | Apr 26, 08:50 UTC | Apr 26, 13:30 UTC | 4h 40m |
| 2026-04-26 | HVN587 | KHH → HAN | Apr 26, 00:25 UTC | Apr 26, 01:25 UTC | 1h 0m |
| 2026-04-25 | HVN586 | HAN → KHH | Apr 25, 12:25 UTC | Apr 25, 13:25 UTC | 1h 0m |
| 2026-04-25 | HVN1822 | PQC → SGN | Apr 25, 03:10 UTC | Apr 25, 03:35 UTC | 25m |
| 2026-04-22 | HVN812 | SAI → SGN | Apr 22, 12:45 UTC | Apr 22, 13:20 UTC | 35m |
| 2026-04-22 | HVN813 | SGN → SAI | Apr 22, 10:35 UTC | Apr 22, 10:45 UTC | 10m |
| 2026-04-22 | HVN1822 | PQC → SGN | Apr 22, 03:15 UTC | Apr 22, 03:40 UTC | 25m |
| 2026-04-22 | HVN1823 | SGN → PQC | Apr 22, 01:15 UTC | Apr 22, 01:30 UTC | 15m |
| 2026-04-21 | HVN1404 | SGN → VDH | Apr 21, 00:10 UTC | Apr 21, 00:35 UTC | 25m |
| 2026-04-20 | HVN119 | DAD → SGN | Apr 20, 05:05 UTC | Apr 20, 05:15 UTC | 10m |
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-A603 page for operator, model, and routing details .