sensors Mode-S transponder
8880AF
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A689 · AIRBUS A-320
- Hex
- 8880AF
- Octal
- 42100257
- Decimal
- 8,945,839
- Country
- VN
- Tail
- VN-A689
- Type
- A320
- Flights observed
- 31
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 8880AF 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 |
|---|---|---|---|
| VJC977 | VietJet Air | 1 | 2026-05-20 |
| VJC976 | VietJet Air | 1 | 2026-05-20 |
| VJC906 | VietJet Air | 1 | 2026-05-26 |
| VJC905 | VietJet Air | 1 | 2026-05-26 |
| VJC902 | VietJet Air | 1 | 2026-06-01 |
| VJC901 | VietJet Air | 1 | 2026-06-01 |
| VJC827 | VietJet Air | 1 | 2026-05-01 |
| VJC824 | VietJet Air | 1 | 2026-05-01 |
| VJC814 | VietJet Air | 1 | 2026-04-15 |
| VJC802 | VietJet Air | 1 | 2026-04-26 |
| VJC801 | VietJet Air | 1 | 2026-04-26 |
| VJC7712 | VietJet Air | 1 | 2026-06-01 |
| VJC767 | VietJet Air | 1 | 2026-05-31 |
| VJC463 | VietJet Air | 1 | 2026-04-20 |
| VJC434 | VietJet Air | 1 | 2026-06-02 |
| VJC433 | VietJet Air | 1 | 2026-06-02 |
| VJC3948 | VietJet Air | 1 | 2026-04-30 |
| VJC387 | VietJet Air | 1 | 2026-04-26 |
| VJC386 | VietJet Air | 1 | 2026-04-26 |
| VJC384 | VietJet Air | 1 | 2026-04-18 |
Recent flights last 31
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VJC161 | - | Jun 2, 14:10 UTC | Jun 2, 14:40 UTC | 30m |
| 2026-06-02 | VJC434 | UIH → HAN | Jun 2, 09:45 UTC | Jun 2, 10:05 UTC | 20m |
| 2026-06-02 | VJC433 | HAN → UIH | Jun 2, 06:50 UTC | Jun 2, 07:20 UTC | 30m |
| 2026-06-02 | VJC198 | SGN → HAN | Jun 2, 05:30 UTC | Jun 2, 05:45 UTC | 15m |
| 2026-06-02 | VJC197 | - | Jun 2, 00:40 UTC | Jun 2, 00:55 UTC | 15m |
| 2026-06-01 | VJC7712 | HAN → PKX | Jun 1, 13:15 UTC | Jun 1, 13:40 UTC | 25m |
| 2026-06-01 | VJC902 | BKK → HAN | Jun 1, 07:15 UTC | Jun 1, 08:05 UTC | 50m |
| 2026-06-01 | VJC901 | HAN → BKK | Jun 1, 04:25 UTC | Jun 1, 06:00 UTC | 1h 35m |
| 2026-05-31 | VJC194 | SGN → HAN | May 31, 15:50 UTC | May 31, 16:00 UTC | 10m |
| 2026-05-31 | VJC767 | HPH → PQC | May 31, 09:15 UTC | May 31, 09:45 UTC | 30m |
| 2026-05-31 | VJC124 | SGN → HAN | May 31, 00:30 UTC | May 31, 00:40 UTC | 10m |
| 2026-05-26 | VJC906 | KUL → HAN | May 26, 04:50 UTC | May 26, 05:00 UTC | 10m |
| 2026-05-26 | VJC905 | HAN → KUL | May 26, 03:15 UTC | May 26, 03:45 UTC | 30m |
| 2026-05-20 | VJC977 | ICN → PQC | May 20, 20:10 UTC | May 20, 23:05 UTC | 2h 55m |
| 2026-05-20 | VJC976 | PQC → ICN | May 20, 16:00 UTC | May 20, 19:00 UTC | 3h 0m |
| 2026-05-01 | VJC824 | KUL → DAD | May 1, 06:50 UTC | May 1, 07:00 UTC | 10m |
| 2026-05-01 | VJC827 | DAD → KUL | May 1, 05:15 UTC | May 1, 05:40 UTC | 25m |
| 2026-04-30 | VJC3948 | SGN → PKX | Apr 30, 13:15 UTC | Apr 30, 20:45 UTC | 7h 30m |
| 2026-04-26 | VJC387 | UIH → SGN | Apr 26, 10:05 UTC | Apr 26, 10:15 UTC | 10m |
| 2026-04-26 | VJC386 | SGN → UIH | Apr 26, 07:50 UTC | Apr 26, 08:00 UTC | 10m |
| 2026-04-26 | VJC802 | BKK → SGN | Apr 26, 04:50 UTC | Apr 26, 06:00 UTC | 1h 10m |
| 2026-04-26 | VJC801 | SGN → BKK | Apr 26, 02:30 UTC | Apr 26, 03:20 UTC | 50m |
| 2026-04-25 | VJC328 | PQC → SGN | Apr 25, 13:55 UTC | Apr 25, 14:20 UTC | 25m |
| 2026-04-25 | VJC331 | SGN → PQC | Apr 25, 12:05 UTC | Apr 25, 12:15 UTC | 10m |
| 2026-04-25 | VJC330 | PQC → SGN | Apr 25, 04:35 UTC | Apr 25, 04:55 UTC | 20m |
| 2026-04-25 | VJC321 | SGN → PQC | Apr 25, 02:45 UTC | Apr 25, 02:55 UTC | 10m |
| 2026-04-20 | VJC463 | HAN → VCA | Apr 20, 05:15 UTC | Apr 20, 05:25 UTC | 10m |
| 2026-04-18 | VJC384 | SGN → UIH | Apr 18, 09:50 UTC | Apr 18, 10:00 UTC | 10m |
| 2026-04-17 | VJC376 | - | Apr 17, 12:00 UTC | Apr 17, 12:10 UTC | 10m |
| 2026-04-17 | VJC308 | SGN → HUI | Apr 17, 07:55 UTC | Apr 17, 08:05 UTC | 10m |
| 2026-04-15 | VJC814 | SIN → SGN | Apr 15, 10:15 UTC | Apr 15, 10:35 UTC | 20m |
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-A689 page for operator, model, and routing details .