sensors Mode-S transponder
8880C0
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A608 · AIRBUS A-321
- Hex
- 8880C0
- Octal
- 42100300
- Decimal
- 8,945,856
- Country
- VN
- Tail
- VN-A608
- Type
- A321
- Flights observed
- 64
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 23h ago
Current position
Country allocation
The ICAO 24-bit address 8880C0 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 |
|---|---|---|---|
| HVN578 | Vietnam Airlines | 5 | 2026-05-25 |
| HVN592 | Vietnam Airlines | 4 | 2026-05-27 |
| HVN984 | Vietnam Airlines | 3 | 2026-05-15 |
| HVN680 | Vietnam Airlines | 3 | 2026-05-19 |
| HVN634 | Vietnam Airlines | 3 | 2026-05-16 |
| HVN611 | Vietnam Airlines | 3 | 2026-05-12 |
| HVN610 | Vietnam Airlines | 3 | 2026-05-13 |
| HVN593 | Vietnam Airlines | 3 | 2026-05-27 |
| HVN579 | Vietnam Airlines | 3 | 2026-05-25 |
| HVN985 | Vietnam Airlines | 2 | 2026-04-29 |
| HVN681 | Vietnam Airlines | 2 | 2026-05-19 |
| HVN660 | Vietnam Airlines | 2 | 2026-05-20 |
| HVN635 | Vietnam Airlines | 2 | 2026-05-16 |
| HVN1 | Vietnam Airlines | 2 | 2026-05-05 |
| HVN980 | Vietnam Airlines | 1 | 2026-05-06 |
| HVN922 | - | 1 | 2026-04-18 |
| HVN920 | Vietnam Airlines | 1 | 2026-05-10 |
| HVN661 | Vietnam Airlines | 1 | 2026-05-20 |
| HVN647 | Vietnam Airlines | 1 | 2026-05-17 |
| HVN646 | Vietnam Airlines | 1 | 2026-05-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | HVN524 | SGN → PVG | May 29, 02:25 UTC | May 29, 09:15 UTC | 6h 50m |
| 2026-05-28 | HVN595 | HKG → SGN | May 28, 11:05 UTC | May 28, 11:20 UTC | 15m |
| 2026-05-28 | HVN594 | SGN → HKG | May 28, 08:40 UTC | May 28, 09:00 UTC | 20m |
| 2026-05-28 | HVN247 | HAN → SGN | May 28, 03:10 UTC | May 28, 03:25 UTC | 15m |
| 2026-05-28 | HVN1716 | VII → HAN | May 28, 01:40 UTC | May 28, 02:00 UTC | 20m |
| 2026-05-28 | HVN1715 | HAN → VII | May 28, 00:05 UTC | May 28, 00:20 UTC | 15m |
| 2026-05-27 | HVN1562 | - | May 27, 10:30 UTC | May 27, 15:10 UTC | 4h 40m |
| 2026-05-27 | HVN593 | HKG → HAN | May 27, 06:55 UTC | May 27, 07:10 UTC | 15m |
| 2026-05-27 | HVN592 | HAN → HKG | May 27, 04:49 UTC | May 27, 05:24 UTC | 35m |
| 2026-05-26 | HVN593 | HKG → HAN | May 26, 06:54 UTC | May 26, 07:10 UTC | 15m |
| 2026-05-26 | HVN592 | HAN → HKG | May 26, 04:39 UTC | May 26, 05:15 UTC | 35m |
| 2026-05-25 | HVN579 | TPE → HAN | May 25, 23:49 UTC | May 26, 01:00 UTC | 1h 10m |
| 2026-05-25 | HVN578 | HAN → TPE | May 25, 11:35 UTC | May 25, 13:05 UTC | 1h 30m |
| 2026-05-24 | HVN587 | KHH → HAN | May 24, 00:35 UTC | May 24, 01:30 UTC | 55m |
| 2026-05-23 | HVN586 | HAN → KHH | May 23, 09:05 UTC | May 23, 13:55 UTC | 4h 50m |
| 2026-05-21 | HVN606 | BKK → SGN | May 21, 12:40 UTC | May 21, 13:10 UTC | 30m |
| 2026-05-21 | HVN607 | SGN → BKK | May 21, 10:30 UTC | May 21, 11:15 UTC | 45m |
| 2026-05-20 | HVN660 | SIN → HAN | May 20, 05:30 UTC | May 20, 05:45 UTC | 15m |
| 2026-05-20 | HVN661 | HAN → SIN | May 20, 03:00 UTC | May 20, 03:30 UTC | 30m |
| 2026-05-19 | HVN680 | KUL → HAN | May 19, 12:15 UTC | May 19, 12:25 UTC | 10m |
| 2026-05-19 | HVN681 | HAN → KUL | May 19, 10:35 UTC | May 19, 11:05 UTC | 30m |
| 2026-05-17 | HVN646 | MNL → HAN | May 17, 21:25 UTC | May 17, 22:01 UTC | 35m |
| 2026-05-17 | HVN647 | HAN → MNL | May 17, 05:20 UTC | May 17, 20:05 UTC | 14h 45m |
| 2026-05-16 | HVN634 | CGK → HAN | May 16, 18:40 UTC | May 17, 03:20 UTC | 8h 40m |
| 2026-05-16 | HVN635 | HAN → CGK | May 16, 16:55 UTC | May 16, 17:05 UTC | 10m |
| 2026-05-16 | HVN614 | BKK → HAN | May 16, 09:21 UTC | May 16, 10:16 UTC | 55m |
| 2026-05-15 | HVN984 | HYD → HAN | May 15, 13:40 UTC | May 16, 08:01 UTC | 18h 21m |
| 2026-05-15 | HVN984 | HYD → HAN | May 15, 00:05 UTC | May 15, 20:40 UTC | 20h 34m |
| 2026-05-14 | HVN984 | HYD → HAN | May 14, 23:50 UTC | May 15, 20:40 UTC | 20h 49m |
| 2026-05-14 | HVN578 | HAN → TPE | May 14, 11:35 UTC | May 14, 12:55 UTC | 1h 20m |
| 2026-05-13 | HVN578 | HAN → TPE | May 13, 12:15 UTC | May 14, 12:00 UTC | 23h 45m |
| 2026-05-13 | HVN610 | BKK → HAN | May 13, 05:10 UTC | May 13, 10:40 UTC | 5h 30m |
| 2026-05-12 | HVN611 | HAN → BKK | May 12, 08:35 UTC | May 13, 03:40 UTC | 19h 5m |
| 2026-05-10 | HVN920 | VTE → HAN | May 10, 12:15 UTC | May 10, 12:25 UTC | 10m |
| 2026-05-07 | HVN660 | SIN → HAN | May 7, 05:45 UTC | May 7, 06:05 UTC | 20m |
| 2026-05-06 | HVN980 | DEL → HAN | May 6, 19:10 UTC | May 6, 22:05 UTC | 2h 55m |
| 2026-05-05 | HVN1 | HAN → ORY | May 5, 08:25 UTC | May 5, 09:45 UTC | 1h 20m |
| 2026-05-05 | HVN1 | HAN → ORY | May 5, 02:55 UTC | May 5, 05:00 UTC | 2h 5m |
| 2026-05-02 | HVN507 | CAN → HAN | May 2, 08:40 UTC | May 2, 08:55 UTC | 15m |
| 2026-04-29 | HVN985 | HAN → HYD | Apr 29, 13:35 UTC | Apr 29, 20:35 UTC | 7h 0m |
| 2026-04-26 | HVN985 | HAN → HYD | Apr 26, 09:00 UTC | Apr 26, 20:30 UTC | 11h 30m |
| 2026-04-26 | HVN615 | HAN → BKK | Apr 26, 07:20 UTC | Apr 26, 07:50 UTC | 30m |
| 2026-04-26 | HVN1200 | VCA → HAN | Apr 26, 02:55 UTC | Apr 26, 03:05 UTC | 10m |
| 2026-04-24 | HVN680 | KUL → HAN | Apr 24, 12:25 UTC | Apr 24, 12:40 UTC | 15m |
| 2026-04-24 | HVN610 | BKK → HAN | Apr 24, 05:10 UTC | Apr 24, 11:10 UTC | 6h 0m |
| 2026-04-24 | HVN611 | HAN → BKK | Apr 24, 02:45 UTC | Apr 24, 03:45 UTC | 1h 0m |
| 2026-04-23 | HVN207 | HAN → SGN | Apr 23, 02:30 UTC | Apr 23, 02:40 UTC | 10m |
| 2026-04-18 | HVN922 | - | Apr 18, 14:25 UTC | Apr 19, 13:25 UTC | 23h 0m |
| 2026-04-18 | HVN680 | - | Apr 18, 13:00 UTC | Apr 18, 13:10 UTC | 10m |
| 2026-04-18 | HVN681 | HAN → KUL | Apr 18, 11:00 UTC | Apr 18, 11:20 UTC | 20m |
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-A608 page for operator, model, and routing details .