sensors Mode-S transponder
88811B
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A671 · AIRBUS A-320
- Hex
- 88811B
- Octal
- 42100433
- Decimal
- 8,945,947
- Country
- VN
- Tail
- VN-A671
- Type
- A320
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 88811B 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 |
|---|---|---|---|
| VJC806 | VietJet Air | 4 | 2026-07-03 |
| VJC805 | - | 4 | 2026-07-03 |
| VJC801 | - | 4 | 2026-06-12 |
| VJC766 | - | 4 | 2026-06-30 |
| VJC137 | - | 4 | 2026-07-02 |
| VJC767 | - | 3 | 2026-06-30 |
| VJC802 | VietJet Air | 2 | 2026-06-13 |
| VJC775 | VietJet Air | 2 | 2026-06-26 |
| VJC461 | VietJet Air | 2 | 2026-06-18 |
| VJC449 | VietJet Air | 2 | 2026-06-25 |
| VJC247 | VietJet Air | 2 | 2026-06-20 |
| VJC1981 | VietJet Air | 2 | 2026-06-25 |
| VJC1980 | VietJet Air | 2 | 2026-06-24 |
| VJC125 | - | 2 | 2026-06-29 |
| VJC953 | VietJet Air | 1 | 2026-05-26 |
| VJC952 | VietJet Air | 1 | 2026-05-26 |
| VJC906 | VietJet Air | 1 | 2026-05-21 |
| VJC905 | VietJet Air | 1 | 2026-05-21 |
| VJC904 | VietJet Air | 1 | 2026-06-25 |
| VJC903 | VietJet Air | 1 | 2026-06-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-04 | VJC465 | - | Jul 4, 11:30 UTC | Jul 4, 15:55 UTC | 4h 25m |
| 2026-07-04 | VJC772 | - | Jul 4, 05:30 UTC | Jul 4, 10:15 UTC | 4h 45m |
| 2026-07-03 | VJC450 | - | Jul 3, 23:55 UTC | Jul 4, 04:15 UTC | 4h 20m |
| 2026-07-03 | VJC806 | BKK → SGN | Jul 3, 13:10 UTC | Jul 3, 19:35 UTC | 6h 25m |
| 2026-07-03 | VJC805 | - | Jul 3, 11:05 UTC | Jul 3, 11:45 UTC | 40m |
| 2026-07-02 | VJC137 | - | Jul 2, 08:00 UTC | Jul 2, 08:25 UTC | 25m |
| 2026-07-02 | VJC128 | - | Jul 2, 00:40 UTC | Jul 2, 06:35 UTC | 5h 55m |
| 2026-07-01 | VJC160 | - | Jul 1, 15:40 UTC | Jul 1, 16:00 UTC | 20m |
| 2026-06-30 | VJC767 | - | Jun 30, 08:50 UTC | Jun 30, 09:10 UTC | 20m |
| 2026-06-30 | VJC766 | - | Jun 30, 07:25 UTC | Jun 30, 07:55 UTC | 30m |
| 2026-06-29 | VJC137 | - | Jun 29, 05:59 UTC | Jun 29, 06:24 UTC | 25m |
| 2026-06-29 | VJC125 | - | Jun 29, 00:29 UTC | Jun 29, 04:45 UTC | 4h 15m |
| 2026-06-28 | VJC141 | HAN → SGN | Jun 28, 12:19 UTC | Jun 28, 17:04 UTC | 4h 45m |
| 2026-06-28 | VJC530 | - | Jun 28, 09:25 UTC | Jun 28, 09:50 UTC | 25m |
| 2026-06-28 | VJC505 | HAN → DAD | Jun 28, 02:25 UTC | Jun 28, 02:54 UTC | 30m |
| 2026-06-27 | VJC1785 | HAN → CXR | Jun 27, 13:55 UTC | Jun 27, 17:59 UTC | 4h 5m |
| 2026-06-27 | VJC439 | - | Jun 27, 09:04 UTC | Jun 27, 12:25 UTC | 3h 20m |
| 2026-06-27 | VJC437 | HAN → UIH | Jun 27, 04:00 UTC | Jun 27, 07:19 UTC | 3h 20m |
| 2026-06-26 | VJC431 | - | Jun 26, 23:25 UTC | Jun 27, 02:45 UTC | 3h 20m |
| 2026-06-26 | VJC153 | HAN → SGN | Jun 26, 11:34 UTC | Jun 26, 16:30 UTC | 4h 55m |
| 2026-06-26 | VJC775 | HAN → CXR | Jun 26, 05:50 UTC | Jun 26, 09:45 UTC | 3h 55m |
| 2026-06-25 | VJC449 | HAN → PQC | Jun 25, 23:59 UTC | Jun 26, 04:39 UTC | 4h 40m |
| 2026-06-25 | VJC904 | BKK → HAN | Jun 25, 12:19 UTC | Jun 25, 14:09 UTC | 1h 50m |
| 2026-06-25 | VJC903 | HAN → BKK | Jun 25, 09:10 UTC | Jun 25, 11:10 UTC | 2h 0m |
| 2026-06-25 | VJC1981 | FSZ → HAN | Jun 25, 02:05 UTC | Jun 25, 06:55 UTC | 4h 50m |
| 2026-06-24 | VJC1980 | HAN → FSZ | Jun 24, 19:44 UTC | Jun 25, 00:14 UTC | 4h 30m |
| 2026-06-24 | VJC150 | SGN → HAN | Jun 24, 09:09 UTC | Jun 24, 15:14 UTC | 6h 5m |
| 2026-06-24 | VJC766 | PQC → HPH | Jun 24, 07:50 UTC | Jun 24, 08:09 UTC | 20m |
| 2026-06-24 | VJC127 | HAN → SGN | Jun 24, 01:34 UTC | Jun 24, 01:55 UTC | 20m |
| 2026-06-23 | VJC195 | HAN → SGN | Jun 23, 05:00 UTC | Jun 23, 23:59 UTC | 19h 0m |
| 2026-06-23 | VJC190 | SGN → HAN | Jun 23, 03:15 UTC | Jun 23, 03:34 UTC | 20m |
| 2026-06-20 | VJC247 | THD → SGN | Jun 20, 07:39 UTC | Jun 20, 07:49 UTC | 10m |
| 2026-06-19 | VJC169 | HAN → SGN | Jun 19, 16:34 UTC | Jun 19, 17:09 UTC | 35m |
| 2026-06-19 | VJC767 | HPH → PQC | Jun 19, 08:54 UTC | Jun 19, 15:24 UTC | 6h 30m |
| 2026-06-19 | VJC766 | PQC → HPH | Jun 19, 07:29 UTC | Jun 19, 07:49 UTC | 20m |
| 2026-06-19 | VJC241 | THD → SGN | Jun 19, 01:29 UTC | Jun 19, 01:39 UTC | 10m |
| 2026-06-18 | VJC137 | HAN → SGN | Jun 18, 06:30 UTC | Jun 18, 06:55 UTC | 25m |
| 2026-06-18 | VJC461 | HAN → VCA | Jun 18, 00:30 UTC | Jun 18, 05:15 UTC | 4h 45m |
| 2026-06-17 | VJC168 | SGN → HAN | Jun 17, 19:05 UTC | Jun 17, 19:30 UTC | 25m |
| 2026-06-15 | VJC806 | BKK → SGN | Jun 15, 13:20 UTC | Jun 15, 13:50 UTC | 30m |
| 2026-06-15 | VJC805 | - | Jun 15, 11:05 UTC | Jun 15, 11:49 UTC | 45m |
| 2026-06-13 | VJC802 | BKK → SGN | Jun 13, 04:35 UTC | Jun 13, 05:10 UTC | 35m |
| 2026-06-12 | VJC801 | - | Jun 12, 09:10 UTC | Jun 13, 03:15 UTC | 18h 5m |
| 2026-06-12 | VJC801 | - | Jun 12, 04:50 UTC | Jun 13, 03:15 UTC | 22h 25m |
| 2026-06-12 | VJC3674 | - | Jun 12, 04:40 UTC | Jun 13, 02:45 UTC | 22h 5m |
| 2026-06-11 | VJC801 | - | Jun 11, 14:40 UTC | Jun 12, 03:10 UTC | 12h 31m |
| 2026-06-11 | VJC247 | THD → SGN | Jun 11, 07:15 UTC | Jun 11, 07:25 UTC | 10m |
| 2026-06-10 | VJC167 | HAN → SGN | Jun 10, 16:00 UTC | Jun 10, 16:25 UTC | 25m |
| 2026-06-10 | VJC1431 | HAN → UIH | Jun 10, 11:05 UTC | Jun 10, 14:15 UTC | 3h 10m |
| 2026-06-10 | VJC775 | HAN → CXR | Jun 10, 05:05 UTC | Jun 10, 09:00 UTC | 3h 55m |
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-A671 page for operator, model, and routing details .