sensors Mode-S transponder
888170
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A625 · AIRBUS A-321neo
- Hex
- 888170
- Octal
- 42100560
- Decimal
- 8,946,032
- Country
- VN
- Tail
- VN-A625
- Type
- A21N
- Flights observed
- 49
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 888170 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 |
|---|---|---|---|
| HVN430 | Vietnam Airlines | 5 | 2026-05-23 |
| HVN431 | Vietnam Airlines | 4 | 2026-05-24 |
| HVN649 | Vietnam Airlines | 2 | 2026-05-24 |
| HVN648 | Vietnam Airlines | 2 | 2026-04-24 |
| HVN617 | Vietnam Airlines | 2 | 2026-05-29 |
| HVN616 | Vietnam Airlines | 2 | 2026-05-29 |
| HVN1186 | Vietnam Airlines | 2 | 2026-05-27 |
| HVN983 | Vietnam Airlines | 1 | 2026-04-28 |
| HVN982 | Vietnam Airlines | 1 | 2026-04-28 |
| HVN680 | Vietnam Airlines | 1 | 2026-04-27 |
| HVN679 | Vietnam Airlines | 1 | 2026-05-01 |
| HVN678 | Vietnam Airlines | 1 | 2026-05-01 |
| HVN651 | Vietnam Airlines | 1 | 2026-05-07 |
| HVN647 | Vietnam Airlines | 1 | 2026-04-26 |
| HVN646 | Vietnam Airlines | 1 | 2026-04-26 |
| HVN643 | Vietnam Airlines | 1 | 2026-05-10 |
| HVN631 | Vietnam Airlines | 1 | 2026-05-27 |
| HVN630 | Vietnam Airlines | 1 | 2026-05-27 |
| HVN619 | Vietnam Airlines | 1 | 2026-05-10 |
| HVN610 | Vietnam Airlines | 1 | 2026-04-27 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | HVN356 | HAN → FUK | May 29, 18:45 UTC | May 29, 19:10 UTC | 25m |
| 2026-05-29 | HVN616 | BKK → HAN | May 29, 15:20 UTC | May 29, 16:40 UTC | 1h 20m |
| 2026-05-29 | HVN617 | HAN → BKK | May 29, 12:10 UTC | May 29, 13:35 UTC | 1h 25m |
| 2026-05-29 | HVN232 | SGN → HAN | May 29, 10:25 UTC | May 29, 10:40 UTC | 15m |
| 2026-05-27 | HVN1187 | HPH → SGN | May 27, 13:50 UTC | May 27, 14:10 UTC | 20m |
| 2026-05-27 | HVN1186 | SGN → HPH | May 27, 12:25 UTC | May 27, 12:45 UTC | 20m |
| 2026-05-27 | HVN630 | CGK → SGN | May 27, 07:05 UTC | May 27, 08:25 UTC | 1h 20m |
| 2026-05-27 | HVN631 | SGN → CGK | May 27, 05:35 UTC | May 27, 05:49 UTC | 15m |
| 2026-05-24 | HVN649 | MNL → SGN | May 24, 20:10 UTC | May 24, 20:40 UTC | 30m |
| 2026-05-24 | HVN431 | ICN → DAD | May 24, 02:35 UTC | May 24, 18:40 UTC | 16h 5m |
| 2026-05-23 | HVN430 | DAD → ICN | May 23, 11:50 UTC | May 23, 20:50 UTC | 9h 0m |
| 2026-05-23 | HVN431 | ICN → DAD | May 23, 02:15 UTC | May 23, 09:55 UTC | 7h 39m |
| 2026-05-22 | HVN430 | DAD → ICN | May 22, 17:55 UTC | May 22, 20:40 UTC | 2h 45m |
| 2026-05-10 | HVN643 | HAN → CEB | May 10, 12:30 UTC | May 10, 21:59 UTC | 9h 30m |
| 2026-05-10 | HVN619 | HAN → BKK | May 10, 10:05 UTC | May 10, 11:10 UTC | 1h 5m |
| 2026-05-08 | HVN431 | ICN → DAD | May 8, 02:35 UTC | May 8, 05:29 UTC | 2h 55m |
| 2026-05-07 | HVN430 | DAD → ICN | May 7, 05:55 UTC | May 7, 20:35 UTC | 14h 40m |
| 2026-05-07 | HVN651 | SGN → SIN | May 7, 03:20 UTC | May 7, 03:40 UTC | 20m |
| 2026-05-05 | HVN435 | PUS → CXR | May 5, 23:25 UTC | May 6, 02:01 UTC | 2h 35m |
| 2026-05-05 | HVN434 | CXR → PUS | May 5, 18:25 UTC | May 5, 19:30 UTC | 1h 5m |
| 2026-05-02 | HVN502 | SGN → CAN | May 2, 05:15 UTC | May 2, 05:35 UTC | 20m |
| 2026-05-01 | HVN678 | KUL → SGN | May 1, 13:05 UTC | May 1, 13:20 UTC | 15m |
| 2026-05-01 | HVN679 | SGN → KUL | May 1, 09:55 UTC | May 1, 10:45 UTC | 50m |
| 2026-04-30 | HVN604 | BKK → SGN | Apr 30, 08:00 UTC | Apr 30, 08:30 UTC | 30m |
| 2026-04-30 | HVN605 | SGN → BKK | Apr 30, 05:40 UTC | Apr 30, 06:20 UTC | 40m |
| 2026-04-28 | HVN982 | BLR → HAN | Apr 28, 19:30 UTC | Apr 28, 22:45 UTC | 3h 15m |
| 2026-04-28 | HVN983 | HAN → BLR | Apr 28, 14:15 UTC | Apr 28, 17:55 UTC | 3h 40m |
| 2026-04-27 | HVN680 | KUL → HAN | Apr 27, 12:20 UTC | Apr 27, 12:35 UTC | 15m |
| 2026-04-27 | HVN610 | BKK → HAN | Apr 27, 05:10 UTC | Apr 27, 10:45 UTC | 5h 35m |
| 2026-04-26 | HVN646 | MNL → HAN | Apr 26, 21:40 UTC | Apr 27, 03:50 UTC | 6h 10m |
| 2026-04-26 | HVN647 | HAN → MNL | Apr 26, 18:15 UTC | Apr 26, 19:55 UTC | 1h 40m |
| 2026-04-25 | HVN616 | BKK → HAN | Apr 25, 15:35 UTC | Apr 25, 16:00 UTC | 25m |
| 2026-04-25 | HVN617 | HAN → BKK | Apr 25, 13:55 UTC | Apr 25, 14:25 UTC | 30m |
| 2026-04-25 | HVN246 | SGN → HAN | Apr 25, 04:20 UTC | Apr 25, 04:30 UTC | 10m |
| 2026-04-25 | HVN1340 | SGN → CXR | Apr 25, 00:15 UTC | Apr 25, 00:30 UTC | 15m |
| 2026-04-24 | HVN649 | MNL → SGN | Apr 24, 20:25 UTC | Apr 24, 20:55 UTC | 30m |
| 2026-04-24 | HVN648 | SGN → MNL | Apr 24, 18:20 UTC | Apr 24, 18:55 UTC | 35m |
| 2026-04-24 | HVN648 | SGN → MNL | Apr 24, 16:50 UTC | Apr 24, 17:00 UTC | 10m |
| 2026-04-24 | HVN1273 | THD → SGN | Apr 24, 07:40 UTC | Apr 24, 07:55 UTC | 15m |
| 2026-04-23 | HVN1186 | SGN → HPH | Apr 23, 11:01 UTC | Apr 23, 11:15 UTC | 15m |
| 2026-04-23 | HVN119 | DAD → SGN | Apr 23, 05:30 UTC | Apr 23, 05:40 UTC | 10m |
| 2026-04-23 | HVN118 | SGN → DAD | Apr 23, 02:30 UTC | Apr 23, 02:40 UTC | 10m |
| 2026-04-22 | HVN1345 | CXR → SGN | Apr 22, 08:45 UTC | Apr 22, 08:55 UTC | 10m |
| 2026-04-22 | HVN1344 | SGN → CXR | Apr 22, 06:20 UTC | Apr 22, 06:30 UTC | 10m |
| 2026-04-22 | HVN1342 | SGN → CXR | Apr 22, 02:20 UTC | Apr 22, 02:40 UTC | 20m |
| 2026-04-21 | HVN112 | SGN → DAD | Apr 21, 01:15 UTC | Apr 21, 01:35 UTC | 20m |
| 2026-04-14 | HVN431 | ICN → DAD | Apr 14, 05:15 UTC | Apr 14, 05:30 UTC | 15m |
| 2026-04-13 | HVN430 | DAD → ICN | Apr 13, 19:55 UTC | Apr 13, 20:40 UTC | 45m |
| 2026-04-13 | HVN430 | DAD → ICN | Apr 13, 17:45 UTC | Apr 13, 20:10 UTC | 2h 25m |
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-A625 page for operator, model, and routing details .