sensors Mode-S transponder
8881F2
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A547 · AIRBUS A-321neo
- Hex
- 8881F2
- Octal
- 42100762
- Decimal
- 8,946,162
- Country
- VN
- Tail
- VN-A547
- Type
- A21N
- Flights observed
- 68
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 8881F2 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 |
|---|---|---|---|
| VJC8893 | VietJet Air | 5 | 2026-05-22 |
| VJC8891 | VietJet Air | 4 | 2026-05-10 |
| VJC8890 | - | 4 | 2026-05-25 |
| VJC935 | VietJet Air | 3 | 2026-06-01 |
| VJC921 | VietJet Air | 3 | 2026-04-26 |
| VJC878 | VietJet Air | 3 | 2026-05-24 |
| VJC1802 | VietJet Air | 3 | 2026-05-18 |
| VJC1801 | VietJet Air | 3 | 2026-05-17 |
| VJC943 | VietJet Air | 2 | 2026-05-04 |
| VJC938 | VietJet Air | 2 | 2026-05-13 |
| VJC934 | VietJet Air | 2 | 2026-06-01 |
| VJC933 | VietJet Air | 2 | 2026-06-02 |
| VJC932 | VietJet Air | 2 | 2026-06-01 |
| VJC920 | VietJet Air | 2 | 2026-04-25 |
| VJC907 | VietJet Air | 2 | 2026-04-20 |
| VJC896 | VietJet Air | 2 | 2026-05-20 |
| VJC895 | VietJet Air | 2 | 2026-05-20 |
| VJC883 | VietJet Air | 2 | 2026-06-02 |
| VJC879 | VietJet Air | 2 | 2026-05-23 |
| VJC997 | VietJet Air | 1 | 2026-04-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VJC883 | SGN → BOM | Jun 2, 18:40 UTC | Jun 2, 18:55 UTC | 15m |
| 2026-06-02 | VJC883 | SGN → BOM | Jun 2, 08:10 UTC | Jun 2, 17:25 UTC | 9h 15m |
| 2026-06-02 | VJC933 | NRT → HAN | Jun 2, 01:30 UTC | Jun 2, 06:35 UTC | 5h 5m |
| 2026-06-01 | VJC932 | HAN → NRT | Jun 1, 17:50 UTC | Jun 1, 22:45 UTC | 4h 55m |
| 2026-06-01 | VJC935 | NRT → HAN | Jun 1, 07:55 UTC | Jun 1, 13:05 UTC | 5h 10m |
| 2026-06-01 | VJC934 | HAN → NRT | Jun 1, 01:30 UTC | Jun 1, 06:30 UTC | 5h 0m |
| 2026-05-31 | VJC28 | - | May 31, 12:45 UTC | May 31, 13:30 UTC | 45m |
| 2026-05-25 | VJC8892 | - | May 25, 12:45 UTC | May 25, 12:55 UTC | 10m |
| 2026-05-25 | VJC8890 | - | May 25, 06:40 UTC | May 25, 06:50 UTC | 10m |
| 2026-05-24 | VJC878 | DAD → ICN | May 24, 18:15 UTC | May 24, 21:10 UTC | 2h 55m |
| 2026-05-24 | VJC8890 | - | May 24, 06:40 UTC | May 24, 06:50 UTC | 10m |
| 2026-05-23 | VJC879 | ICN → DAD | May 23, 23:55 UTC | May 24, 02:55 UTC | 3h 0m |
| 2026-05-23 | VJC878 | DAD → ICN | May 23, 19:45 UTC | May 23, 22:35 UTC | 2h 50m |
| 2026-05-23 | VJC8890 | - | May 23, 06:40 UTC | May 23, 06:50 UTC | 10m |
| 2026-05-22 | VJC8893 | MFM → MFM | May 22, 14:15 UTC | May 22, 14:30 UTC | 15m |
| 2026-05-22 | VJC8890 | - | May 22, 06:40 UTC | May 22, 06:50 UTC | 10m |
| 2026-05-20 | VJC896 | DEL → SGN | May 20, 19:00 UTC | May 20, 23:00 UTC | 4h 0m |
| 2026-05-20 | VJC895 | SGN → DEL | May 20, 13:25 UTC | May 20, 17:35 UTC | 4h 10m |
| 2026-05-18 | VJC1802 | BLR → SGN | May 18, 21:30 UTC | May 18, 22:45 UTC | 1h 15m |
| 2026-05-18 | VJC1802 | BLR → SGN | May 18, 19:00 UTC | May 18, 19:15 UTC | 15m |
| 2026-05-17 | VJC1801 | SGN → BLR | May 17, 22:35 UTC | May 18, 17:25 UTC | 18h 50m |
| 2026-05-17 | VJC1801 | SGN → BLR | May 17, 21:20 UTC | May 18, 17:25 UTC | 20h 5m |
| 2026-05-17 | VJC1802 | BLR → SGN | May 17, 18:50 UTC | May 17, 19:01 UTC | 10m |
| 2026-05-17 | VJC1801 | SGN → BLR | May 17, 08:20 UTC | May 17, 17:10 UTC | 8h 50m |
| 2026-05-15 | VJC896 | DEL → SGN | May 15, 19:00 UTC | May 15, 22:55 UTC | 3h 55m |
| 2026-05-15 | VJC895 | SGN → DEL | May 15, 13:30 UTC | May 15, 17:45 UTC | 4h 14m |
| 2026-05-14 | VJC939 | KIX → HAN | May 14, 00:55 UTC | May 14, 01:40 UTC | 45m |
| 2026-05-13 | VJC938 | HAN → KIX | May 13, 06:05 UTC | May 13, 22:45 UTC | 16h 40m |
| 2026-05-11 | VJC8893 | MFM → MFM | May 11, 14:15 UTC | May 11, 14:30 UTC | 15m |
| 2026-05-11 | VJC824 | KUL → DAD | May 11, 06:55 UTC | May 11, 07:10 UTC | 15m |
| 2026-05-10 | VJC827 | DAD → KUL | May 10, 14:09 UTC | May 11, 05:25 UTC | 15h 15m |
| 2026-05-10 | VJC8891 | MFM → DAD | May 10, 08:10 UTC | May 10, 08:20 UTC | 10m |
| 2026-05-09 | VJC8893 | MFM → MFM | May 9, 14:10 UTC | May 9, 14:25 UTC | 15m |
| 2026-05-09 | VJC8891 | MFM → DAD | May 9, 08:10 UTC | May 9, 08:25 UTC | 15m |
| 2026-05-08 | VJC8893 | MFM → MFM | May 8, 14:20 UTC | May 8, 14:35 UTC | 15m |
| 2026-05-08 | VJC8891 | MFM → DAD | May 8, 08:05 UTC | May 8, 08:19 UTC | 15m |
| 2026-05-07 | VJC879 | ICN → DAD | May 7, 22:10 UTC | May 8, 01:09 UTC | 2h 59m |
| 2026-05-07 | VJC878 | DAD → ICN | May 7, 18:15 UTC | May 7, 21:10 UTC | 2h 55m |
| 2026-05-07 | VJC8893 | MFM → MFM | May 7, 14:35 UTC | May 7, 14:50 UTC | 15m |
| 2026-05-07 | VJC8891 | MFM → DAD | May 7, 08:05 UTC | May 7, 08:15 UTC | 10m |
| 2026-05-04 | VJC943 | TPE → HAN | May 4, 12:00 UTC | May 4, 18:45 UTC | 6h 46m |
| 2026-05-04 | VJC942 | HAN → TPE | May 4, 00:45 UTC | May 4, 10:05 UTC | 9h 20m |
| 2026-05-03 | VJC931 | KIX → HAN | May 3, 07:00 UTC | May 3, 22:34 UTC | 15h 35m |
| 2026-05-03 | VJC930 | HAN → KIX | May 3, 04:25 UTC | May 3, 05:10 UTC | 45m |
| 2026-04-27 | VJC916 | SIN → HAN | Apr 27, 07:15 UTC | Apr 27, 07:45 UTC | 30m |
| 2026-04-26 | VJC943 | TPE → HAN | Apr 26, 11:35 UTC | Apr 27, 05:55 UTC | 18h 20m |
| 2026-04-26 | VJC921 | NGO → HAN | Apr 26, 00:55 UTC | Apr 26, 10:00 UTC | 9h 5m |
| 2026-04-25 | VJC920 | HAN → NGO | Apr 25, 22:30 UTC | Apr 25, 23:00 UTC | 30m |
| 2026-04-25 | VJC920 | HAN → NGO | Apr 25, 02:35 UTC | Apr 25, 23:00 UTC | 20h 25m |
| 2026-04-25 | VJC933 | NRT → HAN | Apr 25, 00:55 UTC | Apr 25, 23:00 UTC | 22h 5m |
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-A547 page for operator, model, and routing details .