sensors Mode-S transponder
888214
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A553 · AIRBUS A-321neo
- Hex
- 888214
- Octal
- 42101024
- Decimal
- 8,946,196
- Country
- VN
- Tail
- VN-A553
- Type
- A21N
- Flights observed
- 103
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 23m ago
Last known position
Country allocation
The ICAO 24-bit address 888214 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 |
|---|---|---|---|
| VJC884 | VietJet Air | 8 | 2026-04-28 |
| VJC883 | VietJet Air | 6 | 2026-04-28 |
| VJC977 | VietJet Air | 3 | 2026-04-30 |
| VJC932 | VietJet Air | 3 | 2026-06-02 |
| VJC8891 | VietJet Air | 3 | 2026-05-19 |
| VJC986 | VietJet Air | 2 | 2026-05-23 |
| VJC985 | VietJet Air | 2 | 2026-05-23 |
| VJC979 | VietJet Air | 2 | 2026-05-23 |
| VJC976 | VietJet Air | 2 | 2026-04-30 |
| VJC973 | VietJet Air | 2 | 2026-05-03 |
| VJC968 | VietJet Air | 2 | 2026-05-22 |
| VJC933 | VietJet Air | 2 | 2026-05-29 |
| VJC8892 | - | 2 | 2026-05-18 |
| VJC8890 | - | 2 | 2026-05-20 |
| VJC860 | VietJet Air | 2 | 2026-04-21 |
| VJC822 | VietJet Air | 2 | 2026-04-23 |
| VJC814 | VietJet Air | 2 | 2026-04-25 |
| VJC807 | VietJet Air | 2 | 2026-04-23 |
| VJC800 | VietJet Air | 2 | 2026-04-23 |
| VJC7707 | - | 2 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VJC932 | HAN → NRT | Jun 2, 17:45 UTC | Jun 2, 22:35 UTC | 4h 50m |
| 2026-06-02 | VJC191 | HAN → SGN | Jun 2, 07:25 UTC | Jun 2, 12:00 UTC | 4h 35m |
| 2026-06-01 | VJC520 | - | Jun 1, 14:40 UTC | Jun 1, 15:15 UTC | 35m |
| 2026-06-01 | VJC2925 | - | Jun 1, 02:50 UTC | Jun 1, 03:20 UTC | 30m |
| 2026-05-31 | VJC2925 | - | May 31, 20:30 UTC | Jun 1, 01:40 UTC | 5h 10m |
| 2026-05-31 | VJC2924 | - | May 31, 09:30 UTC | May 31, 15:35 UTC | 6h 5m |
| 2026-05-31 | VJC197 | - | May 31, 00:40 UTC | May 31, 00:55 UTC | 15m |
| 2026-05-30 | VJC7707 | - | May 30, 08:05 UTC | May 30, 15:15 UTC | 7h 10m |
| 2026-05-29 | VJC7706 | HAN → KHV | May 29, 18:25 UTC | May 30, 06:45 UTC | 12h 20m |
| 2026-05-29 | VJC781 | HAN → CXR | May 29, 11:35 UTC | May 29, 17:20 UTC | 5h 46m |
| 2026-05-29 | VJC933 | NRT → HAN | May 29, 00:35 UTC | May 29, 05:35 UTC | 5h 0m |
| 2026-05-28 | VJC932 | HAN → NRT | May 28, 17:55 UTC | May 28, 22:45 UTC | 4h 50m |
| 2026-05-28 | VJC774 | CXR → HAN | May 28, 10:25 UTC | May 28, 10:50 UTC | 25m |
| 2026-05-26 | VJC7707 | - | May 26, 21:04 UTC | May 27, 04:34 UTC | 7h 30m |
| 2026-05-25 | VJC1802 | BLR → SGN | May 25, 19:40 UTC | May 25, 22:34 UTC | 2h 55m |
| 2026-05-25 | VJC1802 | BLR → SGN | May 25, 18:50 UTC | May 25, 19:00 UTC | 10m |
| 2026-05-25 | VJC1801 | SGN → BLR | May 25, 03:10 UTC | May 25, 17:15 UTC | 14h 5m |
| 2026-05-24 | VJC1801 | SGN → BLR | May 24, 19:05 UTC | May 25, 17:15 UTC | 22h 10m |
| 2026-05-23 | VJC979 | ICN → PQC | May 23, 21:05 UTC | May 24, 19:40 UTC | 22h 35m |
| 2026-05-23 | VJC979 | ICN → PQC | May 23, 19:15 UTC | May 23, 22:15 UTC | 3h 0m |
| 2026-05-23 | VJC978 | PQC → ICN | May 23, 15:10 UTC | May 23, 18:05 UTC | 2h 55m |
| 2026-05-23 | VJC985 | HKG → PQC | May 23, 09:30 UTC | May 23, 09:50 UTC | 20m |
| 2026-05-23 | VJC986 | PQC → HKG | May 23, 07:50 UTC | May 23, 08:15 UTC | 25m |
| 2026-05-22 | VJC968 | PQC → PUS | May 22, 18:20 UTC | May 23, 01:40 UTC | 7h 20m |
| 2026-05-21 | VJC968 | PQC → PUS | May 21, 20:25 UTC | May 22, 19:00 UTC | 22h 35m |
| 2026-05-20 | VJC2924 | - | May 20, 21:10 UTC | May 21, 15:00 UTC | 17h 50m |
| 2026-05-20 | VJC7658 | - | May 20, 15:30 UTC | May 20, 21:25 UTC | 5h 55m |
| 2026-05-20 | VJC8890 | - | May 20, 06:45 UTC | May 20, 06:55 UTC | 10m |
| 2026-05-19 | VJC879 | ICN → DAD | May 19, 22:20 UTC | May 20, 01:10 UTC | 2h 50m |
| 2026-05-19 | VJC878 | DAD → ICN | May 19, 14:10 UTC | May 19, 21:05 UTC | 6h 55m |
| 2026-05-19 | VJC8891 | MFM → DAD | May 19, 08:15 UTC | May 19, 08:30 UTC | 15m |
| 2026-05-18 | VJC8892 | - | May 18, 12:40 UTC | May 18, 12:55 UTC | 15m |
| 2026-05-18 | VJC8890 | - | May 18, 06:50 UTC | May 18, 07:00 UTC | 10m |
| 2026-05-17 | VJC8892 | - | May 17, 12:45 UTC | May 17, 13:05 UTC | 20m |
| 2026-05-17 | VJC8891 | MFM → DAD | May 17, 08:15 UTC | May 17, 08:30 UTC | 15m |
| 2026-05-16 | VJC2987 | - | May 16, 17:30 UTC | May 16, 17:40 UTC | 10m |
| 2026-05-16 | VJC2986 | - | May 16, 15:16 UTC | May 16, 15:31 UTC | 15m |
| 2026-05-12 | VJC5069 | - | May 12, 23:20 UTC | May 12, 23:35 UTC | 15m |
| 2026-05-12 | VJC5068 | - | May 12, 21:05 UTC | May 12, 21:25 UTC | 20m |
| 2026-05-11 | VJC947 | KHH → HAN | May 11, 11:15 UTC | May 11, 12:15 UTC | 1h 0m |
| 2026-05-11 | VJC933 | NRT → HAN | May 11, 00:49 UTC | May 11, 10:05 UTC | 9h 15m |
| 2026-05-10 | VJC932 | HAN → NRT | May 10, 10:45 UTC | May 10, 22:30 UTC | 11h 45m |
| 2026-05-10 | VJC946 | HAN → KHH | May 10, 00:45 UTC | May 10, 09:55 UTC | 9h 10m |
| 2026-05-09 | VJC928 | CGK → HAN | May 9, 07:00 UTC | May 9, 22:49 UTC | 15h 50m |
| 2026-05-08 | VJC910 | BOM → HAN | May 8, 21:10 UTC | May 9, 05:50 UTC | 8h 40m |
| 2026-05-08 | VJC907 | HAN → BOM | May 8, 02:55 UTC | May 8, 18:25 UTC | 15h 30m |
| 2026-05-07 | VJC862 | SGN → ICN | May 7, 07:30 UTC | May 8, 00:40 UTC | 17h 10m |
| 2026-05-06 | VJC901 | HAN → BKK | May 6, 21:40 UTC | May 7, 06:10 UTC | 8h 30m |
| 2026-05-06 | VJC962 | HAN → ICN | May 6, 20:00 UTC | May 6, 20:10 UTC | 10m |
| 2026-05-05 | VJC885 | KHH → SGN | May 5, 04:50 UTC | May 5, 05:30 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-A553 page for operator, model, and routing details .