sensors Mode-S transponder
888219
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A580 · AIRBUS A-321neo
- Hex
- 888219
- Octal
- 42101031
- Decimal
- 8,946,201
- Country
- VN
- Tail
- VN-A580
- Type
- A21N
- Flights observed
- 94
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 888219 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 |
|---|---|---|---|
| VJC835 | VietJet Air | 8 | 2026-05-03 |
| VJC834 | VietJet Air | 6 | 2026-05-03 |
| VJC7620 | - | 5 | 2026-05-16 |
| VJC863 | VietJet Air | 4 | 2026-05-28 |
| VJC5069 | - | 4 | 2026-05-29 |
| VJC5068 | - | 4 | 2026-05-29 |
| VJC862 | VietJet Air | 3 | 2026-05-27 |
| VJC7706 | VietJet Air | 3 | 2026-05-08 |
| VJC986 | VietJet Air | 2 | 2026-05-12 |
| VJC918 | VietJet Air | 2 | 2026-04-30 |
| VJC896 | VietJet Air | 2 | 2026-05-18 |
| VJC885 | VietJet Air | 2 | 2026-05-14 |
| VJC883 | VietJet Air | 2 | 2026-05-21 |
| VJC869 | VietJet Air | 2 | 2026-04-22 |
| VJC868 | VietJet Air | 2 | 2026-04-22 |
| VJC843 | VietJet Air | 2 | 2026-04-23 |
| VJC842 | VietJet Air | 2 | 2026-04-23 |
| VJC829 | VietJet Air | 2 | 2026-05-24 |
| VJC1802 | VietJet Air | 2 | 2026-05-22 |
| VJC985 | VietJet Air | 1 | 2026-04-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | VJC5069 | - | May 29, 23:50 UTC | May 30, 00:15 UTC | 25m |
| 2026-05-29 | VJC5069 | - | May 29, 17:55 UTC | May 29, 23:00 UTC | 5h 5m |
| 2026-05-29 | VJC5068 | - | May 29, 16:05 UTC | May 29, 16:30 UTC | 25m |
| 2026-05-29 | VJC5068 | - | May 29, 11:00 UTC | May 29, 11:20 UTC | 20m |
| 2026-05-29 | VJC5068 | - | May 29, 09:35 UTC | May 29, 09:50 UTC | 15m |
| 2026-05-29 | VJC775 | HAN → CXR | May 29, 05:00 UTC | May 29, 05:15 UTC | 15m |
| 2026-05-28 | VJC123 | HAN → SGN | May 28, 22:45 UTC | May 28, 23:15 UTC | 30m |
| 2026-05-28 | VJC863 | ICN → SGN | May 28, 03:00 UTC | May 28, 12:10 UTC | 9h 10m |
| 2026-05-27 | VJC862 | SGN → ICN | May 27, 21:35 UTC | May 28, 00:35 UTC | 3h 0m |
| 2026-05-26 | VJC5069 | - | May 26, 17:55 UTC | May 26, 18:10 UTC | 15m |
| 2026-05-26 | VJC5068 | - | May 26, 15:49 UTC | May 26, 16:05 UTC | 15m |
| 2026-05-24 | VJC829 | KIX → SGN | May 24, 00:55 UTC | May 24, 04:00 UTC | 3h 5m |
| 2026-05-23 | VJC828 | SGN → KIX | May 23, 20:10 UTC | May 23, 23:10 UTC | 3h 0m |
| 2026-05-23 | VJC7079 | MFM → HPH | May 23, 08:20 UTC | May 23, 08:30 UTC | 10m |
| 2026-05-23 | VJC7078 | - | May 23, 07:00 UTC | May 23, 07:10 UTC | 10m |
| 2026-05-22 | VJC1802 | BLR → SGN | May 22, 20:10 UTC | May 22, 23:15 UTC | 3h 5m |
| 2026-05-22 | VJC1802 | BLR → SGN | May 22, 19:20 UTC | May 22, 19:30 UTC | 10m |
| 2026-05-21 | VJC1801 | SGN → BLR | May 21, 22:45 UTC | May 22, 18:05 UTC | 19h 20m |
| 2026-05-21 | VJC884 | BOM → SGN | May 21, 20:00 UTC | May 21, 20:20 UTC | 20m |
| 2026-05-21 | VJC883 | SGN → BOM | May 21, 18:05 UTC | May 21, 18:35 UTC | 30m |
| 2026-05-21 | VJC883 | SGN → BOM | May 21, 08:05 UTC | May 21, 15:30 UTC | 7h 25m |
| 2026-05-19 | VJC5069 | - | May 19, 17:55 UTC | May 19, 18:10 UTC | 15m |
| 2026-05-18 | VJC896 | DEL → SGN | May 18, 22:20 UTC | May 19, 16:20 UTC | 18h 0m |
| 2026-05-18 | VJC896 | DEL → SGN | May 18, 18:55 UTC | May 19, 16:20 UTC | 21h 25m |
| 2026-05-18 | VJC895 | SGN → DEL | May 18, 06:45 UTC | May 18, 17:30 UTC | 10h 45m |
| 2026-05-18 | VJC855 | SGN → CGK | May 18, 05:20 UTC | May 18, 05:35 UTC | 15m |
| 2026-05-16 | VJC7620 | - | May 16, 14:05 UTC | May 16, 19:45 UTC | 5h 40m |
| 2026-05-15 | VJC7620 | - | May 15, 18:20 UTC | May 16, 14:25 UTC | 20h 6m |
| 2026-05-15 | VJC7620 | - | May 15, 18:10 UTC | May 16, 14:25 UTC | 20h 16m |
| 2026-05-14 | VJC3908 | SGN → CAN | May 14, 17:45 UTC | May 14, 18:05 UTC | 20m |
| 2026-05-14 | VJC885 | KHH → SGN | May 14, 05:10 UTC | May 14, 05:50 UTC | 40m |
| 2026-05-14 | VJC885 | KHH → SGN | May 14, 02:55 UTC | May 14, 03:50 UTC | 55m |
| 2026-05-13 | VJC863 | ICN → SGN | May 13, 04:50 UTC | May 14, 03:50 UTC | 23h 0m |
| 2026-05-13 | VJC863 | ICN → SGN | May 13, 03:10 UTC | May 13, 06:00 UTC | 2h 50m |
| 2026-05-12 | VJC862 | SGN → ICN | May 12, 08:55 UTC | May 13, 00:30 UTC | 15h 35m |
| 2026-05-12 | VJC986 | PQC → HKG | May 12, 07:20 UTC | May 12, 07:35 UTC | 15m |
| 2026-05-11 | VJC863 | ICN → SGN | May 11, 03:05 UTC | May 11, 06:00 UTC | 2h 55m |
| 2026-05-10 | VJC862 | SGN → ICN | May 10, 21:49 UTC | May 11, 00:45 UTC | 2h 55m |
| 2026-05-10 | VJC809 | SGN → HKT | May 10, 02:45 UTC | May 10, 05:55 UTC | 3h 10m |
| 2026-05-08 | VJC7706 | HAN → KHV | May 8, 21:15 UTC | May 9, 04:05 UTC | 6h 50m |
| 2026-05-08 | VJC7706 | HAN → KHV | May 8, 03:49 UTC | May 8, 21:40 UTC | 17h 50m |
| 2026-05-07 | VJC7614 | - | May 7, 21:55 UTC | May 8, 04:04 UTC | 6h 9m |
| 2026-05-05 | VJC829 | KIX → SGN | May 5, 20:15 UTC | May 6, 04:10 UTC | 7h 55m |
| 2026-05-03 | VJC835 | ICN → CXR | May 3, 21:54 UTC | May 4, 01:05 UTC | 3h 10m |
| 2026-05-03 | VJC834 | CXR → ICN | May 3, 10:25 UTC | May 3, 20:20 UTC | 9h 55m |
| 2026-05-02 | VJC5512 | - | May 2, 19:50 UTC | May 3, 09:10 UTC | 13h 19m |
| 2026-05-02 | VJC7620 | - | May 2, 14:50 UTC | May 2, 15:10 UTC | 20m |
| 2026-05-01 | VJC7620 | - | May 1, 17:30 UTC | May 2, 15:10 UTC | 21h 41m |
| 2026-04-30 | VJC919 | PUS → CXR | Apr 30, 21:45 UTC | May 1, 16:00 UTC | 18h 15m |
| 2026-04-30 | VJC918 | CXR → PUS | Apr 30, 03:15 UTC | Apr 30, 23:00 UTC | 19h 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-A580 page for operator, model, and routing details .