sensors Mode-S transponder
8881EF
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A543 · AIRBUS A-321neo
- Hex
- 8881EF
- Octal
- 42100757
- Decimal
- 8,946,159
- Country
- VN
- Tail
- VN-A543
- Type
- A21N
- Flights observed
- 88
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 8881EF 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 |
|---|---|---|---|
| VJC834 | VietJet Air | 5 | 2026-05-09 |
| VJC828 | VietJet Air | 5 | 2026-04-20 |
| VJC835 | VietJet Air | 4 | 2026-05-09 |
| VJC829 | VietJet Air | 4 | 2026-04-21 |
| VJC947 | VietJet Air | 3 | 2026-05-25 |
| VJC946 | VietJet Air | 3 | 2026-05-25 |
| VJC928 | VietJet Air | 3 | 2026-05-16 |
| VJC884 | VietJet Air | 3 | 2026-04-16 |
| VJC883 | VietJet Air | 3 | 2026-04-16 |
| VJC5306 | - | 3 | 2026-05-03 |
| VJC3908 | VietJet Air | 3 | 2026-04-24 |
| VJC939 | VietJet Air | 2 | 2026-05-15 |
| VJC907 | VietJet Air | 2 | 2026-04-29 |
| VJC868 | VietJet Air | 2 | 2026-04-18 |
| VJC861 | VietJet Air | 2 | 2026-04-23 |
| VJC860 | VietJet Air | 2 | 2026-04-23 |
| VJC854 | VietJet Air | 2 | 2026-05-11 |
| VJC5347 | - | 2 | 2026-05-05 |
| VJC3909 | VietJet Air | 2 | 2026-04-24 |
| VJC998 | VietJet Air | 1 | 2026-04-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-25 | VJC947 | KHH → HAN | May 25, 11:00 UTC | May 25, 11:55 UTC | 55m |
| 2026-05-25 | VJC946 | HAN → KHH | May 25, 08:50 UTC | May 25, 10:05 UTC | 1h 15m |
| 2026-05-18 | VJC902 | BKK → HAN | May 18, 07:30 UTC | May 18, 07:55 UTC | 25m |
| 2026-05-17 | VJC943 | TPE → HAN | May 17, 12:15 UTC | May 18, 05:45 UTC | 17h 30m |
| 2026-05-17 | VJC942 | HAN → TPE | May 17, 01:00 UTC | May 17, 10:25 UTC | 9h 25m |
| 2026-05-16 | VJC928 | CGK → HAN | May 16, 07:25 UTC | May 16, 23:20 UTC | 15h 54m |
| 2026-05-15 | VJC929 | HAN → CGK | May 15, 10:25 UTC | May 16, 05:05 UTC | 18h 39m |
| 2026-05-15 | VJC939 | KIX → HAN | May 15, 00:45 UTC | May 15, 09:10 UTC | 8h 25m |
| 2026-05-14 | VJC938 | HAN → KIX | May 14, 22:00 UTC | May 14, 22:55 UTC | 55m |
| 2026-05-12 | VJC809 | SGN → HKT | May 12, 11:50 UTC | May 13, 06:10 UTC | 18h 20m |
| 2026-05-12 | VJC983 | PQC → SIN | May 12, 10:05 UTC | May 12, 10:15 UTC | 10m |
| 2026-05-12 | VJC984 | SIN → PQC | May 12, 05:40 UTC | May 12, 06:05 UTC | 25m |
| 2026-05-12 | VJC811 | SGN → SIN | May 12, 03:40 UTC | May 12, 03:55 UTC | 15m |
| 2026-05-11 | VJC854 | CGK → SGN | May 11, 07:50 UTC | May 12, 03:55 UTC | 20h 5m |
| 2026-05-11 | VJC854 | CGK → SGN | May 11, 06:50 UTC | May 12, 03:55 UTC | 21h 6m |
| 2026-05-11 | VJC855 | SGN → CGK | May 11, 05:20 UTC | May 11, 05:35 UTC | 15m |
| 2026-05-09 | VJC835 | ICN → CXR | May 9, 22:05 UTC | May 10, 01:00 UTC | 2h 55m |
| 2026-05-09 | VJC834 | CXR → ICN | May 9, 08:00 UTC | May 9, 20:55 UTC | 12h 55m |
| 2026-05-08 | VJC5349 | - | May 8, 15:05 UTC | May 9, 12:30 UTC | 21h 25m |
| 2026-05-08 | VJC5348 | - | May 8, 10:35 UTC | May 9, 08:05 UTC | 21h 30m |
| 2026-05-06 | VJC5102 | CXR → CXR | May 6, 08:55 UTC | May 6, 14:10 UTC | 5h 15m |
| 2026-05-05 | VJC5347 | - | May 5, 14:40 UTC | May 6, 09:15 UTC | 18h 35m |
| 2026-05-05 | VJC5347 | - | May 5, 11:30 UTC | May 6, 09:15 UTC | 21h 45m |
| 2026-05-04 | VJC835 | ICN → CXR | May 4, 21:55 UTC | May 5, 15:35 UTC | 17h 40m |
| 2026-05-04 | VJC834 | CXR → ICN | May 4, 07:45 UTC | May 4, 20:35 UTC | 12h 51m |
| 2026-05-03 | VJC5306 | - | May 3, 16:05 UTC | May 4, 08:35 UTC | 16h 30m |
| 2026-05-03 | VJC5306 | - | May 3, 11:50 UTC | May 4, 08:35 UTC | 20h 45m |
| 2026-05-03 | VJC5306 | - | May 3, 11:15 UTC | May 4, 08:35 UTC | 21h 20m |
| 2026-05-02 | VJC835 | ICN → CXR | May 2, 21:55 UTC | May 3, 16:09 UTC | 18h 14m |
| 2026-05-02 | VJC834 | CXR → ICN | May 2, 17:55 UTC | May 2, 20:40 UTC | 2h 45m |
| 2026-05-01 | VJC834 | CXR → ICN | May 1, 23:50 UTC | May 2, 20:40 UTC | 20h 51m |
| 2026-05-01 | VJC835 | ICN → CXR | May 1, 22:00 UTC | May 2, 20:40 UTC | 22h 40m |
| 2026-05-01 | VJC834 | CXR → ICN | May 1, 07:50 UTC | May 1, 20:45 UTC | 12h 55m |
| 2026-05-01 | VJC901 | HAN → BKK | May 1, 05:15 UTC | May 1, 06:00 UTC | 45m |
| 2026-04-30 | VJC928 | CGK → HAN | Apr 30, 07:50 UTC | May 1, 06:00 UTC | 22h 11m |
| 2026-04-30 | VJC928 | CGK → HAN | Apr 30, 07:40 UTC | May 1, 05:45 UTC | 22h 5m |
| 2026-04-29 | VJC910 | BOM → HAN | Apr 29, 21:15 UTC | Apr 30, 06:15 UTC | 8h 59m |
| 2026-04-29 | VJC907 | HAN → BOM | Apr 29, 18:15 UTC | Apr 29, 18:40 UTC | 25m |
| 2026-04-29 | VJC907 | HAN → BOM | Apr 29, 07:15 UTC | Apr 29, 16:45 UTC | 9h 31m |
| 2026-04-29 | VJC915 | HAN → SIN | Apr 29, 05:20 UTC | Apr 29, 05:50 UTC | 30m |
| 2026-04-27 | VJC939 | KIX → HAN | Apr 27, 00:40 UTC | Apr 27, 01:25 UTC | 45m |
| 2026-04-26 | VJC947 | KHH → HAN | Apr 26, 11:10 UTC | Apr 26, 22:25 UTC | 11h 15m |
| 2026-04-26 | VJC946 | HAN → KHH | Apr 26, 02:25 UTC | Apr 26, 10:15 UTC | 7h 50m |
| 2026-04-25 | VJC960 | HAN → ICN | Apr 25, 22:20 UTC | Apr 25, 22:55 UTC | 35m |
| 2026-04-25 | VJC998 | DPS → HAN | Apr 25, 11:10 UTC | Apr 25, 12:25 UTC | 1h 15m |
| 2026-04-24 | VJC3909 | CAN → SGN | Apr 24, 20:05 UTC | Apr 24, 20:15 UTC | 10m |
| 2026-04-24 | VJC3908 | SGN → CAN | Apr 24, 17:45 UTC | Apr 24, 18:20 UTC | 35m |
| 2026-04-24 | VJC3908 | SGN → CAN | Apr 24, 15:50 UTC | Apr 24, 16:00 UTC | 10m |
| 2026-04-24 | VJC7079 | MFM → HPH | Apr 24, 08:35 UTC | Apr 24, 08:45 UTC | 10m |
| 2026-04-24 | VJC7078 | - | Apr 24, 06:45 UTC | Apr 24, 07:05 UTC | 20m |
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-A543 page for operator, model, and routing details .