sensors Mode-S transponder
88816A
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A619 · AIRBUS A-321neo
- Hex
- 88816A
- Octal
- 42100552
- Decimal
- 8,946,026
- Country
- VN
- Tail
- VN-A619
- Type
- A21N
- Flights observed
- 36
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address 88816A 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 |
|---|---|---|---|
| HVN643 | Vietnam Airlines | 3 | 2026-04-23 |
| HVN357 | Vietnam Airlines | 3 | 2026-05-04 |
| HVN977 | Vietnam Airlines | 2 | 2026-05-19 |
| HVN661 | Vietnam Airlines | 2 | 2026-05-06 |
| HVN647 | Vietnam Airlines | 2 | 2026-04-22 |
| HVN611 | Vietnam Airlines | 2 | 2026-04-22 |
| HVN579 | Vietnam Airlines | 2 | 2026-05-16 |
| HVN356 | Vietnam Airlines | 2 | 2026-05-03 |
| HVN983 | Vietnam Airlines | 1 | 2026-04-26 |
| HVN982 | Vietnam Airlines | 1 | 2026-04-26 |
| HVN976 | Vietnam Airlines | 1 | 2026-05-19 |
| HVN9335 | Vietnam Airlines | 1 | 2026-04-29 |
| HVN9334 | Vietnam Airlines | 1 | 2026-04-28 |
| HVN921 | Vietnam Airlines | 1 | 2026-05-08 |
| HVN660 | Vietnam Airlines | 1 | 2026-04-27 |
| HVN657 | Vietnam Airlines | 1 | 2026-05-18 |
| HVN655 | Vietnam Airlines | 1 | 2026-05-14 |
| HVN648 | Vietnam Airlines | 1 | 2026-05-18 |
| HVN642 | Vietnam Airlines | 1 | 2026-04-21 |
| HVN618 | Vietnam Airlines | 1 | 2026-05-16 |
Recent flights last 36
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-19 | HVN976 | DEL → SGN | May 19, 19:15 UTC | May 19, 23:10 UTC | 3h 55m |
| 2026-05-19 | HVN977 | SGN → DEL | May 19, 12:50 UTC | May 19, 17:05 UTC | 4h 15m |
| 2026-05-18 | HVN977 | SGN → DEL | May 18, 20:35 UTC | May 19, 17:05 UTC | 20h 30m |
| 2026-05-18 | HVN648 | SGN → MNL | May 18, 13:35 UTC | May 18, 19:05 UTC | 5h 29m |
| 2026-05-18 | HVN657 | SGN → SIN | May 18, 11:40 UTC | May 18, 12:15 UTC | 35m |
| 2026-05-16 | HVN618 | BKK → HAN | May 16, 12:31 UTC | May 16, 12:55 UTC | 25m |
| 2026-05-16 | HVN579 | TPE → HAN | May 16, 00:15 UTC | May 16, 11:01 UTC | 10h 46m |
| 2026-05-15 | HVN431 | ICN → DAD | May 15, 02:35 UTC | May 15, 12:50 UTC | 10h 15m |
| 2026-05-14 | HVN430 | DAD → ICN | May 14, 10:40 UTC | May 14, 20:45 UTC | 10h 5m |
| 2026-05-14 | HVN655 | SGN → SIN | May 14, 08:30 UTC | May 14, 08:45 UTC | 15m |
| 2026-05-08 | HVN921 | HAN → VTE | May 8, 04:14 UTC | May 8, 04:34 UTC | 20m |
| 2026-05-06 | HVN579 | TPE → HAN | May 6, 23:55 UTC | May 7, 01:05 UTC | 1h 10m |
| 2026-05-06 | HVN578 | HAN → TPE | May 6, 05:30 UTC | May 6, 12:50 UTC | 7h 20m |
| 2026-05-06 | HVN661 | HAN → SIN | May 6, 03:05 UTC | May 6, 03:20 UTC | 15m |
| 2026-05-04 | HVN357 | FUK → HAN | May 4, 01:20 UTC | May 4, 01:35 UTC | 15m |
| 2026-05-03 | HVN356 | HAN → FUK | May 3, 22:39 UTC | May 3, 22:49 UTC | 10m |
| 2026-05-01 | HVN616 | BKK → HAN | May 1, 15:35 UTC | May 1, 16:00 UTC | 25m |
| 2026-05-01 | HVN617 | HAN → BKK | May 1, 13:30 UTC | May 1, 14:00 UTC | 30m |
| 2026-05-01 | HVN357 | FUK → HAN | May 1, 01:25 UTC | May 1, 01:35 UTC | 10m |
| 2026-04-30 | HVN356 | HAN → FUK | Apr 30, 22:25 UTC | Apr 30, 22:35 UTC | 10m |
| 2026-04-29 | HVN9335 | IZO → HAN | Apr 29, 02:35 UTC | Apr 29, 03:10 UTC | 35m |
| 2026-04-28 | HVN9334 | HAN → IZO | Apr 28, 23:29 UTC | Apr 28, 23:54 UTC | 25m |
| 2026-04-28 | HVN357 | FUK → HAN | Apr 28, 01:15 UTC | Apr 28, 01:25 UTC | 10m |
| 2026-04-27 | HVN660 | SIN → HAN | Apr 27, 05:35 UTC | Apr 27, 05:50 UTC | 15m |
| 2026-04-27 | HVN661 | HAN → SIN | Apr 27, 03:15 UTC | Apr 27, 04:00 UTC | 45m |
| 2026-04-26 | HVN982 | BLR → HAN | Apr 26, 18:25 UTC | Apr 26, 21:30 UTC | 3h 5m |
| 2026-04-26 | HVN983 | HAN → BLR | Apr 26, 13:05 UTC | Apr 26, 16:45 UTC | 3h 40m |
| 2026-04-23 | HVN643 | HAN → CEB | Apr 23, 05:25 UTC | Apr 23, 21:55 UTC | 16h 29m |
| 2026-04-22 | HVN611 | HAN → BKK | Apr 22, 21:10 UTC | Apr 23, 03:50 UTC | 6h 40m |
| 2026-04-22 | HVN647 | HAN → MNL | Apr 22, 09:50 UTC | Apr 22, 19:50 UTC | 10h 0m |
| 2026-04-21 | HVN647 | HAN → MNL | Apr 21, 21:10 UTC | Apr 22, 19:50 UTC | 22h 40m |
| 2026-04-21 | HVN642 | CEB → HAN | Apr 21, 18:35 UTC | Apr 22, 18:30 UTC | 23h 55m |
| 2026-04-21 | HVN643 | HAN → CEB | Apr 21, 17:10 UTC | Apr 22, 09:50 UTC | 16h 40m |
| 2026-04-21 | HVN643 | HAN → CEB | Apr 21, 05:20 UTC | Apr 21, 22:00 UTC | 16h 40m |
| 2026-04-21 | HVN611 | HAN → BKK | Apr 21, 02:40 UTC | Apr 21, 03:40 UTC | 1h 0m |
| 2026-04-13 | HVN502 | SGN → CAN | Apr 13, 05:25 UTC | Apr 13, 05:45 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-A619 page for operator, model, and routing details .