sensors Mode-S transponder
8881F4
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A549 · AIRBUS A-321neo
- Hex
- 8881F4
- Octal
- 42100764
- Decimal
- 8,946,164
- Country
- VN
- Tail
- VN-A549
- Type
- A21N
- Flights observed
- 71
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 55m ago
Last known position
Country allocation
The ICAO 24-bit address 8881F4 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 |
|---|---|---|---|
| VJC7621 | - | 4 | 2026-06-07 |
| VJC7620 | - | 3 | 2026-06-06 |
| VJC7614 | - | 3 | 2026-05-31 |
| VJC5068 | - | 3 | 2026-06-05 |
| VJC935 | VietJet Air | 2 | 2026-05-02 |
| VJC934 | VietJet Air | 2 | 2026-05-01 |
| VJC929 | VietJet Air | 2 | 2026-06-04 |
| VJC8893 | VietJet Air | 2 | 2026-05-14 |
| VJC883 | VietJet Air | 2 | 2026-04-23 |
| VJC853 | VietJet Air | 2 | 2026-04-23 |
| VJC780 | VietJet Air | 2 | 2026-06-02 |
| VJC5069 | - | 2 | 2026-06-06 |
| VJC989 | VietJet Air | 1 | 2026-05-07 |
| VJC979 | VietJet Air | 1 | 2026-05-03 |
| VJC978 | VietJet Air | 1 | 2026-05-03 |
| VJC970 | VietJet Air | 1 | 2026-05-06 |
| VJC961 | VietJet Air | 1 | 2026-05-17 |
| VJC960 | VietJet Air | 1 | 2026-05-16 |
| VJC949 | VietJet Air | 1 | 2026-04-26 |
| VJC948 | VietJet Air | 1 | 2026-04-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-07 | VJC7621 | - | Jun 7, 02:19 UTC | Jun 7, 10:45 UTC | 8h 25m |
| 2026-06-06 | VJC7621 | - | Jun 6, 20:05 UTC | Jun 7, 01:15 UTC | 5h 10m |
| 2026-06-06 | VJC7620 | - | Jun 6, 15:25 UTC | Jun 6, 15:50 UTC | 25m |
| 2026-06-06 | VJC7620 | - | Jun 6, 10:00 UTC | Jun 6, 10:20 UTC | 20m |
| 2026-06-06 | VJC5069 | - | Jun 6, 00:40 UTC | Jun 6, 08:05 UTC | 7h 25m |
| 2026-06-05 | VJC5069 | - | Jun 5, 18:25 UTC | Jun 5, 23:30 UTC | 5h 5m |
| 2026-06-05 | VJC5068 | - | Jun 5, 16:35 UTC | Jun 5, 16:50 UTC | 15m |
| 2026-06-05 | VJC5068 | - | Jun 5, 11:05 UTC | Jun 5, 11:15 UTC | 10m |
| 2026-06-05 | VJC5068 | - | Jun 5, 05:05 UTC | Jun 5, 09:35 UTC | 4h 30m |
| 2026-06-04 | VJC1925 | HAN → AMD | Jun 4, 13:10 UTC | Jun 4, 23:05 UTC | 9h 55m |
| 2026-06-04 | VJC928 | CGK → HAN | Jun 4, 07:15 UTC | Jun 4, 11:15 UTC | 4h 0m |
| 2026-06-04 | VJC929 | HAN → CGK | Jun 4, 05:35 UTC | Jun 4, 05:55 UTC | 20m |
| 2026-06-04 | VJC929 | HAN → CGK | Jun 4, 01:50 UTC | Jun 4, 05:00 UTC | 3h 10m |
| 2026-06-03 | VJC773 | HAN → CXR | Jun 3, 09:40 UTC | Jun 3, 14:15 UTC | 4h 35m |
| 2026-06-03 | VJC198 | SGN → HAN | Jun 3, 00:55 UTC | Jun 3, 07:40 UTC | 6h 45m |
| 2026-06-02 | VJC780 | CXR → HAN | Jun 2, 15:35 UTC | Jun 2, 15:50 UTC | 15m |
| 2026-06-01 | VJC835 | ICN → CXR | Jun 1, 22:00 UTC | Jun 2, 12:25 UTC | 14h 25m |
| 2026-06-01 | VJC834 | CXR → ICN | Jun 1, 02:55 UTC | Jun 1, 20:35 UTC | 17h 40m |
| 2026-06-01 | VJC7615 | - | Jun 1, 01:15 UTC | Jun 1, 01:30 UTC | 15m |
| 2026-05-31 | VJC7614 | - | May 31, 13:30 UTC | May 31, 13:55 UTC | 25m |
| 2026-05-30 | VJC7704 | - | May 30, 18:20 UTC | May 31, 12:05 UTC | 17h 45m |
| 2026-05-30 | VJC781 | HAN → CXR | May 30, 12:10 UTC | May 30, 17:10 UTC | 5h 0m |
| 2026-05-30 | VJC772 | CXR → HAN | May 30, 09:10 UTC | May 30, 09:25 UTC | 15m |
| 2026-05-30 | VJC775 | HAN → CXR | May 30, 05:35 UTC | May 30, 06:10 UTC | 35m |
| 2026-05-30 | VJC524 | DAD → HAN | May 30, 03:30 UTC | May 30, 03:45 UTC | 15m |
| 2026-05-30 | VJC503 | HAN → DAD | May 30, 01:00 UTC | May 30, 01:20 UTC | 20m |
| 2026-05-29 | VJC780 | CXR → HAN | May 29, 07:30 UTC | May 29, 15:30 UTC | 8h 0m |
| 2026-05-28 | VJC7614 | - | May 28, 21:30 UTC | May 29, 06:05 UTC | 8h 35m |
| 2026-05-28 | VJC7614 | - | May 28, 18:50 UTC | May 28, 19:10 UTC | 20m |
| 2026-05-28 | VJC7621 | - | May 28, 02:25 UTC | May 28, 17:40 UTC | 15h 15m |
| 2026-05-27 | VJC7621 | - | May 27, 20:00 UTC | May 28, 01:30 UTC | 5h 30m |
| 2026-05-27 | VJC7620 | - | May 27, 15:20 UTC | May 27, 15:35 UTC | 15m |
| 2026-05-19 | VJC7706 | HAN → KHV | May 19, 12:00 UTC | May 20, 04:25 UTC | 16h 25m |
| 2026-05-17 | VJC961 | ICN → HAN | May 17, 02:20 UTC | May 17, 02:45 UTC | 25m |
| 2026-05-16 | VJC960 | HAN → ICN | May 16, 22:05 UTC | May 16, 22:50 UTC | 45m |
| 2026-05-14 | VJC8893 | MFM → MFM | May 14, 14:10 UTC | May 14, 14:20 UTC | 10m |
| 2026-05-13 | VJC933 | NRT → HAN | May 13, 00:50 UTC | May 13, 02:15 UTC | 1h 25m |
| 2026-05-12 | VJC932 | HAN → NRT | May 12, 21:15 UTC | May 12, 22:45 UTC | 1h 30m |
| 2026-05-11 | VJC829 | KIX → SGN | May 11, 01:00 UTC | May 11, 04:20 UTC | 3h 20m |
| 2026-05-10 | VJC828 | SGN → KIX | May 10, 08:00 UTC | May 10, 23:19 UTC | 15h 20m |
| 2026-05-08 | VJC3909 | CAN → SGN | May 8, 20:15 UTC | May 8, 20:40 UTC | 25m |
| 2026-05-08 | VJC3908 | SGN → CAN | May 8, 18:05 UTC | May 8, 18:40 UTC | 35m |
| 2026-05-08 | VJC814 | SIN → SGN | May 8, 10:09 UTC | May 8, 10:25 UTC | 15m |
| 2026-05-07 | VJC989 | PUS → DAD | May 7, 19:10 UTC | May 8, 08:19 UTC | 13h 10m |
| 2026-05-06 | VJC2987 | - | May 6, 18:15 UTC | May 6, 18:30 UTC | 15m |
| 2026-05-06 | VJC970 | SIN → DAD | May 6, 03:35 UTC | May 6, 16:25 UTC | 12h 50m |
| 2026-05-06 | VJC813 | SGN → SIN | May 6, 01:50 UTC | May 6, 02:01 UTC | 10m |
| 2026-05-04 | VJC861 | ICN → SGN | May 4, 12:25 UTC | May 4, 15:35 UTC | 3h 10m |
| 2026-05-03 | VJC979 | ICN → PQC | May 3, 19:15 UTC | May 4, 10:10 UTC | 14h 55m |
| 2026-05-03 | VJC978 | PQC → ICN | May 3, 02:25 UTC | May 3, 18:00 UTC | 15h 34m |
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-A549 page for operator, model, and routing details .