sensors Mode-S transponder
888040
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A685 · AIRBUS A-321
- Hex
- 888040
- Octal
- 42100100
- Decimal
- 8,945,728
- Country
- VN
- Tail
- VN-A685
- Type
- A321
- Flights observed
- 62
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 888040 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 |
|---|---|---|---|
| VJC984 | VietJet Air | 3 | 2026-05-28 |
| VJC859 | VietJet Air | 3 | 2026-05-13 |
| VJC858 | VietJet Air | 3 | 2026-05-13 |
| VJC800 | VietJet Air | 3 | 2026-04-19 |
| VJC3908 | VietJet Air | 3 | 2026-06-03 |
| VJC960 | VietJet Air | 2 | 2026-05-26 |
| VJC929 | VietJet Air | 2 | 2026-05-01 |
| VJC925 | VietJet Air | 2 | 2026-06-02 |
| VJC902 | VietJet Air | 2 | 2026-05-25 |
| VJC901 | VietJet Air | 2 | 2026-05-25 |
| VJC886 | VietJet Air | 2 | 2026-05-12 |
| VJC807 | VietJet Air | 2 | 2026-04-19 |
| VJC7527 | VietJet Air | 2 | 2026-05-25 |
| VJC962 | VietJet Air | 1 | 2026-05-22 |
| VJC961 | VietJet Air | 1 | 2026-05-24 |
| VJC928 | VietJet Air | 1 | 2026-05-01 |
| VJC926 | VietJet Air | 1 | 2026-06-01 |
| VJC919 | VietJet Air | 1 | 2026-05-07 |
| VJC918 | VietJet Air | 1 | 2026-05-06 |
| VJC916 | VietJet Air | 1 | 2026-05-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | VJC3908 | SGN → CAN | Jun 3, 17:20 UTC | Jun 3, 17:40 UTC | 20m |
| 2026-06-02 | VJC271 | HPH → SGN | Jun 2, 05:35 UTC | Jun 2, 05:45 UTC | 10m |
| 2026-06-02 | VJC925 | ICN → HPH | Jun 2, 02:45 UTC | Jun 2, 03:10 UTC | 25m |
| 2026-06-01 | VJC925 | ICN → HPH | Jun 1, 23:05 UTC | Jun 2, 02:05 UTC | 3h 0m |
| 2026-06-01 | VJC926 | HPH → ICN | Jun 1, 17:05 UTC | Jun 1, 20:55 UTC | 3h 50m |
| 2026-06-01 | VJC1284 | - | Jun 1, 14:55 UTC | Jun 1, 15:10 UTC | 15m |
| 2026-06-01 | VJC814 | SIN → SGN | Jun 1, 10:25 UTC | Jun 1, 10:45 UTC | 20m |
| 2026-05-31 | VJC2855 | - | May 31, 19:00 UTC | Jun 1, 08:45 UTC | 13h 45m |
| 2026-05-31 | VJC2854 | - | May 31, 11:40 UTC | May 31, 17:30 UTC | 5h 50m |
| 2026-05-31 | VJC889 | DAD → SIN | May 31, 09:25 UTC | May 31, 09:40 UTC | 15m |
| 2026-05-30 | VJC8021 | - | May 30, 19:35 UTC | May 30, 20:00 UTC | 25m |
| 2026-05-30 | VJC8020 | DAD → MNL | May 30, 03:25 UTC | May 30, 18:20 UTC | 14h 55m |
| 2026-05-30 | - | - | May 30, 01:35 UTC | May 30, 01:55 UTC | 20m |
| 2026-05-28 | VJC3909 | CAN → SGN | May 28, 19:40 UTC | May 28, 19:50 UTC | 10m |
| 2026-05-28 | VJC3908 | SGN → CAN | May 28, 11:40 UTC | May 28, 17:40 UTC | 6h 0m |
| 2026-05-28 | VJC984 | SIN → PQC | May 28, 05:25 UTC | May 28, 09:55 UTC | 4h 30m |
| 2026-05-27 | VJC167 | HAN → SGN | May 27, 16:05 UTC | May 28, 03:45 UTC | 11h 40m |
| 2026-05-27 | VJC904 | BKK → HAN | May 27, 12:40 UTC | May 27, 14:45 UTC | 2h 5m |
| 2026-05-27 | VJC903 | HAN → BKK | May 27, 02:24 UTC | May 27, 10:35 UTC | 8h 10m |
| 2026-05-26 | VJC960 | HAN → ICN | May 26, 22:25 UTC | May 26, 22:44 UTC | 20m |
| 2026-05-25 | VJC7527 | CAN → HAN | May 25, 19:20 UTC | May 25, 19:30 UTC | 10m |
| 2026-05-25 | VJC902 | BKK → HAN | May 25, 07:45 UTC | May 25, 08:40 UTC | 55m |
| 2026-05-25 | VJC901 | HAN → BKK | May 25, 05:25 UTC | May 25, 06:25 UTC | 1h 0m |
| 2026-05-24 | VJC961 | ICN → HAN | May 24, 02:25 UTC | May 24, 02:50 UTC | 25m |
| 2026-05-23 | VJC960 | HAN → ICN | May 23, 22:20 UTC | May 23, 22:40 UTC | 20m |
| 2026-05-23 | VJC902 | BKK → HAN | May 23, 07:20 UTC | May 23, 08:15 UTC | 55m |
| 2026-05-22 | VJC901 | HAN → BKK | May 22, 21:55 UTC | May 23, 05:55 UTC | 8h 0m |
| 2026-05-22 | VJC962 | HAN → ICN | May 22, 20:20 UTC | May 22, 20:35 UTC | 15m |
| 2026-05-21 | VJC7527 | CAN → HAN | May 21, 19:15 UTC | May 21, 19:25 UTC | 10m |
| 2026-05-21 | VJC984 | SIN → PQC | May 21, 05:20 UTC | May 21, 05:45 UTC | 25m |
| 2026-05-17 | VJC916 | SIN → HAN | May 17, 07:40 UTC | May 17, 08:00 UTC | 20m |
| 2026-05-17 | VJC915 | HAN → SIN | May 17, 05:45 UTC | May 17, 05:55 UTC | 10m |
| 2026-05-14 | VJC812 | SIN → SGN | May 14, 11:40 UTC | May 14, 12:10 UTC | 30m |
| 2026-05-14 | VJC984 | SIN → PQC | May 14, 05:25 UTC | May 14, 09:50 UTC | 4h 25m |
| 2026-05-13 | VJC859 | MNL → SGN | May 13, 19:20 UTC | May 13, 19:50 UTC | 30m |
| 2026-05-13 | VJC858 | SGN → MNL | May 13, 03:25 UTC | May 13, 18:05 UTC | 14h 40m |
| 2026-05-12 | VJC885 | KHH → SGN | May 12, 04:50 UTC | May 12, 05:30 UTC | 40m |
| 2026-05-12 | VJC886 | SGN → KHH | May 12, 02:55 UTC | May 12, 03:50 UTC | 55m |
| 2026-05-11 | VJC886 | SGN → KHH | May 11, 05:25 UTC | May 12, 03:50 UTC | 22h 26m |
| 2026-05-10 | VJC859 | MNL → SGN | May 10, 19:19 UTC | May 11, 06:00 UTC | 10h 40m |
| 2026-05-10 | VJC858 | SGN → MNL | May 10, 17:25 UTC | May 10, 17:55 UTC | 30m |
| 2026-05-10 | VJC826 | KUL → SGN | May 10, 06:04 UTC | May 10, 06:20 UTC | 15m |
| 2026-05-10 | VJC825 | SGN → KUL | May 10, 04:25 UTC | May 10, 04:45 UTC | 20m |
| 2026-05-09 | VJC3908 | SGN → CAN | May 9, 16:55 UTC | May 9, 17:25 UTC | 30m |
| 2026-05-08 | VJC859 | MNL → SGN | May 8, 19:30 UTC | May 8, 20:05 UTC | 35m |
| 2026-05-08 | VJC858 | SGN → MNL | May 8, 17:25 UTC | May 8, 18:05 UTC | 40m |
| 2026-05-07 | VJC919 | PUS → CXR | May 7, 01:55 UTC | May 7, 04:30 UTC | 2h 35m |
| 2026-05-06 | VJC918 | CXR → PUS | May 6, 21:45 UTC | May 6, 22:55 UTC | 1h 10m |
| 2026-05-03 | VJC2821 | - | May 3, 10:25 UTC | May 3, 11:00 UTC | 35m |
| 2026-05-03 | VJC7290 | - | May 3, 07:15 UTC | May 3, 08:15 UTC | 1h 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-A685 page for operator, model, and routing details .