sensors Mode-S transponder
88813D
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A634 · AIRBUS A-321
- Hex
- 88813D
- Octal
- 42100475
- Decimal
- 8,945,981
- Country
- VN
- Tail
- VN-A634
- Type
- A321
- Flights observed
- 34
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 23d ago
Last known position
Country allocation
The ICAO 24-bit address 88813D 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 | 4 | 2026-05-03 |
| VJC949 | VietJet Air | 3 | 2026-05-03 |
| VJC929 | VietJet Air | 2 | 2026-04-17 |
| VJC928 | VietJet Air | 2 | 2026-04-17 |
| VJC834 | VietJet Air | 2 | 2026-04-23 |
| VJC814 | VietJet Air | 2 | 2026-04-24 |
| VJC970 | VietJet Air | 1 | 2026-04-13 |
| VJC959 | VietJet Air | 1 | 2026-04-30 |
| VJC919 | VietJet Air | 1 | 2026-04-25 |
| VJC918 | VietJet Air | 1 | 2026-04-22 |
| VJC902 | VietJet Air | 1 | 2026-04-15 |
| VJC901 | VietJet Air | 1 | 2026-04-15 |
| VJC879 | VietJet Air | 1 | 2026-04-23 |
| VJC859 | - | 1 | 2026-04-12 |
| VJC858 | VietJet Air | 1 | 2026-04-12 |
| VJC813 | - | 1 | 2026-04-13 |
| VJC809 | VietJet Air | 1 | 2026-05-06 |
| VJC7816 | - | 1 | 2026-04-17 |
| VJC7815 | - | 1 | 2026-04-17 |
| VJC7814 | - | 1 | 2026-04-13 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-06 | VJC809 | SGN → HKT | May 6, 02:35 UTC | May 6, 06:05 UTC | 3h 30m |
| 2026-05-03 | VJC949 | RMQ → HAN | May 3, 10:20 UTC | May 3, 11:30 UTC | 1h 10m |
| 2026-05-03 | VJC948 | HAN → RMQ | May 3, 08:05 UTC | May 3, 09:10 UTC | 1h 5m |
| 2026-05-01 | VJC949 | RMQ → HAN | May 1, 10:15 UTC | May 1, 11:20 UTC | 1h 5m |
| 2026-05-01 | VJC948 | HAN → RMQ | May 1, 07:40 UTC | May 1, 08:50 UTC | 1h 10m |
| 2026-04-30 | VJC948 | HAN → RMQ | Apr 30, 11:20 UTC | May 1, 08:50 UTC | 21h 30m |
| 2026-04-30 | VJC949 | RMQ → HAN | Apr 30, 10:25 UTC | May 1, 08:50 UTC | 22h 25m |
| 2026-04-30 | VJC948 | HAN → RMQ | Apr 30, 07:50 UTC | Apr 30, 08:55 UTC | 1h 5m |
| 2026-04-30 | VJC959 | FUK → HAN | Apr 30, 00:20 UTC | Apr 30, 00:30 UTC | 10m |
| 2026-04-29 | VJC7291 | - | Apr 29, 05:50 UTC | Apr 29, 06:25 UTC | 35m |
| 2026-04-29 | VJC2820 | - | Apr 29, 03:10 UTC | Apr 29, 04:00 UTC | 50m |
| 2026-04-25 | VJC919 | PUS → CXR | Apr 25, 21:40 UTC | Apr 26, 04:25 UTC | 6h 45m |
| 2026-04-24 | VJC814 | SIN → SGN | Apr 24, 11:20 UTC | Apr 24, 11:40 UTC | 20m |
| 2026-04-24 | VJC814 | SIN → SGN | Apr 24, 10:15 UTC | Apr 24, 10:30 UTC | 15m |
| 2026-04-23 | VJC879 | ICN → DAD | Apr 23, 22:15 UTC | Apr 24, 08:55 UTC | 10h 40m |
| 2026-04-23 | VJC834 | CXR → ICN | Apr 23, 02:05 UTC | Apr 23, 20:30 UTC | 18h 25m |
| 2026-04-22 | VJC834 | CXR → ICN | Apr 22, 21:55 UTC | Apr 23, 20:30 UTC | 22h 35m |
| 2026-04-22 | VJC918 | CXR → PUS | Apr 22, 08:15 UTC | Apr 23, 04:35 UTC | 20h 20m |
| 2026-04-22 | VJC5508 | - | Apr 22, 06:40 UTC | Apr 22, 07:15 UTC | 35m |
| 2026-04-17 | VJC7816 | - | Apr 17, 17:55 UTC | Apr 17, 18:25 UTC | 30m |
| 2026-04-17 | VJC7815 | - | Apr 17, 15:35 UTC | Apr 17, 16:25 UTC | 50m |
| 2026-04-17 | VJC928 | CGK → HAN | Apr 17, 08:10 UTC | Apr 17, 08:40 UTC | 30m |
| 2026-04-17 | VJC928 | CGK → HAN | Apr 17, 07:20 UTC | Apr 17, 07:35 UTC | 15m |
| 2026-04-17 | VJC929 | HAN → CGK | Apr 17, 05:40 UTC | Apr 17, 06:00 UTC | 20m |
| 2026-04-17 | VJC929 | HAN → CGK | Apr 17, 04:20 UTC | Apr 17, 04:50 UTC | 31m |
| 2026-04-16 | VJC703 | DAD → VCA | Apr 16, 07:29 UTC | Apr 16, 07:39 UTC | 10m |
| 2026-04-15 | VJC902 | BKK → HAN | Apr 15, 07:50 UTC | Apr 15, 08:20 UTC | 30m |
| 2026-04-15 | VJC901 | HAN → BKK | Apr 15, 06:00 UTC | Apr 15, 06:40 UTC | 40m |
| 2026-04-13 | VJC7814 | - | Apr 13, 19:50 UTC | Apr 13, 23:25 UTC | 3h 35m |
| 2026-04-13 | VJC7813 | - | Apr 13, 19:30 UTC | Apr 13, 19:45 UTC | 15m |
| 2026-04-13 | VJC970 | SIN → DAD | Apr 13, 03:25 UTC | Apr 13, 03:50 UTC | 25m |
| 2026-04-13 | VJC813 | - | Apr 13, 01:35 UTC | Apr 13, 01:50 UTC | 15m |
| 2026-04-12 | VJC859 | - | Apr 12, 19:25 UTC | Apr 12, 19:55 UTC | 30m |
| 2026-04-12 | VJC858 | SGN → MNL | Apr 12, 17:35 UTC | Apr 12, 18:10 UTC | 35m |
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-A634 page for operator, model, and routing details .