sensors Mode-S transponder
88813A
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A895 · AIRBUS A-350-900
- Hex
- 88813A
- Octal
- 42100472
- Decimal
- 8,945,978
- Country
- VN
- Tail
- VN-A895
- Type
- A359
- Flights observed
- 153
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- Jul 26, 19:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 88813A 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 |
|---|---|---|---|
| HVN781 | Vietnam Airlines | 13 | 2026-07-24 |
| HVN73 | - | 12 | 2026-07-03 |
| HVN19 | Vietnam Airlines | 10 | 2026-07-21 |
| HVN10 | - | 8 | 2026-07-15 |
| HVN780 | Vietnam Airlines | 7 | 2026-07-21 |
| HVN72 | - | 7 | 2026-07-04 |
| HVN384 | Vietnam Airlines | 7 | 2026-07-23 |
| HVN385 | Vietnam Airlines | 6 | 2026-07-23 |
| HVN35 | Vietnam Airlines | 6 | 2026-04-16 |
| HVN773 | - | 5 | 2026-07-16 |
| HVN34 | - | 5 | 2026-04-16 |
| HVN18 | Vietnam Airlines | 5 | 2026-07-22 |
| HVN787 | - | 4 | 2026-07-10 |
| HVN415 | Vietnam Airlines | 4 | 2026-06-05 |
| HVN414 | Vietnam Airlines | 4 | 2026-06-05 |
| HVN11 | - | 4 | 2026-07-14 |
| HVN98 | Vietnam Airlines | 3 | 2026-07-25 |
| HVN349 | - | 3 | 2026-07-14 |
| HVN348 | - | 3 | 2026-07-13 |
| HVN786 | - | 2 | 2026-06-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | HVN99 | SFO → SGN | Jul 26, 06:05 UTC | Jul 26, 19:00 UTC | 12h 56m |
| 2026-07-25 | HVN98 | SGN → SFO | Jul 25, 07:15 UTC | Jul 26, 01:05 UTC | 17h 50m |
| 2026-07-25 | HVN98 | SGN → SFO | Jul 25, 04:35 UTC | Jul 26, 01:05 UTC | 20h 30m |
| 2026-07-25 | HVN98 | SGN → SFO | Jul 25, 00:35 UTC | Jul 26, 00:30 UTC | 23h 55m |
| 2026-07-24 | HVN781 | SGN → MEL | Jul 24, 06:55 UTC | Jul 24, 22:15 UTC | 15h 20m |
| 2026-07-24 | HVN207 | HAN → SGN | Jul 24, 00:20 UTC | Jul 24, 00:35 UTC | 15m |
| 2026-07-23 | HVN385 | HND → HAN | Jul 23, 12:15 UTC | Jul 23, 12:25 UTC | 10m |
| 2026-07-23 | HVN385 | HND → HAN | Jul 23, 08:00 UTC | Jul 23, 11:30 UTC | 3h 30m |
| 2026-07-23 | HVN384 | HAN → HND | Jul 23, 04:30 UTC | Jul 23, 06:05 UTC | 1h 35m |
| 2026-07-23 | HVN384 | HAN → HND | Jul 23, 01:25 UTC | Jul 23, 01:35 UTC | 10m |
| 2026-07-22 | HVN18 | CDG → HAN | Jul 22, 12:25 UTC | Jul 22, 22:25 UTC | 10h 0m |
| 2026-07-21 | HVN19 | HAN → CDG | Jul 21, 17:10 UTC | Jul 22, 04:55 UTC | 11h 45m |
| 2026-07-21 | HVN780 | MEL → SGN | Jul 21, 00:45 UTC | Jul 21, 13:00 UTC | 12h 15m |
| 2026-07-20 | HVN781 | SGN → MEL | Jul 20, 04:40 UTC | Jul 20, 22:10 UTC | 17h 30m |
| 2026-07-20 | HVN780 | MEL → SGN | Jul 20, 00:50 UTC | Jul 20, 22:10 UTC | 21h 20m |
| 2026-07-19 | HVN781 | SGN → MEL | Jul 19, 10:55 UTC | Jul 19, 22:40 UTC | 11h 45m |
| 2026-07-18 | HVN214 | - | Jul 18, 23:10 UTC | Jul 19, 09:00 UTC | 9h 50m |
| 2026-07-18 | HVN780 | MEL → SGN | Jul 18, 01:00 UTC | Jul 18, 12:30 UTC | 11h 31m |
| 2026-07-17 | HVN781 | - | Jul 17, 06:50 UTC | Jul 17, 22:45 UTC | 15h 55m |
| 2026-07-17 | HVN781 | - | Jul 17, 04:10 UTC | Jul 17, 22:45 UTC | 18h 35m |
| 2026-07-17 | HVN772 | SYD → MEL | Jul 17, 00:40 UTC | Jul 17, 22:45 UTC | 22h 5m |
| 2026-07-16 | HVN773 | - | Jul 16, 09:00 UTC | Jul 16, 22:35 UTC | 13h 35m |
| 2026-07-16 | HVN773 | - | Jul 16, 02:35 UTC | Jul 16, 22:35 UTC | 20h 0m |
| 2026-07-15 | HVN524 | - | Jul 15, 19:15 UTC | Jul 16, 15:45 UTC | 20h 30m |
| 2026-07-15 | HVN10 | - | Jul 15, 16:50 UTC | Jul 16, 09:10 UTC | 16h 20m |
| 2026-07-15 | HVN10 | - | Jul 15, 12:35 UTC | Jul 16, 09:10 UTC | 20h 35m |
| 2026-07-15 | HVN10 | - | Jul 15, 10:35 UTC | Jul 16, 09:10 UTC | 22h 35m |
| 2026-07-14 | HVN11 | - | Jul 14, 17:15 UTC | Jul 15, 04:55 UTC | 11h 39m |
| 2026-07-14 | HVN219 | HAN → SGN | Jul 14, 12:25 UTC | Jul 14, 12:35 UTC | 10m |
| 2026-07-14 | HVN349 | - | Jul 14, 04:30 UTC | Jul 14, 04:40 UTC | 10m |
| 2026-07-14 | HVN349 | - | Jul 14, 00:40 UTC | Jul 14, 03:35 UTC | 2h 55m |
| 2026-07-13 | HVN348 | - | Jul 13, 20:25 UTC | Jul 13, 21:25 UTC | 1h 0m |
| 2026-07-13 | HVN348 | - | Jul 13, 17:25 UTC | Jul 13, 17:35 UTC | 10m |
| 2026-07-13 | HVN385 | - | Jul 13, 08:10 UTC | Jul 13, 11:40 UTC | 3h 30m |
| 2026-07-13 | HVN384 | - | Jul 13, 04:30 UTC | Jul 13, 06:15 UTC | 1h 45m |
| 2026-07-13 | HVN384 | - | Jul 13, 01:25 UTC | Jul 13, 01:35 UTC | 10m |
| 2026-07-12 | HVN18 | - | Jul 12, 12:55 UTC | Jul 12, 22:55 UTC | 10h 0m |
| 2026-07-11 | HVN19 | - | Jul 11, 11:10 UTC | Jul 12, 04:45 UTC | 17h 35m |
| 2026-07-11 | HVN19 | - | Jul 11, 08:35 UTC | Jul 12, 04:45 UTC | 20h 10m |
| 2026-07-11 | HVN19 | - | Jul 11, 04:35 UTC | Jul 12, 04:30 UTC | 23h 55m |
| 2026-07-11 | HVN19 | - | Jul 11, 04:25 UTC | Jul 12, 01:00 UTC | 20h 35m |
| 2026-07-10 | HVN787 | - | Jul 10, 19:30 UTC | Jul 11, 02:10 UTC | 6h 40m |
| 2026-07-10 | HVN787 | - | Jul 10, 17:20 UTC | Jul 10, 17:30 UTC | 10m |
| 2026-07-10 | HVN253 | - | Jul 10, 07:35 UTC | Jul 10, 12:30 UTC | 4h 55m |
| 2026-07-10 | HVN335 | - | Jul 10, 01:15 UTC | Jul 10, 02:15 UTC | 1h 0m |
| 2026-07-09 | HVN334 | - | Jul 9, 20:40 UTC | Jul 9, 21:45 UTC | 1h 5m |
| 2026-07-06 | HVN18 | - | Jul 6, 12:25 UTC | Jul 6, 22:35 UTC | 10h 10m |
| 2026-07-05 | HVN19 | - | Jul 5, 17:50 UTC | Jul 6, 05:00 UTC | 11h 10m |
| 2026-07-05 | HVN385 | - | Jul 5, 07:55 UTC | Jul 5, 13:05 UTC | 5h 10m |
| 2026-07-05 | HVN384 | - | Jul 5, 01:30 UTC | Jul 5, 06:00 UTC | 4h 30m |
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-A895 page for operator, model, and routing details .