sensors Mode-S transponder
8881A7
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A522 · AIRBUS A-321
- Hex
- 8881A7
- Octal
- 42100647
- Decimal
- 8,946,087
- Country
- VN
- Tail
- VN-A522
- Type
- A321
- Flights observed
- 63
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address 8881A7 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 |
|---|---|---|---|
| VJC1802 | VietJet Air | 6 | 2026-05-15 |
| VJC1801 | VietJet Air | 4 | 2026-05-15 |
| VJC861 | VietJet Air | 3 | 2026-05-26 |
| VJC916 | VietJet Air | 2 | 2026-05-02 |
| VJC915 | VietJet Air | 2 | 2026-05-02 |
| VJC877 | VietJet Air | 2 | 2026-05-29 |
| VJC876 | VietJet Air | 2 | 2026-05-29 |
| VJC860 | VietJet Air | 2 | 2026-05-26 |
| VJC859 | VietJet Air | 2 | 2026-05-11 |
| VJC858 | VietJet Air | 2 | 2026-05-11 |
| VJC807 | VietJet Air | 2 | 2026-04-17 |
| VJC800 | VietJet Air | 2 | 2026-04-17 |
| VJC979 | VietJet Air | 1 | 2026-05-31 |
| VJC978 | VietJet Air | 1 | 2026-05-31 |
| VJC961 | VietJet Air | 1 | 2026-04-27 |
| VJC960 | VietJet Air | 1 | 2026-04-26 |
| VJC949 | VietJet Air | 1 | 2026-04-28 |
| VJC948 | VietJet Air | 1 | 2026-04-27 |
| VJC926 | VietJet Air | 1 | 2026-05-06 |
| VJC925 | VietJet Air | 1 | 2026-05-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VJC1803 | SGN → HYD | Jun 2, 06:30 UTC | Jun 2, 20:45 UTC | 14h 15m |
| 2026-06-02 | VJC274 | SGN → HPH | Jun 2, 05:05 UTC | Jun 2, 05:25 UTC | 20m |
| 2026-05-31 | VJC979 | ICN → PQC | May 31, 19:05 UTC | May 31, 21:55 UTC | 2h 50m |
| 2026-05-31 | VJC978 | PQC → ICN | May 31, 15:00 UTC | May 31, 17:50 UTC | 2h 50m |
| 2026-05-29 | VJC877 | HKG → SGN | May 29, 12:35 UTC | May 29, 12:45 UTC | 10m |
| 2026-05-29 | VJC876 | SGN → HKG | May 29, 10:30 UTC | May 29, 10:50 UTC | 20m |
| 2026-05-27 | VJC802 | BKK → SGN | May 27, 04:45 UTC | May 27, 05:14 UTC | 30m |
| 2026-05-26 | VJC861 | ICN → SGN | May 26, 12:40 UTC | May 27, 03:04 UTC | 14h 25m |
| 2026-05-26 | VJC860 | SGN → ICN | May 26, 10:05 UTC | May 26, 10:44 UTC | 40m |
| 2026-05-25 | VJC861 | ICN → SGN | May 25, 13:55 UTC | May 26, 08:54 UTC | 18h 59m |
| 2026-05-25 | VJC861 | ICN → SGN | May 25, 12:15 UTC | May 25, 12:45 UTC | 30m |
| 2026-05-25 | VJC860 | SGN → ICN | May 25, 07:35 UTC | May 25, 10:35 UTC | 3h 0m |
| 2026-05-24 | VJC877 | HKG → SGN | May 24, 13:30 UTC | May 24, 13:50 UTC | 20m |
| 2026-05-24 | VJC876 | SGN → HKG | May 24, 11:00 UTC | May 24, 11:20 UTC | 20m |
| 2026-05-24 | VJC885 | KHH → SGN | May 24, 04:35 UTC | May 24, 05:25 UTC | 50m |
| 2026-05-24 | VJC886 | SGN → KHH | May 24, 03:05 UTC | May 24, 03:40 UTC | 35m |
| 2026-05-17 | VJC853 | RMQ → SGN | May 17, 07:35 UTC | May 17, 08:25 UTC | 50m |
| 2026-05-17 | VJC852 | SGN → RMQ | May 17, 05:35 UTC | May 17, 06:20 UTC | 45m |
| 2026-05-15 | VJC1802 | BLR → SGN | May 15, 19:50 UTC | May 15, 22:40 UTC | 2h 50m |
| 2026-05-15 | VJC1802 | BLR → SGN | May 15, 19:00 UTC | May 15, 19:10 UTC | 10m |
| 2026-05-15 | VJC1801 | SGN → BLR | May 15, 07:55 UTC | May 15, 17:35 UTC | 9h 39m |
| 2026-05-11 | VJC859 | MNL → SGN | May 11, 19:35 UTC | May 11, 20:05 UTC | 30m |
| 2026-05-11 | VJC858 | SGN → MNL | May 11, 10:10 UTC | May 11, 18:05 UTC | 7h 56m |
| 2026-05-10 | VJC879 | ICN → DAD | May 10, 22:20 UTC | May 11, 08:30 UTC | 10h 10m |
| 2026-05-10 | VJC878 | DAD → ICN | May 10, 03:35 UTC | May 10, 21:00 UTC | 17h 25m |
| 2026-05-10 | VJC813 | SGN → SIN | May 10, 01:30 UTC | May 10, 01:50 UTC | 20m |
| 2026-05-06 | VJC925 | ICN → HPH | May 6, 22:15 UTC | May 6, 22:55 UTC | 40m |
| 2026-05-06 | VJC926 | HPH → ICN | May 6, 20:15 UTC | May 6, 20:55 UTC | 40m |
| 2026-05-02 | VJC916 | SIN → HAN | May 2, 07:15 UTC | May 2, 07:25 UTC | 10m |
| 2026-05-02 | VJC915 | HAN → SIN | May 2, 05:25 UTC | May 2, 05:45 UTC | 20m |
| 2026-04-30 | VJC916 | SIN → HAN | Apr 30, 07:30 UTC | Apr 30, 07:45 UTC | 15m |
| 2026-04-30 | VJC915 | HAN → SIN | Apr 30, 05:20 UTC | Apr 30, 05:50 UTC | 30m |
| 2026-04-28 | VJC949 | RMQ → HAN | Apr 28, 10:10 UTC | Apr 28, 11:20 UTC | 1h 10m |
| 2026-04-27 | VJC948 | HAN → RMQ | Apr 27, 23:50 UTC | Apr 28, 08:55 UTC | 9h 5m |
| 2026-04-27 | VJC961 | ICN → HAN | Apr 27, 02:15 UTC | Apr 27, 23:50 UTC | 21h 35m |
| 2026-04-26 | VJC960 | HAN → ICN | Apr 26, 22:30 UTC | Apr 26, 22:50 UTC | 20m |
| 2026-04-26 | VJC902 | BKK → HAN | Apr 26, 07:25 UTC | Apr 26, 07:50 UTC | 25m |
| 2026-04-26 | VJC901 | HAN → BKK | Apr 26, 05:35 UTC | Apr 26, 06:00 UTC | 25m |
| 2026-04-25 | VJC1128 | SGN → HAN | Apr 25, 15:40 UTC | Apr 25, 15:50 UTC | 10m |
| 2026-04-25 | VJC1831 | SGN → VTE | Apr 25, 09:45 UTC | Apr 25, 09:55 UTC | 10m |
| 2026-04-25 | VJC245 | THD → SGN | Apr 25, 08:05 UTC | Apr 25, 08:15 UTC | 10m |
| 2026-04-24 | VJC601 | CXR → SGN | Apr 24, 10:30 UTC | Apr 24, 10:40 UTC | 10m |
| 2026-04-22 | VJC600 | SGN → CXR | Apr 22, 08:10 UTC | Apr 22, 08:20 UTC | 10m |
| 2026-04-19 | VJC621 | DAD → SGN | Apr 19, 23:25 UTC | Apr 19, 23:35 UTC | 10m |
| 2026-04-19 | VJC481 | VII → VCA | Apr 19, 12:00 UTC | Apr 19, 12:10 UTC | 10m |
| 2026-04-19 | VJC480 | VCA → VII | Apr 19, 08:40 UTC | Apr 19, 08:50 UTC | 10m |
| 2026-04-19 | VJC703 | DAD → VCA | Apr 19, 07:30 UTC | Apr 19, 07:40 UTC | 10m |
| 2026-04-18 | VJC808 | HKT → SGN | Apr 18, 06:15 UTC | Apr 18, 06:35 UTC | 20m |
| 2026-04-18 | VJC809 | SGN → HKT | Apr 18, 02:10 UTC | Apr 18, 02:25 UTC | 15m |
| 2026-04-17 | VJC1802 | BLR → SGN | Apr 17, 22:45 UTC | Apr 17, 23:00 UTC | 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-A522 page for operator, model, and routing details .