sensors Mode-S transponder
888158
ICAO 24-bit transponder address · allocated to Vietnam
Currently assigned to VN-A653 · AIRBUS A-321neo
- Hex
- 888158
- Octal
- 42100530
- Decimal
- 8,946,008
- Country
- VN
- Tail
- VN-A653
- Type
- A21N
- Flights observed
- 249
- Distinct callsigns
- 20
- Country
- VN
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 888158 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 |
|---|---|---|---|
| VJC822 | - | 30 | 2026-07-09 |
| VJC820 | - | 25 | 2026-07-13 |
| VJC91 | - | 20 | 2026-07-13 |
| VJC821 | - | 20 | 2026-07-13 |
| VJC823 | - | 18 | 2026-07-08 |
| VJC92 | - | 15 | 2026-07-12 |
| VJC826 | VietJet Air | 10 | 2026-05-26 |
| VJC825 | - | 10 | 2026-06-24 |
| VJC829 | VietJet Air | 6 | 2026-05-21 |
| VJC862 | VietJet Air | 5 | 2026-06-01 |
| VJC852 | - | 5 | 2026-06-30 |
| VJC803 | - | 5 | 2026-06-27 |
| VJC979 | VietJet Air | 4 | 2026-06-19 |
| VJC978 | VietJet Air | 4 | 2026-06-19 |
| VJC876 | - | 4 | 2026-06-17 |
| VJC855 | - | 4 | 2026-06-19 |
| VJC853 | VietJet Air | 4 | 2026-06-13 |
| VJC886 | - | 3 | 2026-06-27 |
| VJC828 | VietJet Air | 3 | 2026-05-20 |
| VJC879 | - | 2 | 2026-06-21 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | VJC821 | - | Jul 13, 19:05 UTC | Jul 13, 22:25 UTC | 3h 20m |
| 2026-07-13 | VJC820 | PER → HND | Jul 13, 03:15 UTC | Jul 13, 17:25 UTC | 14h 10m |
| 2026-07-13 | VJC91 | - | Jul 13, 00:01 UTC | Jul 13, 00:40 UTC | 40m |
| 2026-07-12 | VJC806 | BKK → SGN | Jul 12, 14:25 UTC | Jul 12, 14:35 UTC | 10m |
| 2026-07-12 | VJC92 | - | Jul 12, 02:45 UTC | Jul 12, 12:45 UTC | 10h 0m |
| 2026-07-11 | VJC91 | - | Jul 11, 19:45 UTC | Jul 12, 00:45 UTC | 5h 0m |
| 2026-07-11 | VJC91 | KKZ → PER | Jul 11, 02:55 UTC | Jul 12, 00:45 UTC | 21h 50m |
| 2026-07-10 | VJC809 | - | Jul 10, 21:20 UTC | Jul 11, 19:45 UTC | 22h 25m |
| 2026-07-10 | VJC821 | - | Jul 10, 17:45 UTC | Jul 11, 03:30 UTC | 9h 45m |
| 2026-07-10 | VJC820 | NRT → HND | Jul 10, 01:20 UTC | Jul 10, 15:45 UTC | 14h 25m |
| 2026-07-09 | VJC822 | - | Jul 9, 07:25 UTC | Jul 9, 23:40 UTC | 16h 15m |
| 2026-07-09 | VJC822 | PER → NRT | Jul 9, 02:55 UTC | Jul 9, 23:40 UTC | 20h 45m |
| 2026-07-08 | VJC91 | - | Jul 8, 15:50 UTC | Jul 9, 01:10 UTC | 9h 20m |
| 2026-07-08 | VJC823 | - | Jul 8, 00:20 UTC | Jul 8, 14:30 UTC | 14h 10m |
| 2026-07-07 | VJC822 | - | Jul 7, 08:15 UTC | Jul 7, 22:25 UTC | 14h 10m |
| 2026-07-06 | VJC92 | - | Jul 6, 04:05 UTC | Jul 6, 09:15 UTC | 5h 10m |
| 2026-07-05 | VJC91 | - | Jul 5, 07:25 UTC | Jul 6, 00:35 UTC | 17h 10m |
| 2026-07-05 | VJC92 | PER → PER | Jul 5, 02:45 UTC | Jul 6, 00:35 UTC | 21h 50m |
| 2026-07-04 | VJC91 | - | Jul 4, 21:10 UTC | Jul 5, 00:45 UTC | 3h 35m |
| 2026-07-04 | VJC823 | - | Jul 4, 00:40 UTC | Jul 4, 04:25 UTC | 3h 45m |
| 2026-07-03 | VJC822 | - | Jul 3, 07:45 UTC | Jul 3, 23:05 UTC | 15h 20m |
| 2026-07-03 | VJC822 | - | Jul 3, 03:00 UTC | Jul 3, 23:05 UTC | 20h 5m |
| 2026-07-03 | VJC92 | PER → PER | Jul 3, 02:50 UTC | Jul 3, 02:55 UTC | 5m |
| 2026-07-02 | VJC91 | - | Jul 2, 23:55 UTC | Jul 3, 00:35 UTC | 40m |
| 2026-07-02 | VJC92 | - | Jul 2, 02:50 UTC | Jul 2, 08:00 UTC | 5h 10m |
| 2026-07-01 | VJC91 | - | Jul 1, 13:05 UTC | Jul 2, 00:35 UTC | 11h 30m |
| 2026-07-01 | VJC885 | - | Jul 1, 04:50 UTC | Jul 1, 11:45 UTC | 6h 55m |
| 2026-06-30 | VJC1803 | SGN → HYD | Jun 30, 08:05 UTC | Jul 1, 03:45 UTC | 19h 40m |
| 2026-06-30 | VJC852 | - | Jun 30, 06:15 UTC | Jun 30, 06:45 UTC | 30m |
| 2026-06-29 | VJC253 | - | Jun 29, 09:14 UTC | Jun 29, 09:25 UTC | 10m |
| 2026-06-29 | VJC131 | - | Jun 29, 03:49 UTC | Jun 29, 04:09 UTC | 20m |
| 2026-06-28 | VJC821 | - | Jun 28, 17:55 UTC | Jun 29, 02:35 UTC | 8h 40m |
| 2026-06-28 | VJC820 | KHH → HND | Jun 28, 04:55 UTC | Jun 28, 16:09 UTC | 11h 15m |
| 2026-06-27 | VJC886 | - | Jun 27, 13:15 UTC | Jun 28, 03:50 UTC | 14h 35m |
| 2026-06-27 | VJC805 | - | Jun 27, 07:19 UTC | Jun 27, 12:04 UTC | 4h 45m |
| 2026-06-27 | VJC803 | - | Jun 27, 05:25 UTC | Jun 27, 06:15 UTC | 50m |
| 2026-06-26 | VJC803 | - | Jun 26, 10:05 UTC | Jun 27, 06:15 UTC | 20h 10m |
| 2026-06-26 | VJC803 | - | Jun 26, 09:59 UTC | Jun 27, 06:15 UTC | 20h 15m |
| 2026-06-26 | VJC278 | SGN → HPH | Jun 26, 08:45 UTC | Jun 26, 09:05 UTC | 20m |
| 2026-06-25 | VJC723 | HPH → DAD | Jun 25, 12:54 UTC | Jun 25, 13:20 UTC | 25m |
| 2026-06-25 | VJC722 | DAD → HPH | Jun 25, 11:30 UTC | Jun 25, 11:44 UTC | 15m |
| 2026-06-25 | VJC131 | HAN → SGN | Jun 25, 04:04 UTC | Jun 25, 04:29 UTC | 25m |
| 2026-06-24 | VJC821 | - | Jun 24, 17:29 UTC | Jun 25, 02:45 UTC | 9h 15m |
| 2026-06-24 | VJC820 | - | Jun 24, 06:50 UTC | Jun 24, 15:39 UTC | 8h 50m |
| 2026-06-24 | VJC825 | - | Jun 24, 04:15 UTC | Jun 24, 04:34 UTC | 20m |
| 2026-06-23 | VJC802 | - | Jun 23, 04:55 UTC | Jun 23, 05:29 UTC | 35m |
| 2026-06-22 | VJC801 | - | Jun 22, 13:39 UTC | Jun 23, 03:09 UTC | 13h 30m |
| 2026-06-22 | VJC92 | - | Jun 22, 02:54 UTC | Jun 22, 12:19 UTC | 9h 25m |
| 2026-06-21 | VJC91 | - | Jun 21, 21:14 UTC | Jun 22, 00:50 UTC | 3h 35m |
| 2026-06-21 | VJC879 | - | Jun 21, 00:14 UTC | Jun 21, 21:19 UTC | 21h 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-A653 page for operator, model, and routing details .