sensors Mode-S transponder
88804E
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A353 · AIRBUS A-321
- Hex
- 88804E
- Octal
- 42100116
- Decimal
- 8,945,742
- Country
- VN
- Tail
- VN-A353
- Type
- A321
- Flights observed
- 139
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 88804E 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 |
|---|---|---|---|
| HVN441 | Vietnam Airlines | 9 | 2026-05-19 |
| HVN440 | Vietnam Airlines | 7 | 2026-05-19 |
| HVN649 | - | 5 | 2026-07-01 |
| HVN434 | Vietnam Airlines | 5 | 2026-05-17 |
| HVN657 | - | 4 | 2026-07-12 |
| HVN656 | - | 4 | 2026-07-12 |
| HVN648 | - | 4 | 2026-06-24 |
| HVN570 | - | 4 | 2026-07-14 |
| HVN431 | Vietnam Airlines | 4 | 2026-05-01 |
| HVN430 | Vietnam Airlines | 4 | 2026-04-30 |
| HVN678 | - | 3 | 2026-07-03 |
| HVN582 | - | 3 | 2026-06-29 |
| HVN571 | - | 3 | 2026-07-01 |
| HVN435 | Vietnam Airlines | 3 | 2026-05-20 |
| HVN157 | - | 3 | 2026-07-04 |
| HVN679 | Vietnam Airlines | 2 | 2026-05-27 |
| HVN651 | - | 2 | 2026-07-10 |
| HVN650 | - | 2 | 2026-07-10 |
| HVN616 | Vietnam Airlines | 2 | 2026-06-26 |
| HVN583 | - | 2 | 2026-06-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | HVN570 | - | Jul 14, 11:50 UTC | Jul 14, 13:15 UTC | 1h 25m |
| 2026-07-12 | HVN656 | - | Jul 12, 14:01 UTC | Jul 12, 14:30 UTC | 30m |
| 2026-07-12 | HVN657 | - | Jul 12, 12:01 UTC | Jul 12, 12:25 UTC | 25m |
| 2026-07-12 | HVN604 | - | Jul 12, 07:55 UTC | Jul 12, 08:10 UTC | 15m |
| 2026-07-12 | HVN605 | - | Jul 12, 06:01 UTC | Jul 12, 06:30 UTC | 30m |
| 2026-07-10 | HVN650 | - | Jul 10, 05:30 UTC | Jul 10, 05:55 UTC | 25m |
| 2026-07-10 | HVN651 | - | Jul 10, 03:35 UTC | Jul 10, 04:05 UTC | 30m |
| 2026-07-09 | HVN1171 | - | Jul 9, 23:35 UTC | Jul 9, 23:45 UTC | 10m |
| 2026-07-08 | HVN581 | - | Jul 8, 23:40 UTC | Jul 9, 00:00 UTC | 20m |
| 2026-07-08 | HVN580 | SGN → KHH | Jul 8, 13:35 UTC | Jul 8, 14:05 UTC | 30m |
| 2026-07-07 | HVN656 | - | Jul 7, 13:25 UTC | Jul 7, 13:50 UTC | 25m |
| 2026-07-07 | HVN657 | - | Jul 7, 11:15 UTC | Jul 7, 11:50 UTC | 35m |
| 2026-07-07 | HVN1177 | - | Jul 7, 03:25 UTC | Jul 7, 03:40 UTC | 15m |
| 2026-07-07 | HVN1176 | - | Jul 7, 02:15 UTC | Jul 7, 02:25 UTC | 10m |
| 2026-07-06 | HVN267 | HAN → SGN | Jul 6, 15:15 UTC | Jul 6, 15:30 UTC | 15m |
| 2026-07-06 | HVN614 | - | Jul 6, 09:35 UTC | Jul 6, 10:20 UTC | 45m |
| 2026-07-06 | HVN615 | - | Jul 6, 06:35 UTC | Jul 6, 08:20 UTC | 1h 45m |
| 2026-07-06 | HVN1200 | - | Jul 6, 00:05 UTC | Jul 6, 04:40 UTC | 4h 35m |
| 2026-07-05 | HVN174 | - | Jul 5, 10:30 UTC | Jul 5, 10:45 UTC | 15m |
| 2026-07-05 | HVN173 | - | Jul 5, 07:55 UTC | Jul 5, 08:10 UTC | 15m |
| 2026-07-05 | HVN7544 | - | Jul 5, 03:30 UTC | Jul 5, 06:20 UTC | 2h 50m |
| 2026-07-04 | HVN157 | - | Jul 4, 23:05 UTC | Jul 5, 01:55 UTC | 2h 50m |
| 2026-07-04 | HVN7171 | HPH → SGN | Jul 4, 13:45 UTC | Jul 4, 16:45 UTC | 3h 0m |
| 2026-07-04 | HVN532 | - | Jul 4, 03:55 UTC | Jul 4, 12:20 UTC | 8h 25m |
| 2026-07-03 | HVN158 | - | Jul 3, 23:00 UTC | Jul 4, 02:15 UTC | 3h 15m |
| 2026-07-03 | HVN7270 | - | Jul 3, 17:40 UTC | Jul 3, 18:00 UTC | 20m |
| 2026-07-03 | HVN678 | - | Jul 3, 11:30 UTC | Jul 3, 11:45 UTC | 15m |
| 2026-07-03 | HVN650 | - | Jul 3, 05:35 UTC | Jul 3, 09:50 UTC | 4h 15m |
| 2026-07-02 | HVN651 | - | Jul 2, 13:20 UTC | Jul 3, 03:45 UTC | 14h 25m |
| 2026-07-01 | HVN649 | - | Jul 1, 20:15 UTC | Jul 2, 12:00 UTC | 15h 45m |
| 2026-07-01 | HVN571 | - | Jul 1, 00:35 UTC | Jul 1, 18:50 UTC | 18h 15m |
| 2026-06-30 | HVN570 | - | Jun 30, 11:50 UTC | Jun 30, 13:00 UTC | 1h 10m |
| 2026-06-29 | HVN583 | - | Jun 29, 05:15 UTC | Jun 29, 05:45 UTC | 30m |
| 2026-06-29 | HVN582 | - | Jun 29, 03:10 UTC | Jun 29, 03:49 UTC | 40m |
| 2026-06-27 | HVN267 | HAN → SGN | Jun 27, 15:24 UTC | Jun 27, 15:55 UTC | 30m |
| 2026-06-27 | HVN1718 | VII → HAN | Jun 27, 13:49 UTC | Jun 27, 14:09 UTC | 20m |
| 2026-06-27 | HVN1717 | HAN → VII | Jun 27, 12:15 UTC | Jun 27, 12:34 UTC | 20m |
| 2026-06-27 | HVN170 | - | Jun 27, 10:25 UTC | Jun 27, 10:45 UTC | 20m |
| 2026-06-27 | HVN169 | - | Jun 27, 07:49 UTC | Jun 27, 08:14 UTC | 25m |
| 2026-06-27 | HVN1236 | - | Jun 27, 00:55 UTC | Jun 27, 06:19 UTC | 5h 25m |
| 2026-06-26 | HVN616 | BKK → HAN | Jun 26, 15:25 UTC | Jun 26, 16:54 UTC | 1h 30m |
| 2026-06-26 | HVN617 | HAN → BKK | Jun 26, 12:34 UTC | Jun 26, 14:05 UTC | 1h 30m |
| 2026-06-26 | HVN1558 | CXR → HAN | Jun 26, 06:45 UTC | Jun 26, 11:00 UTC | 4h 15m |
| 2026-06-26 | HVN163 | HAN → DAD | Jun 26, 01:24 UTC | Jun 26, 04:20 UTC | 2h 55m |
| 2026-06-24 | HVN649 | - | Jun 24, 20:24 UTC | Jun 25, 14:29 UTC | 18h 5m |
| 2026-06-24 | HVN648 | - | Jun 24, 18:39 UTC | Jun 24, 19:20 UTC | 40m |
| 2026-06-21 | HVN583 | - | Jun 21, 05:20 UTC | Jun 21, 05:49 UTC | 30m |
| 2026-06-21 | HVN582 | - | Jun 21, 03:05 UTC | Jun 21, 03:49 UTC | 45m |
| 2026-06-20 | HVN582 | - | Jun 20, 06:10 UTC | Jun 21, 03:49 UTC | 21h 40m |
| 2026-06-15 | HVN1277 | THD → SGN | Jun 15, 11:00 UTC | Jun 15, 11:10 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-A353 page for operator, model, and routing details .