sensors Mode-S transponder
88809D
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A390 · AIRBUS A-321
- Hex
- 88809D
- Octal
- 42100235
- Decimal
- 8,945,821
- Country
- VN
- Tail
- VN-A390
- Type
- A321
- Flights observed
- 86
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 88809D 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 |
|---|---|---|---|
| HVN337 | Vietnam Airlines | 24 | 2026-05-29 |
| HVN336 | Vietnam Airlines | 22 | 2026-05-28 |
| HVN626 | Vietnam Airlines | 5 | 2026-05-29 |
| HVN610 | Vietnam Airlines | 3 | 2026-04-29 |
| HVN607 | Vietnam Airlines | 3 | 2026-04-16 |
| HVN661 | Vietnam Airlines | 2 | 2026-04-30 |
| HVN611 | Vietnam Airlines | 2 | 2026-04-28 |
| HVN606 | Vietnam Airlines | 2 | 2026-04-16 |
| HVN357 | Vietnam Airlines | 2 | 2026-05-06 |
| HVN320 | Vietnam Airlines | 2 | 2026-05-25 |
| HVN1440 | Vietnam Airlines | 2 | 2026-04-24 |
| HVN837 | Vietnam Airlines | 1 | 2026-05-30 |
| HVN7164 | Vietnam Airlines | 1 | 2026-05-29 |
| HVN681 | Vietnam Airlines | 1 | 2026-04-28 |
| HVN678 | Vietnam Airlines | 1 | 2026-05-26 |
| HVN651 | Vietnam Airlines | 1 | 2026-05-23 |
| HVN513 | Vietnam Airlines | 1 | 2026-05-05 |
| HVN512 | Vietnam Airlines | 1 | 2026-05-05 |
| HVN403 | Vietnam Airlines | 1 | 2026-05-27 |
| HVN402 | Vietnam Airlines | 1 | 2026-05-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | HVN837 | HAN → SAI | May 30, 08:35 UTC | May 30, 08:55 UTC | 20m |
| 2026-05-30 | HVN1552 | CXR → HAN | May 30, 06:55 UTC | May 30, 07:15 UTC | 20m |
| 2026-05-30 | HVN1553 | HAN → CXR | May 30, 03:05 UTC | May 30, 03:30 UTC | 25m |
| 2026-05-30 | HVN1716 | VII → HAN | May 30, 01:30 UTC | May 30, 01:45 UTC | 15m |
| 2026-05-29 | HVN1715 | HAN → VII | May 29, 23:55 UTC | May 30, 00:10 UTC | 15m |
| 2026-05-29 | HVN7164 | DAD → HAN | May 29, 14:25 UTC | May 29, 14:45 UTC | 20m |
| 2026-05-29 | HVN626 | BKK → DAD | May 29, 11:25 UTC | May 29, 12:00 UTC | 35m |
| 2026-05-29 | HVN337 | KIX → DAD | May 29, 00:50 UTC | May 29, 09:55 UTC | 9h 5m |
| 2026-05-28 | HVN336 | DAD → KIX | May 28, 19:35 UTC | May 28, 22:30 UTC | 2h 55m |
| 2026-05-27 | HVN403 | ICN → SGN | May 27, 08:55 UTC | May 27, 11:55 UTC | 3h 0m |
| 2026-05-27 | HVN402 | SGN → ICN | May 27, 04:30 UTC | May 27, 07:25 UTC | 2h 56m |
| 2026-05-26 | HVN678 | KUL → SGN | May 26, 11:44 UTC | May 26, 12:00 UTC | 15m |
| 2026-05-26 | HVN321 | KIX → SGN | May 26, 01:20 UTC | May 26, 10:20 UTC | 9h 0m |
| 2026-05-25 | HVN320 | SGN → KIX | May 25, 03:20 UTC | May 25, 22:19 UTC | 19h 0m |
| 2026-05-25 | HVN320 | SGN → KIX | May 25, 03:00 UTC | May 25, 22:19 UTC | 19h 19m |
| 2026-05-24 | HVN336 | DAD → KIX | May 24, 23:05 UTC | May 24, 23:15 UTC | 10m |
| 2026-05-24 | HVN337 | KIX → DAD | May 24, 03:00 UTC | May 24, 20:50 UTC | 17h 50m |
| 2026-05-24 | HVN337 | KIX → DAD | May 24, 00:35 UTC | May 24, 20:50 UTC | 20h 15m |
| 2026-05-23 | HVN336 | DAD → KIX | May 23, 05:20 UTC | May 23, 22:35 UTC | 17h 15m |
| 2026-05-23 | HVN651 | SGN → SIN | May 23, 03:10 UTC | May 23, 03:30 UTC | 20m |
| 2026-05-22 | HVN337 | KIX → DAD | May 22, 03:20 UTC | May 23, 03:15 UTC | 23h 54m |
| 2026-05-22 | HVN337 | KIX → DAD | May 22, 00:45 UTC | May 22, 03:45 UTC | 3h 0m |
| 2026-05-21 | HVN336 | DAD → KIX | May 21, 11:25 UTC | May 21, 22:40 UTC | 11h 15m |
| 2026-05-21 | HVN337 | KIX → DAD | May 21, 00:35 UTC | May 21, 09:55 UTC | 9h 20m |
| 2026-05-20 | HVN336 | DAD → KIX | May 20, 19:30 UTC | May 20, 22:35 UTC | 3h 5m |
| 2026-05-20 | HVN336 | DAD → KIX | May 20, 01:20 UTC | May 20, 22:35 UTC | 21h 16m |
| 2026-05-19 | HVN334 | HAN → KIX | May 19, 20:40 UTC | May 19, 21:25 UTC | 45m |
| 2026-05-18 | HVN626 | BKK → DAD | May 18, 11:20 UTC | May 18, 11:45 UTC | 25m |
| 2026-05-18 | HVN337 | KIX → DAD | May 18, 00:40 UTC | May 18, 09:40 UTC | 9h 0m |
| 2026-05-17 | HVN336 | DAD → KIX | May 17, 11:25 UTC | May 17, 22:40 UTC | 11h 15m |
| 2026-05-17 | HVN337 | KIX → DAD | May 17, 00:40 UTC | May 17, 09:55 UTC | 9h 15m |
| 2026-05-16 | HVN336 | DAD → KIX | May 16, 19:35 UTC | May 16, 22:40 UTC | 3h 5m |
| 2026-05-15 | HVN337 | KIX → DAD | May 15, 00:50 UTC | May 15, 04:05 UTC | 3h 15m |
| 2026-05-14 | HVN336 | DAD → KIX | May 14, 11:25 UTC | May 14, 22:45 UTC | 11h 20m |
| 2026-05-14 | HVN337 | KIX → DAD | May 14, 00:40 UTC | May 14, 09:50 UTC | 9h 10m |
| 2026-05-13 | HVN336 | DAD → KIX | May 13, 19:30 UTC | May 13, 22:25 UTC | 2h 55m |
| 2026-05-11 | HVN626 | BKK → DAD | May 11, 11:10 UTC | May 11, 11:45 UTC | 35m |
| 2026-05-11 | HVN337 | KIX → DAD | May 11, 00:40 UTC | May 11, 09:40 UTC | 9h 0m |
| 2026-05-10 | HVN336 | DAD → KIX | May 10, 03:20 UTC | May 10, 22:30 UTC | 19h 10m |
| 2026-05-10 | HVN336 | DAD → KIX | May 10, 01:55 UTC | May 10, 22:30 UTC | 20h 35m |
| 2026-05-10 | HVN337 | KIX → DAD | May 10, 00:34 UTC | May 10, 22:30 UTC | 21h 55m |
| 2026-05-09 | HVN336 | DAD → KIX | May 9, 19:45 UTC | May 9, 22:39 UTC | 2h 55m |
| 2026-05-08 | HVN337 | KIX → DAD | May 8, 00:40 UTC | May 8, 04:04 UTC | 3h 25m |
| 2026-05-07 | HVN336 | DAD → KIX | May 7, 11:30 UTC | May 7, 22:45 UTC | 11h 15m |
| 2026-05-06 | HVN336 | DAD → KIX | May 6, 19:30 UTC | May 7, 10:00 UTC | 14h 30m |
| 2026-05-06 | HVN357 | FUK → HAN | May 6, 01:15 UTC | May 6, 01:25 UTC | 10m |
| 2026-05-05 | HVN356 | HAN → FUK | May 5, 22:15 UTC | May 5, 22:25 UTC | 10m |
| 2026-05-05 | HVN513 | PEK → HAN | May 5, 08:05 UTC | May 5, 08:20 UTC | 15m |
| 2026-05-05 | HVN512 | HAN → PEK | May 5, 06:15 UTC | May 5, 06:25 UTC | 10m |
| 2026-05-03 | HVN626 | BKK → DAD | May 3, 11:35 UTC | May 3, 12:05 UTC | 30m |
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-A390 page for operator, model, and routing details .