sensors Mode-S transponder
888183
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A505 · AIRBUS A-321neo
- Hex
- 888183
- Octal
- 42100603
- Decimal
- 8,946,051
- Country
- VN
- Tail
- VN-A505
- Type
- A21N
- Flights observed
- 70
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 59m ago
Last known position
Country allocation
The ICAO 24-bit address 888183 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 |
|---|---|---|---|
| HVN441 | Vietnam Airlines | 6 | 2026-04-15 |
| HVN582 | Vietnam Airlines | 5 | 2026-05-11 |
| HVN647 | Vietnam Airlines | 4 | 2026-05-19 |
| HVN440 | Vietnam Airlines | 4 | 2026-04-15 |
| HVN435 | Vietnam Airlines | 4 | 2026-04-18 |
| HVN434 | Vietnam Airlines | 4 | 2026-04-16 |
| HVN430 | Vietnam Airlines | 4 | 2026-05-28 |
| HVN663 | Vietnam Airlines | 2 | 2026-05-30 |
| HVN646 | Vietnam Airlines | 2 | 2026-05-19 |
| HVN619 | Vietnam Airlines | 2 | 2026-05-23 |
| HVN618 | Vietnam Airlines | 2 | 2026-05-23 |
| HVN586 | Vietnam Airlines | 2 | 2026-04-23 |
| HVN583 | Vietnam Airlines | 2 | 2026-05-11 |
| HVN431 | Vietnam Airlines | 2 | 2026-05-29 |
| HVN357 | Vietnam Airlines | 2 | 2026-05-16 |
| HVN348 | Vietnam Airlines | 2 | 2026-05-18 |
| HVN7162 | Vietnam Airlines | 1 | 2026-05-29 |
| HVN681 | Vietnam Airlines | 1 | 2026-05-17 |
| HVN680 | Vietnam Airlines | 1 | 2026-05-17 |
| HVN662 | Vietnam Airlines | 1 | 2026-04-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | HVN663 | HAN → SIN | May 30, 04:05 UTC | May 30, 04:30 UTC | 25m |
| 2026-05-30 | HVN579 | TPE → HAN | May 30, 00:10 UTC | May 30, 02:30 UTC | 2h 20m |
| 2026-05-29 | HVN578 | HAN → TPE | May 29, 10:30 UTC | May 29, 12:50 UTC | 2h 20m |
| 2026-05-29 | HVN7162 | DAD → HAN | May 29, 08:45 UTC | May 29, 09:00 UTC | 15m |
| 2026-05-29 | HVN431 | ICN → DAD | May 29, 02:30 UTC | May 29, 05:30 UTC | 3h 0m |
| 2026-05-28 | HVN430 | DAD → ICN | May 28, 02:35 UTC | May 28, 20:45 UTC | 18h 10m |
| 2026-05-27 | HVN430 | DAD → ICN | May 27, 18:05 UTC | May 27, 21:00 UTC | 2h 55m |
| 2026-05-27 | HVN430 | DAD → ICN | May 27, 01:19 UTC | May 27, 21:00 UTC | 19h 40m |
| 2026-05-26 | HVN334 | HAN → KIX | May 26, 20:40 UTC | May 26, 21:25 UTC | 45m |
| 2026-05-23 | HVN618 | BKK → HAN | May 23, 12:40 UTC | May 23, 13:35 UTC | 55m |
| 2026-05-23 | HVN619 | HAN → BKK | May 23, 10:10 UTC | May 23, 11:05 UTC | 55m |
| 2026-05-21 | HVN618 | BKK → HAN | May 21, 12:50 UTC | May 21, 13:15 UTC | 25m |
| 2026-05-21 | HVN619 | HAN → BKK | May 21, 10:45 UTC | May 21, 11:20 UTC | 35m |
| 2026-05-21 | HVN593 | HKG → HAN | May 21, 06:45 UTC | May 21, 07:00 UTC | 15m |
| 2026-05-21 | HVN592 | HAN → HKG | May 21, 04:50 UTC | May 21, 05:25 UTC | 35m |
| 2026-05-19 | HVN646 | MNL → HAN | May 19, 21:55 UTC | May 19, 22:25 UTC | 30m |
| 2026-05-19 | HVN647 | HAN → MNL | May 19, 00:50 UTC | May 19, 20:00 UTC | 19h 10m |
| 2026-05-19 | HVN647 | HAN → MNL | May 19, 00:40 UTC | May 19, 20:00 UTC | 19h 20m |
| 2026-05-18 | HVN348 | HAN → NGO | May 18, 21:05 UTC | May 18, 21:50 UTC | 45m |
| 2026-05-18 | HVN349 | NGO → HAN | May 18, 00:50 UTC | May 18, 21:50 UTC | 20h 59m |
| 2026-05-17 | HVN348 | HAN → NGO | May 17, 21:10 UTC | May 17, 22:01 UTC | 50m |
| 2026-05-17 | HVN680 | KUL → HAN | May 17, 12:25 UTC | May 17, 12:40 UTC | 15m |
| 2026-05-17 | HVN681 | HAN → KUL | May 17, 10:30 UTC | May 17, 10:55 UTC | 25m |
| 2026-05-16 | HVN357 | FUK → HAN | May 16, 01:15 UTC | May 16, 01:25 UTC | 10m |
| 2026-05-14 | HVN357 | FUK → HAN | May 14, 01:15 UTC | May 14, 01:25 UTC | 10m |
| 2026-05-11 | HVN649 | MNL → SGN | May 11, 20:30 UTC | May 11, 21:00 UTC | 30m |
| 2026-05-11 | HVN583 | KHH → HAN | May 11, 05:05 UTC | May 11, 18:55 UTC | 13h 50m |
| 2026-05-11 | HVN582 | HAN → KHH | May 11, 02:55 UTC | May 11, 03:40 UTC | 45m |
| 2026-05-09 | HVN581 | KHH → SGN | May 9, 23:30 UTC | May 10, 00:05 UTC | 35m |
| 2026-05-09 | HVN580 | SGN → KHH | May 9, 13:00 UTC | May 9, 13:35 UTC | 35m |
| 2026-05-08 | HVN630 | CGK → SGN | May 8, 07:04 UTC | May 8, 08:24 UTC | 1h 20m |
| 2026-05-08 | HVN631 | SGN → CGK | May 8, 05:24 UTC | May 8, 05:35 UTC | 10m |
| 2026-05-06 | HVN583 | KHH → HAN | May 6, 05:05 UTC | May 6, 05:35 UTC | 30m |
| 2026-05-05 | HVN582 | HAN → KHH | May 5, 20:30 UTC | May 6, 03:50 UTC | 7h 20m |
| 2026-05-05 | HVN648 | SGN → MNL | May 5, 11:30 UTC | May 5, 18:55 UTC | 7h 25m |
| 2026-05-05 | HVN431 | ICN → DAD | May 5, 02:30 UTC | May 5, 10:05 UTC | 7h 35m |
| 2026-05-04 | HVN430 | DAD → ICN | May 4, 05:05 UTC | May 4, 20:40 UTC | 15h 36m |
| 2026-05-04 | HVN582 | HAN → KHH | May 4, 03:00 UTC | May 4, 03:40 UTC | 40m |
| 2026-05-03 | HVN582 | HAN → KHH | May 3, 05:00 UTC | May 4, 03:40 UTC | 22h 40m |
| 2026-05-02 | HVN582 | HAN → KHH | May 2, 13:40 UTC | May 3, 03:45 UTC | 14h 4m |
| 2026-05-02 | HVN657 | SGN → SIN | May 2, 11:40 UTC | May 2, 12:20 UTC | 40m |
| 2026-04-30 | HVN662 | SIN → HAN | Apr 30, 08:20 UTC | Apr 30, 08:35 UTC | 15m |
| 2026-04-30 | HVN663 | HAN → SIN | Apr 30, 05:55 UTC | Apr 30, 06:25 UTC | 30m |
| 2026-04-28 | HVN503 | CAN → SGN | Apr 28, 09:15 UTC | Apr 28, 09:25 UTC | 10m |
| 2026-04-28 | HVN502 | SGN → CAN | Apr 28, 05:10 UTC | Apr 28, 05:30 UTC | 20m |
| 2026-04-24 | HVN646 | MNL → HAN | Apr 24, 21:30 UTC | Apr 25, 09:20 UTC | 11h 50m |
| 2026-04-24 | HVN647 | HAN → MNL | Apr 24, 00:50 UTC | Apr 24, 20:05 UTC | 19h 15m |
| 2026-04-24 | HVN647 | HAN → MNL | Apr 24, 00:30 UTC | Apr 24, 20:05 UTC | 19h 35m |
| 2026-04-23 | HVN586 | HAN → KHH | Apr 23, 12:20 UTC | Apr 23, 13:20 UTC | 1h 0m |
| 2026-04-22 | HVN586 | HAN → KHH | Apr 22, 15:30 UTC | Apr 23, 13:20 UTC | 21h 50m |
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-A505 page for operator, model, and routing details .