sensors Mode-S transponder
888174
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A661 · AIRBUS A-321
- Hex
- 888174
- Octal
- 42100564
- Decimal
- 8,946,036
- Country
- VN
- Tail
- VN-A661
- Type
- A321
- Flights observed
- 66
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 888174 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 |
|---|---|---|---|
| VJC879 | VietJet Air | 5 | 2026-05-04 |
| VJC989 | VietJet Air | 4 | 2026-04-17 |
| VJC878 | VietJet Air | 4 | 2026-05-04 |
| VJC814 | VietJet Air | 4 | 2026-04-17 |
| VJC803 | VietJet Air | 3 | 2026-05-04 |
| VJC7815 | - | 3 | 2026-05-06 |
| VJC126 | VietJet Air | 3 | 2026-06-02 |
| VJC988 | - | 2 | 2026-04-16 |
| VJC973 | VietJet Air | 2 | 2026-04-17 |
| VJC970 | VietJet Air | 2 | 2026-04-18 |
| VJC949 | VietJet Air | 2 | 2026-05-07 |
| VJC948 | VietJet Air | 2 | 2026-05-07 |
| VJC813 | VietJet Air | 2 | 2026-04-18 |
| VJC8020 | VietJet Air | 2 | 2026-04-23 |
| VJC961 | VietJet Air | 1 | 2026-05-08 |
| VJC943 | VietJet Air | 1 | 2026-05-31 |
| VJC942 | VietJet Air | 1 | 2026-05-31 |
| VJC916 | VietJet Air | 1 | 2026-05-09 |
| VJC8893 | VietJet Air | 1 | 2026-04-26 |
| VJC8890 | - | 1 | 2026-04-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VJC126 | SGN → HAN | Jun 2, 16:35 UTC | Jun 3, 02:30 UTC | 9h 55m |
| 2026-06-02 | VJC193 | HAN → SGN | Jun 2, 10:05 UTC | Jun 2, 15:05 UTC | 5h 0m |
| 2026-06-02 | VJC131 | HAN → SGN | Jun 2, 03:50 UTC | Jun 2, 08:25 UTC | 4h 35m |
| 2026-06-02 | VJC126 | SGN → HAN | Jun 2, 02:15 UTC | Jun 2, 02:40 UTC | 25m |
| 2026-06-01 | VJC126 | SGN → HAN | Jun 1, 06:20 UTC | Jun 2, 02:40 UTC | 20h 20m |
| 2026-05-31 | VJC943 | TPE → HAN | May 31, 11:45 UTC | May 31, 14:10 UTC | 2h 25m |
| 2026-05-31 | VJC942 | HAN → TPE | May 31, 08:45 UTC | May 31, 10:10 UTC | 1h 25m |
| 2026-05-30 | VJC456 | PQC → HAN | May 30, 10:25 UTC | May 30, 10:45 UTC | 20m |
| 2026-05-30 | VJC453 | HAN → PQC | May 30, 06:15 UTC | May 30, 06:35 UTC | 20m |
| 2026-05-09 | VJC916 | SIN → HAN | May 9, 07:25 UTC | May 9, 07:35 UTC | 10m |
| 2026-05-08 | VJC961 | ICN → HAN | May 8, 02:09 UTC | May 8, 02:49 UTC | 40m |
| 2026-05-07 | VJC949 | RMQ → HAN | May 7, 10:20 UTC | May 7, 11:25 UTC | 1h 5m |
| 2026-05-07 | VJC948 | HAN → RMQ | May 7, 08:40 UTC | May 7, 09:00 UTC | 20m |
| 2026-05-06 | VJC7816 | - | May 6, 17:40 UTC | May 7, 08:05 UTC | 14h 25m |
| 2026-05-06 | VJC7815 | - | May 6, 15:30 UTC | May 6, 16:20 UTC | 50m |
| 2026-05-05 | VJC7815 | - | May 5, 19:05 UTC | May 6, 16:20 UTC | 21h 15m |
| 2026-05-05 | VJC7815 | - | May 5, 18:55 UTC | May 6, 16:20 UTC | 21h 25m |
| 2026-05-04 | VJC879 | ICN → DAD | May 4, 23:55 UTC | May 5, 17:30 UTC | 17h 35m |
| 2026-05-04 | VJC879 | ICN → DAD | May 4, 22:10 UTC | May 5, 17:30 UTC | 19h 20m |
| 2026-05-04 | VJC878 | DAD → ICN | May 4, 07:10 UTC | May 4, 20:55 UTC | 13h 46m |
| 2026-05-04 | VJC803 | SGN → BKK | May 4, 05:05 UTC | May 4, 05:45 UTC | 40m |
| 2026-05-03 | VJC803 | SGN → BKK | May 3, 07:15 UTC | May 4, 05:45 UTC | 22h 30m |
| 2026-05-03 | VJC803 | SGN → BKK | May 3, 04:50 UTC | May 3, 05:30 UTC | 40m |
| 2026-05-01 | VJC3909 | CAN → SGN | May 1, 19:10 UTC | May 1, 19:20 UTC | 10m |
| 2026-05-01 | VJC3908 | SGN → CAN | May 1, 17:10 UTC | May 1, 17:30 UTC | 20m |
| 2026-05-01 | VJC7079 | MFM → HPH | May 1, 08:30 UTC | May 1, 08:40 UTC | 10m |
| 2026-04-27 | VJC949 | RMQ → HAN | Apr 27, 10:25 UTC | Apr 27, 11:45 UTC | 1h 20m |
| 2026-04-27 | VJC948 | HAN → RMQ | Apr 27, 07:55 UTC | Apr 27, 09:00 UTC | 1h 5m |
| 2026-04-26 | VJC8893 | MFM → MFM | Apr 26, 14:35 UTC | Apr 26, 14:50 UTC | 15m |
| 2026-04-25 | VJC879 | ICN → DAD | Apr 25, 22:00 UTC | Apr 26, 01:05 UTC | 3h 5m |
| 2026-04-25 | VJC878 | DAD → ICN | Apr 25, 18:15 UTC | Apr 25, 20:40 UTC | 2h 25m |
| 2026-04-25 | VJC642 | SGN → DAD | Apr 25, 13:00 UTC | Apr 25, 13:10 UTC | 10m |
| 2026-04-25 | - | - | Apr 25, 11:35 UTC | Apr 25, 11:45 UTC | 10m |
| 2026-04-24 | VJC8511 | - | Apr 24, 11:15 UTC | Apr 24, 12:05 UTC | 50m |
| 2026-04-23 | VJC8510 | DAD → RMQ | Apr 23, 19:45 UTC | Apr 24, 09:45 UTC | 14h 0m |
| 2026-04-23 | VJC8020 | DAD → MNL | Apr 23, 17:40 UTC | Apr 23, 18:20 UTC | 40m |
| 2026-04-22 | VJC8020 | DAD → MNL | Apr 22, 19:05 UTC | Apr 23, 18:20 UTC | 23h 15m |
| 2026-04-22 | VJC2855 | - | Apr 22, 18:40 UTC | Apr 22, 19:10 UTC | 30m |
| 2026-04-22 | VJC2854 | - | Apr 22, 16:50 UTC | Apr 22, 17:25 UTC | 35m |
| 2026-04-20 | VJC480 | VCA → VII | Apr 20, 08:50 UTC | Apr 20, 12:10 UTC | 3h 20m |
| 2026-04-20 | VJC703 | DAD → VCA | Apr 20, 07:35 UTC | Apr 20, 07:45 UTC | 10m |
| 2026-04-19 | VJC646 | - | Apr 19, 14:10 UTC | Apr 19, 14:20 UTC | 10m |
| 2026-04-18 | VJC714 | PQC → DAD | Apr 18, 10:10 UTC | Apr 18, 10:20 UTC | 10m |
| 2026-04-18 | VJC715 | DAD → PQC | Apr 18, 08:20 UTC | Apr 18, 08:35 UTC | 15m |
| 2026-04-18 | VJC970 | SIN → DAD | Apr 18, 04:45 UTC | Apr 18, 05:00 UTC | 15m |
| 2026-04-18 | VJC970 | SIN → DAD | Apr 18, 03:35 UTC | Apr 18, 05:00 UTC | 1h 25m |
| 2026-04-18 | VJC813 | SGN → SIN | Apr 18, 01:35 UTC | Apr 18, 02:10 UTC | 35m |
| 2026-04-18 | VJC813 | SGN → SIN | Apr 18, 00:35 UTC | Apr 18, 00:55 UTC | 20m |
| 2026-04-17 | VJC814 | SIN → SGN | Apr 17, 11:40 UTC | Apr 17, 12:00 UTC | 20m |
| 2026-04-17 | VJC814 | SIN → SGN | Apr 17, 10:30 UTC | Apr 17, 10:45 UTC | 15m |
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-A661 page for operator, model, and routing details .