sensors Mode-S transponder
8880DC
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A658 · AIRBUS A-320
- Hex
- 8880DC
- Octal
- 42100334
- Decimal
- 8,945,884
- Country
- VN
- Tail
- VN-A658
- Type
- A320
- Flights observed
- 63
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 45m ago
Last known position
Country allocation
The ICAO 24-bit address 8880DC 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 |
|---|---|---|---|
| VJC801 | VietJet Air | 10 | 2026-05-28 |
| VJC802 | VietJet Air | 7 | 2026-05-28 |
| VJC3948 | VietJet Air | 5 | 2026-05-26 |
| VJC3949 | VietJet Air | 3 | 2026-05-25 |
| VJC904 | VietJet Air | 2 | 2026-05-03 |
| VJC903 | VietJet Air | 2 | 2026-05-03 |
| VJC806 | VietJet Air | 2 | 2026-05-10 |
| VJC805 | VietJet Air | 2 | 2026-05-10 |
| VJC384 | VietJet Air | 2 | 2026-04-23 |
| VJC906 | VietJet Air | 1 | 2026-05-03 |
| VJC905 | VietJet Air | 1 | 2026-05-03 |
| VJC808 | VietJet Air | 1 | 2026-04-21 |
| VJC771 | VietJet Air | 1 | 2026-05-31 |
| VJC7239 | VietJet Air | 1 | 2026-06-01 |
| VJC648 | VietJet Air | 1 | 2026-04-26 |
| VJC568 | VietJet Air | 1 | 2026-06-01 |
| VJC567 | VietJet Air | 1 | 2026-06-01 |
| VJC566 | VietJet Air | 1 | 2026-06-01 |
| VJC565 | VietJet Air | 1 | 2026-06-01 |
| VJC530 | VietJet Air | 1 | 2026-05-31 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VJC1527 | - | Jun 2, 15:05 UTC | Jun 3, 01:00 UTC | 9h 55m |
| 2026-06-02 | VJC468 | VCA → HAN | Jun 2, 12:15 UTC | Jun 2, 12:30 UTC | 15m |
| 2026-06-02 | VJC467 | HAN → VCA | Jun 2, 07:50 UTC | Jun 2, 08:20 UTC | 30m |
| 2026-06-02 | VJC134 | SGN → HAN | Jun 2, 06:15 UTC | Jun 2, 06:30 UTC | 15m |
| 2026-06-02 | VJC127 | HAN → SGN | Jun 2, 01:25 UTC | Jun 2, 01:40 UTC | 15m |
| 2026-06-01 | VJC7239 | PVG → HAN | Jun 1, 14:35 UTC | Jun 1, 21:20 UTC | 6h 45m |
| 2026-06-01 | VJC568 | HUI → HAN | Jun 1, 11:35 UTC | Jun 1, 11:55 UTC | 20m |
| 2026-06-01 | VJC567 | HAN → HUI | Jun 1, 09:15 UTC | Jun 1, 09:50 UTC | 35m |
| 2026-06-01 | VJC566 | HUI → HAN | Jun 1, 07:05 UTC | Jun 1, 07:30 UTC | 25m |
| 2026-06-01 | VJC565 | HAN → HUI | Jun 1, 04:50 UTC | Jun 1, 05:20 UTC | 30m |
| 2026-05-31 | VJC771 | HAN → CXR | May 31, 23:05 UTC | Jun 1, 03:20 UTC | 4h 15m |
| 2026-05-31 | VJC495 | HAN → BMV | May 31, 10:50 UTC | May 31, 14:30 UTC | 3h 40m |
| 2026-05-31 | VJC530 | DAD → HAN | May 31, 09:05 UTC | May 31, 09:30 UTC | 25m |
| 2026-05-30 | VJC168 | SGN → HAN | May 30, 17:45 UTC | May 30, 18:00 UTC | 15m |
| 2026-05-28 | VJC802 | BKK → SGN | May 28, 04:45 UTC | May 28, 05:10 UTC | 25m |
| 2026-05-28 | VJC801 | SGN → BKK | May 28, 02:25 UTC | May 28, 03:05 UTC | 40m |
| 2026-05-26 | VJC3948 | SGN → PKX | May 26, 13:10 UTC | May 26, 19:50 UTC | 6h 40m |
| 2026-05-25 | VJC3949 | PKX → SGN | May 25, 20:15 UTC | May 26, 13:24 UTC | 17h 10m |
| 2026-05-25 | VJC3948 | SGN → PKX | May 25, 13:35 UTC | May 25, 20:30 UTC | 6h 55m |
| 2026-05-15 | VJC802 | BKK → SGN | May 15, 05:00 UTC | May 15, 05:30 UTC | 30m |
| 2026-05-15 | VJC801 | SGN → BKK | May 15, 02:35 UTC | May 15, 03:10 UTC | 35m |
| 2026-05-10 | VJC806 | BKK → SGN | May 10, 13:14 UTC | May 10, 13:44 UTC | 30m |
| 2026-05-10 | VJC805 | SGN → BKK | May 10, 05:04 UTC | May 10, 11:50 UTC | 6h 45m |
| 2026-05-10 | VJC801 | SGN → BKK | May 10, 02:34 UTC | May 10, 03:14 UTC | 40m |
| 2026-05-08 | VJC806 | BKK → SGN | May 8, 13:25 UTC | May 8, 14:00 UTC | 35m |
| 2026-05-08 | VJC805 | SGN → BKK | May 8, 04:49 UTC | May 8, 12:00 UTC | 7h 10m |
| 2026-05-08 | VJC801 | SGN → BKK | May 8, 02:24 UTC | May 8, 02:59 UTC | 35m |
| 2026-05-07 | VJC801 | SGN → BKK | May 7, 05:05 UTC | May 8, 02:59 UTC | 21h 55m |
| 2026-05-07 | VJC802 | BKK → SGN | May 7, 04:50 UTC | May 8, 02:59 UTC | 22h 10m |
| 2026-05-07 | VJC801 | SGN → BKK | May 7, 02:30 UTC | May 7, 03:20 UTC | 50m |
| 2026-05-03 | VJC904 | BKK → HAN | May 3, 12:30 UTC | May 3, 12:55 UTC | 25m |
| 2026-05-03 | VJC903 | HAN → BKK | May 3, 10:15 UTC | May 3, 10:45 UTC | 30m |
| 2026-05-03 | VJC906 | KUL → HAN | May 3, 04:45 UTC | May 3, 04:55 UTC | 10m |
| 2026-05-03 | VJC905 | HAN → KUL | May 3, 03:10 UTC | May 3, 03:20 UTC | 10m |
| 2026-04-30 | VJC904 | BKK → HAN | Apr 30, 11:55 UTC | Apr 30, 12:10 UTC | 15m |
| 2026-04-30 | VJC903 | HAN → BKK | Apr 30, 10:20 UTC | Apr 30, 11:00 UTC | 40m |
| 2026-04-27 | VJC3948 | SGN → PKX | Apr 27, 13:20 UTC | Apr 27, 21:00 UTC | 7h 40m |
| 2026-04-26 | VJC648 | SGN → DAD | Apr 26, 13:35 UTC | Apr 26, 13:45 UTC | 10m |
| 2026-04-24 | VJC464 | VCA → HAN | Apr 24, 06:45 UTC | Apr 24, 06:55 UTC | 10m |
| 2026-04-24 | VJC463 | HAN → VCA | Apr 24, 05:25 UTC | Apr 24, 05:35 UTC | 10m |
| 2026-04-23 | VJC160 | - | Apr 23, 13:50 UTC | Apr 23, 14:05 UTC | 15m |
| 2026-04-23 | VJC384 | SGN → UIH | Apr 23, 10:05 UTC | Apr 23, 10:20 UTC | 15m |
| 2026-04-22 | VJC216 | SGN → VII | Apr 22, 12:00 UTC | Apr 22, 12:10 UTC | 10m |
| 2026-04-22 | VJC308 | SGN → HUI | Apr 22, 07:40 UTC | Apr 22, 07:50 UTC | 10m |
| 2026-04-22 | VJC802 | BKK → SGN | Apr 22, 05:05 UTC | Apr 22, 06:30 UTC | 1h 25m |
| 2026-04-22 | VJC801 | SGN → BKK | Apr 22, 02:10 UTC | Apr 22, 03:25 UTC | 1h 15m |
| 2026-04-21 | VJC3949 | PKX → SGN | Apr 21, 13:25 UTC | Apr 21, 20:30 UTC | 7h 5m |
| 2026-04-21 | VJC3948 | SGN → PKX | Apr 21, 11:30 UTC | Apr 21, 11:40 UTC | 10m |
| 2026-04-21 | VJC808 | HKT → SGN | Apr 21, 02:15 UTC | Apr 21, 06:40 UTC | 4h 25m |
| 2026-04-20 | VJC384 | SGN → UIH | Apr 20, 10:10 UTC | Apr 20, 10:20 UTC | 10m |
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-A658 page for operator, model, and routing details .