sensors Mode-S transponder
8881C6
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A811 · AIRBUS A-330-300
- Hex
- 8881C6
- Octal
- 42100706
- Decimal
- 8,946,118
- Country
- VN
- Tail
- VN-A811
- Type
- A333
- Flights observed
- 91
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 8881C6 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 |
|---|---|---|---|
| VJC895 | VietJet Air | 10 | 2026-05-10 |
| VJC81 | VietJet Air | 10 | 2026-05-25 |
| VJC83 | VietJet Air | 7 | 2026-05-25 |
| VJC82 | VietJet Air | 7 | 2026-05-26 |
| VJC86 | VietJet Air | 6 | 2026-05-05 |
| VJC85 | VietJet Air | 6 | 2026-05-04 |
| VJC971 | VietJet Air | 5 | 2026-04-16 |
| VJC896 | VietJet Air | 5 | 2026-05-10 |
| VJC64 | - | 5 | 2026-05-02 |
| VJC972 | - | 4 | 2026-04-16 |
| VJC84 | VietJet Air | 4 | 2026-05-25 |
| VJC63 | - | 4 | 2026-05-01 |
| VJC8931 | - | 3 | 2026-05-29 |
| VJC8923 | - | 3 | 2026-06-02 |
| VJC56 | - | 3 | 2026-05-27 |
| VJC55 | - | 3 | 2026-05-26 |
| VJC67 | VietJet Air | 2 | 2026-05-21 |
| VJC8932 | - | 1 | 2026-05-30 |
| VJC8924 | - | 1 | 2026-06-02 |
| VJC138 | VietJet Air | 1 | 2026-04-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VJC8924 | - | Jun 2, 13:05 UTC | Jun 2, 16:40 UTC | 3h 35m |
| 2026-06-02 | VJC8923 | - | Jun 2, 00:35 UTC | Jun 2, 10:05 UTC | 9h 30m |
| 2026-05-30 | VJC8932 | - | May 30, 14:20 UTC | May 30, 22:25 UTC | 8h 5m |
| 2026-05-29 | VJC8931 | - | May 29, 21:10 UTC | May 30, 11:10 UTC | 14h 0m |
| 2026-05-29 | VJC8931 | - | May 29, 13:35 UTC | May 30, 11:10 UTC | 21h 35m |
| 2026-05-29 | VJC8931 | - | May 29, 13:00 UTC | May 30, 11:10 UTC | 22h 10m |
| 2026-05-29 | VJC8923 | - | May 29, 00:15 UTC | May 29, 08:50 UTC | 8h 35m |
| 2026-05-28 | VJC8923 | - | May 28, 11:50 UTC | May 29, 08:50 UTC | 21h 0m |
| 2026-05-27 | VJC56 | - | May 27, 15:35 UTC | May 28, 10:10 UTC | 18h 35m |
| 2026-05-27 | VJC56 | - | May 27, 15:10 UTC | May 28, 10:10 UTC | 19h 0m |
| 2026-05-26 | VJC55 | - | May 26, 21:34 UTC | May 27, 15:40 UTC | 18h 6m |
| 2026-05-26 | VJC55 | - | May 26, 21:25 UTC | May 27, 15:40 UTC | 18h 16m |
| 2026-05-26 | VJC55 | - | May 26, 18:34 UTC | May 27, 15:40 UTC | 21h 6m |
| 2026-05-26 | VJC82 | MEL → SGN | May 26, 15:00 UTC | May 26, 21:44 UTC | 6h 45m |
| 2026-05-25 | VJC81 | SGN → MEL | May 25, 18:10 UTC | May 26, 13:04 UTC | 18h 54m |
| 2026-05-25 | VJC84 | BNE → SGN | May 25, 14:05 UTC | May 26, 13:04 UTC | 22h 59m |
| 2026-05-25 | VJC83 | SGN → BNE | May 25, 05:15 UTC | May 25, 11:25 UTC | 6h 10m |
| 2026-05-23 | VJC82 | MEL → SGN | May 23, 14:40 UTC | May 23, 22:20 UTC | 7h 40m |
| 2026-05-23 | VJC81 | SGN → MEL | May 23, 06:05 UTC | May 23, 12:25 UTC | 6h 20m |
| 2026-05-21 | VJC67 | CXR → NQZ | May 21, 12:30 UTC | May 21, 13:05 UTC | 35m |
| 2026-05-19 | VJC82 | MEL → SGN | May 19, 14:45 UTC | May 19, 22:00 UTC | 7h 15m |
| 2026-05-19 | VJC81 | SGN → MEL | May 19, 05:35 UTC | May 19, 12:20 UTC | 6h 45m |
| 2026-05-14 | VJC67 | CXR → NQZ | May 14, 14:35 UTC | May 14, 18:45 UTC | 4h 10m |
| 2026-05-12 | VJC82 | MEL → SGN | May 12, 14:45 UTC | May 12, 21:55 UTC | 7h 10m |
| 2026-05-12 | VJC81 | SGN → MEL | May 12, 05:50 UTC | May 12, 12:40 UTC | 6h 50m |
| 2026-05-10 | VJC896 | DEL → SGN | May 10, 19:15 UTC | May 10, 23:00 UTC | 3h 45m |
| 2026-05-10 | VJC895 | SGN → DEL | May 10, 13:14 UTC | May 10, 17:45 UTC | 4h 30m |
| 2026-05-09 | VJC895 | SGN → DEL | May 9, 20:49 UTC | May 10, 17:45 UTC | 20h 55m |
| 2026-05-09 | VJC895 | SGN → DEL | May 9, 17:45 UTC | May 10, 17:30 UTC | 23h 45m |
| 2026-05-09 | VJC84 | BNE → SGN | May 9, 13:40 UTC | May 10, 13:30 UTC | 23h 50m |
| 2026-05-08 | VJC83 | SGN → BNE | May 8, 17:50 UTC | May 9, 11:05 UTC | 17h 15m |
| 2026-05-08 | VJC84 | BNE → SGN | May 8, 13:45 UTC | May 9, 11:05 UTC | 21h 20m |
| 2026-05-07 | VJC83 | SGN → BNE | May 7, 21:35 UTC | May 8, 11:19 UTC | 13h 45m |
| 2026-05-07 | VJC83 | SGN → BNE | May 7, 14:45 UTC | May 8, 11:19 UTC | 20h 34m |
| 2026-05-07 | VJC81 | SGN → MEL | May 7, 05:50 UTC | May 7, 12:35 UTC | 6h 45m |
| 2026-05-05 | VJC86 | SYD → SGN | May 5, 00:45 UTC | May 5, 08:15 UTC | 7h 30m |
| 2026-05-04 | VJC85 | SGN → SYD | May 4, 05:15 UTC | May 4, 21:25 UTC | 16h 11m |
| 2026-05-04 | VJC86 | SYD → SGN | May 4, 00:55 UTC | May 4, 21:25 UTC | 20h 31m |
| 2026-05-03 | VJC85 | SGN → SYD | May 3, 14:45 UTC | May 3, 21:35 UTC | 6h 50m |
| 2026-05-02 | VJC64 | - | May 2, 08:55 UTC | May 3, 01:25 UTC | 16h 30m |
| 2026-05-01 | VJC63 | - | May 1, 21:35 UTC | May 2, 19:15 UTC | 21h 40m |
| 2026-05-01 | VJC896 | DEL → SGN | May 1, 19:35 UTC | May 2, 19:15 UTC | 23h 41m |
| 2026-05-01 | VJC896 | DEL → SGN | May 1, 19:15 UTC | May 2, 15:45 UTC | 20h 30m |
| 2026-05-01 | VJC895 | SGN → DEL | May 1, 13:15 UTC | May 1, 17:45 UTC | 4h 30m |
| 2026-04-30 | VJC895 | SGN → DEL | Apr 30, 21:35 UTC | May 1, 17:45 UTC | 20h 10m |
| 2026-04-30 | VJC895 | SGN → DEL | Apr 30, 21:10 UTC | May 1, 17:45 UTC | 20h 35m |
| 2026-04-30 | VJC895 | SGN → DEL | Apr 30, 18:20 UTC | May 1, 17:30 UTC | 23h 10m |
| 2026-04-30 | VJC82 | MEL → SGN | Apr 30, 14:35 UTC | May 1, 13:30 UTC | 22h 55m |
| 2026-04-29 | VJC81 | SGN → MEL | Apr 29, 17:35 UTC | Apr 30, 12:55 UTC | 19h 20m |
| 2026-04-29 | VJC81 | SGN → MEL | Apr 29, 13:50 UTC | Apr 30, 12:55 UTC | 23h 5m |
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-A811 page for operator, model, and routing details .