sensors Mode-S transponder
8881FF
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A500 · AIRBUS A-321neo
- Hex
- 8881FF
- Octal
- 42100777
- Decimal
- 8,946,175
- Country
- VN
- Tail
- VN-A500
- Type
- A21N
- Flights observed
- 98
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 8881FF 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 |
|---|---|---|---|
| VJC907 | VietJet Air | 7 | 2026-05-22 |
| VJC1805 | VietJet Air | 6 | 2026-05-10 |
| VJC878 | VietJet Air | 5 | 2026-05-26 |
| VJC3900 | VietJet Air | 4 | 2026-04-24 |
| VJC879 | VietJet Air | 3 | 2026-05-27 |
| VJC869 | VietJet Air | 3 | 2026-05-13 |
| VJC843 | VietJet Air | 3 | 2026-05-14 |
| VJC814 | VietJet Air | 3 | 2026-05-25 |
| VJC985 | VietJet Air | 2 | 2026-04-16 |
| VJC969 | VietJet Air | 2 | 2026-04-16 |
| VJC968 | VietJet Air | 2 | 2026-04-15 |
| VJC928 | - | 2 | 2026-04-14 |
| VJC926 | VietJet Air | 2 | 2026-04-18 |
| VJC925 | VietJet Air | 2 | 2026-04-18 |
| VJC919 | VietJet Air | 2 | 2026-05-01 |
| VJC916 | VietJet Air | 2 | 2026-05-23 |
| VJC910 | VietJet Air | 2 | 2026-05-22 |
| VJC8892 | - | 2 | 2026-05-27 |
| VJC8890 | - | 2 | 2026-05-28 |
| VJC885 | VietJet Air | 2 | 2026-04-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | VJC720 | DAD → HPH | May 30, 03:25 UTC | May 30, 03:45 UTC | 20m |
| 2026-05-28 | VJC8893 | MFM → MFM | May 28, 14:10 UTC | May 28, 14:25 UTC | 15m |
| 2026-05-28 | VJC8890 | - | May 28, 06:45 UTC | May 28, 06:55 UTC | 10m |
| 2026-05-27 | VJC8892 | - | May 27, 12:35 UTC | May 27, 12:45 UTC | 10m |
| 2026-05-27 | VJC879 | ICN → DAD | May 27, 00:10 UTC | May 27, 02:59 UTC | 2h 50m |
| 2026-05-26 | VJC878 | DAD → ICN | May 26, 19:50 UTC | May 26, 22:54 UTC | 3h 5m |
| 2026-05-26 | VJC8892 | - | May 26, 12:54 UTC | May 26, 13:04 UTC | 10m |
| 2026-05-26 | VJC8890 | - | May 26, 06:49 UTC | May 26, 07:10 UTC | 20m |
| 2026-05-25 | VJC814 | SIN → SGN | May 25, 10:10 UTC | May 25, 10:30 UTC | 20m |
| 2026-05-25 | VJC973 | DAD → SIN | May 25, 08:35 UTC | May 25, 09:00 UTC | 25m |
| 2026-05-23 | VJC916 | SIN → HAN | May 23, 07:50 UTC | May 23, 08:10 UTC | 20m |
| 2026-05-22 | VJC910 | BOM → HAN | May 22, 19:30 UTC | May 23, 06:10 UTC | 10h 39m |
| 2026-05-22 | VJC907 | HAN → BOM | May 22, 17:35 UTC | May 22, 18:05 UTC | 30m |
| 2026-05-22 | VJC907 | HAN → BOM | May 22, 14:10 UTC | May 22, 15:50 UTC | 1h 40m |
| 2026-05-21 | VJC907 | HAN → BOM | May 21, 20:45 UTC | May 22, 15:50 UTC | 19h 5m |
| 2026-05-21 | VJC907 | HAN → BOM | May 21, 19:05 UTC | May 22, 15:50 UTC | 20h 45m |
| 2026-05-21 | VJC933 | NRT → HAN | May 21, 01:30 UTC | May 21, 15:45 UTC | 14h 15m |
| 2026-05-20 | VJC932 | HAN → NRT | May 20, 11:20 UTC | May 20, 22:20 UTC | 11h 0m |
| 2026-05-19 | VJC972 | DEL → HAN | May 19, 19:05 UTC | May 20, 10:10 UTC | 15h 6m |
| 2026-05-19 | VJC971 | HAN → DEL | May 19, 07:10 UTC | May 19, 17:15 UTC | 10h 5m |
| 2026-05-18 | VJC998 | DPS → HAN | May 18, 06:10 UTC | May 18, 11:55 UTC | 5h 45m |
| 2026-05-14 | VJC843 | TPE → SGN | May 14, 11:50 UTC | May 14, 13:01 UTC | 1h 10m |
| 2026-05-13 | VJC869 | PUS → SGN | May 13, 19:20 UTC | May 14, 10:10 UTC | 14h 50m |
| 2026-05-13 | VJC869 | PUS → SGN | May 13, 08:00 UTC | May 14, 02:10 UTC | 18h 10m |
| 2026-05-11 | VJC1806 | AMD → SGN | May 11, 20:25 UTC | May 11, 22:35 UTC | 2h 9m |
| 2026-05-11 | VJC1806 | AMD → SGN | May 11, 18:55 UTC | May 11, 19:10 UTC | 15m |
| 2026-05-10 | VJC1805 | SGN → AMD | May 10, 21:49 UTC | May 11, 16:05 UTC | 18h 15m |
| 2026-05-10 | VJC1805 | SGN → AMD | May 10, 20:54 UTC | May 11, 16:05 UTC | 19h 10m |
| 2026-05-10 | VJC1805 | SGN → AMD | May 10, 18:29 UTC | May 11, 16:05 UTC | 21h 35m |
| 2026-05-10 | VJC1801 | SGN → BLR | May 10, 07:10 UTC | May 10, 17:10 UTC | 10h 0m |
| 2026-05-10 | VJC855 | SGN → CGK | May 10, 05:40 UTC | May 10, 05:55 UTC | 15m |
| 2026-05-09 | VJC884 | BOM → SGN | May 9, 07:45 UTC | May 10, 00:00 UTC | 16h 15m |
| 2026-05-08 | VJC1802 | BLR → SGN | May 8, 18:40 UTC | May 9, 06:30 UTC | 11h 50m |
| 2026-05-08 | VJC1801 | SGN → BLR | May 8, 13:30 UTC | May 8, 17:20 UTC | 3h 50m |
| 2026-05-07 | VJC843 | TPE → SGN | May 7, 11:50 UTC | May 7, 12:55 UTC | 1h 5m |
| 2026-05-07 | VJC869 | PUS → SGN | May 7, 00:05 UTC | May 7, 10:05 UTC | 10h 0m |
| 2026-05-06 | VJC868 | SGN → PUS | May 6, 10:30 UTC | May 6, 21:10 UTC | 10h 39m |
| 2026-05-06 | VJC8664 | - | May 6, 04:05 UTC | May 6, 06:00 UTC | 1h 55m |
| 2026-05-02 | VJC1805 | SGN → AMD | May 2, 03:50 UTC | May 2, 23:05 UTC | 19h 15m |
| 2026-05-02 | VJC1805 | SGN → AMD | May 2, 01:55 UTC | May 2, 23:05 UTC | 21h 11m |
| 2026-05-01 | VJC1805 | SGN → AMD | May 1, 21:55 UTC | May 2, 21:10 UTC | 23h 15m |
| 2026-05-01 | VJC919 | PUS → CXR | May 1, 14:00 UTC | May 2, 13:45 UTC | 23h 45m |
| 2026-05-01 | VJC919 | PUS → CXR | May 1, 09:00 UTC | May 2, 04:25 UTC | 19h 25m |
| 2026-04-30 | VJC918 | CXR → PUS | Apr 30, 23:50 UTC | May 1, 23:10 UTC | 23h 20m |
| 2026-04-30 | VJC835 | ICN → CXR | Apr 30, 22:10 UTC | May 1, 14:15 UTC | 16h 5m |
| 2026-04-30 | VJC878 | DAD → ICN | Apr 30, 18:15 UTC | Apr 30, 20:55 UTC | 2h 40m |
| 2026-04-29 | VJC878 | DAD → ICN | Apr 29, 23:55 UTC | Apr 30, 20:55 UTC | 21h 0m |
| 2026-04-29 | VJC879 | ICN → DAD | Apr 29, 22:00 UTC | Apr 30, 20:55 UTC | 22h 54m |
| 2026-04-29 | VJC878 | DAD → ICN | Apr 29, 11:05 UTC | Apr 29, 20:50 UTC | 9h 45m |
| 2026-04-29 | VJC8510 | DAD → RMQ | Apr 29, 03:49 UTC | Apr 29, 09:50 UTC | 6h 1m |
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-A500 page for operator, model, and routing details .