sensors Mode-S transponder
8881D9
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A528 · AIRBUS A-321neo
- Hex
- 8881D9
- Octal
- 42100731
- Decimal
- 8,946,137
- Country
- VN
- Tail
- VN-A528
- Type
- A21N
- Flights observed
- 104
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 8881D9 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 |
|---|---|---|---|
| VJC883 | VietJet Air | 5 | 2026-05-05 |
| VJC3900 | VietJet Air | 5 | 2026-05-16 |
| VJC8893 | VietJet Air | 4 | 2026-04-20 |
| VJC868 | VietJet Air | 4 | 2026-06-02 |
| VJC1805 | VietJet Air | 4 | 2026-05-04 |
| VJC8891 | VietJet Air | 3 | 2026-04-19 |
| VJC884 | VietJet Air | 3 | 2026-05-07 |
| VJC879 | VietJet Air | 3 | 2026-04-15 |
| VJC855 | VietJet Air | 3 | 2026-05-04 |
| VJC854 | VietJet Air | 3 | 2026-05-20 |
| VJC829 | VietJet Air | 3 | 2026-05-02 |
| VJC828 | VietJet Air | 3 | 2026-05-01 |
| VJC979 | VietJet Air | 2 | 2026-05-18 |
| VJC978 | VietJet Air | 2 | 2026-05-18 |
| VJC918 | VietJet Air | 2 | 2026-05-22 |
| VJC894 | VietJet Air | 2 | 2026-04-25 |
| VJC893 | VietJet Air | 2 | 2026-04-25 |
| VJC8892 | - | 2 | 2026-04-16 |
| VJC886 | VietJet Air | 2 | 2026-06-01 |
| VJC878 | - | 2 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VJC868 | SGN → PUS | Jun 2, 19:25 UTC | Jun 3, 02:25 UTC | 7h 0m |
| 2026-06-02 | VJC868 | SGN → PUS | Jun 2, 04:55 UTC | Jun 3, 02:25 UTC | 21h 30m |
| 2026-06-01 | VJC886 | SGN → KHH | Jun 1, 12:20 UTC | Jun 2, 03:50 UTC | 15h 30m |
| 2026-06-01 | VJC1454 | PQC → HAN | Jun 1, 05:40 UTC | Jun 1, 10:00 UTC | 4h 20m |
| 2026-06-01 | VJC1771 | HAN → CXR | Jun 1, 00:25 UTC | Jun 1, 04:30 UTC | 4h 5m |
| 2026-05-31 | VJC916 | SIN → HAN | May 31, 09:50 UTC | May 31, 10:05 UTC | 15m |
| 2026-05-29 | VJC913 | HAN → SAI | May 29, 09:55 UTC | May 29, 13:40 UTC | 3h 45m |
| 2026-05-29 | VJC510 | DAD → HAN | May 29, 07:55 UTC | May 29, 08:10 UTC | 15m |
| 2026-05-29 | VJC507 | HAN → DAD | May 29, 05:10 UTC | May 29, 05:20 UTC | 10m |
| 2026-05-29 | VJC503 | HAN → DAD | May 29, 00:50 UTC | May 29, 01:05 UTC | 15m |
| 2026-05-28 | VJC853 | RMQ → SGN | May 28, 07:50 UTC | May 28, 15:50 UTC | 8h 0m |
| 2026-05-27 | VJC852 | SGN → RMQ | May 27, 12:50 UTC | May 28, 06:35 UTC | 17h 45m |
| 2026-05-27 | VJC774 | CXR → HAN | May 27, 10:30 UTC | May 27, 10:40 UTC | 10m |
| 2026-05-25 | VJC835 | ICN → CXR | May 25, 22:00 UTC | May 26, 14:09 UTC | 16h 10m |
| 2026-05-25 | VJC834 | CXR → ICN | May 25, 17:45 UTC | May 25, 20:34 UTC | 2h 50m |
| 2026-05-22 | VJC918 | CXR → PUS | May 22, 10:20 UTC | May 23, 04:35 UTC | 18h 15m |
| 2026-05-22 | VJC918 | CXR → PUS | May 22, 10:10 UTC | May 23, 04:35 UTC | 18h 25m |
| 2026-05-21 | VJC835 | ICN → CXR | May 21, 22:15 UTC | May 22, 09:00 UTC | 10h 45m |
| 2026-05-21 | VJC834 | CXR → ICN | May 21, 18:00 UTC | May 21, 20:55 UTC | 2h 55m |
| 2026-05-21 | VJC5531 | MFM → MFM | May 21, 10:30 UTC | May 21, 10:45 UTC | 15m |
| 2026-05-20 | VJC1802 | BLR → SGN | May 20, 21:10 UTC | May 20, 22:20 UTC | 1h 10m |
| 2026-05-20 | VJC1802 | BLR → SGN | May 20, 18:35 UTC | May 20, 18:50 UTC | 15m |
| 2026-05-20 | VJC1801 | SGN → BLR | May 20, 16:40 UTC | May 20, 17:05 UTC | 25m |
| 2026-05-20 | VJC854 | CGK → SGN | May 20, 06:50 UTC | May 20, 14:25 UTC | 7h 35m |
| 2026-05-19 | VJC845 | TPE → PQC | May 19, 07:10 UTC | May 19, 08:10 UTC | 1h 0m |
| 2026-05-18 | VJC979 | ICN → PQC | May 18, 19:10 UTC | May 19, 05:40 UTC | 10h 30m |
| 2026-05-18 | VJC978 | PQC → ICN | May 18, 15:05 UTC | May 18, 17:55 UTC | 2h 50m |
| 2026-05-18 | VJC826 | KUL → SGN | May 18, 05:35 UTC | May 18, 05:50 UTC | 15m |
| 2026-05-18 | VJC825 | SGN → KUL | May 18, 04:00 UTC | May 18, 04:15 UTC | 15m |
| 2026-05-17 | VJC896 | DEL → SGN | May 17, 19:30 UTC | May 17, 21:30 UTC | 2h 0m |
| 2026-05-17 | VJC895 | SGN → DEL | May 17, 03:35 UTC | May 17, 18:01 UTC | 14h 25m |
| 2026-05-16 | VJC3900 | SGN → PVG | May 16, 15:16 UTC | May 17, 02:05 UTC | 10h 50m |
| 2026-05-16 | VJC3900 | SGN → PVG | May 16, 03:40 UTC | May 17, 02:05 UTC | 22h 25m |
| 2026-05-15 | VJC7079 | MFM → HPH | May 15, 08:40 UTC | May 15, 08:55 UTC | 15m |
| 2026-05-13 | VJC3900 | SGN → PVG | May 13, 15:15 UTC | May 13, 20:55 UTC | 5h 40m |
| 2026-05-12 | VJC843 | TPE → SGN | May 12, 11:30 UTC | May 12, 12:35 UTC | 1h 5m |
| 2026-05-11 | VJC868 | SGN → PUS | May 11, 19:35 UTC | May 12, 09:55 UTC | 14h 20m |
| 2026-05-11 | VJC868 | SGN → PUS | May 11, 12:20 UTC | May 12, 09:55 UTC | 21h 36m |
| 2026-05-11 | VJC843 | TPE → SGN | May 11, 12:05 UTC | May 12, 09:55 UTC | 21h 51m |
| 2026-05-10 | VJC979 | ICN → PQC | May 10, 19:05 UTC | May 11, 10:30 UTC | 15h 25m |
| 2026-05-10 | VJC978 | PQC → ICN | May 10, 04:34 UTC | May 10, 17:45 UTC | 13h 10m |
| 2026-05-10 | VJC886 | SGN → KHH | May 10, 02:50 UTC | May 10, 03:35 UTC | 45m |
| 2026-05-07 | VJC884 | BOM → SGN | May 7, 08:00 UTC | May 8, 00:29 UTC | 16h 30m |
| 2026-05-06 | VJC804 | BKK → SGN | May 6, 07:20 UTC | May 6, 07:50 UTC | 30m |
| 2026-05-05 | VJC883 | SGN → BOM | May 5, 13:55 UTC | May 6, 05:40 UTC | 15h 45m |
| 2026-05-05 | VJC883 | SGN → BOM | May 5, 08:20 UTC | May 6, 05:40 UTC | 21h 20m |
| 2026-05-05 | VJC883 | SGN → BOM | May 5, 07:45 UTC | May 6, 05:40 UTC | 21h 55m |
| 2026-05-04 | VJC1805 | SGN → AMD | May 4, 13:00 UTC | May 5, 06:30 UTC | 17h 31m |
| 2026-05-04 | VJC1805 | SGN → AMD | May 4, 08:20 UTC | May 5, 06:30 UTC | 22h 11m |
| 2026-05-04 | VJC1805 | SGN → AMD | May 4, 07:05 UTC | May 5, 06:15 UTC | 23h 11m |
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-A528 page for operator, model, and routing details .