sensors Mode-S transponder
88815E
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A697 · AIRBUS A-321neo
- Hex
- 88815E
- Octal
- 42100536
- Decimal
- 8,946,014
- Country
- VN
- Tail
- VN-A697
- Type
- A21N
- Flights observed
- 56
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 14m ago
Current position
Country allocation
The ICAO 24-bit address 88815E 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 |
|---|---|---|---|
| VJC943 | VietJet Air | 4 | 2026-04-24 |
| VJC921 | VietJet Air | 4 | 2026-05-29 |
| VJC942 | VietJet Air | 3 | 2026-04-24 |
| VJC938 | VietJet Air | 3 | 2026-04-23 |
| VJC930 | VietJet Air | 3 | 2026-05-02 |
| VJC972 | VietJet Air | 2 | 2026-05-26 |
| VJC939 | VietJet Air | 2 | 2026-04-24 |
| VJC920 | VietJet Air | 2 | 2026-05-28 |
| VJC883 | VietJet Air | 2 | 2026-05-23 |
| VJC860 | VietJet Air | 2 | 2026-04-26 |
| VJC1926 | VietJet Air | 2 | 2026-05-02 |
| VJC998 | VietJet Air | 1 | 2026-04-15 |
| VJC997 | VietJet Air | 1 | 2026-04-15 |
| VJC971 | VietJet Air | 1 | 2026-05-26 |
| VJC961 | VietJet Air | 1 | 2026-04-17 |
| VJC960 | VietJet Air | 1 | 2026-04-16 |
| VJC947 | VietJet Air | 1 | 2026-05-29 |
| VJC946 | VietJet Air | 1 | 2026-05-29 |
| VJC931 | VietJet Air | 1 | 2026-04-19 |
| VJC929 | VietJet Air | 1 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | VJC197 | - | May 30, 00:35 UTC | May 30, 05:30 UTC | 4h 55m |
| 2026-05-29 | VJC947 | KHH → HAN | May 29, 11:15 UTC | May 29, 13:15 UTC | 2h 0m |
| 2026-05-29 | VJC946 | HAN → KHH | May 29, 08:00 UTC | May 29, 10:15 UTC | 2h 15m |
| 2026-05-29 | VJC921 | NGO → HAN | May 29, 01:00 UTC | May 29, 01:55 UTC | 55m |
| 2026-05-28 | VJC920 | HAN → NGO | May 28, 19:00 UTC | May 28, 23:05 UTC | 4h 5m |
| 2026-05-28 | VJC781 | HAN → CXR | May 28, 12:15 UTC | May 28, 16:05 UTC | 3h 50m |
| 2026-05-28 | VJC528 | DAD → HAN | May 28, 07:50 UTC | May 28, 10:55 UTC | 3h 5m |
| 2026-05-28 | VJC440 | PQC → HAN | May 28, 02:10 UTC | May 28, 06:35 UTC | 4h 25m |
| 2026-05-26 | VJC972 | DEL → HAN | May 26, 19:34 UTC | May 27, 14:25 UTC | 18h 50m |
| 2026-05-26 | VJC972 | DEL → HAN | May 26, 18:45 UTC | May 27, 14:25 UTC | 19h 40m |
| 2026-05-26 | VJC971 | HAN → DEL | May 26, 07:05 UTC | May 26, 17:20 UTC | 10h 15m |
| 2026-05-26 | VJC929 | HAN → CGK | May 26, 04:15 UTC | May 26, 05:00 UTC | 45m |
| 2026-05-24 | VJC853 | RMQ → SGN | May 24, 07:55 UTC | May 24, 20:20 UTC | 12h 25m |
| 2026-05-23 | VJC884 | BOM → SGN | May 23, 19:45 UTC | May 24, 06:40 UTC | 10h 55m |
| 2026-05-23 | VJC883 | SGN → BOM | May 23, 17:55 UTC | May 23, 18:15 UTC | 20m |
| 2026-05-23 | VJC883 | SGN → BOM | May 23, 14:05 UTC | May 23, 16:55 UTC | 2h 50m |
| 2026-05-13 | VJC1805 | SGN → AMD | May 13, 13:20 UTC | May 13, 23:00 UTC | 9h 40m |
| 2026-05-06 | VJC3900 | SGN → PVG | May 6, 15:10 UTC | May 6, 21:10 UTC | 6h 0m |
| 2026-05-02 | VJC1926 | AMD → HAN | May 2, 20:50 UTC | May 3, 12:00 UTC | 15h 9m |
| 2026-05-02 | VJC1925 | HAN → AMD | May 2, 06:50 UTC | May 2, 16:45 UTC | 9h 55m |
| 2026-05-02 | VJC930 | HAN → KIX | May 2, 04:25 UTC | May 2, 04:45 UTC | 20m |
| 2026-04-30 | VJC1926 | AMD → HAN | Apr 30, 06:40 UTC | Apr 30, 22:25 UTC | 15h 45m |
| 2026-04-30 | VJC930 | HAN → KIX | Apr 30, 04:15 UTC | Apr 30, 04:40 UTC | 25m |
| 2026-04-27 | VJC882 | SIN → SGN | Apr 27, 07:40 UTC | Apr 27, 08:05 UTC | 25m |
| 2026-04-26 | VJC861 | ICN → SGN | Apr 26, 12:25 UTC | Apr 27, 06:10 UTC | 17h 45m |
| 2026-04-26 | VJC860 | SGN → ICN | Apr 26, 08:10 UTC | Apr 26, 11:00 UTC | 2h 50m |
| 2026-04-26 | VJC860 | SGN → ICN | Apr 26, 06:05 UTC | Apr 26, 06:15 UTC | 10m |
| 2026-04-26 | VJC241 | THD → SGN | Apr 26, 03:40 UTC | Apr 26, 03:50 UTC | 10m |
| 2026-04-25 | VJC921 | NGO → HAN | Apr 25, 00:45 UTC | Apr 25, 01:45 UTC | 1h 0m |
| 2026-04-24 | VJC943 | TPE → HAN | Apr 24, 11:55 UTC | Apr 24, 22:50 UTC | 10h 55m |
| 2026-04-24 | VJC942 | HAN → TPE | Apr 24, 08:40 UTC | Apr 24, 10:05 UTC | 1h 25m |
| 2026-04-24 | VJC939 | KIX → HAN | Apr 24, 01:10 UTC | Apr 24, 01:50 UTC | 40m |
| 2026-04-23 | VJC938 | HAN → KIX | Apr 23, 21:55 UTC | Apr 23, 22:20 UTC | 25m |
| 2026-04-23 | VJC938 | HAN → KIX | Apr 23, 01:35 UTC | Apr 23, 22:20 UTC | 20h 45m |
| 2026-04-23 | VJC939 | KIX → HAN | Apr 23, 01:05 UTC | Apr 23, 22:20 UTC | 21h 15m |
| 2026-04-22 | VJC938 | HAN → KIX | Apr 22, 21:50 UTC | Apr 22, 22:15 UTC | 25m |
| 2026-04-22 | VJC466 | VCA → HAN | Apr 22, 13:05 UTC | Apr 22, 13:15 UTC | 10m |
| 2026-04-22 | VJC465 | HAN → VCA | Apr 22, 11:40 UTC | Apr 22, 11:50 UTC | 10m |
| 2026-04-22 | VJC140 | SGN → HAN | Apr 22, 07:25 UTC | Apr 22, 07:35 UTC | 10m |
| 2026-04-20 | VJC943 | TPE → HAN | Apr 20, 11:50 UTC | Apr 20, 13:10 UTC | 1h 20m |
| 2026-04-20 | VJC942 | HAN → TPE | Apr 20, 00:55 UTC | Apr 20, 10:00 UTC | 9h 5m |
| 2026-04-19 | VJC931 | KIX → HAN | Apr 19, 07:10 UTC | Apr 19, 23:15 UTC | 16h 5m |
| 2026-04-19 | VJC930 | HAN → KIX | Apr 19, 04:45 UTC | Apr 19, 05:35 UTC | 50m |
| 2026-04-17 | VJC943 | - | Apr 17, 13:20 UTC | Apr 17, 13:50 UTC | 30m |
| 2026-04-17 | VJC943 | - | Apr 17, 12:30 UTC | Apr 17, 13:15 UTC | 45m |
| 2026-04-17 | VJC942 | HAN → TPE | Apr 17, 09:25 UTC | Apr 17, 10:45 UTC | 1h 20m |
| 2026-04-17 | VJC961 | ICN → HAN | Apr 17, 02:15 UTC | Apr 17, 03:05 UTC | 50m |
| 2026-04-16 | VJC960 | HAN → ICN | Apr 16, 21:39 UTC | Apr 16, 22:24 UTC | 45m |
| 2026-04-16 | VJC921 | NGO → HAN | Apr 16, 01:10 UTC | Apr 16, 01:30 UTC | 20m |
| 2026-04-16 | VJC921 | NGO → HAN | Apr 16, 00:30 UTC | Apr 16, 01:05 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-A697 page for operator, model, and routing details .