sensors Mode-S transponder
8880B5
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A606 · AIRBUS A-321
- Hex
- 8880B5
- Octal
- 42100265
- Decimal
- 8,945,845
- Country
- VN
- Tail
- VN-A606
- Type
- A321
- Flights observed
- 79
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 10m ago
Current position
Country allocation
The ICAO 24-bit address 8880B5 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 |
|---|---|---|---|
| HVN318 | Vietnam Airlines | 17 | 2026-05-19 |
| HVN342 | Vietnam Airlines | 11 | 2026-05-20 |
| HVN343 | Vietnam Airlines | 8 | 2026-05-21 |
| HVN351 | Vietnam Airlines | 7 | 2026-05-13 |
| HVN319 | Vietnam Airlines | 7 | 2026-05-20 |
| HVN350 | Vietnam Airlines | 4 | 2026-05-12 |
| HVN1827 | Vietnam Airlines | 3 | 2026-04-24 |
| HVN1826 | Vietnam Airlines | 3 | 2026-04-24 |
| HVN655 | Vietnam Airlines | 2 | 2026-04-25 |
| HVN654 | Vietnam Airlines | 2 | 2026-04-25 |
| HVN403 | Vietnam Airlines | 2 | 2026-05-30 |
| HVN402 | Vietnam Airlines | 2 | 2026-05-29 |
| HVN7220 | Vietnam Airlines | 1 | 2026-05-29 |
| HVN608 | Vietnam Airlines | 1 | 2026-04-30 |
| HVN595 | Vietnam Airlines | 1 | 2026-04-28 |
| HVN594 | Vietnam Airlines | 1 | 2026-04-28 |
| HVN357 | Vietnam Airlines | 1 | 2026-05-03 |
| HVN349 | - | 1 | 2026-04-13 |
| HVN262 | Vietnam Airlines | 1 | 2026-04-23 |
| HVN243 | Vietnam Airlines | 1 | 2026-04-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | HVN403 | ICN → SGN | May 30, 09:20 UTC | May 30, 11:15 UTC | 1h 55m |
| 2026-05-29 | HVN402 | SGN → ICN | May 29, 22:10 UTC | May 30, 07:10 UTC | 9h 0m |
| 2026-05-29 | HVN7220 | SGN → HAN | May 29, 13:15 UTC | May 29, 13:35 UTC | 20m |
| 2026-05-23 | HVN403 | ICN → SGN | May 23, 08:50 UTC | May 23, 11:40 UTC | 2h 50m |
| 2026-05-23 | HVN402 | SGN → ICN | May 23, 04:25 UTC | May 23, 07:20 UTC | 2h 55m |
| 2026-05-21 | HVN343 | NGO → SGN | May 21, 00:15 UTC | May 21, 03:25 UTC | 3h 10m |
| 2026-05-20 | HVN342 | SGN → NGO | May 20, 03:20 UTC | May 20, 22:20 UTC | 19h 1m |
| 2026-05-20 | HVN342 | SGN → NGO | May 20, 02:10 UTC | May 20, 22:20 UTC | 20h 11m |
| 2026-05-20 | HVN319 | NRT → DAD | May 20, 00:10 UTC | May 20, 22:20 UTC | 22h 11m |
| 2026-05-19 | HVN318 | DAD → NRT | May 19, 18:30 UTC | May 19, 22:10 UTC | 3h 40m |
| 2026-05-18 | HVN319 | NRT → DAD | May 18, 00:20 UTC | May 18, 04:05 UTC | 3h 45m |
| 2026-05-17 | HVN318 | DAD → NRT | May 17, 18:40 UTC | May 17, 22:40 UTC | 4h 0m |
| 2026-05-17 | HVN318 | DAD → NRT | May 17, 01:35 UTC | May 17, 22:40 UTC | 21h 5m |
| 2026-05-17 | HVN318 | DAD → NRT | May 17, 00:20 UTC | May 17, 22:40 UTC | 22h 20m |
| 2026-05-16 | HVN342 | SGN → NGO | May 16, 22:00 UTC | May 16, 22:15 UTC | 15m |
| 2026-05-16 | HVN342 | SGN → NGO | May 16, 19:15 UTC | May 16, 20:55 UTC | 1h 40m |
| 2026-05-15 | HVN319 | NRT → DAD | May 15, 00:15 UTC | May 15, 04:15 UTC | 4h 0m |
| 2026-05-14 | HVN318 | DAD → NRT | May 14, 03:20 UTC | May 14, 22:10 UTC | 18h 50m |
| 2026-05-14 | HVN318 | DAD → NRT | May 14, 01:30 UTC | May 14, 22:10 UTC | 20h 40m |
| 2026-05-14 | HVN318 | DAD → NRT | May 14, 00:05 UTC | May 14, 22:10 UTC | 22h 5m |
| 2026-05-13 | HVN342 | SGN → NGO | May 13, 21:45 UTC | May 13, 21:55 UTC | 10m |
| 2026-05-13 | HVN351 | FUK → SGN | May 13, 02:15 UTC | May 13, 20:45 UTC | 18h 30m |
| 2026-05-13 | HVN351 | FUK → SGN | May 13, 01:20 UTC | May 13, 01:30 UTC | 10m |
| 2026-05-12 | HVN350 | SGN → FUK | May 12, 03:30 UTC | May 12, 21:30 UTC | 18h 0m |
| 2026-05-12 | HVN319 | NRT → DAD | May 12, 02:45 UTC | May 12, 21:30 UTC | 18h 45m |
| 2026-05-11 | HVN318 | DAD → NRT | May 11, 03:20 UTC | May 11, 22:10 UTC | 18h 50m |
| 2026-05-11 | HVN318 | DAD → NRT | May 11, 01:50 UTC | May 11, 22:10 UTC | 20h 20m |
| 2026-05-11 | HVN318 | DAD → NRT | May 11, 00:15 UTC | May 11, 22:10 UTC | 21h 56m |
| 2026-05-10 | HVN342 | SGN → NGO | May 10, 21:44 UTC | May 10, 21:54 UTC | 10m |
| 2026-05-10 | HVN343 | NGO → SGN | May 10, 01:39 UTC | May 10, 20:40 UTC | 19h 0m |
| 2026-05-10 | HVN343 | NGO → SGN | May 10, 00:05 UTC | May 10, 20:40 UTC | 20h 35m |
| 2026-05-09 | HVN342 | SGN → NGO | May 9, 22:00 UTC | May 9, 22:10 UTC | 10m |
| 2026-05-09 | HVN319 | NRT → DAD | May 9, 01:20 UTC | May 9, 21:05 UTC | 19h 45m |
| 2026-05-09 | HVN319 | NRT → DAD | May 9, 00:30 UTC | May 9, 21:05 UTC | 20h 35m |
| 2026-05-08 | HVN318 | DAD → NRT | May 8, 18:30 UTC | May 8, 21:55 UTC | 3h 25m |
| 2026-05-07 | HVN319 | NRT → DAD | May 7, 00:30 UTC | May 7, 04:30 UTC | 4h 0m |
| 2026-05-06 | HVN318 | DAD → NRT | May 6, 03:45 UTC | May 6, 22:40 UTC | 18h 54m |
| 2026-05-06 | HVN318 | DAD → NRT | May 6, 02:35 UTC | May 6, 22:40 UTC | 20h 4m |
| 2026-05-06 | HVN318 | DAD → NRT | May 6, 00:20 UTC | May 6, 22:40 UTC | 22h 19m |
| 2026-05-05 | HVN318 | DAD → NRT | May 5, 18:30 UTC | May 5, 21:50 UTC | 3h 20m |
| 2026-05-03 | HVN357 | FUK → HAN | May 3, 01:50 UTC | May 3, 02:00 UTC | 10m |
| 2026-04-30 | HVN608 | BKK → SGN | Apr 30, 14:15 UTC | Apr 30, 14:30 UTC | 15m |
| 2026-04-29 | HVN343 | NGO → SGN | Apr 29, 19:15 UTC | Apr 30, 12:50 UTC | 17h 34m |
| 2026-04-29 | HVN343 | NGO → SGN | Apr 29, 14:35 UTC | Apr 30, 12:50 UTC | 22h 14m |
| 2026-04-29 | HVN351 | FUK → SGN | Apr 29, 02:09 UTC | Apr 29, 13:30 UTC | 11h 21m |
| 2026-04-29 | HVN351 | FUK → SGN | Apr 29, 01:20 UTC | Apr 29, 01:30 UTC | 10m |
| 2026-04-28 | HVN350 | SGN → FUK | Apr 28, 19:50 UTC | Apr 28, 21:35 UTC | 1h 45m |
| 2026-04-28 | HVN595 | HKG → SGN | Apr 28, 11:05 UTC | Apr 28, 11:20 UTC | 15m |
| 2026-04-28 | HVN594 | SGN → HKG | Apr 28, 08:50 UTC | Apr 28, 08:55 UTC | 5m |
| 2026-04-27 | HVN343 | NGO → SGN | Apr 27, 00:25 UTC | Apr 27, 03:35 UTC | 3h 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-A606 page for operator, model, and routing details .