sensors Mode-S transponder
888135
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A640 · AIRBUS A-321
- Hex
- 888135
- Octal
- 42100465
- Decimal
- 8,945,973
- Country
- VN
- Tail
- VN-A640
- Type
- A321
- Flights observed
- 69
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 888135 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 |
|---|---|---|---|
| VJC948 | VietJet Air | 3 | 2026-05-08 |
| VJC926 | VietJet Air | 3 | 2026-05-16 |
| VJC901 | VietJet Air | 3 | 2026-05-30 |
| VJC879 | VietJet Air | 3 | 2026-05-25 |
| VJC834 | VietJet Air | 3 | 2026-05-14 |
| VJC814 | VietJet Air | 3 | 2026-05-28 |
| VJC8021 | - | 3 | 2026-05-24 |
| VJC949 | VietJet Air | 2 | 2026-04-15 |
| VJC929 | VietJet Air | 2 | 2026-05-10 |
| VJC919 | VietJet Air | 2 | 2026-04-29 |
| VJC859 | VietJet Air | 2 | 2026-05-04 |
| VJC858 | VietJet Air | 2 | 2026-05-04 |
| VJC835 | VietJet Air | 2 | 2026-05-14 |
| VJC8020 | VietJet Air | 2 | 2026-05-24 |
| VJC520 | - | 2 | 2026-05-31 |
| VJC125 | VietJet Air | 2 | 2026-06-03 |
| VJC989 | VietJet Air | 1 | 2026-05-26 |
| VJC982 | VietJet Air | 1 | 2026-05-30 |
| VJC973 | VietJet Air | 1 | 2026-05-27 |
| VJC963 | VietJet Air | 1 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | VJC125 | HAN → SGN | Jun 3, 00:30 UTC | Jun 3, 01:05 UTC | 35m |
| 2026-06-02 | VJC519 | HAN → DAD | Jun 2, 12:40 UTC | Jun 2, 15:25 UTC | 2h 45m |
| 2026-06-02 | VJC731 | HPH → CXR | Jun 2, 06:10 UTC | Jun 2, 10:40 UTC | 4h 30m |
| 2026-06-02 | VJC730 | CXR → HPH | Jun 2, 05:00 UTC | Jun 2, 05:15 UTC | 15m |
| 2026-06-01 | VJC137 | HAN → SGN | Jun 1, 06:30 UTC | Jun 1, 06:50 UTC | 20m |
| 2026-06-01 | VJC128 | SGN → HAN | Jun 1, 04:50 UTC | Jun 1, 05:10 UTC | 20m |
| 2026-06-01 | VJC125 | HAN → SGN | Jun 1, 00:30 UTC | Jun 1, 01:05 UTC | 35m |
| 2026-05-31 | VJC520 | - | May 31, 14:00 UTC | May 31, 14:20 UTC | 20m |
| 2026-05-31 | VJC517 | HAN → DAD | May 31, 11:35 UTC | May 31, 11:55 UTC | 20m |
| 2026-05-30 | VJC982 | HAN → PUS | May 30, 18:20 UTC | May 31, 10:25 UTC | 16h 5m |
| 2026-05-30 | VJC1433 | HAN → UIH | May 30, 11:00 UTC | May 30, 14:30 UTC | 3h 30m |
| 2026-05-30 | VJC902 | BKK → HAN | May 30, 07:35 UTC | May 30, 09:05 UTC | 1h 30m |
| 2026-05-30 | VJC901 | HAN → BKK | May 30, 04:20 UTC | May 30, 05:45 UTC | 1h 25m |
| 2026-05-29 | VJC963 | ICN → HAN | May 29, 22:10 UTC | May 30, 02:06 UTC | 3h 56m |
| 2026-05-29 | VJC962 | HAN → ICN | May 29, 17:05 UTC | May 29, 20:55 UTC | 3h 50m |
| 2026-05-29 | VJC520 | - | May 29, 03:25 UTC | May 29, 13:40 UTC | 10h 15m |
| 2026-05-28 | VJC814 | SIN → SGN | May 28, 10:05 UTC | May 29, 01:55 UTC | 15h 50m |
| 2026-05-27 | VJC3900 | SGN → PVG | May 27, 15:10 UTC | May 28, 08:30 UTC | 17h 20m |
| 2026-05-27 | VJC814 | SIN → SGN | May 27, 10:05 UTC | May 28, 08:30 UTC | 22h 25m |
| 2026-05-27 | VJC973 | DAD → SIN | May 27, 08:25 UTC | May 27, 08:40 UTC | 15m |
| 2026-05-26 | VJC989 | PUS → DAD | May 26, 10:10 UTC | May 27, 03:20 UTC | 17h 10m |
| 2026-05-25 | VJC879 | ICN → DAD | May 25, 23:54 UTC | May 26, 02:29 UTC | 2h 35m |
| 2026-05-25 | VJC878 | DAD → ICN | May 25, 19:44 UTC | May 25, 22:30 UTC | 2h 45m |
| 2026-05-24 | VJC8021 | - | May 24, 20:20 UTC | May 24, 20:45 UTC | 25m |
| 2026-05-24 | VJC8020 | DAD → MNL | May 24, 17:55 UTC | May 24, 18:25 UTC | 30m |
| 2026-05-24 | VJC824 | KUL → DAD | May 24, 08:35 UTC | May 24, 08:50 UTC | 15m |
| 2026-05-23 | VJC8021 | - | May 23, 19:45 UTC | May 24, 05:25 UTC | 9h 40m |
| 2026-05-23 | VJC8020 | DAD → MNL | May 23, 18:00 UTC | May 23, 18:30 UTC | 30m |
| 2026-05-19 | VJC959 | FUK → HAN | May 19, 00:30 UTC | May 19, 00:40 UTC | 10m |
| 2026-05-16 | VJC925 | ICN → HPH | May 16, 22:25 UTC | May 16, 22:55 UTC | 30m |
| 2026-05-16 | VJC926 | HPH → ICN | May 16, 20:40 UTC | May 16, 21:10 UTC | 30m |
| 2026-05-15 | VJC926 | HPH → ICN | May 15, 22:20 UTC | May 16, 21:10 UTC | 22h 50m |
| 2026-05-15 | VJC926 | HPH → ICN | May 15, 20:35 UTC | May 15, 21:00 UTC | 25m |
| 2026-05-14 | VJC835 | ICN → CXR | May 14, 23:25 UTC | May 15, 21:00 UTC | 21h 34m |
| 2026-05-14 | VJC835 | ICN → CXR | May 14, 21:50 UTC | May 15, 21:00 UTC | 23h 9m |
| 2026-05-14 | VJC834 | CXR → ICN | May 14, 17:50 UTC | May 14, 20:35 UTC | 2h 45m |
| 2026-05-12 | VJC918 | CXR → PUS | May 12, 21:50 UTC | May 13, 06:05 UTC | 8h 15m |
| 2026-05-10 | VJC928 | CGK → HAN | May 10, 07:15 UTC | May 10, 08:45 UTC | 1h 30m |
| 2026-05-10 | VJC929 | HAN → CGK | May 10, 04:19 UTC | May 10, 06:00 UTC | 1h 40m |
| 2026-05-09 | VJC929 | HAN → CGK | May 9, 07:20 UTC | May 10, 06:00 UTC | 22h 40m |
| 2026-05-09 | VJC901 | HAN → BKK | May 9, 04:40 UTC | May 9, 05:50 UTC | 1h 10m |
| 2026-05-08 | VJC901 | HAN → BKK | May 8, 10:09 UTC | May 9, 05:50 UTC | 19h 40m |
| 2026-05-08 | VJC948 | HAN → RMQ | May 8, 07:39 UTC | May 8, 08:55 UTC | 1h 15m |
| 2026-05-06 | VJC814 | SIN → SGN | May 6, 10:25 UTC | May 6, 10:40 UTC | 16m |
| 2026-05-05 | VJC8017 | - | May 5, 17:40 UTC | May 6, 08:25 UTC | 14h 45m |
| 2026-05-05 | VJC8016 | DAD → MNL | May 5, 03:40 UTC | May 5, 16:15 UTC | 12h 35m |
| 2026-05-04 | VJC859 | MNL → SGN | May 4, 19:30 UTC | May 5, 02:01 UTC | 6h 30m |
| 2026-05-04 | VJC858 | SGN → MNL | May 4, 03:45 UTC | May 4, 18:05 UTC | 14h 20m |
| 2026-05-03 | VJC859 | MNL → SGN | May 3, 19:30 UTC | May 4, 02:10 UTC | 6h 40m |
| 2026-05-03 | VJC858 | SGN → MNL | May 3, 17:40 UTC | May 3, 18:20 UTC | 40m |
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-A640 page for operator, model, and routing details .