sensors Mode-S transponder
888200
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A516 · AIRBUS A-321neo
- Hex
- 888200
- Octal
- 42101000
- Decimal
- 8,946,176
- Country
- VN
- Tail
- VN-A516
- Type
- A21N
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 888200 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 |
|---|---|---|---|
| VJC834 | VietJet Air | 6 | 2026-05-24 |
| VJC869 | VietJet Air | 5 | 2026-05-05 |
| VJC1801 | VietJet Air | 4 | 2026-05-06 |
| VJC943 | - | 3 | 2026-04-15 |
| VJC942 | VietJet Air | 3 | 2026-04-15 |
| VJC938 | VietJet Air | 3 | 2026-05-12 |
| VJC932 | VietJet Air | 3 | 2026-05-17 |
| VJC7705 | - | 3 | 2026-05-21 |
| VJC949 | - | 2 | 2026-04-14 |
| VJC933 | VietJet Air | 2 | 2026-05-18 |
| VJC926 | VietJet Air | 2 | 2026-04-24 |
| VJC925 | VietJet Air | 2 | 2026-04-24 |
| VJC907 | VietJet Air | 2 | 2026-05-13 |
| VJC835 | VietJet Air | 2 | 2026-05-24 |
| VJC5381 | - | 2 | 2026-05-09 |
| VJC5069 | - | 2 | 2026-05-08 |
| VJC5068 | - | 2 | 2026-05-08 |
| VJC489 | VietJet Air | 2 | 2026-04-25 |
| VJC488 | VietJet Air | 2 | 2026-04-25 |
| VJC961 | - | 1 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-24 | VJC835 | ICN → CXR | May 24, 23:00 UTC | May 24, 23:10 UTC | 10m |
| 2026-05-24 | VJC834 | CXR → ICN | May 24, 08:00 UTC | May 24, 21:30 UTC | 13h 30m |
| 2026-05-24 | VJC834 | CXR → ICN | May 24, 00:05 UTC | May 24, 21:30 UTC | 21h 25m |
| 2026-05-23 | VJC834 | CXR → ICN | May 23, 22:05 UTC | May 24, 21:30 UTC | 23h 25m |
| 2026-05-23 | VJC834 | CXR → ICN | May 23, 17:45 UTC | May 23, 20:30 UTC | 2h 46m |
| 2026-05-21 | VJC7614 | - | May 21, 21:35 UTC | May 22, 03:40 UTC | 6h 5m |
| 2026-05-21 | VJC7705 | - | May 21, 02:05 UTC | May 21, 21:50 UTC | 19h 45m |
| 2026-05-20 | VJC7705 | - | May 20, 20:35 UTC | May 21, 02:25 UTC | 5h 50m |
| 2026-05-20 | VJC7705 | - | May 20, 04:05 UTC | May 21, 02:25 UTC | 22h 21m |
| 2026-05-20 | VJC921 | NGO → HAN | May 20, 03:10 UTC | May 21, 02:00 UTC | 22h 51m |
| 2026-05-20 | VJC920 | HAN → NGO | May 20, 00:35 UTC | May 20, 01:20 UTC | 45m |
| 2026-05-18 | VJC933 | NRT → HAN | May 18, 00:55 UTC | May 18, 02:20 UTC | 1h 25m |
| 2026-05-17 | VJC932 | HAN → NRT | May 17, 21:25 UTC | May 17, 23:00 UTC | 1h 35m |
| 2026-05-16 | VJC933 | NRT → HAN | May 16, 00:55 UTC | May 16, 02:10 UTC | 1h 15m |
| 2026-05-15 | VJC932 | HAN → NRT | May 15, 06:05 UTC | May 15, 22:55 UTC | 16h 49m |
| 2026-05-14 | VJC932 | HAN → NRT | May 14, 22:25 UTC | May 15, 22:00 UTC | 23h 34m |
| 2026-05-14 | VJC1926 | AMD → HAN | May 14, 19:15 UTC | May 15, 11:40 UTC | 16h 25m |
| 2026-05-14 | VJC1925 | HAN → AMD | May 14, 07:00 UTC | May 14, 15:40 UTC | 8h 40m |
| 2026-05-13 | VJC907 | HAN → BOM | May 13, 14:15 UTC | May 14, 05:20 UTC | 15h 5m |
| 2026-05-13 | VJC907 | HAN → BOM | May 13, 00:45 UTC | May 13, 23:20 UTC | 22h 35m |
| 2026-05-12 | VJC938 | HAN → KIX | May 12, 21:55 UTC | May 12, 22:40 UTC | 45m |
| 2026-05-11 | VJC935 | NRT → HAN | May 11, 08:00 UTC | May 11, 22:35 UTC | 14h 35m |
| 2026-05-11 | VJC934 | HAN → NRT | May 11, 04:35 UTC | May 11, 06:00 UTC | 1h 25m |
| 2026-05-09 | VJC5381 | - | May 9, 08:55 UTC | May 9, 14:10 UTC | 5h 15m |
| 2026-05-08 | VJC5381 | - | May 8, 18:05 UTC | May 9, 14:10 UTC | 20h 5m |
| 2026-05-08 | VJC5069 | - | May 8, 17:55 UTC | May 9, 14:10 UTC | 20h 15m |
| 2026-05-08 | VJC5068 | - | May 8, 15:55 UTC | May 8, 16:15 UTC | 20m |
| 2026-05-06 | VJC1802 | BLR → SGN | May 6, 18:30 UTC | May 6, 22:05 UTC | 3h 35m |
| 2026-05-06 | VJC1801 | SGN → BLR | May 6, 13:00 UTC | May 6, 17:05 UTC | 4h 5m |
| 2026-05-05 | VJC1801 | SGN → BLR | May 5, 21:01 UTC | May 6, 17:05 UTC | 20h 5m |
| 2026-05-05 | VJC1801 | SGN → BLR | May 5, 16:10 UTC | May 6, 14:15 UTC | 22h 5m |
| 2026-05-05 | VJC1801 | SGN → BLR | May 5, 15:20 UTC | May 6, 14:00 UTC | 22h 40m |
| 2026-05-05 | VJC869 | PUS → SGN | May 5, 02:05 UTC | May 5, 21:20 UTC | 19h 15m |
| 2026-05-05 | VJC869 | PUS → SGN | May 5, 01:15 UTC | May 5, 21:20 UTC | 20h 5m |
| 2026-05-04 | VJC869 | PUS → SGN | May 4, 23:50 UTC | May 5, 21:20 UTC | 21h 30m |
| 2026-05-04 | VJC868 | SGN → PUS | May 4, 20:00 UTC | May 4, 21:00 UTC | 1h 0m |
| 2026-05-01 | VJC879 | ICN → DAD | May 1, 22:20 UTC | May 2, 01:05 UTC | 2h 45m |
| 2026-05-01 | VJC878 | DAD → ICN | May 1, 18:15 UTC | May 1, 21:10 UTC | 2h 55m |
| 2026-04-30 | VJC2925 | - | Apr 30, 19:40 UTC | Apr 30, 20:00 UTC | 20m |
| 2026-04-29 | VJC835 | ICN → CXR | Apr 29, 22:40 UTC | Apr 30, 14:50 UTC | 16h 10m |
| 2026-04-29 | VJC834 | CXR → ICN | Apr 29, 05:20 UTC | Apr 29, 21:20 UTC | 16h 1m |
| 2026-04-28 | VJC834 | CXR → ICN | Apr 28, 22:20 UTC | Apr 29, 21:20 UTC | 23h 1m |
| 2026-04-28 | VJC869 | PUS → SGN | Apr 28, 02:05 UTC | Apr 28, 22:40 UTC | 20h 35m |
| 2026-04-28 | VJC869 | PUS → SGN | Apr 28, 01:05 UTC | Apr 28, 22:40 UTC | 21h 35m |
| 2026-04-27 | VJC863 | ICN → SGN | Apr 27, 02:55 UTC | Apr 27, 20:45 UTC | 17h 50m |
| 2026-04-26 | VJC862 | SGN → ICN | Apr 26, 22:00 UTC | Apr 27, 00:55 UTC | 2h 55m |
| 2026-04-25 | VJC488 | VCA → HPH | Apr 25, 11:35 UTC | Apr 25, 11:50 UTC | 15m |
| 2026-04-25 | VJC489 | HPH → VCA | Apr 25, 10:10 UTC | Apr 25, 10:20 UTC | 10m |
| 2026-04-24 | VJC925 | ICN → HPH | Apr 24, 22:45 UTC | Apr 24, 23:25 UTC | 40m |
| 2026-04-24 | VJC926 | HPH → ICN | Apr 24, 20:20 UTC | Apr 24, 21:05 UTC | 45m |
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-A516 page for operator, model, and routing details .