sensors Mode-S transponder
88818D
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A878 · BOEING 787-10 Dreamliner
- Hex
- 88818D
- Octal
- 42100615
- Decimal
- 8,946,061
- Country
- VN
- Tail
- VN-A878
- Type
- B78X
- Flights observed
- 88
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 88818D 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 |
|---|---|---|---|
| HVN408 | Vietnam Airlines | 12 | 2026-05-30 |
| HVN334 | Vietnam Airlines | 7 | 2026-05-21 |
| HVN310 | Vietnam Airlines | 7 | 2026-05-23 |
| HVN409 | Vietnam Airlines | 6 | 2026-05-10 |
| HVN417 | Vietnam Airlines | 5 | 2026-05-26 |
| HVN416 | Vietnam Airlines | 5 | 2026-05-25 |
| HVN335 | Vietnam Airlines | 5 | 2026-05-22 |
| HVN979 | Vietnam Airlines | 4 | 2026-05-08 |
| HVN973 | Vietnam Airlines | 4 | 2026-05-02 |
| HVN972 | Vietnam Airlines | 4 | 2026-05-02 |
| HVN311 | Vietnam Airlines | 4 | 2026-05-24 |
| HVN307 | Vietnam Airlines | 4 | 2026-06-02 |
| HVN306 | Vietnam Airlines | 4 | 2026-06-01 |
| HVN978 | Vietnam Airlines | 3 | 2026-05-08 |
| HVN428 | - | 3 | 2026-06-02 |
| HVN977 | Vietnam Airlines | 1 | 2026-05-07 |
| HVN976 | Vietnam Airlines | 1 | 2026-05-07 |
| HVN429 | Vietnam Airlines | 1 | 2026-05-28 |
| HVN258 | Vietnam Airlines | 1 | 2026-05-28 |
| HVN254 | Vietnam Airlines | 1 | 2026-05-31 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | HVN428 | - | Jun 2, 18:30 UTC | Jun 2, 18:40 UTC | 10m |
| 2026-06-02 | HVN307 | NRT → SGN | Jun 2, 01:05 UTC | Jun 2, 14:55 UTC | 13h 50m |
| 2026-06-01 | HVN306 | SGN → NRT | Jun 1, 19:35 UTC | Jun 1, 23:15 UTC | 3h 40m |
| 2026-06-01 | HVN221 | HAN → SGN | Jun 1, 14:20 UTC | Jun 1, 14:30 UTC | 10m |
| 2026-06-01 | HVN216 | SGN → HAN | Jun 1, 10:45 UTC | Jun 1, 10:55 UTC | 10m |
| 2026-06-01 | HVN307 | NRT → SGN | Jun 1, 01:40 UTC | Jun 1, 05:10 UTC | 3h 30m |
| 2026-05-31 | HVN306 | SGN → NRT | May 31, 13:30 UTC | May 31, 22:55 UTC | 9h 25m |
| 2026-05-31 | HVN254 | SGN → HAN | May 31, 11:35 UTC | May 31, 11:50 UTC | 15m |
| 2026-05-30 | HVN408 | SGN → ICN | May 30, 13:35 UTC | May 30, 21:55 UTC | 8h 20m |
| 2026-05-30 | HVN307 | NRT → SGN | May 30, 00:40 UTC | May 30, 11:25 UTC | 10h 45m |
| 2026-05-29 | HVN306 | SGN → NRT | May 29, 11:20 UTC | May 29, 22:50 UTC | 11h 30m |
| 2026-05-28 | HVN428 | - | May 28, 18:25 UTC | May 28, 18:40 UTC | 15m |
| 2026-05-28 | HVN258 | SGN → HAN | May 28, 14:10 UTC | May 28, 14:25 UTC | 15m |
| 2026-05-28 | HVN215 | HAN → SGN | May 28, 08:20 UTC | May 28, 08:30 UTC | 10m |
| 2026-05-28 | HVN429 | PUS → HAN | May 28, 05:10 UTC | May 28, 05:35 UTC | 25m |
| 2026-05-27 | HVN428 | - | May 27, 18:25 UTC | May 27, 18:35 UTC | 10m |
| 2026-05-27 | HVN220 | SGN → HAN | May 27, 15:15 UTC | May 27, 15:45 UTC | 30m |
| 2026-05-26 | HVN417 | ICN → HAN | May 26, 01:24 UTC | May 26, 04:15 UTC | 2h 50m |
| 2026-05-25 | HVN416 | HAN → ICN | May 25, 20:45 UTC | May 25, 21:15 UTC | 30m |
| 2026-05-24 | HVN311 | NRT → HAN | May 24, 00:55 UTC | May 24, 02:20 UTC | 1h 25m |
| 2026-05-23 | HVN310 | HAN → NRT | May 23, 20:55 UTC | May 23, 22:05 UTC | 1h 10m |
| 2026-05-22 | HVN335 | KIX → HAN | May 22, 01:10 UTC | May 22, 01:50 UTC | 40m |
| 2026-05-21 | HVN334 | HAN → KIX | May 21, 01:20 UTC | May 21, 21:10 UTC | 19h 50m |
| 2026-05-20 | HVN416 | HAN → ICN | May 20, 19:50 UTC | May 20, 20:20 UTC | 30m |
| 2026-05-19 | HVN417 | ICN → HAN | May 19, 01:15 UTC | May 19, 01:40 UTC | 25m |
| 2026-05-18 | HVN416 | HAN → ICN | May 18, 01:20 UTC | May 18, 20:25 UTC | 19h 4m |
| 2026-05-18 | HVN311 | NRT → HAN | May 18, 00:40 UTC | May 18, 20:25 UTC | 19h 44m |
| 2026-05-17 | HVN310 | HAN → NRT | May 17, 21:15 UTC | May 17, 22:40 UTC | 1h 25m |
| 2026-05-17 | HVN310 | HAN → NRT | May 17, 01:20 UTC | May 17, 22:40 UTC | 21h 20m |
| 2026-05-17 | HVN310 | HAN → NRT | May 17, 01:10 UTC | May 17, 22:40 UTC | 21h 30m |
| 2026-05-16 | HVN334 | HAN → KIX | May 16, 20:50 UTC | May 16, 21:35 UTC | 45m |
| 2026-05-16 | HVN334 | HAN → KIX | May 16, 01:20 UTC | May 16, 21:35 UTC | 20h 15m |
| 2026-05-15 | HVN334 | HAN → KIX | May 15, 20:50 UTC | May 15, 21:35 UTC | 45m |
| 2026-05-15 | HVN334 | HAN → KIX | May 15, 01:20 UTC | May 15, 21:35 UTC | 20h 14m |
| 2026-05-14 | HVN417 | ICN → HAN | May 14, 01:25 UTC | May 14, 20:40 UTC | 19h 15m |
| 2026-05-13 | HVN416 | HAN → ICN | May 13, 19:45 UTC | May 13, 20:20 UTC | 35m |
| 2026-05-11 | HVN310 | HAN → NRT | May 11, 20:40 UTC | May 11, 21:50 UTC | 1h 10m |
| 2026-05-11 | HVN310 | HAN → NRT | May 11, 01:20 UTC | May 11, 21:50 UTC | 20h 31m |
| 2026-05-10 | HVN409 | ICN → SGN | May 10, 02:00 UTC | May 10, 21:04 UTC | 19h 5m |
| 2026-05-09 | HVN408 | SGN → ICN | May 9, 19:30 UTC | May 9, 22:05 UTC | 2h 35m |
| 2026-05-08 | HVN408 | SGN → ICN | May 8, 21:25 UTC | May 9, 20:25 UTC | 23h 0m |
| 2026-05-08 | HVN978 | BOM → SGN | May 8, 19:25 UTC | May 8, 22:05 UTC | 2h 40m |
| 2026-05-08 | HVN979 | SGN → BOM | May 8, 16:00 UTC | May 8, 16:25 UTC | 25m |
| 2026-05-07 | HVN979 | SGN → BOM | May 7, 19:20 UTC | May 8, 14:40 UTC | 19h 20m |
| 2026-05-07 | HVN976 | DEL → SGN | May 7, 18:35 UTC | May 8, 14:40 UTC | 20h 5m |
| 2026-05-07 | HVN977 | SGN → DEL | May 7, 01:50 UTC | May 7, 16:30 UTC | 14h 41m |
| 2026-05-06 | HVN408 | SGN → ICN | May 6, 03:25 UTC | May 6, 22:25 UTC | 18h 59m |
| 2026-05-06 | HVN408 | SGN → ICN | May 6, 02:01 UTC | May 6, 22:25 UTC | 20h 24m |
| 2026-05-05 | HVN408 | SGN → ICN | May 5, 19:40 UTC | May 5, 22:15 UTC | 2h 35m |
| 2026-05-05 | HVN408 | SGN → ICN | May 5, 02:10 UTC | May 5, 22:15 UTC | 20h 5m |
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-A878 page for operator, model, and routing details .