sensors Mode-S transponder
8880DF
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A861 · BOEING 787-9 Dreamliner
- Hex
- 8880DF
- Octal
- 42100337
- Decimal
- 8,945,887
- Country
- VN
- Tail
- VN-A861
- Type
- B789
- Flights observed
- 126
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 8880DF 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 | - | 18 | 2026-07-13 |
| HVN30 | Vietnam Airlines | 15 | 2026-05-21 |
| HVN31 | Vietnam Airlines | 14 | 2026-05-20 |
| HVN55 | Vietnam Airlines | 13 | 2026-05-06 |
| HVN56 | Vietnam Airlines | 8 | 2026-05-06 |
| HVN51 | Vietnam Airlines | 8 | 2026-05-18 |
| HVN36 | - | 8 | 2026-07-12 |
| HVN50 | Vietnam Airlines | 6 | 2026-05-19 |
| HVN780 | Vietnam Airlines | 4 | 2026-04-21 |
| HVN39 | - | 4 | 2026-07-08 |
| HVN384 | - | 4 | 2026-07-11 |
| HVN38 | - | 3 | 2026-07-09 |
| HVN972 | Vietnam Airlines | 2 | 2026-04-23 |
| HVN781 | Vietnam Airlines | 2 | 2026-04-20 |
| HVN422 | - | 2 | 2026-07-05 |
| HVN385 | - | 2 | 2026-07-11 |
| HVN981 | Vietnam Airlines | 1 | 2026-07-10 |
| HVN980 | - | 1 | 2026-07-10 |
| HVN973 | Vietnam Airlines | 1 | 2026-04-23 |
| HVN7231 | - | 1 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | HVN37 | - | Jul 13, 17:25 UTC | Jul 14, 01:00 UTC | 7h 35m |
| 2026-07-13 | HVN245 | - | Jul 13, 01:20 UTC | Jul 13, 01:30 UTC | 10m |
| 2026-07-12 | HVN36 | - | Jul 12, 12:10 UTC | Jul 12, 21:50 UTC | 9h 40m |
| 2026-07-11 | HVN37 | - | Jul 11, 17:50 UTC | Jul 12, 03:40 UTC | 9h 50m |
| 2026-07-11 | HVN385 | - | Jul 11, 08:05 UTC | Jul 11, 17:45 UTC | 9h 40m |
| 2026-07-11 | HVN384 | - | Jul 11, 04:45 UTC | Jul 11, 06:30 UTC | 1h 45m |
| 2026-07-11 | HVN384 | - | Jul 11, 01:35 UTC | Jul 11, 01:50 UTC | 15m |
| 2026-07-10 | HVN980 | - | Jul 10, 18:20 UTC | Jul 10, 21:40 UTC | 3h 21m |
| 2026-07-10 | HVN981 | HAN → DEL | Jul 10, 13:00 UTC | Jul 10, 16:10 UTC | 3h 10m |
| 2026-07-10 | HVN7231 | - | Jul 10, 02:15 UTC | Jul 10, 08:00 UTC | 5h 45m |
| 2026-07-09 | HVN38 | - | Jul 9, 10:00 UTC | Jul 9, 20:35 UTC | 10h 35m |
| 2026-07-08 | HVN39 | - | Jul 8, 10:15 UTC | Jul 9, 04:40 UTC | 18h 25m |
| 2026-07-08 | HVN247 | - | Jul 8, 03:25 UTC | Jul 8, 03:45 UTC | 20m |
| 2026-07-07 | HVN32 | - | Jul 7, 10:35 UTC | Jul 8, 01:55 UTC | 15h 20m |
| 2026-07-06 | HVN33 | - | Jul 6, 13:35 UTC | Jul 7, 04:55 UTC | 15h 20m |
| 2026-07-06 | HVN423 | - | Jul 6, 01:15 UTC | Jul 6, 03:45 UTC | 2h 30m |
| 2026-07-05 | HVN422 | - | Jul 5, 22:35 UTC | Jul 5, 22:55 UTC | 20m |
| 2026-07-05 | HVN422 | - | Jul 5, 20:15 UTC | Jul 5, 21:35 UTC | 1h 20m |
| 2026-07-05 | HVN215 | - | Jul 5, 08:30 UTC | Jul 5, 08:45 UTC | 15m |
| 2026-07-05 | HVN212 | - | Jul 5, 06:40 UTC | Jul 5, 06:55 UTC | 15m |
| 2026-05-21 | HVN30 | FRA → SGN | May 21, 12:05 UTC | May 21, 22:40 UTC | 10h 35m |
| 2026-05-20 | HVN31 | SGN → FRA | May 20, 17:25 UTC | May 21, 04:35 UTC | 11h 10m |
| 2026-05-20 | HVN31 | SGN → FRA | May 20, 05:50 UTC | May 21, 04:35 UTC | 22h 45m |
| 2026-05-20 | HVN31 | SGN → FRA | May 20, 04:00 UTC | May 21, 03:45 UTC | 23h 46m |
| 2026-05-20 | HVN31 | SGN → FRA | May 20, 01:55 UTC | May 21, 01:45 UTC | 23h 51m |
| 2026-05-19 | HVN50 | LHR → SGN | May 19, 21:50 UTC | May 20, 21:25 UTC | 23h 36m |
| 2026-05-19 | HVN50 | LHR → SGN | May 19, 19:50 UTC | May 20, 19:40 UTC | 23h 51m |
| 2026-05-19 | HVN50 | LHR → SGN | May 19, 19:10 UTC | May 20, 17:45 UTC | 22h 36m |
| 2026-05-18 | HVN51 | SGN → LHR | May 18, 21:50 UTC | May 19, 16:50 UTC | 19h 0m |
| 2026-05-18 | HVN51 | SGN → LHR | May 18, 19:50 UTC | May 19, 16:50 UTC | 21h 0m |
| 2026-05-18 | HVN51 | SGN → LHR | May 18, 18:40 UTC | May 19, 16:50 UTC | 22h 10m |
| 2026-05-18 | HVN51 | SGN → LHR | May 18, 15:50 UTC | May 19, 15:45 UTC | 23h 54m |
| 2026-05-18 | HVN30 | FRA → SGN | May 18, 13:50 UTC | May 19, 13:00 UTC | 23h 9m |
| 2026-05-18 | HVN30 | FRA → SGN | May 18, 12:20 UTC | May 19, 11:45 UTC | 23h 24m |
| 2026-05-17 | HVN37 | HAN → FRA | May 17, 17:30 UTC | May 18, 03:55 UTC | 10h 25m |
| 2026-05-16 | HVN37 | HAN → FRA | May 16, 22:00 UTC | May 17, 21:05 UTC | 23h 5m |
| 2026-05-16 | HVN30 | FRA → SGN | May 16, 19:50 UTC | May 17, 19:45 UTC | 23h 55m |
| 2026-05-16 | HVN30 | FRA → SGN | May 16, 19:00 UTC | May 17, 17:30 UTC | 22h 30m |
| 2026-05-16 | HVN30 | FRA → SGN | May 16, 12:35 UTC | May 16, 23:10 UTC | 10h 35m |
| 2026-05-15 | HVN37 | HAN → FRA | May 15, 17:15 UTC | May 16, 03:50 UTC | 10h 35m |
| 2026-05-15 | HVN37 | HAN → FRA | May 15, 08:00 UTC | May 16, 03:50 UTC | 19h 49m |
| 2026-05-14 | HVN36 | FRA → HAN | May 14, 12:05 UTC | May 15, 06:00 UTC | 17h 55m |
| 2026-05-13 | HVN37 | HAN → FRA | May 13, 07:50 UTC | May 14, 03:45 UTC | 19h 55m |
| 2026-05-12 | HVN384 | HAN → HND | May 12, 11:30 UTC | May 13, 05:45 UTC | 18h 15m |
| 2026-05-12 | HVN384 | HAN → HND | May 12, 07:50 UTC | May 13, 05:45 UTC | 21h 55m |
| 2026-05-12 | HVN385 | HND → HAN | May 12, 07:40 UTC | May 13, 05:45 UTC | 22h 5m |
| 2026-05-11 | HVN36 | FRA → HAN | May 11, 12:30 UTC | May 12, 05:35 UTC | 17h 6m |
| 2026-05-10 | HVN37 | HAN → FRA | May 10, 16:50 UTC | May 11, 03:50 UTC | 11h 0m |
| 2026-05-09 | HVN37 | HAN → FRA | May 9, 19:49 UTC | May 10, 19:45 UTC | 23h 55m |
| 2026-05-09 | HVN38 | CPH → SGN | May 9, 17:49 UTC | May 10, 17:45 UTC | 23h 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-A861 page for operator, model, and routing details .