sensors Mode-S transponder
88812D
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A892 · AIRBUS A-350-900
- Hex
- 88812D
- Octal
- 42100455
- Decimal
- 8,945,965
- Country
- VN
- Tail
- VN-A892
- Type
- A359
- Flights observed
- 93
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 88812D 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 |
|---|---|---|---|
| HVN19 | Vietnam Airlines | 23 | 2026-05-11 |
| HVN18 | Vietnam Airlines | 14 | 2026-05-12 |
| HVN73 | Vietnam Airlines | 8 | 2026-05-15 |
| HVN72 | Vietnam Airlines | 8 | 2026-05-16 |
| HVN787 | Vietnam Airlines | 6 | 2026-05-08 |
| HVN35 | Vietnam Airlines | 4 | 2026-04-29 |
| HVN99 | Vietnam Airlines | 3 | 2026-04-16 |
| HVN978 | Vietnam Airlines | 3 | 2026-05-13 |
| HVN786 | Vietnam Airlines | 3 | 2026-05-09 |
| HVN98 | Vietnam Airlines | 2 | 2026-04-16 |
| HVN979 | Vietnam Airlines | 2 | 2026-05-13 |
| HVN779 | Vietnam Airlines | 2 | 2026-05-10 |
| HVN773 | Vietnam Airlines | 2 | 2026-05-14 |
| HVN415 | Vietnam Airlines | 2 | 2026-05-17 |
| HVN384 | Vietnam Airlines | 2 | 2026-05-10 |
| HVN34 | Vietnam Airlines | 2 | 2026-04-30 |
| HVN414 | Vietnam Airlines | 1 | 2026-04-17 |
| HVN385 | - | 1 | 2026-04-13 |
| HVN349 | Vietnam Airlines | 1 | 2026-04-28 |
| HVN263 | Vietnam Airlines | 1 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | HVN247 | HAN → SGN | May 30, 03:25 UTC | May 30, 03:40 UTC | 15m |
| 2026-05-29 | HVN263 | HAN → SGN | May 29, 13:15 UTC | May 30, 00:40 UTC | 11h 25m |
| 2026-05-17 | HVN415 | ICN → HAN | May 17, 09:15 UTC | May 17, 09:45 UTC | 30m |
| 2026-05-16 | HVN72 | MXP → HAN | May 16, 13:31 UTC | May 17, 07:20 UTC | 17h 50m |
| 2026-05-16 | HVN72 | MXP → HAN | May 16, 11:21 UTC | May 17, 07:20 UTC | 20h 0m |
| 2026-05-16 | HVN72 | MXP → HAN | May 16, 11:05 UTC | May 17, 07:20 UTC | 20h 15m |
| 2026-05-15 | HVN73 | HAN → MXP | May 15, 19:00 UTC | May 16, 05:40 UTC | 10h 40m |
| 2026-05-15 | HVN73 | HAN → MXP | May 15, 07:20 UTC | May 16, 05:40 UTC | 22h 19m |
| 2026-05-15 | HVN73 | HAN → MXP | May 15, 07:05 UTC | May 16, 05:15 UTC | 22h 9m |
| 2026-05-15 | HVN73 | HAN → MXP | May 15, 04:20 UTC | May 16, 02:40 UTC | 22h 19m |
| 2026-05-15 | HVN73 | HAN → MXP | May 15, 00:30 UTC | May 15, 22:25 UTC | 21h 54m |
| 2026-05-14 | HVN773 | SGN → SYD | May 14, 03:20 UTC | May 14, 22:35 UTC | 19h 15m |
| 2026-05-14 | HVN773 | SGN → SYD | May 14, 02:25 UTC | May 14, 22:35 UTC | 20h 10m |
| 2026-05-13 | HVN978 | BOM → SGN | May 13, 21:20 UTC | May 14, 18:20 UTC | 21h 0m |
| 2026-05-13 | HVN978 | BOM → SGN | May 13, 19:20 UTC | May 14, 18:20 UTC | 23h 0m |
| 2026-05-13 | HVN978 | BOM → SGN | May 13, 14:25 UTC | May 14, 09:25 UTC | 19h 0m |
| 2026-05-13 | HVN979 | SGN → BOM | May 13, 12:00 UTC | May 14, 09:25 UTC | 21h 25m |
| 2026-05-12 | HVN979 | SGN → BOM | May 12, 21:20 UTC | May 13, 21:15 UTC | 23h 55m |
| 2026-05-12 | HVN18 | CDG → HAN | May 12, 19:20 UTC | May 13, 19:15 UTC | 23h 55m |
| 2026-05-12 | HVN18 | CDG → HAN | May 12, 18:45 UTC | May 13, 14:45 UTC | 20h 0m |
| 2026-05-12 | HVN18 | CDG → HAN | May 12, 13:20 UTC | May 13, 13:15 UTC | 23h 55m |
| 2026-05-12 | HVN18 | CDG → HAN | May 12, 12:20 UTC | May 12, 21:55 UTC | 9h 35m |
| 2026-05-11 | HVN19 | HAN → CDG | May 11, 12:20 UTC | May 12, 05:30 UTC | 17h 11m |
| 2026-05-11 | HVN19 | HAN → CDG | May 11, 09:20 UTC | May 12, 05:30 UTC | 20h 10m |
| 2026-05-11 | HVN19 | HAN → CDG | May 11, 08:20 UTC | May 12, 05:30 UTC | 21h 10m |
| 2026-05-10 | HVN384 | HAN → HND | May 10, 14:40 UTC | May 11, 06:25 UTC | 15h 45m |
| 2026-05-10 | HVN779 | HAN → MEL | May 10, 05:20 UTC | May 10, 11:55 UTC | 6h 35m |
| 2026-05-09 | HVN779 | HAN → MEL | May 9, 11:45 UTC | May 10, 11:15 UTC | 23h 30m |
| 2026-05-09 | HVN786 | SYD → HAN | May 9, 08:55 UTC | May 10, 05:45 UTC | 20h 50m |
| 2026-05-09 | HVN786 | SYD → HAN | May 9, 04:40 UTC | May 9, 12:15 UTC | 7h 35m |
| 2026-05-08 | HVN787 | HAN → SYD | May 8, 19:20 UTC | May 9, 01:50 UTC | 6h 30m |
| 2026-05-07 | HVN18 | CDG → HAN | May 7, 21:20 UTC | May 8, 19:45 UTC | 22h 25m |
| 2026-05-07 | HVN18 | CDG → HAN | May 7, 12:35 UTC | May 7, 22:15 UTC | 9h 40m |
| 2026-05-06 | HVN19 | HAN → CDG | May 6, 11:30 UTC | May 7, 05:00 UTC | 17h 29m |
| 2026-05-06 | HVN19 | HAN → CDG | May 6, 07:45 UTC | May 7, 05:00 UTC | 21h 14m |
| 2026-05-05 | HVN18 | CDG → HAN | May 5, 12:15 UTC | May 6, 05:40 UTC | 17h 25m |
| 2026-05-05 | HVN19 | HAN → CDG | May 5, 03:25 UTC | May 5, 05:10 UTC | 1h 45m |
| 2026-05-04 | HVN19 | HAN → CDG | May 4, 09:20 UTC | May 5, 03:20 UTC | 18h 1m |
| 2026-05-04 | HVN19 | HAN → CDG | May 4, 07:45 UTC | May 5, 03:20 UTC | 19h 36m |
| 2026-05-03 | HVN18 | CDG → HAN | May 3, 12:25 UTC | May 4, 05:25 UTC | 17h 0m |
| 2026-05-02 | HVN19 | HAN → CDG | May 2, 11:20 UTC | May 3, 06:40 UTC | 19h 19m |
| 2026-05-02 | HVN19 | HAN → CDG | May 2, 11:10 UTC | May 3, 06:40 UTC | 19h 29m |
| 2026-05-02 | HVN19 | HAN → CDG | May 2, 08:30 UTC | May 3, 06:40 UTC | 22h 9m |
| 2026-05-02 | HVN19 | HAN → CDG | May 2, 04:30 UTC | May 3, 03:15 UTC | 22h 45m |
| 2026-05-01 | HVN787 | HAN → SYD | May 1, 19:00 UTC | May 2, 01:50 UTC | 6h 50m |
| 2026-04-30 | HVN34 | MUC → HAN | Apr 30, 19:20 UTC | May 1, 19:15 UTC | 23h 55m |
| 2026-04-30 | HVN34 | MUC → HAN | Apr 30, 11:50 UTC | Apr 30, 20:50 UTC | 9h 0m |
| 2026-04-29 | HVN35 | HAN → MUC | Apr 29, 11:35 UTC | Apr 30, 04:35 UTC | 16h 59m |
| 2026-04-29 | HVN35 | HAN → MUC | Apr 29, 08:45 UTC | Apr 30, 04:35 UTC | 19h 50m |
| 2026-04-29 | HVN35 | HAN → MUC | Apr 29, 05:20 UTC | Apr 30, 04:35 UTC | 23h 15m |
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-A892 page for operator, model, and routing details .