sensors Mode-S transponder
8881AB
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A523 · AIRBUS A-321neo
- Hex
- 8881AB
- Octal
- 42100653
- Decimal
- 8,946,091
- Country
- VN
- Tail
- VN-A523
- Type
- A21N
- Flights observed
- 229
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 8881AB 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 |
|---|---|---|---|
| VJC822 | - | 19 | 2026-07-10 |
| VJC821 | - | 16 | 2026-07-06 |
| VJC823 | - | 15 | 2026-07-11 |
| VJC820 | - | 14 | 2026-07-06 |
| VJC933 | - | 11 | 2026-06-16 |
| VJC91 | - | 11 | 2026-06-19 |
| VJC92 | - | 10 | 2026-07-04 |
| VJC932 | - | 8 | 2026-06-15 |
| VJC883 | VietJet Air | 7 | 2026-05-14 |
| VJC877 | - | 7 | 2026-07-03 |
| VJC876 | - | 7 | 2026-07-03 |
| VJC947 | VietJet Air | 6 | 2026-04-20 |
| VJC1804 | VietJet Air | 5 | 2026-05-16 |
| VJC946 | VietJet Air | 4 | 2026-04-18 |
| VJC934 | - | 4 | 2026-06-15 |
| VJC860 | VietJet Air | 4 | 2026-06-17 |
| VJC948 | - | 3 | 2026-04-13 |
| VJC935 | VietJet Air | 3 | 2026-06-15 |
| VJC885 | - | 3 | 2026-07-08 |
| VJC884 | VietJet Air | 3 | 2026-05-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | VJC157 | HAN → SGN | Jul 14, 13:00 UTC | Jul 14, 13:10 UTC | 10m |
| 2026-07-14 | VJC433 | - | Jul 14, 06:40 UTC | Jul 14, 06:55 UTC | 15m |
| 2026-07-14 | VJC939 | - | Jul 14, 00:45 UTC | Jul 14, 01:45 UTC | 1h 0m |
| 2026-07-13 | VJC938 | - | Jul 13, 18:35 UTC | Jul 13, 22:55 UTC | 4h 20m |
| 2026-07-13 | VJC561 | HAN → HUI | Jul 13, 13:10 UTC | Jul 13, 13:20 UTC | 10m |
| 2026-07-13 | VJC423 | - | Jul 13, 09:00 UTC | Jul 13, 09:15 UTC | 15m |
| 2026-07-13 | VJC921 | - | Jul 13, 02:45 UTC | Jul 13, 03:50 UTC | 1h 5m |
| 2026-07-12 | VJC920 | - | Jul 12, 21:05 UTC | Jul 13, 01:15 UTC | 4h 10m |
| 2026-07-12 | VJC157 | HAN → SGN | Jul 12, 14:40 UTC | Jul 12, 14:55 UTC | 15m |
| 2026-07-11 | VJC823 | - | Jul 11, 01:00 UTC | Jul 11, 05:05 UTC | 4h 5m |
| 2026-07-10 | VJC822 | - | Jul 10, 19:40 UTC | Jul 10, 23:15 UTC | 3h 35m |
| 2026-07-10 | VJC193 | - | Jul 10, 12:35 UTC | Jul 10, 12:50 UTC | 15m |
| 2026-07-10 | VJC142 | - | Jul 10, 10:45 UTC | Jul 10, 11:10 UTC | 25m |
| 2026-07-10 | VJC135 | - | Jul 10, 05:55 UTC | Jul 10, 06:10 UTC | 15m |
| 2026-07-09 | VJC425 | - | Jul 9, 04:45 UTC | Jul 9, 04:55 UTC | 10m |
| 2026-07-08 | VJC150 | SGN → HAN | Jul 8, 16:55 UTC | Jul 8, 17:05 UTC | 10m |
| 2026-07-08 | VJC885 | - | Jul 8, 04:40 UTC | Jul 8, 05:00 UTC | 20m |
| 2026-07-07 | VJC886 | - | Jul 7, 14:05 UTC | Jul 8, 03:35 UTC | 13h 30m |
| 2026-07-07 | VJC854 | - | Jul 7, 07:25 UTC | Jul 7, 12:55 UTC | 5h 30m |
| 2026-07-07 | VJC855 | - | Jul 7, 05:30 UTC | Jul 7, 05:55 UTC | 25m |
| 2026-07-06 | VJC821 | - | Jul 6, 17:25 UTC | Jul 6, 21:00 UTC | 3h 35m |
| 2026-07-06 | VJC820 | KHH → HND | Jul 6, 04:40 UTC | Jul 6, 15:20 UTC | 10h 40m |
| 2026-07-05 | VJC821 | HND → KHH | Jul 5, 17:05 UTC | Jul 6, 03:40 UTC | 10h 35m |
| 2026-07-05 | VJC823 | NRT → HND | Jul 5, 01:00 UTC | Jul 5, 15:30 UTC | 14h 30m |
| 2026-07-04 | VJC822 | - | Jul 4, 13:35 UTC | Jul 4, 22:45 UTC | 9h 10m |
| 2026-07-04 | VJC92 | - | Jul 4, 02:45 UTC | Jul 4, 12:10 UTC | 9h 25m |
| 2026-07-03 | VJC877 | HKG → PER | Jul 3, 12:55 UTC | Jul 4, 00:50 UTC | 11h 55m |
| 2026-07-03 | VJC876 | - | Jul 3, 10:15 UTC | Jul 3, 10:25 UTC | 10m |
| 2026-07-03 | VJC823 | - | Jul 3, 00:35 UTC | Jul 3, 04:25 UTC | 3h 50m |
| 2026-07-02 | VJC822 | TPE → NRT | Jul 2, 12:25 UTC | Jul 2, 22:25 UTC | 10h 0m |
| 2026-07-01 | VJC842 | - | Jul 1, 16:50 UTC | Jul 2, 10:40 UTC | 17h 50m |
| 2026-07-01 | VJC286 | - | Jul 1, 15:55 UTC | Jul 1, 16:10 UTC | 15m |
| 2026-07-01 | VJC854 | - | Jul 1, 06:45 UTC | Jul 1, 08:15 UTC | 1h 30m |
| 2026-06-27 | VJC821 | - | Jun 27, 17:25 UTC | Jun 28, 05:49 UTC | 12h 25m |
| 2026-06-27 | VJC823 | NRT → HND | Jun 27, 01:09 UTC | Jun 27, 15:34 UTC | 14h 25m |
| 2026-06-26 | VJC822 | - | Jun 26, 20:04 UTC | Jun 26, 23:34 UTC | 3h 30m |
| 2026-06-26 | VJC877 | - | Jun 26, 12:29 UTC | Jun 26, 12:44 UTC | 15m |
| 2026-06-26 | VJC876 | - | Jun 26, 10:39 UTC | Jun 26, 10:50 UTC | 10m |
| 2026-06-26 | VJC823 | - | Jun 26, 01:20 UTC | Jun 26, 05:10 UTC | 3h 50m |
| 2026-06-25 | VJC822 | - | Jun 25, 19:54 UTC | Jun 25, 23:34 UTC | 3h 40m |
| 2026-06-25 | VJC822 | - | Jun 25, 03:29 UTC | Jun 25, 23:34 UTC | 20h 5m |
| 2026-06-25 | VJC822 | KIX → NRT | Jun 25, 01:30 UTC | Jun 25, 23:34 UTC | 22h 5m |
| 2026-06-24 | VJC828 | - | Jun 24, 11:20 UTC | Jun 25, 00:05 UTC | 12h 45m |
| 2026-06-24 | VJC8510 | - | Jun 24, 03:29 UTC | Jun 24, 09:59 UTC | 6h 30m |
| 2026-06-23 | VJC767 | HPH → PQC | Jun 23, 08:54 UTC | Jun 24, 02:00 UTC | 17h 5m |
| 2026-06-23 | VJC766 | PQC → HPH | Jun 23, 07:45 UTC | Jun 23, 08:04 UTC | 20m |
| 2026-06-23 | VJC127 | HAN → SGN | Jun 23, 01:15 UTC | Jun 23, 01:40 UTC | 25m |
| 2026-06-22 | VJC169 | HAN → SGN | Jun 22, 16:54 UTC | Jun 22, 23:55 UTC | 7h 0m |
| 2026-06-22 | VJC273 | HPH → SGN | Jun 22, 11:09 UTC | Jun 22, 15:35 UTC | 4h 25m |
| 2026-06-22 | VJC7079 | - | Jun 22, 08:44 UTC | Jun 22, 09:54 UTC | 1h 10m |
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-A523 page for operator, model, and routing details .