sensors Mode-S transponder
8881DB
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A814 · AIRBUS A-330-300
- Hex
- 8881DB
- Octal
- 42100733
- Decimal
- 8,946,139
- Country
- VN
- Tail
- VN-A814
- Type
- A333
- Flights observed
- 87
- Distinct callsigns
- 18
- Country
- VN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 8881DB 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VJC86 | VietJet Air | 13 | 2026-06-01 |
| VJC85 | VietJet Air | 9 | 2026-05-31 |
| VJC896 | VietJet Air | 8 | 2026-05-04 |
| VJC895 | VietJet Air | 8 | 2026-05-04 |
| VJC81 | VietJet Air | 8 | 2026-04-28 |
| VJC971 | VietJet Air | 7 | 2026-05-12 |
| VJC82 | VietJet Air | 7 | 2026-04-29 |
| VJC84 | VietJet Air | 4 | 2026-05-11 |
| VJC5805 | - | 4 | 2026-05-24 |
| VJC63 | - | 3 | 2026-05-13 |
| VJC5060 | - | 3 | 2026-05-29 |
| VJC972 | VietJet Air | 2 | 2026-05-12 |
| VJC83 | VietJet Air | 2 | 2026-05-11 |
| VJC68 | VietJet Air | 2 | 2026-05-07 |
| VJC5806 | - | 2 | 2026-05-25 |
| VJC5063 | VietJet Air | 2 | 2026-05-28 |
| VJC5061 | - | 2 | 2026-05-29 |
| VJC67 | VietJet Air | 1 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | VJC86 | SYD → SGN | Jun 1, 00:45 UTC | Jun 1, 07:55 UTC | 7h 10m |
| 2026-05-31 | VJC85 | SGN → SYD | May 31, 14:45 UTC | May 31, 21:50 UTC | 7h 5m |
| 2026-05-29 | VJC5061 | - | May 29, 21:15 UTC | May 30, 02:50 UTC | 5h 35m |
| 2026-05-29 | VJC5060 | - | May 29, 12:35 UTC | May 29, 18:15 UTC | 5h 41m |
| 2026-05-28 | VJC5063 | KJA → CXR | May 28, 18:45 UTC | May 29, 13:05 UTC | 18h 20m |
| 2026-05-28 | VJC5063 | KJA → CXR | May 28, 05:25 UTC | May 28, 19:20 UTC | 13h 55m |
| 2026-05-25 | VJC5806 | - | May 25, 16:40 UTC | May 25, 17:00 UTC | 20m |
| 2026-05-25 | VJC5806 | - | May 25, 14:20 UTC | May 25, 14:35 UTC | 15m |
| 2026-05-24 | VJC5805 | - | May 24, 16:10 UTC | May 25, 10:05 UTC | 17h 55m |
| 2026-05-24 | VJC5805 | - | May 24, 12:50 UTC | May 25, 10:05 UTC | 21h 15m |
| 2026-05-22 | VJC5805 | - | May 22, 08:45 UTC | May 22, 15:25 UTC | 6h 40m |
| 2026-05-18 | VJC5805 | - | May 18, 06:45 UTC | May 18, 15:15 UTC | 8h 30m |
| 2026-05-15 | VJC5060 | - | May 15, 17:35 UTC | May 15, 22:00 UTC | 4h 25m |
| 2026-05-13 | VJC63 | - | May 13, 08:15 UTC | May 13, 18:35 UTC | 10h 20m |
| 2026-05-12 | VJC63 | - | May 12, 20:50 UTC | May 13, 18:35 UTC | 21h 45m |
| 2026-05-12 | VJC972 | DEL → HAN | May 12, 18:50 UTC | May 13, 18:35 UTC | 23h 45m |
| 2026-05-12 | VJC971 | HAN → DEL | May 12, 13:51 UTC | May 12, 17:25 UTC | 3h 35m |
| 2026-05-11 | VJC971 | HAN → DEL | May 11, 20:50 UTC | May 12, 17:25 UTC | 20h 35m |
| 2026-05-11 | VJC971 | HAN → DEL | May 11, 20:30 UTC | May 12, 17:25 UTC | 20h 55m |
| 2026-05-11 | VJC971 | HAN → DEL | May 11, 17:35 UTC | May 12, 16:45 UTC | 23h 10m |
| 2026-05-11 | VJC84 | BNE → SGN | May 11, 13:45 UTC | May 11, 20:55 UTC | 7h 11m |
| 2026-05-11 | VJC83 | SGN → BNE | May 11, 04:45 UTC | May 11, 11:05 UTC | 6h 20m |
| 2026-05-09 | VJC972 | DEL → HAN | May 9, 18:50 UTC | May 9, 21:40 UTC | 2h 50m |
| 2026-05-09 | VJC971 | HAN → DEL | May 9, 13:40 UTC | May 9, 17:15 UTC | 3h 35m |
| 2026-05-08 | VJC971 | HAN → DEL | May 8, 21:50 UTC | May 9, 17:15 UTC | 19h 25m |
| 2026-05-08 | VJC971 | HAN → DEL | May 8, 17:55 UTC | May 9, 16:45 UTC | 22h 50m |
| 2026-05-07 | VJC68 | NQZ → CXR | May 7, 12:55 UTC | May 7, 17:15 UTC | 4h 20m |
| 2026-05-06 | VJC68 | NQZ → CXR | May 6, 20:50 UTC | May 7, 17:15 UTC | 20h 25m |
| 2026-05-06 | VJC84 | BNE → SGN | May 6, 20:30 UTC | May 7, 17:15 UTC | 20h 45m |
| 2026-05-06 | VJC84 | BNE → SGN | May 6, 17:30 UTC | May 7, 13:25 UTC | 19h 55m |
| 2026-05-06 | VJC84 | BNE → SGN | May 6, 13:35 UTC | May 6, 21:10 UTC | 7h 34m |
| 2026-05-06 | VJC83 | SGN → BNE | May 6, 04:40 UTC | May 6, 11:05 UTC | 6h 25m |
| 2026-05-04 | VJC896 | DEL → SGN | May 4, 19:40 UTC | May 4, 23:30 UTC | 3h 50m |
| 2026-05-04 | VJC895 | SGN → DEL | May 4, 13:15 UTC | May 4, 17:55 UTC | 4h 40m |
| 2026-05-03 | VJC895 | SGN → DEL | May 3, 16:20 UTC | May 4, 14:45 UTC | 22h 25m |
| 2026-05-03 | VJC67 | CXR → NQZ | May 3, 12:45 UTC | May 3, 16:45 UTC | 4h 0m |
| 2026-05-01 | VJC5061 | - | May 1, 21:15 UTC | May 1, 21:50 UTC | 35m |
| 2026-05-01 | VJC5060 | - | May 1, 17:45 UTC | May 1, 18:15 UTC | 30m |
| 2026-04-29 | VJC82 | MEL → SGN | Apr 29, 14:45 UTC | Apr 29, 22:00 UTC | 7h 15m |
| 2026-04-28 | VJC81 | SGN → MEL | Apr 28, 21:05 UTC | Apr 29, 12:50 UTC | 15h 46m |
| 2026-04-28 | VJC81 | SGN → MEL | Apr 28, 18:25 UTC | Apr 29, 12:50 UTC | 18h 25m |
| 2026-04-28 | VJC81 | SGN → MEL | Apr 28, 14:50 UTC | Apr 29, 12:50 UTC | 22h 1m |
| 2026-04-28 | VJC82 | MEL → SGN | Apr 28, 14:35 UTC | Apr 29, 12:45 UTC | 22h 11m |
| 2026-04-27 | VJC81 | SGN → MEL | Apr 27, 18:15 UTC | Apr 28, 12:40 UTC | 18h 25m |
| 2026-04-27 | VJC81 | SGN → MEL | Apr 27, 14:50 UTC | Apr 28, 12:40 UTC | 21h 50m |
| 2026-04-27 | VJC82 | MEL → SGN | Apr 27, 14:40 UTC | Apr 28, 12:40 UTC | 22h 0m |
| 2026-04-27 | VJC81 | SGN → MEL | Apr 27, 05:40 UTC | Apr 27, 12:40 UTC | 7h 0m |
| 2026-04-25 | VJC63 | - | Apr 25, 08:40 UTC | Apr 26, 01:55 UTC | 17h 15m |
| 2026-04-24 | VJC82 | MEL → SGN | Apr 24, 22:30 UTC | Apr 24, 22:50 UTC | 20m |
| 2026-04-24 | VJC82 | MEL → SGN | Apr 24, 14:35 UTC | Apr 24, 21:30 UTC | 6h 55m |
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-A814 page for operator, model, and routing details .