sensors Mode-S transponder
888054
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A358 · AIRBUS A-321
- Hex
- 888054
- Octal
- 42100124
- Decimal
- 8,945,748
- Country
- VN
- Tail
- VN-A358
- Type
- A321
- Flights observed
- 56
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 888054 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 |
|---|---|---|---|
| HVN587 | Vietnam Airlines | 6 | 2026-05-11 |
| HVN586 | Vietnam Airlines | 4 | 2026-04-28 |
| HVN578 | Vietnam Airlines | 4 | 2026-05-07 |
| HVN584 | Vietnam Airlines | 3 | 2026-05-12 |
| HVN579 | Vietnam Airlines | 3 | 2026-05-07 |
| HVN649 | Vietnam Airlines | 2 | 2026-05-30 |
| HVN648 | Vietnam Airlines | 2 | 2026-05-30 |
| HVN595 | Vietnam Airlines | 2 | 2026-06-01 |
| HVN594 | Vietnam Airlines | 2 | 2026-06-01 |
| HVN585 | Vietnam Airlines | 2 | 2026-05-12 |
| HVN435 | Vietnam Airlines | 2 | 2026-05-08 |
| HVN430 | Vietnam Airlines | 2 | 2026-05-09 |
| HVN7559 | - | 1 | 2026-05-28 |
| HVN7160 | - | 1 | 2026-05-28 |
| HVN661 | Vietnam Airlines | 1 | 2026-04-27 |
| HVN657 | Vietnam Airlines | 1 | 2026-05-03 |
| HVN647 | Vietnam Airlines | 1 | 2026-04-19 |
| HVN619 | Vietnam Airlines | 1 | 2026-04-26 |
| HVN618 | Vietnam Airlines | 1 | 2026-04-26 |
| HVN615 | Vietnam Airlines | 1 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | HVN595 | HKG → SGN | Jun 1, 11:25 UTC | Jun 1, 11:40 UTC | 15m |
| 2026-06-01 | HVN594 | SGN → HKG | Jun 1, 08:55 UTC | Jun 1, 09:10 UTC | 15m |
| 2026-05-30 | HVN649 | MNL → SGN | May 30, 21:55 UTC | May 30, 22:25 UTC | 30m |
| 2026-05-30 | HVN648 | SGN → MNL | May 30, 18:30 UTC | May 30, 19:05 UTC | 35m |
| 2026-05-29 | HVN649 | MNL → SGN | May 29, 20:25 UTC | May 30, 19:00 UTC | 22h 35m |
| 2026-05-29 | HVN648 | SGN → MNL | May 29, 09:05 UTC | May 29, 19:20 UTC | 10h 16m |
| 2026-05-29 | HVN1622 | UIH → HAN | May 29, 07:30 UTC | May 29, 07:45 UTC | 15m |
| 2026-05-29 | HVN1623 | HAN → UIH | May 29, 04:30 UTC | May 29, 04:45 UTC | 15m |
| 2026-05-28 | HVN157 | HAN → DAD | May 28, 23:00 UTC | May 29, 01:35 UTC | 2h 35m |
| 2026-05-28 | HVN7559 | - | May 28, 13:55 UTC | May 28, 17:45 UTC | 3h 50m |
| 2026-05-28 | HVN7160 | - | May 28, 09:35 UTC | May 28, 12:50 UTC | 3h 15m |
| 2026-05-28 | HVN248 | SGN → HAN | May 28, 07:45 UTC | May 28, 08:10 UTC | 25m |
| 2026-05-26 | HVN502 | SGN → CAN | May 26, 05:20 UTC | May 26, 05:40 UTC | 20m |
| 2026-05-19 | HVN595 | HKG → SGN | May 19, 10:55 UTC | May 19, 11:10 UTC | 15m |
| 2026-05-19 | HVN594 | SGN → HKG | May 19, 08:50 UTC | May 19, 08:55 UTC | 5m |
| 2026-05-12 | HVN585 | KHH → HAN | May 12, 05:00 UTC | May 12, 06:00 UTC | 1h 0m |
| 2026-05-12 | HVN584 | HAN → KHH | May 12, 02:45 UTC | May 12, 03:35 UTC | 50m |
| 2026-05-11 | HVN587 | KHH → HAN | May 11, 00:30 UTC | May 11, 01:30 UTC | 1h 0m |
| 2026-05-10 | HVN431 | ICN → DAD | May 10, 02:39 UTC | May 10, 13:19 UTC | 10h 40m |
| 2026-05-09 | HVN430 | DAD → ICN | May 9, 01:05 UTC | May 9, 20:40 UTC | 19h 35m |
| 2026-05-08 | HVN430 | DAD → ICN | May 8, 23:25 UTC | May 9, 20:40 UTC | 21h 15m |
| 2026-05-08 | HVN435 | PUS → CXR | May 8, 19:05 UTC | May 9, 19:00 UTC | 23h 55m |
| 2026-05-08 | HVN435 | PUS → CXR | May 8, 18:35 UTC | May 9, 02:00 UTC | 7h 25m |
| 2026-05-08 | HVN434 | CXR → PUS | May 8, 01:04 UTC | May 9, 01:00 UTC | 23h 55m |
| 2026-05-07 | HVN579 | TPE → HAN | May 7, 23:59 UTC | May 8, 19:40 UTC | 19h 40m |
| 2026-05-07 | HVN578 | HAN → TPE | May 7, 11:30 UTC | May 7, 12:50 UTC | 1h 20m |
| 2026-05-05 | HVN593 | HKG → HAN | May 5, 06:55 UTC | May 5, 07:05 UTC | 10m |
| 2026-05-04 | HVN579 | TPE → HAN | May 4, 23:55 UTC | May 5, 05:15 UTC | 5h 20m |
| 2026-05-04 | HVN578 | HAN → TPE | May 4, 11:20 UTC | May 4, 12:30 UTC | 1h 10m |
| 2026-05-03 | HVN578 | HAN → TPE | May 3, 13:35 UTC | May 4, 12:30 UTC | 22h 55m |
| 2026-05-03 | HVN657 | SGN → SIN | May 3, 11:25 UTC | May 3, 12:05 UTC | 40m |
| 2026-05-01 | HVN608 | BKK → SGN | May 1, 14:20 UTC | May 1, 14:45 UTC | 25m |
| 2026-05-01 | HVN579 | TPE → HAN | May 1, 00:00 UTC | May 1, 12:50 UTC | 12h 50m |
| 2026-04-30 | HVN578 | HAN → TPE | Apr 30, 11:30 UTC | Apr 30, 13:00 UTC | 1h 30m |
| 2026-04-29 | HVN587 | KHH → HAN | Apr 29, 00:30 UTC | Apr 29, 01:15 UTC | 45m |
| 2026-04-28 | HVN586 | HAN → KHH | Apr 28, 05:20 UTC | Apr 28, 13:20 UTC | 8h 0m |
| 2026-04-27 | HVN661 | HAN → SIN | Apr 27, 15:40 UTC | Apr 28, 03:40 UTC | 12h 0m |
| 2026-04-27 | HVN614 | BKK → HAN | Apr 27, 08:50 UTC | Apr 27, 14:25 UTC | 5h 35m |
| 2026-04-27 | HVN615 | HAN → BKK | Apr 27, 07:00 UTC | Apr 27, 07:35 UTC | 35m |
| 2026-04-26 | HVN618 | BKK → HAN | Apr 26, 12:40 UTC | Apr 27, 07:35 UTC | 18h 55m |
| 2026-04-26 | HVN619 | HAN → BKK | Apr 26, 10:50 UTC | Apr 26, 11:20 UTC | 30m |
| 2026-04-23 | HVN587 | KHH → HAN | Apr 23, 00:30 UTC | Apr 23, 01:30 UTC | 1h 0m |
| 2026-04-22 | HVN586 | HAN → KHH | Apr 22, 12:35 UTC | Apr 22, 13:35 UTC | 1h 0m |
| 2026-04-21 | HVN587 | KHH → HAN | Apr 21, 00:30 UTC | Apr 21, 01:25 UTC | 55m |
| 2026-04-20 | HVN610 | BKK → HAN | Apr 20, 05:15 UTC | Apr 20, 13:30 UTC | 8h 15m |
| 2026-04-19 | HVN611 | HAN → BKK | Apr 19, 21:25 UTC | Apr 20, 03:40 UTC | 6h 15m |
| 2026-04-19 | HVN647 | HAN → MNL | Apr 19, 18:15 UTC | Apr 19, 19:45 UTC | 1h 30m |
| 2026-04-18 | HVN585 | KHH → HAN | Apr 18, 03:50 UTC | Apr 18, 04:50 UTC | 1h 0m |
| 2026-04-18 | HVN584 | HAN → KHH | Apr 18, 01:25 UTC | Apr 18, 02:10 UTC | 45m |
| 2026-04-18 | HVN584 | HAN → KHH | Apr 18, 01:10 UTC | Apr 18, 01:20 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-A358 page for operator, model, and routing details .