sensors Mode-S transponder
88803F
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A684 · AIRBUS A-321
- Hex
- 88803F
- Octal
- 42100077
- Decimal
- 8,945,727
- Country
- VN
- Tail
- VN-A684
- Type
- A321
- Flights observed
- 86
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 88803F 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 |
|---|---|---|---|
| VJC813 | VietJet Air | 4 | 2026-04-22 |
| VJC948 | VietJet Air | 3 | 2026-05-14 |
| VJC886 | VietJet Air | 3 | 2026-04-23 |
| VJC854 | VietJet Air | 3 | 2026-04-18 |
| VJC812 | VietJet Air | 3 | 2026-04-24 |
| VJC811 | VietJet Air | 3 | 2026-04-24 |
| VJC983 | VietJet Air | 2 | 2026-04-24 |
| VJC970 | VietJet Air | 2 | 2026-04-22 |
| VJC949 | VietJet Air | 2 | 2026-05-14 |
| VJC885 | VietJet Air | 2 | 2026-04-23 |
| VJC859 | VietJet Air | 2 | 2026-04-22 |
| VJC858 | VietJet Air | 2 | 2026-04-22 |
| VJC855 | VietJet Air | 2 | 2026-04-18 |
| VJC852 | VietJet Air | 2 | 2026-04-25 |
| VJC826 | VietJet Air | 2 | 2026-04-26 |
| VJC825 | VietJet Air | 2 | 2026-04-26 |
| VJC7816 | - | 2 | 2026-05-24 |
| VJC7815 | - | 2 | 2026-05-24 |
| VJC131 | VietJet Air | 2 | 2026-05-30 |
| VJC984 | VietJet Air | 1 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VJC151 | HAN → SGN | Jun 2, 10:30 UTC | Jun 2, 11:00 UTC | 30m |
| 2026-06-02 | VJC515 | HAN → DAD | Jun 2, 05:55 UTC | Jun 2, 08:45 UTC | 2h 50m |
| 2026-06-02 | VJC461 | HAN → VCA | Jun 2, 00:10 UTC | Jun 2, 04:40 UTC | 4h 30m |
| 2026-06-01 | VJC1789 | HAN → CXR | Jun 1, 12:25 UTC | Jun 1, 16:25 UTC | 4h 0m |
| 2026-06-01 | VJC456 | PQC → HAN | Jun 1, 06:15 UTC | Jun 1, 10:45 UTC | 4h 30m |
| 2026-05-31 | VJC8511 | - | May 31, 11:20 UTC | May 31, 18:50 UTC | 7h 30m |
| 2026-05-31 | VJC8510 | DAD → RMQ | May 31, 09:05 UTC | May 31, 10:05 UTC | 1h 0m |
| 2026-05-30 | VJC131 | HAN → SGN | May 30, 04:00 UTC | May 30, 04:25 UTC | 25m |
| 2026-05-30 | VJC126 | SGN → HAN | May 30, 02:20 UTC | May 30, 02:40 UTC | 20m |
| 2026-05-29 | VJC167 | HAN → SGN | May 29, 15:55 UTC | May 29, 16:15 UTC | 20m |
| 2026-05-29 | VJC154 | SGN → HAN | May 29, 13:35 UTC | May 29, 13:55 UTC | 20m |
| 2026-05-29 | VJC131 | HAN → SGN | May 29, 04:05 UTC | May 29, 04:15 UTC | 10m |
| 2026-05-28 | VJC273 | HPH → SGN | May 28, 11:15 UTC | May 28, 11:35 UTC | 20m |
| 2026-05-28 | VJC7079 | MFM → HPH | May 28, 09:15 UTC | May 28, 09:55 UTC | 40m |
| 2026-05-28 | VJC7078 | - | May 28, 05:45 UTC | May 28, 06:25 UTC | 40m |
| 2026-05-28 | VJC272 | SGN → HPH | May 28, 04:10 UTC | May 28, 04:20 UTC | 10m |
| 2026-05-24 | VJC7816 | - | May 24, 18:10 UTC | May 24, 18:40 UTC | 30m |
| 2026-05-24 | VJC7815 | - | May 24, 08:30 UTC | May 24, 16:10 UTC | 7h 40m |
| 2026-05-24 | VJC915 | HAN → SIN | May 24, 05:20 UTC | May 24, 05:35 UTC | 15m |
| 2026-05-23 | VJC961 | ICN → HAN | May 23, 02:15 UTC | May 23, 02:40 UTC | 24m |
| 2026-05-22 | VJC902 | BKK → HAN | May 22, 07:45 UTC | May 22, 23:00 UTC | 15h 15m |
| 2026-05-22 | VJC901 | HAN → BKK | May 22, 05:15 UTC | May 22, 06:25 UTC | 1h 10m |
| 2026-05-15 | VJC947 | KHH → HAN | May 15, 11:25 UTC | May 15, 12:20 UTC | 55m |
| 2026-05-15 | VJC946 | HAN → KHH | May 15, 09:25 UTC | May 15, 10:25 UTC | 1h 0m |
| 2026-05-14 | VJC949 | RMQ → HAN | May 14, 10:20 UTC | May 15, 09:40 UTC | 23h 20m |
| 2026-05-14 | VJC948 | HAN → RMQ | May 14, 08:40 UTC | May 14, 09:00 UTC | 20m |
| 2026-05-14 | VJC948 | HAN → RMQ | May 14, 07:50 UTC | May 14, 08:10 UTC | 20m |
| 2026-05-14 | VJC959 | FUK → HAN | May 14, 00:25 UTC | May 14, 00:35 UTC | 10m |
| 2026-05-13 | VJC943 | TPE → HAN | May 13, 11:50 UTC | May 13, 13:10 UTC | 1h 20m |
| 2026-05-13 | VJC942 | HAN → TPE | May 13, 08:55 UTC | May 13, 10:20 UTC | 1h 25m |
| 2026-05-04 | VJC949 | RMQ → HAN | May 4, 10:20 UTC | May 4, 11:30 UTC | 1h 10m |
| 2026-05-04 | VJC948 | HAN → RMQ | May 4, 07:45 UTC | May 4, 08:50 UTC | 1h 5m |
| 2026-05-02 | VJC7638 | - | May 2, 03:30 UTC | May 2, 03:40 UTC | 10m |
| 2026-05-01 | VJC5531 | MFM → MFM | May 1, 10:20 UTC | May 1, 10:35 UTC | 15m |
| 2026-04-29 | VJC5513 | - | Apr 29, 10:10 UTC | Apr 29, 11:25 UTC | 1h 15m |
| 2026-04-29 | VJC5512 | - | Apr 29, 07:40 UTC | Apr 29, 08:55 UTC | 1h 15m |
| 2026-04-26 | VJC7816 | - | Apr 26, 18:05 UTC | Apr 26, 18:35 UTC | 30m |
| 2026-04-26 | VJC7815 | - | Apr 26, 15:35 UTC | Apr 26, 16:20 UTC | 45m |
| 2026-04-26 | VJC144 | SGN → HAN | Apr 26, 09:15 UTC | Apr 26, 09:25 UTC | 10m |
| 2026-04-26 | VJC826 | KUL → SGN | Apr 26, 06:45 UTC | Apr 26, 07:05 UTC | 20m |
| 2026-04-26 | VJC826 | KUL → SGN | Apr 26, 05:35 UTC | Apr 26, 05:45 UTC | 10m |
| 2026-04-26 | VJC825 | SGN → KUL | Apr 26, 04:05 UTC | Apr 26, 04:20 UTC | 15m |
| 2026-04-26 | VJC825 | SGN → KUL | Apr 26, 02:55 UTC | Apr 26, 03:05 UTC | 10m |
| 2026-04-25 | VJC1326 | PQC → SGN | Apr 25, 14:20 UTC | Apr 25, 14:45 UTC | 25m |
| 2026-04-25 | VJC853 | RMQ → SGN | Apr 25, 07:35 UTC | Apr 25, 08:30 UTC | 55m |
| 2026-04-25 | VJC852 | SGN → RMQ | Apr 25, 05:45 UTC | Apr 25, 06:35 UTC | 50m |
| 2026-04-25 | VJC852 | SGN → RMQ | Apr 25, 03:30 UTC | Apr 25, 03:40 UTC | 10m |
| 2026-04-24 | VJC812 | SIN → SGN | Apr 24, 11:45 UTC | Apr 24, 13:10 UTC | 1h 25m |
| 2026-04-24 | VJC983 | PQC → SIN | Apr 24, 05:40 UTC | Apr 24, 10:25 UTC | 4h 45m |
| 2026-04-24 | VJC811 | SGN → SIN | Apr 24, 04:00 UTC | Apr 24, 04:30 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-A684 page for operator, model, and routing details .