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
- 219
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- Jul 26, 22:30 UTC
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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HVN37 | - | 37 | 2026-07-08 |
| HVN36 | - | 28 | 2026-07-07 |
| HVN30 | Vietnam Airlines | 21 | 2026-07-23 |
| HVN31 | Vietnam Airlines | 18 | 2026-07-22 |
| HVN51 | - | 11 | 2026-06-29 |
| HVN56 | Vietnam Airlines | 9 | 2026-07-26 |
| HVN50 | - | 9 | 2026-07-01 |
| HVN385 | - | 9 | 2026-07-08 |
| HVN384 | - | 8 | 2026-07-08 |
| HVN35 | Vietnam Airlines | 8 | 2026-07-24 |
| HVN55 | Vietnam Airlines | 7 | 2026-07-26 |
| HVN39 | - | 5 | 2026-07-13 |
| HVN34 | Vietnam Airlines | 5 | 2026-07-25 |
| HVN38 | - | 4 | 2026-07-14 |
| HVN212 | - | 4 | 2026-07-02 |
| HVN979 | Vietnam Airlines | 2 | 2026-06-05 |
| HVN978 | Vietnam Airlines | 2 | 2026-06-05 |
| HVN977 | Vietnam Airlines | 2 | 2026-07-16 |
| HVN973 | Vietnam Airlines | 2 | 2026-06-09 |
| HVN972 | Vietnam Airlines | 2 | 2026-06-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | HVN56 | LHR → HAN | Jul 26, 19:40 UTC | Jul 26, 22:30 UTC | 2h 50m |
| 2026-07-26 | HVN55 | HAN → LHR | Jul 26, 16:15 UTC | Jul 26, 16:25 UTC | 10m |
| 2026-07-26 | HVN55 | HAN → LHR | Jul 26, 04:30 UTC | Jul 26, 16:10 UTC | 11h 41m |
| 2026-07-25 | HVN34 | MUC → HAN | Jul 25, 12:00 UTC | Jul 25, 21:30 UTC | 9h 30m |
| 2026-07-24 | HVN35 | HAN → MUC | Jul 24, 18:00 UTC | Jul 25, 04:10 UTC | 10h 10m |
| 2026-07-24 | HVN211 | HAN → SGN | Jul 24, 04:40 UTC | Jul 24, 04:50 UTC | 10m |
| 2026-07-23 | HVN30 | FRA → SGN | Jul 23, 11:55 UTC | Jul 23, 22:30 UTC | 10h 35m |
| 2026-07-22 | HVN31 | SGN → FRA | Jul 22, 12:20 UTC | Jul 23, 04:10 UTC | 15h 50m |
| 2026-07-22 | HVN409 | ICN → SGN | Jul 22, 02:00 UTC | Jul 22, 04:40 UTC | 2h 40m |
| 2026-07-21 | HVN408 | SGN → ICN | Jul 21, 19:35 UTC | Jul 21, 22:15 UTC | 2h 40m |
| 2026-07-20 | HVN30 | FRA → SGN | Jul 20, 11:55 UTC | Jul 20, 22:10 UTC | 10h 15m |
| 2026-07-19 | HVN31 | SGN → FRA | Jul 19, 13:00 UTC | Jul 20, 04:05 UTC | 15h 5m |
| 2026-07-19 | HVN211 | HAN → SGN | Jul 19, 04:20 UTC | Jul 19, 10:50 UTC | 6h 30m |
| 2026-07-19 | HVN208 | SGN → HAN | Jul 19, 02:35 UTC | Jul 19, 02:45 UTC | 10m |
| 2026-07-18 | HVN30 | FRA → SGN | Jul 18, 12:20 UTC | Jul 18, 22:40 UTC | 10h 20m |
| 2026-07-17 | HVN31 | SGN → FRA | Jul 17, 16:59 UTC | Jul 18, 03:50 UTC | 10h 51m |
| 2026-07-17 | HVN31 | SGN → FRA | Jul 17, 06:54 UTC | Jul 18, 03:50 UTC | 20h 56m |
| 2026-07-16 | HVN976 | - | Jul 16, 18:25 UTC | Jul 17, 01:59 UTC | 7h 35m |
| 2026-07-16 | HVN977 | SGN → DEL | Jul 16, 15:35 UTC | Jul 16, 16:44 UTC | 1h 10m |
| 2026-07-16 | HVN977 | SGN → DEL | Jul 16, 09:00 UTC | Jul 16, 15:30 UTC | 6h 30m |
| 2026-07-15 | HVN56 | - | Jul 15, 18:35 UTC | Jul 16, 05:10 UTC | 10h 35m |
| 2026-07-15 | HVN55 | - | Jul 15, 04:30 UTC | Jul 15, 15:50 UTC | 11h 20m |
| 2026-07-14 | HVN38 | - | Jul 14, 09:55 UTC | Jul 14, 20:05 UTC | 10h 10m |
| 2026-07-13 | HVN39 | - | Jul 13, 10:50 UTC | Jul 14, 05:10 UTC | 18h 20m |
| 2026-07-12 | HVN56 | - | Jul 12, 20:15 UTC | Jul 13, 06:40 UTC | 10h 25m |
| 2026-07-12 | HVN55 | - | Jul 12, 04:15 UTC | Jul 12, 16:30 UTC | 12h 15m |
| 2026-07-11 | HVN38 | - | Jul 11, 10:00 UTC | Jul 11, 20:10 UTC | 10h 10m |
| 2026-07-10 | HVN39 | - | Jul 10, 17:25 UTC | Jul 11, 04:50 UTC | 11h 25m |
| 2026-07-10 | HVN39 | - | Jul 10, 05:55 UTC | Jul 11, 04:30 UTC | 22h 35m |
| 2026-07-09 | HVN30 | - | Jul 9, 12:00 UTC | Jul 9, 22:25 UTC | 10h 25m |
| 2026-07-08 | HVN37 | - | Jul 8, 17:00 UTC | Jul 9, 03:25 UTC | 10h 25m |
| 2026-07-08 | HVN385 | - | Jul 8, 07:40 UTC | Jul 8, 11:20 UTC | 3h 40m |
| 2026-07-08 | HVN384 | - | Jul 8, 04:25 UTC | Jul 8, 06:00 UTC | 1h 35m |
| 2026-07-08 | HVN384 | - | Jul 8, 01:25 UTC | Jul 8, 01:35 UTC | 10m |
| 2026-07-07 | HVN36 | - | Jul 7, 12:15 UTC | Jul 7, 21:45 UTC | 9h 30m |
| 2026-07-06 | HVN37 | - | Jul 6, 16:55 UTC | Jul 7, 03:45 UTC | 10h 50m |
| 2026-07-06 | HVN415 | - | Jul 6, 09:10 UTC | Jul 6, 12:45 UTC | 3h 35m |
| 2026-07-06 | HVN414 | - | Jul 6, 03:50 UTC | Jul 6, 07:25 UTC | 3h 35m |
| 2026-07-05 | HVN36 | - | Jul 5, 12:20 UTC | Jul 5, 22:00 UTC | 9h 40m |
| 2026-07-04 | HVN37 | - | Jul 4, 16:30 UTC | Jul 5, 03:45 UTC | 11h 15m |
| 2026-07-04 | HVN214 | - | Jul 4, 04:50 UTC | Jul 4, 10:10 UTC | 5h 20m |
| 2026-07-03 | HVN208 | - | Jul 3, 15:20 UTC | Jul 4, 03:20 UTC | 12h 0m |
| 2026-07-03 | HVN307 | - | Jul 3, 01:10 UTC | Jul 3, 12:00 UTC | 10h 50m |
| 2026-07-02 | HVN306 | - | Jul 2, 12:55 UTC | Jul 2, 22:55 UTC | 10h 0m |
| 2026-07-02 | HVN212 | - | Jul 2, 02:35 UTC | Jul 2, 07:45 UTC | 5h 10m |
| 2026-07-01 | HVN206 | - | Jul 1, 06:35 UTC | Jul 2, 00:55 UTC | 18h 20m |
| 2026-07-01 | HVN50 | - | Jul 1, 04:35 UTC | Jul 2, 00:55 UTC | 20h 20m |
| 2026-07-01 | HVN50 | - | Jul 1, 02:40 UTC | Jul 2, 00:55 UTC | 22h 15m |
| 2026-07-01 | HVN50 | - | Jul 1, 02:25 UTC | Jul 2, 00:30 UTC | 22h 5m |
| 2026-06-30 | HVN50 | - | Jun 30, 19:40 UTC | Jul 1, 06:35 UTC | 10h 55m |
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 .