sensors Mode-S transponder
8880E1
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A863 · BOEING 787-9 Dreamliner
- Hex
- 8880E1
- Octal
- 42100341
- Decimal
- 8,945,889
- Country
- VN
- Tail
- VN-A863
- Type
- B789
- Flights observed
- 227
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 8880E1 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 |
|---|---|---|---|
| HVN36 | - | 29 | 2026-07-09 |
| HVN31 | - | 28 | 2026-07-11 |
| HVN37 | - | 25 | 2026-07-01 |
| HVN51 | - | 20 | 2026-06-24 |
| HVN30 | - | 18 | 2026-07-12 |
| HVN50 | - | 15 | 2026-06-25 |
| HVN56 | - | 9 | 2026-06-18 |
| HVN385 | - | 9 | 2026-07-10 |
| HVN384 | - | 9 | 2026-07-10 |
| HVN34 | - | 7 | 2026-07-04 |
| HVN55 | - | 6 | 2026-06-17 |
| HVN779 | Vietnam Airlines | 5 | 2026-04-25 |
| HVN780 | Vietnam Airlines | 4 | 2026-04-29 |
| HVN35 | - | 4 | 2026-07-03 |
| HVN978 | Vietnam Airlines | 3 | 2026-05-15 |
| HVN973 | Vietnam Airlines | 3 | 2026-06-16 |
| HVN781 | Vietnam Airlines | 3 | 2026-04-28 |
| HVN208 | - | 3 | 2026-07-11 |
| HVN981 | Vietnam Airlines | 2 | 2026-05-17 |
| HVN972 | Vietnam Airlines | 2 | 2026-06-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | HVN30 | - | Jul 12, 11:50 UTC | Jul 12, 21:55 UTC | 10h 5m |
| 2026-07-11 | HVN31 | - | Jul 11, 11:00 UTC | Jul 12, 04:30 UTC | 17h 30m |
| 2026-07-11 | HVN211 | - | Jul 11, 04:50 UTC | Jul 11, 05:01 UTC | 10m |
| 2026-07-11 | HVN208 | - | Jul 11, 02:55 UTC | Jul 11, 03:05 UTC | 10m |
| 2026-07-10 | HVN265 | HAN → SGN | Jul 10, 14:45 UTC | Jul 10, 14:55 UTC | 10m |
| 2026-07-10 | HVN385 | - | Jul 10, 08:10 UTC | Jul 10, 09:40 UTC | 1h 30m |
| 2026-07-10 | HVN384 | - | Jul 10, 04:25 UTC | Jul 10, 06:05 UTC | 1h 40m |
| 2026-07-09 | HVN36 | - | Jul 9, 12:15 UTC | Jul 9, 21:55 UTC | 9h 40m |
| 2026-07-08 | HVN31 | - | Jul 8, 11:45 UTC | Jul 9, 04:10 UTC | 16h 25m |
| 2026-07-08 | HVN250 | - | Jul 8, 09:35 UTC | Jul 8, 10:00 UTC | 25m |
| 2026-07-08 | HVN211 | - | Jul 8, 04:15 UTC | Jul 8, 04:30 UTC | 15m |
| 2026-07-08 | HVN208 | - | Jul 8, 02:45 UTC | Jul 8, 02:55 UTC | 10m |
| 2026-07-07 | HVN259 | - | Jul 7, 11:20 UTC | Jul 7, 11:40 UTC | 20m |
| 2026-07-07 | HVN212 | - | Jul 7, 06:55 UTC | Jul 7, 07:10 UTC | 15m |
| 2026-07-06 | HVN30 | - | Jul 6, 11:55 UTC | Jul 6, 22:05 UTC | 10h 10m |
| 2026-07-05 | HVN31 | - | Jul 5, 12:45 UTC | Jul 6, 04:30 UTC | 15h 45m |
| 2026-07-04 | HVN34 | - | Jul 4, 19:20 UTC | Jul 5, 04:45 UTC | 9h 25m |
| 2026-07-03 | HVN35 | - | Jul 3, 17:25 UTC | Jul 4, 04:25 UTC | 11h 0m |
| 2026-07-03 | HVN385 | - | Jul 3, 07:50 UTC | Jul 3, 12:45 UTC | 4h 55m |
| 2026-07-03 | HVN384 | - | Jul 3, 01:20 UTC | Jul 3, 05:50 UTC | 4h 30m |
| 2026-07-02 | HVN36 | - | Jul 2, 12:20 UTC | Jul 2, 22:00 UTC | 9h 40m |
| 2026-07-01 | HVN37 | - | Jul 1, 16:45 UTC | Jul 2, 03:45 UTC | 11h 0m |
| 2026-07-01 | HVN385 | - | Jul 1, 07:55 UTC | Jul 1, 13:00 UTC | 5h 5m |
| 2026-07-01 | HVN384 | - | Jul 1, 01:25 UTC | Jul 1, 06:00 UTC | 4h 35m |
| 2026-06-30 | HVN258 | SGN → HAN | Jun 30, 13:40 UTC | Jun 30, 14:00 UTC | 20m |
| 2026-06-30 | HVN213 | - | Jun 30, 06:55 UTC | Jun 30, 07:15 UTC | 20m |
| 2026-06-30 | HVN210 | - | Jun 30, 00:14 UTC | Jun 30, 05:20 UTC | 5h 6m |
| 2026-06-29 | HVN34 | - | Jun 29, 11:50 UTC | Jun 29, 21:19 UTC | 9h 30m |
| 2026-06-28 | HVN35 | - | Jun 28, 18:44 UTC | Jun 29, 05:45 UTC | 11h 0m |
| 2026-06-28 | HVN220 | SGN → HAN | Jun 28, 11:19 UTC | Jun 28, 16:19 UTC | 5h 0m |
| 2026-06-27 | HVN30 | - | Jun 27, 14:20 UTC | Jun 28, 09:15 UTC | 18h 55m |
| 2026-06-27 | HVN30 | - | Jun 27, 12:19 UTC | Jun 28, 09:15 UTC | 20h 55m |
| 2026-06-27 | HVN30 | - | Jun 27, 12:04 UTC | Jun 28, 09:15 UTC | 21h 10m |
| 2026-06-26 | HVN31 | - | Jun 26, 12:14 UTC | Jun 27, 04:09 UTC | 15h 55m |
| 2026-06-25 | HVN50 | - | Jun 25, 18:10 UTC | Jun 26, 10:50 UTC | 16h 40m |
| 2026-06-24 | HVN51 | - | Jun 24, 20:20 UTC | Jun 25, 15:34 UTC | 19h 15m |
| 2026-06-24 | HVN51 | - | Jun 24, 18:20 UTC | Jun 25, 15:34 UTC | 21h 15m |
| 2026-06-24 | HVN51 | - | Jun 24, 14:20 UTC | Jun 25, 14:14 UTC | 23h 55m |
| 2026-06-24 | HVN30 | - | Jun 24, 12:20 UTC | Jun 25, 11:54 UTC | 23h 35m |
| 2026-06-24 | HVN30 | - | Jun 24, 12:09 UTC | Jun 25, 07:15 UTC | 19h 5m |
| 2026-06-23 | HVN31 | - | Jun 23, 16:54 UTC | Jun 24, 04:24 UTC | 11h 30m |
| 2026-06-23 | HVN31 | - | Jun 23, 09:20 UTC | Jun 24, 04:24 UTC | 19h 5m |
| 2026-06-23 | HVN212 | SGN → HAN | Jun 23, 02:20 UTC | Jun 23, 07:15 UTC | 4h 55m |
| 2026-06-22 | HVN36 | - | Jun 22, 12:54 UTC | Jun 22, 21:40 UTC | 8h 45m |
| 2026-06-21 | HVN37 | - | Jun 21, 17:05 UTC | Jun 22, 04:30 UTC | 11h 25m |
| 2026-06-21 | HVN385 | - | Jun 21, 07:49 UTC | Jun 21, 12:49 UTC | 5h 0m |
| 2026-06-21 | HVN384 | - | Jun 21, 01:14 UTC | Jun 21, 05:44 UTC | 4h 30m |
| 2026-06-20 | HVN34 | MUC → HAN | Jun 20, 22:05 UTC | Jun 20, 22:25 UTC | 20m |
| 2026-06-20 | HVN34 | MUC → HAN | Jun 20, 12:30 UTC | Jun 20, 21:34 UTC | 9h 5m |
| 2026-06-19 | HVN35 | - | Jun 19, 17:55 UTC | Jun 20, 04:49 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-A863 page for operator, model, and routing details .