sensors Mode-S transponder
8880E2
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A864 · BOEING 787-9 Dreamliner
- Hex
- 8880E2
- Octal
- 42100342
- Decimal
- 8,945,890
- Country
- VN
- Tail
- VN-A864
- Type
- B789
- Flights observed
- 100
- Distinct callsigns
- 19
- Country
- VN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 8880E2 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HVN37 | Vietnam Airlines | 24 | 2026-05-18 |
| HVN36 | Vietnam Airlines | 19 | 2026-05-19 |
| HVN31 | Vietnam Airlines | 11 | 2026-05-15 |
| HVN30 | Vietnam Airlines | 11 | 2026-05-14 |
| HVN51 | Vietnam Airlines | 8 | 2026-05-28 |
| HVN56 | Vietnam Airlines | 5 | 2026-05-17 |
| HVN50 | Vietnam Airlines | 5 | 2026-05-28 |
| HVN35 | Vietnam Airlines | 5 | 2026-05-29 |
| HVN55 | Vietnam Airlines | 2 | 2026-05-17 |
| HVN39 | Vietnam Airlines | 1 | 2026-04-24 |
| HVN385 | Vietnam Airlines | 1 | 2026-05-05 |
| HVN38 | Vietnam Airlines | 1 | 2026-04-25 |
| HVN34D | - | 1 | 2026-05-23 |
| HVN34 | Vietnam Airlines | 1 | 2026-05-02 |
| HVN262 | Vietnam Airlines | 1 | 2026-05-29 |
| HVN258 | - | 1 | 2026-04-17 |
| HVN254 | Vietnam Airlines | 1 | 2026-05-27 |
| HVN212 | Vietnam Airlines | 1 | 2026-04-17 |
| HVN209 | Vietnam Airlines | 1 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | HVN35 | HAN → MUC | May 29, 17:10 UTC | May 30, 04:25 UTC | 11h 15m |
| 2026-05-29 | HVN262 | SGN → HAN | May 29, 14:15 UTC | May 29, 14:30 UTC | 15m |
| 2026-05-28 | HVN50 | LHR → SGN | May 28, 18:35 UTC | May 29, 05:35 UTC | 11h 0m |
| 2026-05-28 | HVN51 | SGN → LHR | May 28, 03:25 UTC | May 28, 16:15 UTC | 12h 50m |
| 2026-05-27 | HVN51 | SGN → LHR | May 27, 13:30 UTC | May 28, 12:25 UTC | 22h 55m |
| 2026-05-27 | HVN254 | SGN → HAN | May 27, 11:20 UTC | May 27, 11:35 UTC | 15m |
| 2026-05-23 | HVN34D | - | May 23, 16:25 UTC | May 24, 01:25 UTC | 9h 0m |
| 2026-05-20 | HVN35 | HAN → MUC | May 20, 08:35 UTC | May 21, 04:20 UTC | 19h 45m |
| 2026-05-20 | HVN35 | HAN → MUC | May 20, 07:55 UTC | May 21, 04:20 UTC | 20h 25m |
| 2026-05-19 | HVN36 | FRA → HAN | May 19, 12:30 UTC | May 20, 05:35 UTC | 17h 6m |
| 2026-05-18 | HVN37 | HAN → FRA | May 18, 18:05 UTC | May 19, 04:40 UTC | 10h 34m |
| 2026-05-18 | HVN37 | HAN → FRA | May 18, 04:40 UTC | May 19, 04:30 UTC | 23h 49m |
| 2026-05-18 | HVN37 | HAN → FRA | May 18, 02:35 UTC | May 19, 01:50 UTC | 23h 14m |
| 2026-05-18 | HVN37 | HAN → FRA | May 18, 02:15 UTC | May 18, 21:45 UTC | 19h 29m |
| 2026-05-17 | HVN56 | LHR → HAN | May 17, 23:10 UTC | May 18, 21:45 UTC | 22h 34m |
| 2026-05-17 | HVN56 | LHR → HAN | May 17, 20:35 UTC | May 18, 20:30 UTC | 23h 54m |
| 2026-05-17 | HVN56 | LHR → HAN | May 17, 19:25 UTC | May 18, 18:20 UTC | 22h 55m |
| 2026-05-17 | HVN55 | HAN → LHR | May 17, 12:25 UTC | May 17, 16:35 UTC | 4h 10m |
| 2026-05-16 | HVN36 | FRA → HAN | May 16, 18:35 UTC | May 17, 16:35 UTC | 22h 0m |
| 2026-05-16 | HVN36 | FRA → HAN | May 16, 18:25 UTC | May 17, 16:30 UTC | 22h 5m |
| 2026-05-16 | HVN36 | FRA → HAN | May 16, 15:05 UTC | May 17, 14:30 UTC | 23h 25m |
| 2026-05-16 | HVN36 | FRA → HAN | May 16, 12:35 UTC | May 17, 12:30 UTC | 23h 55m |
| 2026-05-16 | HVN36 | FRA → HAN | May 16, 12:16 UTC | May 16, 21:45 UTC | 9h 30m |
| 2026-05-15 | HVN31 | SGN → FRA | May 15, 17:10 UTC | May 16, 04:40 UTC | 11h 30m |
| 2026-05-14 | HVN31 | SGN → FRA | May 14, 21:05 UTC | May 15, 20:30 UTC | 23h 24m |
| 2026-05-14 | HVN30 | FRA → SGN | May 14, 18:35 UTC | May 15, 18:30 UTC | 23h 54m |
| 2026-05-14 | HVN30 | FRA → SGN | May 14, 12:00 UTC | May 14, 22:15 UTC | 10h 15m |
| 2026-05-13 | HVN31 | SGN → FRA | May 13, 17:25 UTC | May 14, 05:20 UTC | 11h 55m |
| 2026-05-13 | HVN31 | SGN → FRA | May 13, 04:35 UTC | May 14, 04:30 UTC | 23h 55m |
| 2026-05-13 | HVN31 | SGN → FRA | May 13, 02:35 UTC | May 14, 02:20 UTC | 23h 45m |
| 2026-05-13 | HVN31 | SGN → FRA | May 13, 02:25 UTC | May 13, 21:50 UTC | 19h 25m |
| 2026-05-12 | HVN50 | LHR → SGN | May 12, 23:01 UTC | May 13, 21:50 UTC | 22h 50m |
| 2026-05-12 | HVN50 | LHR → SGN | May 12, 20:35 UTC | May 13, 20:30 UTC | 23h 55m |
| 2026-05-12 | HVN50 | LHR → SGN | May 12, 19:15 UTC | May 13, 18:30 UTC | 23h 15m |
| 2026-05-12 | HVN51 | SGN → LHR | May 12, 04:05 UTC | May 12, 17:00 UTC | 12h 55m |
| 2026-05-11 | HVN51 | SGN → LHR | May 11, 20:35 UTC | May 12, 17:00 UTC | 20h 25m |
| 2026-05-11 | HVN51 | SGN → LHR | May 11, 18:35 UTC | May 12, 17:00 UTC | 22h 25m |
| 2026-05-11 | HVN51 | SGN → LHR | May 11, 18:10 UTC | May 12, 16:30 UTC | 22h 20m |
| 2026-05-11 | HVN51 | SGN → LHR | May 11, 15:10 UTC | May 12, 14:30 UTC | 23h 21m |
| 2026-05-11 | HVN30 | FRA → SGN | May 11, 12:35 UTC | May 12, 12:30 UTC | 23h 56m |
| 2026-05-11 | HVN30 | FRA → SGN | May 11, 12:05 UTC | May 12, 08:25 UTC | 20h 21m |
| 2026-05-10 | HVN31 | SGN → FRA | May 10, 16:20 UTC | May 11, 04:10 UTC | 11h 50m |
| 2026-05-09 | HVN31 | SGN → FRA | May 9, 20:34 UTC | May 10, 20:25 UTC | 23h 50m |
| 2026-05-09 | HVN30 | FRA → SGN | May 9, 18:35 UTC | May 10, 18:29 UTC | 23h 55m |
| 2026-05-09 | HVN30 | FRA → SGN | May 9, 18:25 UTC | May 10, 16:30 UTC | 22h 5m |
| 2026-05-09 | HVN30 | FRA → SGN | May 9, 12:10 UTC | May 9, 22:30 UTC | 10h 20m |
| 2026-05-08 | HVN31 | SGN → FRA | May 8, 16:45 UTC | May 9, 04:35 UTC | 11h 50m |
| 2026-05-05 | HVN385 | HND → HAN | May 5, 07:40 UTC | May 5, 11:50 UTC | 4h 10m |
| 2026-05-04 | HVN36 | FRA → HAN | May 4, 12:25 UTC | May 5, 05:40 UTC | 17h 16m |
| 2026-05-03 | HVN37 | HAN → FRA | May 3, 08:35 UTC | May 4, 04:09 UTC | 19h 35m |
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-A864 page for operator, model, and routing details .