sensors Mode-S transponder
8880EA
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A655 · AIRBUS A-320
- Hex
- 8880EA
- Octal
- 42100352
- Decimal
- 8,945,898
- Country
- VN
- Tail
- VN-A655
- Type
- A320
- Flights observed
- 59
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 8880EA 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 | 9 | 2026-05-24 |
| VJC802 | VietJet Air | 5 | 2026-05-24 |
| VJC827 | VietJet Air | 4 | 2026-05-29 |
| VJC824 | VietJet Air | 3 | 2026-05-29 |
| VJC3948 | VietJet Air | 3 | 2026-05-12 |
| VJC1981 | VietJet Air | 3 | 2026-06-02 |
| VJC806 | VietJet Air | 2 | 2026-04-25 |
| VJC805 | VietJet Air | 2 | 2026-04-25 |
| VJC1980 | VietJet Air | 2 | 2026-06-01 |
| VJC977 | VietJet Air | 1 | 2026-05-21 |
| VJC976 | VietJet Air | 1 | 2026-05-21 |
| VJC953 | VietJet Air | 1 | 2026-05-17 |
| VJC952 | VietJet Air | 1 | 2026-05-17 |
| VJC7853 | - | 1 | 2026-05-02 |
| VJC644 | VietJet Air | 1 | 2026-04-26 |
| VJC520 | - | 1 | 2026-05-27 |
| VJC517 | VietJet Air | 1 | 2026-05-27 |
| VJC509 | VietJet Air | 1 | 2026-05-30 |
| VJC465 | VietJet Air | 1 | 2026-06-02 |
| VJC431 | VietJet Air | 1 | 2026-05-31 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VJC465 | HAN → VCA | Jun 2, 10:15 UTC | Jun 2, 15:10 UTC | 4h 55m |
| 2026-06-02 | VJC1981 | FSZ → HAN | Jun 2, 07:35 UTC | Jun 2, 07:45 UTC | 10m |
| 2026-06-02 | VJC1981 | FSZ → HAN | Jun 2, 03:05 UTC | Jun 2, 04:10 UTC | 1h 5m |
| 2026-06-01 | VJC1980 | HAN → FSZ | Jun 1, 19:40 UTC | Jun 2, 00:10 UTC | 4h 30m |
| 2026-06-01 | VJC1785 | HAN → CXR | Jun 1, 13:20 UTC | Jun 1, 17:10 UTC | 3h 50m |
| 2026-06-01 | VJC423 | HAN → PXU | Jun 1, 08:25 UTC | Jun 1, 11:25 UTC | 3h 0m |
| 2026-06-01 | VJC1436 | UIH → HAN | Jun 1, 06:35 UTC | Jun 1, 06:55 UTC | 20m |
| 2026-06-01 | VJC1437 | HAN → UIH | Jun 1, 03:40 UTC | Jun 1, 04:00 UTC | 20m |
| 2026-05-31 | VJC431 | HAN → UIH | May 31, 23:20 UTC | Jun 1, 02:35 UTC | 3h 15m |
| 2026-05-31 | VJC1128 | SGN → HAN | May 31, 17:00 UTC | May 31, 17:20 UTC | 20m |
| 2026-05-30 | VJC509 | HAN → DAD | May 30, 06:20 UTC | May 30, 06:55 UTC | 35m |
| 2026-05-30 | VJC1435 | HAN → UIH | May 30, 02:00 UTC | May 30, 05:15 UTC | 3h 15m |
| 2026-05-30 | VJC1508 | DAD → HAN | May 30, 00:45 UTC | May 30, 01:00 UTC | 15m |
| 2026-05-29 | VJC824 | KUL → DAD | May 29, 07:05 UTC | May 29, 07:15 UTC | 10m |
| 2026-05-29 | VJC827 | DAD → KUL | May 29, 05:15 UTC | May 29, 05:40 UTC | 25m |
| 2026-05-28 | VJC827 | DAD → KUL | May 28, 06:35 UTC | May 29, 05:40 UTC | 23h 5m |
| 2026-05-28 | VJC125 | HAN → SGN | May 28, 00:40 UTC | May 28, 05:25 UTC | 4h 45m |
| 2026-05-27 | VJC520 | - | May 27, 14:20 UTC | May 27, 15:00 UTC | 40m |
| 2026-05-27 | VJC517 | HAN → DAD | May 27, 11:15 UTC | May 27, 11:35 UTC | 20m |
| 2026-05-24 | VJC802 | BKK → SGN | May 24, 04:50 UTC | May 24, 05:25 UTC | 35m |
| 2026-05-24 | VJC801 | SGN → BKK | May 24, 02:40 UTC | May 24, 03:10 UTC | 30m |
| 2026-05-21 | VJC977 | ICN → PQC | May 21, 20:20 UTC | May 21, 23:10 UTC | 2h 50m |
| 2026-05-21 | VJC976 | PQC → ICN | May 21, 04:45 UTC | May 21, 18:55 UTC | 14h 10m |
| 2026-05-21 | VJC801 | SGN → BKK | May 21, 02:25 UTC | May 21, 03:15 UTC | 50m |
| 2026-05-17 | VJC953 | HIJ → HAN | May 17, 05:25 UTC | May 17, 05:50 UTC | 25m |
| 2026-05-17 | VJC952 | HAN → HIJ | May 17, 03:25 UTC | May 17, 04:05 UTC | 40m |
| 2026-05-12 | VJC3948 | SGN → PKX | May 12, 13:25 UTC | May 12, 20:10 UTC | 6h 45m |
| 2026-05-03 | VJC1981 | FSZ → HAN | May 3, 01:50 UTC | May 3, 03:05 UTC | 1h 15m |
| 2026-05-02 | VJC1980 | HAN → FSZ | May 2, 12:15 UTC | May 3, 00:01 UTC | 11h 45m |
| 2026-05-02 | VJC7853 | - | May 2, 00:55 UTC | May 2, 10:40 UTC | 9h 45m |
| 2026-05-01 | VJC3884 | - | May 1, 20:00 UTC | May 1, 23:00 UTC | 3h 0m |
| 2026-04-30 | VJC802 | BKK → SGN | Apr 30, 05:05 UTC | Apr 30, 05:40 UTC | 35m |
| 2026-04-29 | VJC801 | SGN → BKK | Apr 29, 14:00 UTC | Apr 30, 03:10 UTC | 13h 9m |
| 2026-04-29 | VJC801 | SGN → BKK | Apr 29, 04:44 UTC | Apr 30, 03:10 UTC | 22h 25m |
| 2026-04-28 | VJC801 | SGN → BKK | Apr 28, 13:15 UTC | Apr 29, 03:04 UTC | 13h 50m |
| 2026-04-26 | VJC644 | SGN → DAD | Apr 26, 12:35 UTC | Apr 26, 12:45 UTC | 10m |
| 2026-04-26 | VJC1243 | THD → SGN | Apr 26, 03:50 UTC | Apr 26, 04:10 UTC | 20m |
| 2026-04-25 | VJC806 | BKK → SGN | Apr 25, 13:15 UTC | Apr 25, 14:25 UTC | 1h 10m |
| 2026-04-25 | VJC805 | SGN → BKK | Apr 25, 11:00 UTC | Apr 25, 12:10 UTC | 1h 10m |
| 2026-04-25 | VJC241 | THD → SGN | Apr 25, 04:00 UTC | Apr 25, 04:10 UTC | 10m |
| 2026-04-24 | VJC806 | BKK → SGN | Apr 24, 13:15 UTC | Apr 24, 14:25 UTC | 1h 10m |
| 2026-04-24 | VJC805 | SGN → BKK | Apr 24, 10:30 UTC | Apr 24, 11:55 UTC | 1h 25m |
| 2026-04-24 | VJC246 | SGN → THD | Apr 24, 05:05 UTC | Apr 24, 05:15 UTC | 10m |
| 2026-04-23 | VJC3948 | SGN → PKX | Apr 23, 13:35 UTC | Apr 23, 20:55 UTC | 7h 19m |
| 2026-04-23 | VJC3948 | SGN → PKX | Apr 23, 11:40 UTC | Apr 23, 11:55 UTC | 15m |
| 2026-04-22 | VJC133 | HAN → SGN | Apr 22, 06:35 UTC | Apr 22, 06:45 UTC | 10m |
| 2026-04-22 | VJC130 | SGN → HAN | Apr 22, 02:00 UTC | Apr 22, 02:25 UTC | 25m |
| 2026-04-19 | VJC824 | KUL → DAD | Apr 19, 08:05 UTC | Apr 19, 08:20 UTC | 15m |
| 2026-04-19 | VJC824 | KUL → DAD | Apr 19, 06:55 UTC | Apr 19, 07:05 UTC | 10m |
| 2026-04-19 | VJC827 | DAD → KUL | Apr 19, 05:25 UTC | Apr 19, 05:55 UTC | 30m |
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-A655 page for operator, model, and routing details .