sensors Mode-S transponder
888215
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A554 · AIRBUS A-321neo
- Hex
- 888215
- Octal
- 42101025
- Decimal
- 8,946,197
- Country
- VN
- Tail
- VN-A554
- Type
- A21N
- Flights observed
- 87
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 888215 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 |
|---|---|---|---|
| VJC862 | VietJet Air | 5 | 2026-04-30 |
| VJC979 | VietJet Air | 4 | 2026-05-05 |
| VJC960 | VietJet Air | 4 | 2026-05-28 |
| VJC938 | VietJet Air | 4 | 2026-05-29 |
| VJC978 | VietJet Air | 3 | 2026-05-05 |
| VJC918 | VietJet Air | 3 | 2026-05-20 |
| VJC7989 | VietJet Air | 3 | 2026-05-17 |
| VJC3908 | VietJet Air | 3 | 2026-05-03 |
| VJC961 | VietJet Air | 2 | 2026-05-29 |
| VJC939 | VietJet Air | 2 | 2026-05-30 |
| VJC935 | - | 2 | 2026-04-13 |
| VJC863 | VietJet Air | 2 | 2026-05-01 |
| VJC811 | VietJet Air | 2 | 2026-04-28 |
| VJC7658 | - | 2 | 2026-05-30 |
| VJC7527 | - | 2 | 2026-04-13 |
| VJC567 | VietJet Air | 2 | 2026-05-30 |
| VJC3909 | VietJet Air | 2 | 2026-05-03 |
| VJC2979 | VietJet Air | 2 | 2026-05-21 |
| VJC1806 | VietJet Air | 2 | 2026-05-16 |
| VJC1805 | VietJet Air | 2 | 2026-05-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | VJC7658 | - | May 30, 18:10 UTC | May 30, 21:15 UTC | 3h 5m |
| 2026-05-30 | VJ523 | HAN → DAD | May 30, 13:05 UTC | May 30, 16:35 UTC | 3h 30m |
| 2026-05-30 | VJC567 | HAN → HUI | May 30, 09:10 UTC | May 30, 11:50 UTC | 2h 40m |
| 2026-05-30 | VJC939 | KIX → HAN | May 30, 00:40 UTC | May 30, 05:05 UTC | 4h 25m |
| 2026-05-29 | VJC938 | HAN → KIX | May 29, 18:40 UTC | May 29, 22:40 UTC | 4h 0m |
| 2026-05-29 | VJC567 | HAN → HUI | May 29, 09:20 UTC | May 29, 12:00 UTC | 2h 40m |
| 2026-05-29 | VJC961 | ICN → HAN | May 29, 02:15 UTC | May 29, 02:40 UTC | 25m |
| 2026-05-28 | VJC960 | HAN → ICN | May 28, 18:55 UTC | May 28, 22:45 UTC | 3h 50m |
| 2026-05-28 | VJC1153 | HAN → SGN | May 28, 11:30 UTC | May 28, 16:15 UTC | 4h 45m |
| 2026-05-28 | VJC454 | PQC → HAN | May 28, 09:30 UTC | May 28, 09:45 UTC | 15m |
| 2026-05-28 | VJC451 | HAN → PQC | May 28, 05:05 UTC | May 28, 05:35 UTC | 30m |
| 2026-05-27 | VJC963 | ICN → HAN | May 27, 22:15 UTC | May 28, 02:05 UTC | 3h 50m |
| 2026-05-27 | VJC962 | HAN → ICN | May 27, 17:00 UTC | May 27, 20:50 UTC | 3h 50m |
| 2026-05-27 | VJC914 | SAI → HAN | May 27, 14:10 UTC | May 27, 14:55 UTC | 45m |
| 2026-05-22 | VJC5069 | - | May 22, 18:10 UTC | May 22, 18:25 UTC | 15m |
| 2026-05-21 | VJC2979 | HAN → CXR | May 21, 23:00 UTC | May 22, 16:35 UTC | 17h 35m |
| 2026-05-21 | VJC2979 | HAN → CXR | May 21, 17:30 UTC | May 22, 16:35 UTC | 23h 5m |
| 2026-05-21 | VJC919 | PUS → CXR | May 21, 03:50 UTC | May 21, 23:25 UTC | 19h 35m |
| 2026-05-20 | VJC918 | CXR → PUS | May 20, 21:50 UTC | May 21, 17:50 UTC | 20h 0m |
| 2026-05-20 | VJC918 | CXR → PUS | May 20, 01:20 UTC | May 20, 23:15 UTC | 21h 56m |
| 2026-05-20 | VJC918 | CXR → PUS | May 20, 00:35 UTC | May 20, 23:15 UTC | 22h 41m |
| 2026-05-19 | VJC938 | HAN → KIX | May 19, 05:00 UTC | May 19, 22:35 UTC | 17h 35m |
| 2026-05-19 | VJC938 | HAN → KIX | May 19, 02:15 UTC | May 19, 22:35 UTC | 20h 20m |
| 2026-05-18 | VJC960 | HAN → ICN | May 18, 22:00 UTC | May 18, 22:40 UTC | 40m |
| 2026-05-18 | VJC960 | HAN → ICN | May 18, 02:05 UTC | May 18, 22:40 UTC | 20h 34m |
| 2026-05-17 | VJC7989 | HAN → DAD | May 17, 20:40 UTC | May 18, 02:30 UTC | 5h 50m |
| 2026-05-16 | VJC1806 | AMD → SGN | May 16, 21:40 UTC | May 17, 20:50 UTC | 23h 10m |
| 2026-05-16 | VJC1806 | AMD → SGN | May 16, 18:45 UTC | May 16, 22:55 UTC | 4h 10m |
| 2026-05-16 | VJC1805 | SGN → AMD | May 16, 17:10 UTC | May 16, 17:25 UTC | 15m |
| 2026-05-16 | VJC1805 | SGN → AMD | May 16, 08:05 UTC | May 16, 15:55 UTC | 7h 50m |
| 2026-05-13 | VJC8511 | - | May 13, 11:00 UTC | May 13, 11:45 UTC | 45m |
| 2026-05-13 | VJC8510 | DAD → RMQ | May 13, 08:55 UTC | May 13, 09:40 UTC | 45m |
| 2026-05-11 | VJC932 | HAN → NRT | May 11, 11:45 UTC | May 11, 22:35 UTC | 10h 50m |
| 2026-05-11 | VJC939 | KIX → HAN | May 11, 00:49 UTC | May 11, 10:00 UTC | 9h 10m |
| 2026-05-10 | VJC938 | HAN → KIX | May 10, 22:20 UTC | May 10, 23:00 UTC | 40m |
| 2026-05-09 | VJC7658 | - | May 9, 20:30 UTC | May 9, 20:49 UTC | 20m |
| 2026-05-07 | VJC7989 | - | May 7, 17:25 UTC | May 7, 23:19 UTC | 5h 54m |
| 2026-05-07 | VJC7989 | - | May 7, 03:35 UTC | May 7, 23:19 UTC | 19h 45m |
| 2026-05-07 | VJC813 | SGN → SIN | May 7, 01:35 UTC | May 7, 01:50 UTC | 15m |
| 2026-05-05 | VJC979 | ICN → PQC | May 5, 19:00 UTC | May 5, 22:15 UTC | 3h 15m |
| 2026-05-05 | VJC978 | PQC → ICN | May 5, 06:20 UTC | May 5, 17:30 UTC | 11h 10m |
| 2026-05-04 | VJC979 | ICN → PQC | May 4, 18:55 UTC | May 5, 04:55 UTC | 10h 0m |
| 2026-05-04 | VJC978 | PQC → ICN | May 4, 15:00 UTC | May 4, 17:30 UTC | 2h 30m |
| 2026-05-04 | VJC826 | KUL → SGN | May 4, 05:55 UTC | May 4, 06:10 UTC | 15m |
| 2026-05-04 | VJC825 | SGN → KUL | May 4, 04:05 UTC | May 4, 04:29 UTC | 25m |
| 2026-05-03 | VJC3909 | CAN → SGN | May 3, 22:39 UTC | May 3, 22:54 UTC | 15m |
| 2026-05-03 | VJC3908 | SGN → CAN | May 3, 20:35 UTC | May 3, 21:14 UTC | 40m |
| 2026-05-02 | VJC979 | ICN → PQC | May 2, 19:00 UTC | May 2, 22:05 UTC | 3h 5m |
| 2026-05-02 | VJC978 | PQC → ICN | May 2, 07:00 UTC | May 2, 17:40 UTC | 10h 40m |
| 2026-05-01 | VJC979 | ICN → PQC | May 1, 19:15 UTC | May 2, 05:45 UTC | 10h 30m |
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-A554 page for operator, model, and routing details .