sensors Mode-S transponder
888152
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A896 · AIRBUS A-350-900
- Hex
- 888152
- Octal
- 42100522
- Decimal
- 8,946,002
- Country
- VN
- Tail
- VN-A896
- Type
- A359
- Flights observed
- 82
- Distinct callsigns
- 19
- Country
- VN
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 888152 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HVN18 | Vietnam Airlines | 20 | 2026-05-28 |
| HVN19 | Vietnam Airlines | 15 | 2026-05-27 |
| HVN72 | Vietnam Airlines | 5 | 2026-05-09 |
| HVN786 | Vietnam Airlines | 4 | 2026-05-27 |
| HVN773 | Vietnam Airlines | 4 | 2026-05-23 |
| HVN73 | Vietnam Airlines | 4 | 2026-05-29 |
| HVN34 | - | 4 | 2026-04-13 |
| HVN11 | Vietnam Airlines | 4 | 2026-05-19 |
| HVN99 | Vietnam Airlines | 3 | 2026-05-25 |
| HVN98 | Vietnam Airlines | 3 | 2026-05-03 |
| HVN979 | Vietnam Airlines | 3 | 2026-05-18 |
| HVN787 | Vietnam Airlines | 3 | 2026-05-26 |
| HVN778 | Vietnam Airlines | 2 | 2026-05-14 |
| HVN35 | Vietnam Airlines | 2 | 2026-04-13 |
| HVN10 | Vietnam Airlines | 2 | 2026-05-20 |
| HVN978 | Vietnam Airlines | 1 | 2026-05-18 |
| HVN772 | Vietnam Airlines | 1 | 2026-05-24 |
| HVN246 | Vietnam Airlines | 1 | 2026-05-29 |
| HVN245 | Vietnam Airlines | 1 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | HVN73 | HAN → MXP | May 29, 18:55 UTC | May 30, 04:30 UTC | 9h 35m |
| 2026-05-29 | HVN246 | SGN → HAN | May 29, 06:05 UTC | May 29, 06:15 UTC | 10m |
| 2026-05-29 | HVN245 | HAN → SGN | May 29, 01:35 UTC | May 29, 01:45 UTC | 10m |
| 2026-05-28 | HVN18 | CDG → HAN | May 28, 13:15 UTC | May 28, 23:40 UTC | 10h 25m |
| 2026-05-27 | HVN19 | HAN → CDG | May 27, 17:35 UTC | May 28, 05:10 UTC | 11h 35m |
| 2026-05-27 | HVN786 | SYD → HAN | May 27, 04:24 UTC | May 27, 13:40 UTC | 9h 15m |
| 2026-05-26 | HVN787 | HAN → SYD | May 26, 19:25 UTC | May 27, 02:04 UTC | 6h 40m |
| 2026-05-25 | HVN99 | SFO → SGN | May 25, 06:20 UTC | May 25, 19:25 UTC | 13h 4m |
| 2026-05-24 | HVN772 | SYD → SGN | May 24, 00:30 UTC | May 24, 16:25 UTC | 15h 55m |
| 2026-05-23 | HVN773 | SGN → SYD | May 23, 15:10 UTC | May 23, 21:30 UTC | 6h 21m |
| 2026-05-22 | HVN773 | SGN → SYD | May 22, 22:35 UTC | May 23, 21:30 UTC | 22h 55m |
| 2026-05-22 | HVN18 | CDG → HAN | May 22, 20:35 UTC | May 23, 18:15 UTC | 21h 40m |
| 2026-05-22 | HVN18 | CDG → HAN | May 22, 19:25 UTC | May 23, 18:15 UTC | 22h 50m |
| 2026-05-22 | HVN18 | CDG → HAN | May 22, 16:35 UTC | May 23, 15:30 UTC | 22h 54m |
| 2026-05-22 | HVN18 | CDG → HAN | May 22, 12:50 UTC | May 22, 22:50 UTC | 10h 0m |
| 2026-05-21 | HVN19 | HAN → CDG | May 21, 18:20 UTC | May 22, 05:30 UTC | 11h 10m |
| 2026-05-20 | HVN19 | HAN → CDG | May 20, 20:35 UTC | May 21, 20:30 UTC | 23h 55m |
| 2026-05-20 | HVN10 | CDG → SGN | May 20, 18:35 UTC | May 21, 18:25 UTC | 23h 50m |
| 2026-05-20 | HVN10 | CDG → SGN | May 20, 09:55 UTC | May 20, 21:05 UTC | 11h 10m |
| 2026-05-19 | HVN11 | SGN → CDG | May 19, 08:55 UTC | May 20, 04:30 UTC | 19h 35m |
| 2026-05-19 | HVN11 | SGN → CDG | May 19, 02:35 UTC | May 20, 02:30 UTC | 23h 55m |
| 2026-05-19 | HVN11 | SGN → CDG | May 19, 02:25 UTC | May 20, 00:30 UTC | 22h 5m |
| 2026-05-18 | HVN11 | SGN → CDG | May 18, 20:40 UTC | May 19, 20:30 UTC | 23h 50m |
| 2026-05-18 | HVN978 | BOM → SGN | May 18, 17:50 UTC | May 18, 18:00 UTC | 10m |
| 2026-05-18 | HVN979 | SGN → BOM | May 18, 15:35 UTC | May 18, 15:55 UTC | 20m |
| 2026-05-17 | HVN979 | SGN → BOM | May 17, 21:30 UTC | May 18, 13:10 UTC | 15h 40m |
| 2026-05-17 | HVN979 | SGN → BOM | May 17, 14:35 UTC | May 18, 13:10 UTC | 22h 35m |
| 2026-05-16 | HVN18 | CDG → HAN | May 16, 16:35 UTC | May 17, 11:40 UTC | 19h 5m |
| 2026-05-16 | HVN18 | CDG → HAN | May 16, 14:35 UTC | May 17, 11:40 UTC | 21h 5m |
| 2026-05-16 | HVN18 | CDG → HAN | May 16, 12:35 UTC | May 17, 11:40 UTC | 23h 5m |
| 2026-05-15 | HVN19 | HAN → CDG | May 15, 18:00 UTC | May 16, 05:10 UTC | 11h 10m |
| 2026-05-14 | HVN19 | HAN → CDG | May 14, 20:35 UTC | May 15, 20:30 UTC | 23h 54m |
| 2026-05-14 | HVN778 | MEL → HAN | May 14, 14:15 UTC | May 14, 21:05 UTC | 6h 50m |
| 2026-05-13 | HVN18 | CDG → HAN | May 13, 16:35 UTC | May 14, 12:10 UTC | 19h 35m |
| 2026-05-13 | HVN18 | CDG → HAN | May 13, 14:35 UTC | May 14, 12:10 UTC | 21h 35m |
| 2026-05-13 | HVN18 | CDG → HAN | May 13, 12:35 UTC | May 14, 12:10 UTC | 23h 35m |
| 2026-05-12 | HVN19 | HAN → CDG | May 12, 17:25 UTC | May 13, 05:00 UTC | 11h 35m |
| 2026-05-10 | HVN19 | HAN → CDG | May 10, 09:15 UTC | May 10, 18:39 UTC | 9h 25m |
| 2026-05-09 | HVN72 | MXP → HAN | May 9, 12:35 UTC | May 10, 07:15 UTC | 18h 40m |
| 2026-05-09 | HVN72 | MXP → HAN | May 9, 11:30 UTC | May 10, 07:15 UTC | 19h 45m |
| 2026-05-08 | HVN73 | HAN → MXP | May 8, 18:35 UTC | May 9, 05:30 UTC | 10h 55m |
| 2026-05-07 | HVN73 | HAN → MXP | May 7, 21:00 UTC | May 8, 20:30 UTC | 23h 30m |
| 2026-05-07 | HVN778 | MEL → HAN | May 7, 14:25 UTC | May 7, 21:35 UTC | 7h 10m |
| 2026-05-06 | HVN18 | CDG → HAN | May 6, 19:00 UTC | May 7, 11:45 UTC | 16h 45m |
| 2026-05-06 | HVN18 | CDG → HAN | May 6, 14:35 UTC | May 7, 11:45 UTC | 21h 10m |
| 2026-05-06 | HVN18 | CDG → HAN | May 6, 12:35 UTC | May 7, 11:45 UTC | 23h 10m |
| 2026-05-06 | HVN18 | CDG → HAN | May 6, 12:15 UTC | May 7, 08:25 UTC | 20h 10m |
| 2026-05-05 | HVN19 | HAN → CDG | May 5, 17:25 UTC | May 6, 04:45 UTC | 11h 20m |
| 2026-05-04 | HVN99 | SFO → SGN | May 4, 19:00 UTC | May 5, 18:30 UTC | 23h 30m |
| 2026-05-04 | HVN99 | SFO → SGN | May 4, 06:15 UTC | May 4, 19:50 UTC | 13h 36m |
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-A896 page for operator, model, and routing details .