sensors Mode-S transponder
8881DE
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A817 · AIRBUS A-330-300
- Hex
- 8881DE
- Octal
- 42100736
- Decimal
- 8,946,142
- Country
- VN
- Tail
- VN-A817
- Type
- A333
- Flights observed
- 136
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 45m ago
Last known position
Country allocation
The ICAO 24-bit address 8881DE 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 |
|---|---|---|---|
| VJC85 | - | 20 | 2026-07-17 |
| VJC56 | - | 18 | 2026-06-28 |
| VJC5060 | - | 11 | 2026-07-07 |
| VJC5061 | - | 10 | 2026-07-06 |
| VJC5805 | - | 9 | 2026-07-02 |
| VJC2873 | - | 8 | 2026-07-02 |
| VJC55 | - | 6 | 2026-07-04 |
| VJC86 | - | 5 | 2026-07-18 |
| VJC5806 | - | 5 | 2026-07-03 |
| VJC8931 | - | 4 | 2026-06-13 |
| VJC2872 | - | 4 | 2026-07-02 |
| VJC896 | VietJet Air | 3 | 2026-05-08 |
| VJC895 | VietJet Air | 3 | 2026-05-08 |
| VJC8932 | - | 3 | 2026-06-13 |
| VJC82 | VietJet Air | 3 | 2026-05-09 |
| VJC81 | VietJet Air | 3 | 2026-05-01 |
| VJC8923 | - | 2 | 2026-06-19 |
| VJC8911 | - | 2 | 2026-06-20 |
| VJC8910 | - | 2 | 2026-06-19 |
| VJC67 | - | 2 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | VJC86 | - | Jul 18, 00:39 UTC | Jul 18, 07:30 UTC | 6h 51m |
| 2026-07-17 | VJC85 | - | Jul 17, 04:25 UTC | Jul 17, 22:15 UTC | 17h 50m |
| 2026-07-17 | VJC85 | SYD → SYD | Jul 17, 00:35 UTC | Jul 17, 22:15 UTC | 21h 40m |
| 2026-07-16 | VJC85 | - | Jul 16, 07:45 UTC | Jul 16, 22:45 UTC | 15h 0m |
| 2026-07-16 | VJC85 | - | Jul 16, 01:35 UTC | Jul 16, 22:45 UTC | 21h 10m |
| 2026-07-16 | VJC85 | SYD → SYD | Jul 16, 01:20 UTC | Jul 16, 22:45 UTC | 21h 25m |
| 2026-07-15 | VJC85 | - | Jul 15, 04:25 UTC | Jul 15, 22:15 UTC | 17h 50m |
| 2026-07-15 | VJC85 | SYD → SYD | Jul 15, 00:30 UTC | Jul 15, 22:15 UTC | 21h 45m |
| 2026-07-14 | VJC85 | - | Jul 14, 04:45 UTC | Jul 14, 21:50 UTC | 17h 5m |
| 2026-07-14 | VJC85 | SYD → SYD | Jul 14, 00:40 UTC | Jul 14, 21:50 UTC | 21h 10m |
| 2026-07-13 | VJC85 | - | Jul 13, 05:15 UTC | Jul 13, 21:50 UTC | 16h 35m |
| 2026-07-13 | VJC85 | - | Jul 13, 01:35 UTC | Jul 13, 21:50 UTC | 20h 15m |
| 2026-07-13 | VJC86 | SYD → SYD | Jul 13, 01:10 UTC | Jul 13, 21:50 UTC | 20h 40m |
| 2026-07-12 | VJC85 | - | Jul 12, 05:05 UTC | Jul 12, 22:25 UTC | 17h 20m |
| 2026-07-12 | VJC86 | SYD → SYD | Jul 12, 00:50 UTC | Jul 12, 22:25 UTC | 21h 35m |
| 2026-07-11 | VJC85 | - | Jul 11, 04:50 UTC | Jul 11, 21:55 UTC | 17h 5m |
| 2026-07-11 | VJC86 | SYD → SYD | Jul 11, 00:40 UTC | Jul 11, 21:55 UTC | 21h 15m |
| 2026-07-10 | VJC85 | - | Jul 10, 05:20 UTC | Jul 10, 21:40 UTC | 16h 20m |
| 2026-07-10 | VJC85 | - | Jul 10, 01:35 UTC | Jul 10, 21:40 UTC | 20h 5m |
| 2026-07-10 | VJC85 | SYD → SYD | Jul 10, 01:10 UTC | Jul 10, 21:40 UTC | 20h 30m |
| 2026-07-09 | VJC85 | DRW → SYD | Jul 9, 05:40 UTC | Jul 9, 22:00 UTC | 16h 20m |
| 2026-07-09 | VJC85 | - | Jul 9, 01:35 UTC | Jul 9, 22:00 UTC | 20h 25m |
| 2026-07-09 | VJC86 | SYD → SYD | Jul 9, 01:10 UTC | Jul 9, 22:00 UTC | 20h 50m |
| 2026-07-08 | VJC85 | SGN → SYD | Jul 8, 05:20 UTC | Jul 8, 21:00 UTC | 15h 40m |
| 2026-07-08 | VJC85 | SGN → SYD | Jul 8, 00:40 UTC | Jul 8, 21:00 UTC | 20h 20m |
| 2026-07-07 | VJC5060 | - | Jul 7, 03:35 UTC | Jul 7, 21:50 UTC | 18h 15m |
| 2026-07-07 | VJC5060 | - | Jul 7, 03:25 UTC | Jul 7, 21:50 UTC | 18h 25m |
| 2026-07-06 | VJC5061 | - | Jul 6, 22:35 UTC | Jul 7, 21:30 UTC | 22h 55m |
| 2026-07-06 | VJC5060 | - | Jul 6, 13:35 UTC | Jul 6, 19:20 UTC | 5h 45m |
| 2026-07-05 | VJC527 | HAN → DAD | Jul 5, 15:15 UTC | Jul 5, 15:30 UTC | 15m |
| 2026-07-05 | VJC135 | - | Jul 5, 05:00 UTC | Jul 5, 09:45 UTC | 4h 45m |
| 2026-07-05 | VJC504 | DAD → HAN | Jul 5, 03:05 UTC | Jul 5, 03:15 UTC | 10m |
| 2026-07-04 | VJC55 | - | Jul 4, 09:40 UTC | Jul 5, 00:05 UTC | 14h 25m |
| 2026-07-03 | VJC55 | - | Jul 3, 21:45 UTC | Jul 4, 19:10 UTC | 21h 25m |
| 2026-07-03 | VJC55 | - | Jul 3, 17:35 UTC | Jul 4, 15:45 UTC | 22h 10m |
| 2026-07-03 | VJC5806 | - | Jul 3, 17:10 UTC | Jul 4, 15:30 UTC | 22h 20m |
| 2026-07-03 | VJC5806 | - | Jul 3, 04:00 UTC | Jul 3, 22:20 UTC | 18h 20m |
| 2026-07-02 | VJC5805 | - | Jul 2, 19:35 UTC | Jul 3, 17:45 UTC | 22h 10m |
| 2026-07-02 | VJC5805 | - | Jul 2, 15:35 UTC | Jul 3, 09:45 UTC | 18h 10m |
| 2026-07-02 | VJC2873 | - | Jul 2, 15:05 UTC | Jul 3, 09:45 UTC | 18h 40m |
| 2026-07-02 | VJC2873 | - | Jul 2, 07:35 UTC | Jul 3, 04:35 UTC | 21h 0m |
| 2026-07-02 | VJC2872 | - | Jul 2, 02:15 UTC | Jul 2, 20:15 UTC | 18h 0m |
| 2026-07-01 | VJC2872 | - | Jul 1, 05:35 UTC | Jul 2, 02:55 UTC | 21h 20m |
| 2026-07-01 | VJC5061 | - | Jul 1, 05:15 UTC | Jul 2, 02:55 UTC | 21h 40m |
| 2026-07-01 | VJC5061 | - | Jul 1, 00:15 UTC | Jul 1, 05:55 UTC | 5h 40m |
| 2026-06-30 | VJC5060 | - | Jun 30, 03:40 UTC | Jun 30, 21:15 UTC | 17h 35m |
| 2026-06-29 | VJC5061 | - | Jun 29, 22:35 UTC | Jun 30, 21:15 UTC | 22h 41m |
| 2026-06-29 | VJC5060 | - | Jun 29, 00:05 UTC | Jun 29, 19:29 UTC | 19h 25m |
| 2026-06-28 | VJC56 | - | Jun 28, 19:04 UTC | Jun 29, 14:14 UTC | 19h 10m |
| 2026-06-28 | VJC56 | - | Jun 28, 09:30 UTC | Jun 29, 00:44 UTC | 15h 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-A817 page for operator, model, and routing details .