sensors Mode-S transponder
8881AC
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A524 · AIRBUS A-321neo
- Hex
- 8881AC
- Octal
- 42100654
- Decimal
- 8,946,092
- Country
- VN
- Tail
- VN-A524
- Type
- A21N
- Flights observed
- 106
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 37m ago
Last known position
Country allocation
The ICAO 24-bit address 8881AC 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 |
|---|---|---|---|
| VJC862 | VietJet Air | 4 | 2026-05-18 |
| VJC3908 | VietJet Air | 4 | 2026-04-21 |
| VJC1802 | VietJet Air | 4 | 2026-04-29 |
| VJC933 | VietJet Air | 3 | 2026-05-28 |
| VJC8893 | VietJet Air | 3 | 2026-05-16 |
| VJC868 | - | 3 | 2026-04-14 |
| VJC863 | VietJet Air | 3 | 2026-05-19 |
| VJC854 | - | 3 | 2026-04-13 |
| VJC843 | VietJet Air | 3 | 2026-05-05 |
| VJC977 | VietJet Air | 2 | 2026-04-25 |
| VJC976 | VietJet Air | 2 | 2026-04-25 |
| VJC969 | VietJet Air | 2 | 2026-04-27 |
| VJC932 | VietJet Air | 2 | 2026-05-27 |
| VJC907 | VietJet Air | 2 | 2026-05-20 |
| VJC884 | VietJet Air | 2 | 2026-05-28 |
| VJC883 | VietJet Air | 2 | 2026-05-28 |
| VJC879 | VietJet Air | 2 | 2026-05-14 |
| VJC878 | VietJet Air | 2 | 2026-05-14 |
| VJC860 | VietJet Air | 2 | 2026-04-20 |
| VJC842 | VietJet Air | 2 | 2026-05-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | VJC979 | ICN → PQC | May 29, 19:15 UTC | May 30, 05:00 UTC | 9h 45m |
| 2026-05-29 | VJC978 | PQC → ICN | May 29, 15:00 UTC | May 29, 18:00 UTC | 3h 0m |
| 2026-05-29 | VJC804 | BKK → SGN | May 29, 07:40 UTC | May 29, 07:55 UTC | 15m |
| 2026-05-29 | VJC803 | SGN → BKK | May 29, 05:30 UTC | May 29, 05:55 UTC | 25m |
| 2026-05-28 | VJC884 | BOM → SGN | May 28, 21:05 UTC | May 29, 00:10 UTC | 3h 5m |
| 2026-05-28 | VJC884 | BOM → SGN | May 28, 19:55 UTC | May 28, 20:05 UTC | 10m |
| 2026-05-28 | VJC883 | SGN → BOM | May 28, 18:15 UTC | May 28, 18:35 UTC | 20m |
| 2026-05-28 | VJC883 | SGN → BOM | May 28, 08:40 UTC | May 28, 17:05 UTC | 8h 25m |
| 2026-05-28 | VJC933 | NRT → HAN | May 28, 00:50 UTC | May 28, 05:45 UTC | 4h 55m |
| 2026-05-27 | VJC932 | HAN → NRT | May 27, 17:55 UTC | May 27, 22:50 UTC | 4h 55m |
| 2026-05-27 | VJC780 | - | May 27, 11:40 UTC | May 27, 16:05 UTC | 4h 25m |
| 2026-05-27 | VJC916 | SIN → HAN | May 27, 07:15 UTC | May 27, 07:40 UTC | 25m |
| 2026-05-26 | VJC1926 | AMD → HAN | May 26, 20:29 UTC | May 26, 22:35 UTC | 2h 5m |
| 2026-05-26 | VJC1925 | HAN → AMD | May 26, 07:10 UTC | May 26, 17:30 UTC | 10h 20m |
| 2026-05-26 | VJC915 | HAN → SIN | May 26, 05:15 UTC | May 26, 05:45 UTC | 30m |
| 2026-05-24 | VJC7527 | CAN → HAN | May 24, 18:50 UTC | May 24, 19:10 UTC | 20m |
| 2026-05-24 | VJC943 | TPE → HAN | May 24, 12:00 UTC | May 24, 13:10 UTC | 1h 10m |
| 2026-05-24 | VJC942 | HAN → TPE | May 24, 00:40 UTC | May 24, 10:30 UTC | 9h 50m |
| 2026-05-23 | VJC938 | HAN → KIX | May 23, 21:55 UTC | May 23, 22:40 UTC | 45m |
| 2026-05-23 | VJC933 | NRT → HAN | May 23, 01:05 UTC | May 23, 22:40 UTC | 21h 35m |
| 2026-05-23 | VJC933 | NRT → HAN | May 23, 00:55 UTC | May 23, 22:40 UTC | 21h 45m |
| 2026-05-22 | VJC932 | HAN → NRT | May 22, 21:35 UTC | May 22, 23:00 UTC | 1h 25m |
| 2026-05-21 | VJC972 | DEL → HAN | May 21, 18:45 UTC | May 21, 20:45 UTC | 2h 0m |
| 2026-05-21 | VJC971 | HAN → DEL | May 21, 07:10 UTC | May 21, 17:20 UTC | 10h 10m |
| 2026-05-20 | VJC910 | BOM → HAN | May 20, 19:50 UTC | May 21, 05:20 UTC | 9h 30m |
| 2026-05-20 | VJC907 | HAN → BOM | May 20, 17:55 UTC | May 20, 18:15 UTC | 20m |
| 2026-05-20 | VJC907 | HAN → BOM | May 20, 14:20 UTC | May 20, 16:05 UTC | 1h 45m |
| 2026-05-20 | VJC826 | KUL → SGN | May 20, 05:45 UTC | May 20, 06:00 UTC | 15m |
| 2026-05-20 | VJC825 | SGN → KUL | May 20, 04:05 UTC | May 20, 04:30 UTC | 25m |
| 2026-05-19 | VJC863 | ICN → SGN | May 19, 03:10 UTC | May 19, 05:55 UTC | 2h 45m |
| 2026-05-18 | VJC862 | SGN → ICN | May 18, 05:05 UTC | May 19, 00:35 UTC | 19h 29m |
| 2026-05-18 | VJC862 | SGN → ICN | May 18, 03:05 UTC | May 19, 00:35 UTC | 21h 29m |
| 2026-05-18 | VJC862 | SGN → ICN | May 18, 02:50 UTC | May 19, 00:35 UTC | 21h 44m |
| 2026-05-18 | VJC863 | ICN → SGN | May 18, 02:35 UTC | May 18, 02:40 UTC | 5m |
| 2026-05-17 | VJC862 | SGN → ICN | May 17, 10:30 UTC | May 18, 00:45 UTC | 14h 15m |
| 2026-05-16 | VJC989 | PUS → DAD | May 16, 19:05 UTC | May 17, 08:40 UTC | 13h 35m |
| 2026-05-16 | VJC8893 | MFM → MFM | May 16, 14:11 UTC | May 16, 14:20 UTC | 10m |
| 2026-05-15 | VJC8893 | MFM → MFM | May 15, 14:30 UTC | May 15, 14:45 UTC | 15m |
| 2026-05-15 | VJC8891 | MFM → DAD | May 15, 08:25 UTC | May 15, 08:45 UTC | 20m |
| 2026-05-14 | VJC879 | ICN → DAD | May 14, 22:05 UTC | May 15, 00:55 UTC | 2h 50m |
| 2026-05-14 | VJC878 | DAD → ICN | May 14, 18:05 UTC | May 14, 20:55 UTC | 2h 50m |
| 2026-05-05 | VJC843 | TPE → SGN | May 5, 11:35 UTC | May 5, 12:40 UTC | 1h 5m |
| 2026-05-05 | VJC842 | SGN → TPE | May 5, 09:05 UTC | May 5, 10:10 UTC | 1h 5m |
| 2026-05-01 | VJC925 | ICN → HPH | May 1, 23:45 UTC | May 2, 00:25 UTC | 40m |
| 2026-05-01 | VJC926 | HPH → ICN | May 1, 21:00 UTC | May 1, 21:40 UTC | 40m |
| 2026-04-30 | VJC877 | HKG → SGN | Apr 30, 12:35 UTC | Apr 30, 12:50 UTC | 15m |
| 2026-04-30 | VJC876 | SGN → HKG | Apr 30, 10:25 UTC | Apr 30, 10:35 UTC | 10m |
| 2026-04-29 | VJC1802 | BLR → SGN | Apr 29, 19:00 UTC | Apr 30, 06:10 UTC | 11h 9m |
| 2026-04-29 | VJC1801 | SGN → BLR | Apr 29, 07:55 UTC | Apr 29, 17:35 UTC | 9h 41m |
| 2026-04-28 | VJC985 | HKG → PQC | Apr 28, 08:55 UTC | Apr 28, 09:10 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-A524 page for operator, model, and routing details .