sensors Mode-S transponder
88803E
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A683 · AIRBUS A-321
- Hex
- 88803E
- Octal
- 42100076
- Decimal
- 8,945,726
- Country
- VN
- Tail
- VN-A683
- Type
- A321
- Flights observed
- 91
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 88803E 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 |
|---|---|---|---|
| VJC949 | VietJet Air | 6 | 2026-05-24 |
| VJC960 | VietJet Air | 5 | 2026-05-27 |
| VJC948 | VietJet Air | 5 | 2026-05-24 |
| VJC814 | VietJet Air | 5 | 2026-04-26 |
| VJC8021 | - | 5 | 2026-05-29 |
| VJC8020 | VietJet Air | 5 | 2026-05-29 |
| VJC989 | VietJet Air | 4 | 2026-05-28 |
| VJC961 | VietJet Air | 4 | 2026-05-28 |
| VJC959 | VietJet Air | 4 | 2026-05-26 |
| VJC926 | VietJet Air | 4 | 2026-05-11 |
| VJC858 | VietJet Air | 3 | 2026-05-18 |
| VJC988 | VietJet Air | 2 | 2026-04-23 |
| VJC902 | VietJet Air | 2 | 2026-05-27 |
| VJC901 | VietJet Air | 2 | 2026-05-27 |
| VJC859 | VietJet Air | 2 | 2026-05-18 |
| VJC855 | VietJet Air | 2 | 2026-04-20 |
| VJC854 | VietJet Air | 2 | 2026-04-20 |
| VJC813 | VietJet Air | 2 | 2026-04-21 |
| VJC7527 | VietJet Air | 2 | 2026-05-16 |
| VJC973 | VietJet Air | 1 | 2026-04-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | VJC8021 | - | May 29, 19:55 UTC | May 29, 20:25 UTC | 30m |
| 2026-05-29 | VJC8020 | DAD → MNL | May 29, 11:40 UTC | May 29, 18:30 UTC | 6h 50m |
| 2026-05-28 | VJC989 | PUS → DAD | May 28, 19:00 UTC | May 29, 01:40 UTC | 6h 40m |
| 2026-05-28 | VJC517 | HAN → DAD | May 28, 11:10 UTC | May 28, 11:25 UTC | 15m |
| 2026-05-28 | VJC961 | ICN → HAN | May 28, 02:10 UTC | May 28, 06:00 UTC | 3h 50m |
| 2026-05-27 | VJC960 | HAN → ICN | May 27, 22:35 UTC | May 27, 23:00 UTC | 25m |
| 2026-05-27 | VJC960 | HAN → ICN | May 27, 19:05 UTC | May 27, 19:25 UTC | 20m |
| 2026-05-27 | VJC496 | - | May 27, 11:05 UTC | May 27, 15:25 UTC | 4h 20m |
| 2026-05-27 | VJC902 | BKK → HAN | May 27, 07:20 UTC | May 27, 08:15 UTC | 55m |
| 2026-05-27 | VJC901 | HAN → BKK | May 27, 04:49 UTC | May 27, 05:49 UTC | 1h 0m |
| 2026-05-26 | VJC959 | FUK → HAN | May 26, 00:24 UTC | May 26, 00:35 UTC | 10m |
| 2026-05-24 | VJC963 | ICN → HAN | May 24, 21:40 UTC | May 24, 21:45 UTC | 5m |
| 2026-05-24 | VJC949 | RMQ → HAN | May 24, 10:15 UTC | May 24, 20:25 UTC | 10h 10m |
| 2026-05-24 | VJC948 | HAN → RMQ | May 24, 07:45 UTC | May 24, 09:05 UTC | 1h 20m |
| 2026-05-22 | VJC961 | ICN → HAN | May 22, 02:15 UTC | May 22, 02:40 UTC | 25m |
| 2026-05-21 | VJC960 | HAN → ICN | May 21, 10:10 UTC | May 21, 22:35 UTC | 12h 25m |
| 2026-05-20 | VJC8021 | - | May 20, 20:20 UTC | May 20, 20:55 UTC | 35m |
| 2026-05-20 | VJC8020 | DAD → MNL | May 20, 18:05 UTC | May 20, 18:50 UTC | 45m |
| 2026-05-19 | VJC8021 | - | May 19, 20:10 UTC | May 20, 18:50 UTC | 22h 41m |
| 2026-05-19 | VJC8020 | DAD → MNL | May 19, 08:05 UTC | May 19, 18:20 UTC | 10h 15m |
| 2026-05-18 | VJC8020 | DAD → MNL | May 18, 19:35 UTC | May 19, 18:20 UTC | 22h 45m |
| 2026-05-18 | VJC859 | MNL → SGN | May 18, 19:25 UTC | May 19, 08:30 UTC | 13h 5m |
| 2026-05-18 | VJC858 | SGN → MNL | May 18, 17:35 UTC | May 18, 18:15 UTC | 40m |
| 2026-05-16 | VJC7527 | CAN → HAN | May 16, 18:35 UTC | May 16, 18:45 UTC | 10m |
| 2026-05-16 | VJC949 | RMQ → HAN | May 16, 10:50 UTC | May 16, 11:55 UTC | 1h 5m |
| 2026-05-16 | VJC948 | HAN → RMQ | May 16, 08:31 UTC | May 16, 09:40 UTC | 1h 10m |
| 2026-05-16 | VJC959 | FUK → HAN | May 16, 00:35 UTC | May 16, 00:45 UTC | 10m |
| 2026-05-15 | VJC943 | TPE → HAN | May 15, 12:25 UTC | May 15, 13:40 UTC | 1h 15m |
| 2026-05-15 | VJC942 | HAN → TPE | May 15, 08:40 UTC | May 15, 10:25 UTC | 1h 45m |
| 2026-05-11 | VJC926 | HPH → ICN | May 11, 20:20 UTC | May 11, 21:00 UTC | 40m |
| 2026-05-10 | VJC7078 | - | May 10, 06:45 UTC | May 10, 06:55 UTC | 10m |
| 2026-05-09 | VJC925 | ICN → HPH | May 9, 22:30 UTC | May 10, 01:24 UTC | 2h 55m |
| 2026-05-09 | VJC926 | HPH → ICN | May 9, 20:10 UTC | May 9, 20:49 UTC | 40m |
| 2026-05-08 | VJC926 | HPH → ICN | May 8, 22:15 UTC | May 9, 20:49 UTC | 22h 35m |
| 2026-05-08 | VJC926 | HPH → ICN | May 8, 20:10 UTC | May 8, 20:50 UTC | 40m |
| 2026-05-05 | VJC7527 | CAN → HAN | May 5, 18:50 UTC | May 5, 19:05 UTC | 15m |
| 2026-05-04 | VJC902 | BKK → HAN | May 4, 07:20 UTC | May 4, 07:40 UTC | 20m |
| 2026-05-03 | VJC901 | HAN → BKK | May 3, 19:00 UTC | May 4, 06:00 UTC | 11h 0m |
| 2026-05-03 | VJC7037 | - | May 3, 10:40 UTC | May 3, 11:45 UTC | 1h 5m |
| 2026-05-02 | VJC7036 | - | May 2, 18:30 UTC | May 3, 08:45 UTC | 14h 14m |
| 2026-05-02 | VJC949 | RMQ → HAN | May 2, 10:15 UTC | May 2, 11:20 UTC | 1h 5m |
| 2026-05-02 | VJC948 | HAN → RMQ | May 2, 07:40 UTC | May 2, 08:45 UTC | 1h 5m |
| 2026-05-02 | VJC959 | FUK → HAN | May 2, 00:20 UTC | May 2, 00:30 UTC | 10m |
| 2026-04-30 | VJC843 | TPE → SGN | Apr 30, 13:05 UTC | Apr 30, 14:10 UTC | 1h 5m |
| 2026-04-30 | VJC842 | SGN → TPE | Apr 30, 10:25 UTC | Apr 30, 11:20 UTC | 55m |
| 2026-04-26 | VJC8021 | - | Apr 26, 20:20 UTC | Apr 26, 20:50 UTC | 30m |
| 2026-04-26 | VJC8020 | DAD → MNL | Apr 26, 17:40 UTC | Apr 26, 18:25 UTC | 45m |
| 2026-04-26 | VJC814 | SIN → SGN | Apr 26, 11:35 UTC | Apr 26, 11:45 UTC | 10m |
| 2026-04-26 | VJC814 | SIN → SGN | Apr 26, 10:20 UTC | Apr 26, 10:35 UTC | 15m |
| 2026-04-25 | VJC989 | PUS → DAD | Apr 25, 19:10 UTC | Apr 26, 09:10 UTC | 14h 0m |
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-A683 page for operator, model, and routing details .