sensors Mode-S transponder
8880E5
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A887 · AIRBUS A-350-900
- Hex
- 8880E5
- Octal
- 42100345
- Decimal
- 8,945,893
- Country
- VN
- Tail
- VN-A887
- Type
- A359
- Flights observed
- 199
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 8880E5 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 |
|---|---|---|---|
| HVN320 | - | 30 | 2026-07-13 |
| HVN321 | - | 24 | 2026-07-14 |
| HVN978 | Vietnam Airlines | 13 | 2026-06-10 |
| HVN349 | - | 9 | 2026-07-09 |
| HVN979 | Vietnam Airlines | 7 | 2026-06-10 |
| HVN787 | - | 7 | 2026-07-02 |
| HVN348 | - | 7 | 2026-07-08 |
| HVN981 | Vietnam Airlines | 6 | 2026-06-29 |
| HVN786 | - | 6 | 2026-07-03 |
| HVN980 | - | 5 | 2026-06-29 |
| HVN772 | Vietnam Airlines | 5 | 2026-05-09 |
| HVN415 | - | 5 | 2026-07-05 |
| HVN414 | - | 5 | 2026-07-05 |
| HVN972 | Vietnam Airlines | 4 | 2026-05-26 |
| HVN83 | - | 4 | 2026-07-07 |
| HVN976 | - | 3 | 2026-07-11 |
| HVN82 | - | 3 | 2026-07-07 |
| HVN773 | Vietnam Airlines | 3 | 2026-05-08 |
| HVN262 | Vietnam Airlines | 3 | 2026-06-28 |
| HVN243 | - | 3 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | HVN321 | - | Jul 14, 01:55 UTC | Jul 14, 04:35 UTC | 2h 40m |
| 2026-07-13 | HVN320 | - | Jul 13, 03:50 UTC | Jul 13, 22:30 UTC | 18h 40m |
| 2026-07-13 | HVN320 | - | Jul 13, 01:35 UTC | Jul 13, 22:30 UTC | 20h 55m |
| 2026-07-12 | HVN320 | - | Jul 12, 07:05 UTC | Jul 12, 22:25 UTC | 15h 20m |
| 2026-07-11 | HVN976 | - | Jul 11, 21:20 UTC | Jul 12, 21:15 UTC | 23h 55m |
| 2026-07-11 | HVN976 | - | Jul 11, 19:30 UTC | Jul 12, 19:15 UTC | 23h 45m |
| 2026-07-11 | HVN976 | - | Jul 11, 18:30 UTC | Jul 12, 13:01 UTC | 18h 30m |
| 2026-07-11 | HVN977 | SGN → DEL | Jul 11, 05:50 UTC | Jul 11, 16:20 UTC | 10h 30m |
| 2026-07-10 | HVN243 | - | Jul 10, 23:40 UTC | Jul 11, 00:00 UTC | 20m |
| 2026-07-10 | HVN72 | - | Jul 10, 11:25 UTC | Jul 10, 21:00 UTC | 9h 35m |
| 2026-07-09 | HVN73 | - | Jul 9, 19:00 UTC | Jul 10, 05:45 UTC | 10h 45m |
| 2026-07-09 | HVN211 | - | Jul 9, 07:00 UTC | Jul 9, 07:15 UTC | 15m |
| 2026-07-09 | HVN349 | - | Jul 9, 00:40 UTC | Jul 9, 01:45 UTC | 1h 5m |
| 2026-07-08 | HVN348 | - | Jul 8, 20:35 UTC | Jul 8, 21:40 UTC | 1h 5m |
| 2026-07-08 | HVN348 | - | Jul 8, 17:40 UTC | Jul 8, 17:50 UTC | 10m |
| 2026-07-08 | HVN218 | SGN → HAN | Jul 8, 09:10 UTC | Jul 8, 14:05 UTC | 4h 55m |
| 2026-07-08 | HVN212 | - | Jul 8, 07:20 UTC | Jul 8, 07:45 UTC | 25m |
| 2026-07-08 | HVN209 | - | Jul 8, 02:25 UTC | Jul 8, 02:40 UTC | 15m |
| 2026-07-07 | HVN82 | - | Jul 7, 12:30 UTC | Jul 7, 22:25 UTC | 9h 55m |
| 2026-07-07 | HVN83 | - | Jul 7, 06:35 UTC | Jul 7, 08:25 UTC | 1h 50m |
| 2026-07-06 | HVN215 | - | Jul 6, 08:25 UTC | Jul 6, 13:15 UTC | 4h 50m |
| 2026-07-06 | HVN349 | - | Jul 6, 00:40 UTC | Jul 6, 01:50 UTC | 1h 10m |
| 2026-07-05 | HVN348 | - | Jul 5, 20:20 UTC | Jul 5, 21:25 UTC | 1h 5m |
| 2026-07-05 | HVN415 | - | Jul 5, 09:20 UTC | Jul 5, 12:55 UTC | 3h 35m |
| 2026-07-05 | HVN414 | - | Jul 5, 06:40 UTC | Jul 5, 07:25 UTC | 45m |
| 2026-07-05 | HVN414 | - | Jul 5, 03:45 UTC | Jul 5, 03:55 UTC | 10m |
| 2026-07-04 | HVN82 | - | Jul 4, 13:20 UTC | Jul 4, 23:10 UTC | 9h 50m |
| 2026-07-03 | HVN83 | - | Jul 3, 21:05 UTC | Jul 4, 09:15 UTC | 12h 10m |
| 2026-07-03 | HVN786 | - | Jul 3, 04:30 UTC | Jul 3, 14:20 UTC | 9h 50m |
| 2026-07-02 | HVN787 | - | Jul 2, 17:00 UTC | Jul 3, 01:40 UTC | 8h 40m |
| 2026-07-02 | HVN335 | - | Jul 2, 08:45 UTC | Jul 2, 09:15 UTC | 30m |
| 2026-07-02 | HVN335 | KIX → HPH | Jul 2, 01:25 UTC | Jul 2, 06:45 UTC | 5h 20m |
| 2026-07-01 | HVN334 | - | Jul 1, 17:30 UTC | Jul 1, 21:35 UTC | 4h 5m |
| 2026-07-01 | HVN786 | - | Jul 1, 04:30 UTC | Jul 1, 14:10 UTC | 9h 40m |
| 2026-06-30 | HVN787 | - | Jun 30, 17:05 UTC | Jul 1, 02:05 UTC | 9h 0m |
| 2026-06-30 | HVN415 | - | Jun 30, 09:25 UTC | Jun 30, 13:15 UTC | 3h 50m |
| 2026-06-30 | HVN414 | - | Jun 30, 03:35 UTC | Jun 30, 07:15 UTC | 3h 40m |
| 2026-06-29 | HVN980 | - | Jun 29, 18:30 UTC | Jun 29, 21:39 UTC | 3h 10m |
| 2026-06-29 | HVN981 | HAN → DEL | Jun 29, 12:29 UTC | Jun 29, 16:10 UTC | 3h 40m |
| 2026-06-29 | HVN349 | - | Jun 29, 00:49 UTC | Jun 29, 05:20 UTC | 4h 30m |
| 2026-06-28 | HVN348 | - | Jun 28, 18:29 UTC | Jun 28, 22:20 UTC | 3h 50m |
| 2026-06-28 | HVN262 | SGN → HAN | Jun 28, 02:29 UTC | Jun 28, 14:39 UTC | 12h 10m |
| 2026-06-27 | HVN262 | SGN → HAN | Jun 27, 15:19 UTC | Jun 28, 14:39 UTC | 23h 20m |
| 2026-06-27 | HVN7205 | HAN → SGN | Jun 27, 15:00 UTC | Jun 28, 09:20 UTC | 18h 20m |
| 2026-06-27 | HVN218 | SGN → HAN | Jun 27, 06:19 UTC | Jun 27, 13:00 UTC | 6h 40m |
| 2026-06-26 | HVN228 | SGN → HAN | Jun 26, 23:49 UTC | Jun 27, 04:54 UTC | 5h 5m |
| 2026-06-26 | HVN786 | - | Jun 26, 04:34 UTC | Jun 26, 13:40 UTC | 9h 5m |
| 2026-06-25 | HVN787 | - | Jun 25, 16:55 UTC | Jun 26, 01:54 UTC | 9h 0m |
| 2026-06-25 | HVN220 | SGN → HAN | Jun 25, 06:30 UTC | Jun 25, 15:04 UTC | 8h 35m |
| 2026-06-25 | HVN207 | HAN → SGN | Jun 25, 00:19 UTC | Jun 25, 05:05 UTC | 4h 45m |
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-A887 page for operator, model, and routing details .