sensors Mode-S transponder
888217
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A552 · AIRBUS A-321neo
- Hex
- 888217
- Octal
- 42101027
- Decimal
- 8,946,199
- Country
- VN
- Tail
- VN-A552
- Type
- A21N
- Flights observed
- 125
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 888217 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 |
|---|---|---|---|
| VJC918 | VietJet Air | 8 | 2026-06-02 |
| VJC829 | VietJet Air | 7 | 2026-05-08 |
| VJC854 | VietJet Air | 5 | 2026-04-21 |
| VJC828 | VietJet Air | 5 | 2026-05-07 |
| VJC855 | VietJet Air | 4 | 2026-04-21 |
| VJC1803 | VietJet Air | 4 | 2026-05-09 |
| VJC934 | VietJet Air | 3 | 2026-05-06 |
| VJC933 | VietJet Air | 3 | 2026-06-01 |
| VJC916 | VietJet Air | 3 | 2026-05-30 |
| VJC915 | VietJet Air | 3 | 2026-05-30 |
| VJC869 | VietJet Air | 3 | 2026-05-08 |
| VJC861 | VietJet Air | 3 | 2026-04-30 |
| VJC860 | VietJet Air | 3 | 2026-04-30 |
| VJC835 | VietJet Air | 3 | 2026-05-22 |
| VJC834 | VietJet Air | 3 | 2026-05-22 |
| VJC1926 | VietJet Air | 3 | 2026-05-28 |
| VJC1925 | VietJet Air | 3 | 2026-05-28 |
| VJC1804 | VietJet Air | 3 | 2026-05-09 |
| VJC985 | VietJet Air | 2 | 2026-04-23 |
| VJC972 | VietJet Air | 2 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VJC918 | CXR → PUS | Jun 2, 10:35 UTC | Jun 3, 04:15 UTC | 17h 40m |
| 2026-06-02 | VJC918 | CXR → PUS | Jun 2, 00:20 UTC | Jun 2, 23:00 UTC | 22h 40m |
| 2026-06-01 | VJC947 | KHH → HAN | Jun 1, 10:50 UTC | Jun 1, 13:00 UTC | 2h 10m |
| 2026-06-01 | VJC946 | HAN → KHH | Jun 1, 07:55 UTC | Jun 1, 10:00 UTC | 2h 5m |
| 2026-06-01 | VJC933 | NRT → HAN | Jun 1, 05:25 UTC | Jun 1, 05:50 UTC | 25m |
| 2026-06-01 | VJC933 | NRT → HAN | Jun 1, 00:45 UTC | Jun 1, 02:15 UTC | 1h 30m |
| 2026-05-31 | VJC932 | HAN → NRT | May 31, 17:55 UTC | May 31, 22:45 UTC | 4h 50m |
| 2026-05-30 | VJC972 | DEL → HAN | May 30, 19:50 UTC | May 31, 14:25 UTC | 18h 35m |
| 2026-05-30 | VJC972 | DEL → HAN | May 30, 19:00 UTC | May 31, 14:25 UTC | 19h 25m |
| 2026-05-30 | VJC971 | HAN → DEL | May 30, 14:00 UTC | May 30, 17:20 UTC | 3h 20m |
| 2026-05-30 | VJC916 | SIN → HAN | May 30, 09:55 UTC | May 30, 10:10 UTC | 15m |
| 2026-05-30 | VJC916 | SIN → HAN | May 30, 07:20 UTC | May 30, 07:45 UTC | 25m |
| 2026-05-30 | VJC915 | HAN → SIN | May 30, 03:00 UTC | May 30, 05:35 UTC | 2h 35m |
| 2026-05-29 | VJC7527 | CAN → HAN | May 29, 20:00 UTC | May 29, 20:40 UTC | 40m |
| 2026-05-29 | VJC7526 | HAN → CAN | May 29, 16:00 UTC | May 29, 16:25 UTC | 25m |
| 2026-05-29 | VJC916 | SIN → HAN | May 29, 07:25 UTC | May 29, 10:15 UTC | 2h 50m |
| 2026-05-29 | VJC915 | HAN → SIN | May 29, 03:05 UTC | May 29, 05:45 UTC | 2h 40m |
| 2026-05-28 | VJC1926 | AMD → HAN | May 28, 20:55 UTC | May 28, 22:45 UTC | 1h 50m |
| 2026-05-28 | VJC1925 | HAN → AMD | May 28, 13:15 UTC | May 28, 15:50 UTC | 2h 35m |
| 2026-05-28 | VJC928 | CGK → HAN | May 28, 07:15 UTC | May 28, 11:15 UTC | 4h 0m |
| 2026-05-28 | VJC929 | HAN → CGK | May 28, 01:55 UTC | May 28, 05:55 UTC | 4h 0m |
| 2026-05-27 | VJC943 | TPE → HAN | May 27, 12:00 UTC | May 27, 14:30 UTC | 2h 30m |
| 2026-05-27 | VJC933 | NRT → HAN | May 27, 00:49 UTC | May 27, 10:25 UTC | 9h 35m |
| 2026-05-26 | VJC932 | HAN → NRT | May 26, 02:24 UTC | May 26, 22:20 UTC | 19h 55m |
| 2026-05-25 | VJC960 | HAN → ICN | May 25, 04:20 UTC | May 25, 22:44 UTC | 18h 25m |
| 2026-05-23 | VJC918 | CXR → PUS | May 23, 10:45 UTC | May 24, 04:30 UTC | 17h 46m |
| 2026-05-22 | VJC918 | CXR → PUS | May 22, 23:50 UTC | May 23, 23:00 UTC | 23h 10m |
| 2026-05-22 | VJC835 | ICN → CXR | May 22, 22:05 UTC | May 23, 21:45 UTC | 23h 40m |
| 2026-05-22 | VJC834 | CXR → ICN | May 22, 03:30 UTC | May 22, 21:00 UTC | 17h 30m |
| 2026-05-21 | VJC834 | CXR → ICN | May 21, 21:50 UTC | May 22, 21:00 UTC | 23h 10m |
| 2026-05-21 | VJC918 | CXR → PUS | May 21, 14:10 UTC | May 22, 13:35 UTC | 23h 25m |
| 2026-05-21 | VJC918 | CXR → PUS | May 21, 09:55 UTC | May 22, 04:40 UTC | 18h 45m |
| 2026-05-21 | VJC918 | CXR → PUS | May 21, 09:00 UTC | May 22, 04:40 UTC | 19h 40m |
| 2026-05-20 | VJC5349 | - | May 20, 14:45 UTC | May 21, 10:00 UTC | 19h 15m |
| 2026-05-20 | VJC5349 | - | May 20, 10:35 UTC | May 21, 09:45 UTC | 23h 10m |
| 2026-05-19 | VJC918 | CXR → PUS | May 19, 21:50 UTC | May 20, 15:25 UTC | 17h 36m |
| 2026-05-17 | VJC7614 | - | May 17, 16:05 UTC | May 17, 22:40 UTC | 6h 35m |
| 2026-05-16 | VJC835 | ICN → CXR | May 16, 23:50 UTC | May 17, 22:40 UTC | 22h 50m |
| 2026-05-16 | VJC835 | ICN → CXR | May 16, 22:00 UTC | May 17, 16:25 UTC | 18h 25m |
| 2026-05-16 | VJC834 | CXR → ICN | May 16, 17:55 UTC | May 16, 20:50 UTC | 2h 55m |
| 2026-05-12 | VJC8893 | MFM → MFM | May 12, 14:15 UTC | May 12, 14:25 UTC | 10m |
| 2026-05-12 | VJC8890 | - | May 12, 06:40 UTC | May 12, 06:50 UTC | 10m |
| 2026-05-11 | VJC8891 | MFM → DAD | May 11, 08:05 UTC | May 11, 08:20 UTC | 15m |
| 2026-05-10 | VJC2925 | - | May 10, 19:40 UTC | May 10, 20:00 UTC | 20m |
| 2026-05-09 | VJC1804 | HYD → SGN | May 9, 20:25 UTC | May 10, 15:35 UTC | 19h 10m |
| 2026-05-09 | VJC1804 | HYD → SGN | May 9, 18:45 UTC | May 10, 15:35 UTC | 20h 50m |
| 2026-05-09 | VJC1804 | HYD → SGN | May 9, 15:55 UTC | May 10, 15:35 UTC | 23h 40m |
| 2026-05-09 | VJC1803 | SGN → HYD | May 9, 01:50 UTC | May 9, 21:45 UTC | 19h 55m |
| 2026-05-08 | VJC1803 | SGN → HYD | May 8, 23:50 UTC | May 9, 21:45 UTC | 21h 55m |
| 2026-05-08 | VJC1803 | SGN → HYD | May 8, 19:50 UTC | May 9, 19:10 UTC | 23h 20m |
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-A552 page for operator, model, and routing details .