sensors Mode-S transponder
88817D
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A536 · AIRBUS A-321neo
- Hex
- 88817D
- Octal
- 42100575
- Decimal
- 8,946,045
- Country
- VN
- Tail
- VN-A536
- Type
- A21N
- Flights observed
- 40
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 88817D 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 |
|---|---|---|---|
| VJC919 | VietJet Air | 3 | 2026-05-24 |
| VJC863 | VietJet Air | 3 | 2026-05-27 |
| VJC862 | VietJet Air | 3 | 2026-05-26 |
| VJC861 | - | 3 | 2026-04-14 |
| VJC854 | VietJet Air | 3 | 2026-04-16 |
| VJC976 | VietJet Air | 2 | 2026-04-13 |
| VJC868 | VietJet Air | 2 | 2026-05-27 |
| VJC860 | - | 2 | 2026-04-14 |
| VJC829 | VietJet Air | 2 | 2026-04-13 |
| VJC5381 | - | 2 | 2026-05-19 |
| VJC1806 | VietJet Air | 2 | 2026-04-15 |
| VJC1805 | VietJet Air | 2 | 2026-04-15 |
| VJC977 | - | 1 | 2026-04-13 |
| VJC943 | VietJet Air | 1 | 2026-05-29 |
| VJC942 | VietJet Air | 1 | 2026-05-29 |
| VJC939 | VietJet Air | 1 | 2026-05-29 |
| VJC938 | VietJet Air | 1 | 2026-05-28 |
| VJC929 | VietJet Air | 1 | 2026-05-21 |
| VJC928 | VietJet Air | 1 | 2026-05-21 |
| VJC921 | VietJet Air | 1 | 2026-05-22 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | VJC943 | TPE → HAN | May 29, 12:15 UTC | May 29, 14:45 UTC | 2h 30m |
| 2026-05-29 | VJC942 | HAN → TPE | May 29, 07:55 UTC | May 29, 10:40 UTC | 2h 45m |
| 2026-05-29 | VJC939 | KIX → HAN | May 29, 00:35 UTC | May 29, 01:20 UTC | 45m |
| 2026-05-28 | VJC938 | HAN → KIX | May 28, 18:40 UTC | May 28, 22:40 UTC | 4h 0m |
| 2026-05-27 | VJC868 | SGN → PUS | May 27, 19:35 UTC | May 28, 14:10 UTC | 18h 35m |
| 2026-05-27 | VJC868 | SGN → PUS | May 27, 05:19 UTC | May 28, 02:10 UTC | 20h 50m |
| 2026-05-27 | VJC863 | ICN → SGN | May 27, 03:34 UTC | May 28, 02:10 UTC | 22h 35m |
| 2026-05-26 | VJC862 | SGN → ICN | May 26, 21:44 UTC | May 27, 00:49 UTC | 3h 5m |
| 2026-05-24 | VJC919 | PUS → CXR | May 24, 23:00 UTC | May 25, 11:35 UTC | 12h 35m |
| 2026-05-24 | VJC919 | PUS → CXR | May 24, 14:10 UTC | May 25, 11:35 UTC | 21h 25m |
| 2026-05-24 | VJC919 | PUS → CXR | May 24, 09:20 UTC | May 25, 04:10 UTC | 18h 50m |
| 2026-05-22 | VJC921 | NGO → HAN | May 22, 00:50 UTC | May 22, 01:40 UTC | 50m |
| 2026-05-21 | VJC928 | CGK → HAN | May 21, 08:15 UTC | May 21, 22:55 UTC | 14h 40m |
| 2026-05-21 | VJC929 | HAN → CGK | May 21, 04:30 UTC | May 21, 06:15 UTC | 1h 45m |
| 2026-05-19 | VJC5381 | - | May 19, 13:45 UTC | May 19, 14:05 UTC | 20m |
| 2026-05-18 | VJC5381 | - | May 18, 15:20 UTC | May 19, 14:05 UTC | 22h 44m |
| 2026-05-18 | VJC5349 | - | May 18, 10:30 UTC | May 18, 15:35 UTC | 5h 5m |
| 2026-05-02 | VJC828 | SGN → KIX | May 2, 20:30 UTC | May 3, 04:25 UTC | 7h 54m |
| 2026-04-16 | VJC854 | CGK → SGN | Apr 16, 09:15 UTC | Apr 16, 09:45 UTC | 30m |
| 2026-04-16 | VJC854 | CGK → SGN | Apr 16, 07:54 UTC | Apr 16, 08:24 UTC | 30m |
| 2026-04-16 | VJC854 | CGK → SGN | Apr 16, 06:55 UTC | Apr 16, 07:05 UTC | 10m |
| 2026-04-16 | VJC855 | SGN → CGK | Apr 16, 05:24 UTC | Apr 16, 05:39 UTC | 15m |
| 2026-04-15 | VJC1806 | AMD → SGN | Apr 15, 21:05 UTC | Apr 15, 23:00 UTC | 1h 55m |
| 2026-04-15 | VJC1806 | AMD → SGN | Apr 15, 20:30 UTC | Apr 15, 21:00 UTC | 30m |
| 2026-04-15 | VJC1805 | SGN → AMD | Apr 15, 15:05 UTC | Apr 15, 16:05 UTC | 1h 0m |
| 2026-04-15 | VJC1805 | SGN → AMD | Apr 15, 13:10 UTC | Apr 15, 14:25 UTC | 1h 15m |
| 2026-04-15 | VJC863 | ICN → SGN | Apr 15, 05:00 UTC | Apr 15, 05:55 UTC | 55m |
| 2026-04-15 | VJC863 | ICN → SGN | Apr 15, 03:00 UTC | Apr 15, 04:50 UTC | 1h 50m |
| 2026-04-14 | VJC862 | SGN → ICN | Apr 14, 22:55 UTC | Apr 15, 00:50 UTC | 1h 55m |
| 2026-04-14 | VJC862 | SGN → ICN | Apr 14, 22:10 UTC | Apr 14, 22:50 UTC | 40m |
| 2026-04-14 | VJC861 | - | Apr 14, 14:50 UTC | Apr 14, 15:20 UTC | 30m |
| 2026-04-14 | VJC861 | - | Apr 14, 12:50 UTC | Apr 14, 14:45 UTC | 1h 55m |
| 2026-04-14 | VJC861 | - | Apr 14, 12:25 UTC | Apr 14, 12:45 UTC | 20m |
| 2026-04-14 | VJC860 | - | Apr 14, 09:55 UTC | Apr 14, 10:30 UTC | 35m |
| 2026-04-14 | VJC860 | - | Apr 14, 07:45 UTC | Apr 14, 08:50 UTC | 1h 5m |
| 2026-04-13 | VJC977 | - | Apr 13, 20:15 UTC | Apr 13, 23:05 UTC | 2h 50m |
| 2026-04-13 | VJC976 | PQC → ICN | Apr 13, 16:15 UTC | Apr 13, 18:45 UTC | 2h 30m |
| 2026-04-13 | VJC976 | PQC → ICN | Apr 13, 16:00 UTC | Apr 13, 16:15 UTC | 15m |
| 2026-04-13 | VJC829 | KIX → SGN | Apr 13, 03:55 UTC | Apr 13, 04:10 UTC | 15m |
| 2026-04-13 | VJC829 | KIX → SGN | Apr 13, 01:05 UTC | Apr 13, 04:10 UTC | 3h 5m |
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-A536 page for operator, model, and routing details .