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
- 199
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- Jul 26, 22:30 UTC
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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HVN18 | Vietnam Airlines | 29 | 2026-07-26 |
| HVN19 | Vietnam Airlines | 26 | 2026-07-25 |
| HVN773 | Vietnam Airlines | 15 | 2026-07-23 |
| HVN11 | - | 10 | 2026-07-09 |
| HVN10 | - | 10 | 2026-07-10 |
| HVN778 | - | 9 | 2026-07-02 |
| HVN72 | Vietnam Airlines | 9 | 2026-05-30 |
| HVN787 | Vietnam Airlines | 8 | 2026-07-24 |
| HVN98 | - | 6 | 2026-07-04 |
| HVN786 | Vietnam Airlines | 6 | 2026-07-25 |
| HVN99 | - | 5 | 2026-07-05 |
| HVN979 | - | 5 | 2026-07-13 |
| HVN779 | - | 5 | 2026-07-02 |
| HVN772 | Vietnam Airlines | 4 | 2026-07-24 |
| HVN73 | Vietnam Airlines | 4 | 2026-05-29 |
| HVN34 | - | 4 | 2026-04-13 |
| HVN981 | Vietnam Airlines | 3 | 2026-06-15 |
| HVN978 | - | 3 | 2026-07-13 |
| HVN781 | Vietnam Airlines | 3 | 2026-07-22 |
| HVN68 | - | 3 | 2026-06-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | HVN18 | CDG → HAN | Jul 26, 13:35 UTC | Jul 26, 22:30 UTC | 8h 55m |
| 2026-07-25 | HVN19 | HAN → CDG | Jul 25, 17:50 UTC | Jul 26, 04:30 UTC | 10h 40m |
| 2026-07-25 | HVN786 | SYD → HAN | Jul 25, 04:30 UTC | Jul 25, 11:50 UTC | 7h 20m |
| 2026-07-24 | HVN787 | HAN → SYD | Jul 24, 19:30 UTC | Jul 25, 02:00 UTC | 6h 30m |
| 2026-07-24 | HVN787 | HAN → SYD | Jul 24, 17:20 UTC | Jul 24, 17:30 UTC | 10m |
| 2026-07-24 | HVN772 | SYD → SGN | Jul 24, 00:45 UTC | Jul 24, 08:05 UTC | 7h 20m |
| 2026-07-23 | HVN773 | SGN → SYD | Jul 23, 04:50 UTC | Jul 23, 21:50 UTC | 17h 0m |
| 2026-07-23 | HVN773 | SGN → SYD | Jul 23, 00:50 UTC | Jul 23, 21:50 UTC | 21h 0m |
| 2026-07-22 | HVN781 | SGN → MEL | Jul 22, 11:30 UTC | Jul 22, 22:25 UTC | 10h 55m |
| 2026-07-21 | HVN7220 | - | Jul 21, 23:40 UTC | Jul 22, 04:30 UTC | 4h 50m |
| 2026-07-19 | HVN18 | CDG → HAN | Jul 19, 12:30 UTC | Jul 19, 22:35 UTC | 10h 5m |
| 2026-07-18 | HVN19 | HAN → CDG | Jul 18, 10:50 UTC | Jul 19, 05:10 UTC | 18h 20m |
| 2026-07-18 | HVN19 | HAN → CDG | Jul 18, 08:05 UTC | Jul 19, 05:10 UTC | 21h 5m |
| 2026-07-18 | HVN19 | HAN → CDG | Jul 18, 04:35 UTC | Jul 19, 04:30 UTC | 23h 55m |
| 2026-07-17 | HVN787 | HAN → SYD | Jul 17, 19:05 UTC | Jul 18, 02:05 UTC | 7h 0m |
| 2026-07-17 | HVN787 | HAN → SYD | Jul 17, 16:55 UTC | Jul 17, 17:09 UTC | 15m |
| 2026-07-17 | HVN385 | - | Jul 17, 11:55 UTC | Jul 17, 12:04 UTC | 10m |
| 2026-07-17 | HVN385 | - | Jul 17, 07:55 UTC | Jul 17, 09:20 UTC | 1h 25m |
| 2026-07-17 | HVN384 | HAN → HND | Jul 17, 04:29 UTC | Jul 17, 06:20 UTC | 1h 50m |
| 2026-07-16 | HVN18 | - | Jul 16, 12:14 UTC | Jul 16, 22:35 UTC | 10h 20m |
| 2026-07-15 | HVN19 | - | Jul 15, 18:05 UTC | Jul 16, 05:00 UTC | 10h 55m |
| 2026-07-15 | HVN251 | - | Jul 15, 05:45 UTC | Jul 15, 06:00 UTC | 15m |
| 2026-07-14 | HVN243 | - | Jul 14, 23:20 UTC | Jul 14, 23:35 UTC | 15m |
| 2026-07-13 | HVN978 | - | Jul 13, 19:05 UTC | Jul 14, 09:00 UTC | 13h 55m |
| 2026-07-13 | HVN978 | - | Jul 13, 17:45 UTC | Jul 13, 17:55 UTC | 10m |
| 2026-07-13 | HVN979 | - | Jul 13, 15:30 UTC | Jul 13, 15:50 UTC | 20m |
| 2026-07-13 | HVN979 | - | Jul 13, 00:45 UTC | Jul 13, 14:35 UTC | 13h 50m |
| 2026-07-12 | HVN773 | - | Jul 12, 04:55 UTC | Jul 12, 22:20 UTC | 17h 25m |
| 2026-07-12 | HVN773 | SYD → SYD | Jul 12, 01:00 UTC | Jul 12, 22:20 UTC | 21h 20m |
| 2026-07-11 | HVN773 | - | Jul 11, 02:40 UTC | Jul 11, 22:10 UTC | 19h 30m |
| 2026-07-10 | HVN524 | - | Jul 10, 20:35 UTC | Jul 11, 18:35 UTC | 22h 0m |
| 2026-07-10 | HVN10 | - | Jul 10, 18:35 UTC | Jul 11, 15:50 UTC | 21h 15m |
| 2026-07-10 | HVN10 | - | Jul 10, 16:35 UTC | Jul 11, 15:50 UTC | 23h 16m |
| 2026-07-10 | HVN10 | - | Jul 10, 16:20 UTC | Jul 11, 09:00 UTC | 16h 40m |
| 2026-07-10 | HVN10 | - | Jul 10, 12:35 UTC | Jul 11, 09:00 UTC | 20h 25m |
| 2026-07-10 | HVN10 | - | Jul 10, 10:35 UTC | Jul 11, 09:00 UTC | 22h 25m |
| 2026-07-10 | HVN10 | - | Jul 10, 10:10 UTC | Jul 11, 03:35 UTC | 17h 26m |
| 2026-07-09 | HVN11 | - | Jul 9, 12:00 UTC | Jul 10, 04:55 UTC | 16h 55m |
| 2026-07-09 | HVN214 | - | Jul 9, 09:35 UTC | Jul 9, 09:45 UTC | 10m |
| 2026-07-09 | HVN321 | - | Jul 9, 01:25 UTC | Jul 9, 03:55 UTC | 2h 30m |
| 2026-07-08 | HVN320 | - | Jul 8, 19:55 UTC | Jul 8, 22:30 UTC | 2h 35m |
| 2026-07-08 | HVN1187 | HPH → SGN | Jul 8, 14:00 UTC | Jul 8, 14:15 UTC | 15m |
| 2026-07-08 | HVN1186 | SGN → HPH | Jul 8, 12:35 UTC | Jul 8, 12:45 UTC | 10m |
| 2026-07-08 | HVN772 | - | Jul 8, 00:40 UTC | Jul 8, 08:25 UTC | 7h 45m |
| 2026-07-07 | HVN773 | - | Jul 7, 04:50 UTC | Jul 7, 21:40 UTC | 16h 50m |
| 2026-07-07 | HVN773 | SYD → SYD | Jul 7, 00:45 UTC | Jul 7, 21:40 UTC | 20h 55m |
| 2026-07-06 | HVN773 | - | Jul 6, 06:30 UTC | Jul 6, 22:10 UTC | 15h 40m |
| 2026-07-05 | HVN99 | - | Jul 5, 06:10 UTC | Jul 5, 19:20 UTC | 13h 10m |
| 2026-07-04 | HVN98 | - | Jul 4, 07:20 UTC | Jul 5, 01:00 UTC | 17h 40m |
| 2026-07-04 | HVN780 | - | Jul 4, 00:55 UTC | Jul 5, 00:30 UTC | 23h 35m |
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 .