sensors Mode-S transponder
888173
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A629 · AIRBUS A-321
- Hex
- 888173
- Octal
- 42100563
- Decimal
- 8,946,035
- Country
- VN
- Tail
- VN-A629
- Type
- A321
- Flights observed
- 58
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 888173 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 |
|---|---|---|---|
| VJC926 | VietJet Air | 5 | 2026-05-25 |
| VJC925 | VietJet Air | 4 | 2026-05-25 |
| VJC835 | VietJet Air | 3 | 2026-04-19 |
| VJC834 | VietJet Air | 3 | 2026-04-19 |
| VJC813 | VietJet Air | 3 | 2026-04-25 |
| VJC7079 | VietJet Air | 3 | 2026-05-27 |
| VJC970 | VietJet Air | 2 | 2026-04-25 |
| VJC960 | VietJet Air | 2 | 2026-04-27 |
| VJC918 | VietJet Air | 2 | 2026-04-20 |
| VJC902 | VietJet Air | 2 | 2026-05-29 |
| VJC901 | VietJet Air | 2 | 2026-05-29 |
| VJC7078 | - | 2 | 2026-05-27 |
| VJC973 | VietJet Air | 1 | 2026-04-13 |
| VJC949 | VietJet Air | 1 | 2026-04-24 |
| VJC948 | VietJet Air | 1 | 2026-04-23 |
| VJC947 | VietJet Air | 1 | 2026-04-28 |
| VJC946 | VietJet Air | 1 | 2026-04-28 |
| VJC919 | VietJet Air | 1 | 2026-04-21 |
| VJC916 | VietJet Air | 1 | 2026-05-01 |
| VJC915 | VietJet Air | 1 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | VJC447 | HAN → PQC | May 30, 02:06 UTC | May 30, 02:25 UTC | 19m |
| 2026-05-29 | VJC7816 | - | May 29, 17:45 UTC | May 29, 20:25 UTC | 2h 40m |
| 2026-05-29 | VJC7815 | - | May 29, 13:40 UTC | May 29, 16:35 UTC | 2h 55m |
| 2026-05-29 | VJC902 | BKK → HAN | May 29, 07:30 UTC | May 29, 08:55 UTC | 1h 25m |
| 2026-05-29 | VJC901 | HAN → BKK | May 29, 04:20 UTC | May 29, 05:45 UTC | 1h 25m |
| 2026-05-28 | VJC131 | HAN → SGN | May 28, 03:35 UTC | May 28, 03:55 UTC | 20m |
| 2026-05-28 | VJC126 | SGN → HAN | May 28, 02:10 UTC | May 28, 02:30 UTC | 20m |
| 2026-05-27 | VJC859 | MNL → SGN | May 27, 19:50 UTC | May 27, 20:15 UTC | 25m |
| 2026-05-27 | VJC858 | SGN → MNL | May 27, 17:35 UTC | May 27, 18:20 UTC | 45m |
| 2026-05-27 | VJC273 | HPH → SGN | May 27, 11:15 UTC | May 27, 11:30 UTC | 15m |
| 2026-05-27 | VJC7079 | MFM → HPH | May 27, 08:10 UTC | May 27, 08:20 UTC | 10m |
| 2026-05-27 | VJC7078 | - | May 27, 06:49 UTC | May 27, 07:00 UTC | 11m |
| 2026-05-25 | VJC925 | ICN → HPH | May 25, 22:30 UTC | May 25, 23:00 UTC | 30m |
| 2026-05-25 | VJC926 | HPH → ICN | May 25, 20:24 UTC | May 25, 20:59 UTC | 35m |
| 2026-05-25 | VJC7079 | MFM → HPH | May 25, 08:10 UTC | May 25, 08:25 UTC | 15m |
| 2026-05-23 | VJC925 | ICN → HPH | May 23, 22:30 UTC | May 23, 22:55 UTC | 25m |
| 2026-05-23 | VJC926 | HPH → ICN | May 23, 20:20 UTC | May 23, 20:55 UTC | 35m |
| 2026-05-22 | VJC925 | ICN → HPH | May 22, 22:45 UTC | May 22, 23:10 UTC | 25m |
| 2026-05-22 | VJC926 | HPH → ICN | May 22, 20:25 UTC | May 22, 21:00 UTC | 35m |
| 2026-05-03 | VJC854 | CGK → SGN | May 3, 08:50 UTC | May 3, 21:20 UTC | 12h 30m |
| 2026-05-03 | VJC855 | SGN → CGK | May 3, 07:05 UTC | May 3, 07:25 UTC | 20m |
| 2026-05-01 | VJC916 | SIN → HAN | May 1, 07:10 UTC | May 1, 07:35 UTC | 25m |
| 2026-05-01 | VJC915 | HAN → SIN | May 1, 05:15 UTC | May 1, 05:25 UTC | 10m |
| 2026-04-28 | VJC947 | KHH → HAN | Apr 28, 11:05 UTC | Apr 28, 12:05 UTC | 1h 0m |
| 2026-04-28 | VJC946 | HAN → KHH | Apr 28, 02:15 UTC | Apr 28, 10:10 UTC | 7h 55m |
| 2026-04-27 | VJC960 | HAN → ICN | Apr 27, 22:00 UTC | Apr 27, 22:45 UTC | 45m |
| 2026-04-26 | VJC960 | HAN → ICN | Apr 26, 23:50 UTC | Apr 27, 22:45 UTC | 22h 55m |
| 2026-04-25 | VJC8021 | - | Apr 25, 20:00 UTC | Apr 25, 20:35 UTC | 35m |
| 2026-04-25 | VJC970 | SIN → DAD | Apr 25, 03:45 UTC | Apr 25, 18:30 UTC | 14h 45m |
| 2026-04-25 | VJC813 | SGN → SIN | Apr 25, 01:55 UTC | Apr 25, 02:20 UTC | 25m |
| 2026-04-24 | VJC949 | RMQ → HAN | Apr 24, 10:25 UTC | Apr 24, 11:35 UTC | 1h 10m |
| 2026-04-23 | VJC948 | HAN → RMQ | Apr 23, 23:45 UTC | Apr 24, 08:50 UTC | 9h 5m |
| 2026-04-22 | VJC151 | HAN → SGN | Apr 22, 12:45 UTC | Apr 22, 13:00 UTC | 15m |
| 2026-04-22 | VJC902 | BKK → HAN | Apr 22, 08:30 UTC | Apr 22, 09:25 UTC | 55m |
| 2026-04-22 | VJC901 | HAN → BKK | Apr 22, 06:01 UTC | Apr 22, 07:00 UTC | 1h 0m |
| 2026-04-21 | VJC919 | PUS → CXR | Apr 21, 02:40 UTC | Apr 21, 05:15 UTC | 2h 35m |
| 2026-04-20 | VJC918 | CXR → PUS | Apr 20, 22:00 UTC | Apr 20, 23:05 UTC | 1h 5m |
| 2026-04-20 | VJC918 | CXR → PUS | Apr 20, 00:50 UTC | Apr 20, 23:05 UTC | 22h 15m |
| 2026-04-19 | VJC835 | ICN → CXR | Apr 19, 23:35 UTC | Apr 20, 22:45 UTC | 23h 10m |
| 2026-04-19 | VJC835 | ICN → CXR | Apr 19, 22:00 UTC | Apr 20, 00:50 UTC | 2h 50m |
| 2026-04-19 | VJC834 | CXR → ICN | Apr 19, 10:20 UTC | Apr 19, 20:35 UTC | 10h 15m |
| 2026-04-18 | VJC835 | ICN → CXR | Apr 18, 21:55 UTC | Apr 19, 08:55 UTC | 11h 0m |
| 2026-04-18 | VJC834 | CXR → ICN | Apr 18, 17:40 UTC | Apr 18, 20:15 UTC | 2h 35m |
| 2026-04-17 | VJC834 | CXR → ICN | Apr 17, 23:40 UTC | Apr 18, 20:15 UTC | 20h 35m |
| 2026-04-17 | VJC714 | PQC → DAD | Apr 17, 10:35 UTC | Apr 17, 10:45 UTC | 10m |
| 2026-04-17 | VJC715 | DAD → PQC | Apr 17, 08:15 UTC | Apr 17, 08:30 UTC | 15m |
| 2026-04-17 | VJC970 | SIN → DAD | Apr 17, 03:30 UTC | Apr 17, 05:00 UTC | 1h 31m |
| 2026-04-17 | VJC813 | SGN → SIN | Apr 17, 01:40 UTC | Apr 17, 01:50 UTC | 10m |
| 2026-04-17 | VJC813 | SGN → SIN | Apr 17, 00:35 UTC | Apr 17, 00:55 UTC | 20m |
| 2026-04-16 | VJC7079 | MFM → HPH | Apr 16, 09:45 UTC | Apr 16, 09:54 UTC | 10m |
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-A629 page for operator, model, and routing details .