sensors Mode-S transponder
8881C5
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A810 · AIRBUS A-330-300
- Hex
- 8881C5
- Octal
- 42100705
- Decimal
- 8,946,117
- Country
- VN
- Tail
- VN-A810
- Type
- A333
- Flights observed
- 200
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 27m ago
Last known position
Country allocation
The ICAO 24-bit address 8881C5 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 |
|---|---|---|---|
| VJC81 | - | 25 | 2026-07-09 |
| VJC82 | - | 24 | 2026-07-09 |
| VJC85 | VietJet Air | 21 | 2026-07-03 |
| VJC86 | - | 16 | 2026-07-04 |
| VJC84 | - | 15 | 2026-07-13 |
| VJC83 | - | 13 | 2026-07-12 |
| VJC68 | - | 10 | 2026-06-23 |
| VJC5060 | - | 8 | 2026-06-26 |
| VJC55 | - | 7 | 2026-06-21 |
| VJC5061 | - | 6 | 2026-06-27 |
| VJC2831 | - | 6 | 2026-06-17 |
| VJC8924 | - | 5 | 2026-07-10 |
| VJC56 | - | 5 | 2026-06-21 |
| VJC2873 | - | 5 | 2026-06-11 |
| VJC8923 | - | 4 | 2026-07-10 |
| VJC67 | VietJet Air | 4 | 2026-06-18 |
| VJC2832 | - | 4 | 2026-06-17 |
| VJC52 | - | 3 | 2026-06-27 |
| VJC5063 | VietJet Air | 3 | 2026-06-25 |
| VJC5806 | - | 2 | 2026-06-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | VJC771 | - | Jul 14, 03:00 UTC | Jul 14, 03:15 UTC | 15m |
| 2026-07-14 | VJC124 | - | Jul 14, 01:25 UTC | Jul 14, 01:40 UTC | 15m |
| 2026-07-13 | VJC84 | - | Jul 13, 13:55 UTC | Jul 13, 20:55 UTC | 7h 0m |
| 2026-07-12 | VJC83 | - | Jul 12, 18:20 UTC | Jul 13, 11:40 UTC | 17h 20m |
| 2026-07-12 | VJC154 | SGN → HAN | Jul 12, 16:50 UTC | Jul 12, 17:01 UTC | 10m |
| 2026-07-12 | VJC133 | - | Jul 12, 11:55 UTC | Jul 12, 12:05 UTC | 10m |
| 2026-07-12 | VJC129 | - | Jul 12, 05:15 UTC | Jul 12, 05:30 UTC | 15m |
| 2026-07-12 | VJC126 | - | Jul 12, 03:15 UTC | Jul 12, 03:25 UTC | 10m |
| 2026-07-11 | VJC8911 | - | Jul 11, 13:45 UTC | Jul 11, 19:05 UTC | 5h 20m |
| 2026-07-10 | VJC8924 | - | Jul 10, 20:35 UTC | Jul 11, 10:40 UTC | 14h 5m |
| 2026-07-10 | VJC8924 | - | Jul 10, 10:30 UTC | Jul 11, 05:25 UTC | 18h 56m |
| 2026-07-10 | VJC8923 | - | Jul 10, 05:45 UTC | Jul 10, 06:00 UTC | 15m |
| 2026-07-09 | VJC82 | - | Jul 9, 14:40 UTC | Jul 9, 21:50 UTC | 7h 10m |
| 2026-07-09 | VJC81 | - | Jul 9, 06:10 UTC | Jul 9, 12:55 UTC | 6h 45m |
| 2026-07-08 | VJC81 | - | Jul 8, 13:20 UTC | Jul 9, 12:55 UTC | 23h 35m |
| 2026-07-08 | VIC155 | - | Jul 8, 13:00 UTC | Jul 9, 06:40 UTC | 17h 40m |
| 2026-07-08 | VJC144 | - | Jul 8, 10:50 UTC | Jul 8, 11:25 UTC | 35m |
| 2026-07-04 | VJC86 | - | Jul 4, 00:55 UTC | Jul 4, 08:30 UTC | 7h 35m |
| 2026-07-03 | VJC85 | SGN → SYD | Jul 3, 08:10 UTC | Jul 3, 21:25 UTC | 13h 15m |
| 2026-07-03 | VJC85 | SGN → SYD | Jul 3, 01:20 UTC | Jul 3, 21:25 UTC | 20h 5m |
| 2026-07-03 | VJC86 | SYD → SYD | Jul 3, 00:55 UTC | Jul 3, 21:25 UTC | 20h 30m |
| 2026-07-02 | VJC85 | SGN → SYD | Jul 2, 01:20 UTC | Jul 2, 21:00 UTC | 19h 40m |
| 2026-07-02 | VJC86 | SYD → SYD | Jul 2, 01:05 UTC | Jul 2, 21:00 UTC | 19h 55m |
| 2026-07-01 | VJC85 | SGN → SYD | Jul 1, 01:20 UTC | Jul 1, 21:10 UTC | 19h 50m |
| 2026-07-01 | VJC86 | SYD → SYD | Jul 1, 00:50 UTC | Jul 1, 21:10 UTC | 20h 20m |
| 2026-06-30 | VJC85 | SGN → SYD | Jun 30, 01:19 UTC | Jun 30, 21:05 UTC | 19h 46m |
| 2026-06-30 | VJC86 | SYD → SYD | Jun 30, 01:14 UTC | Jun 30, 21:05 UTC | 19h 51m |
| 2026-06-29 | VJC85 | SGN → SYD | Jun 29, 01:20 UTC | Jun 29, 21:30 UTC | 20h 10m |
| 2026-06-29 | VJC86 | SYD → SYD | Jun 29, 01:00 UTC | Jun 29, 21:30 UTC | 20h 30m |
| 2026-06-28 | VJC85 | SGN → SYD | Jun 28, 14:19 UTC | Jun 28, 21:14 UTC | 6h 55m |
| 2026-06-27 | VJC85 | SGN → SYD | Jun 27, 23:34 UTC | Jun 28, 21:14 UTC | 21h 40m |
| 2026-06-27 | VJC52 | - | Jun 27, 10:50 UTC | Jun 28, 00:20 UTC | 13h 30m |
| 2026-06-27 | VJC5061 | - | Jun 27, 02:14 UTC | Jun 28, 00:20 UTC | 22h 5m |
| 2026-06-26 | VJC5061 | - | Jun 26, 21:20 UTC | Jun 27, 11:25 UTC | 14h 5m |
| 2026-06-26 | VJC5060 | - | Jun 26, 12:24 UTC | Jun 26, 18:04 UTC | 5h 40m |
| 2026-06-25 | VJC5060 | - | Jun 25, 21:20 UTC | Jun 26, 18:04 UTC | 20h 45m |
| 2026-06-25 | VJC5060 | - | Jun 25, 20:30 UTC | Jun 26, 18:04 UTC | 21h 35m |
| 2026-06-25 | VJC5063 | KJA → CXR | Jun 25, 07:49 UTC | Jun 25, 21:20 UTC | 13h 30m |
| 2026-06-24 | VJC5063 | KJA → CXR | Jun 24, 23:20 UTC | Jun 25, 21:20 UTC | 22h 0m |
| 2026-06-24 | VJC5063 | KJA → CXR | Jun 24, 23:10 UTC | Jun 25, 21:15 UTC | 22h 5m |
| 2026-06-24 | VJC52 | - | Jun 24, 10:25 UTC | Jun 25, 08:24 UTC | 22h 0m |
| 2026-06-23 | VJC68 | - | Jun 23, 23:19 UTC | Jun 24, 23:14 UTC | 23h 55m |
| 2026-06-23 | VJC68 | - | Jun 23, 14:35 UTC | Jun 24, 10:49 UTC | 20h 15m |
| 2026-06-23 | VJC68 | - | Jun 23, 08:59 UTC | Jun 24, 00:05 UTC | 15h 5m |
| 2026-06-23 | VJC68 | - | Jun 23, 04:29 UTC | Jun 24, 00:05 UTC | 19h 35m |
| 2026-06-22 | VJC5061 | - | Jun 22, 23:20 UTC | Jun 23, 18:50 UTC | 19h 30m |
| 2026-06-22 | VJC5060 | - | Jun 22, 13:54 UTC | Jun 22, 19:29 UTC | 5h 35m |
| 2026-06-21 | VJC5060 | - | Jun 21, 23:30 UTC | Jun 22, 19:29 UTC | 20h 0m |
| 2026-06-21 | VJC56 | - | Jun 21, 18:39 UTC | Jun 22, 14:34 UTC | 19h 55m |
| 2026-06-21 | VJC56 | - | Jun 21, 15:19 UTC | Jun 22, 14:34 UTC | 23h 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-A810 page for operator, model, and routing details .