sensors Mode-S transponder
801696
ICAO 24-bit transponder address · allocated to India
Currently assigned to VT-CVA · BOMBARDIER CL-600 Challenger
- Hex
- 801696
- Octal
- 40013226
- Decimal
- 8,394,390
- Country
- IN
- Tail
- VT-CVA
- Type
- CL60
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- IN
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 801696 falls within the block assigned to India (IN) by ICAO Annex 10, Volume III. Every aircraft registered in India 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VJI563 | - | 49 | 2026-06-15 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-15 | VJI563 | - | Jun 15, 07:05 UTC | Jun 15, 07:15 UTC | 10m |
| 2026-06-14 | VJI563 | - | Jun 14, 14:40 UTC | Jun 14, 15:10 UTC | 30m |
| 2026-06-14 | VJI563 | - | Jun 14, 13:45 UTC | Jun 14, 13:55 UTC | 10m |
| 2026-06-14 | VJI563 | - | Jun 14, 04:50 UTC | Jun 14, 05:00 UTC | 10m |
| 2026-06-14 | VJI563 | - | Jun 14, 01:00 UTC | Jun 14, 01:15 UTC | 15m |
| 2026-06-13 | VJI563 | - | Jun 13, 14:00 UTC | Jun 13, 15:35 UTC | 1h 35m |
| 2026-06-13 | VJI563 | - | Jun 13, 09:45 UTC | Jun 13, 12:05 UTC | 2h 20m |
| 2026-06-12 | VJI563 | - | Jun 12, 15:40 UTC | Jun 12, 16:10 UTC | 30m |
| 2026-06-12 | VJI563 | - | Jun 12, 14:55 UTC | Jun 12, 15:05 UTC | 10m |
| 2026-06-12 | VJI563 | - | Jun 12, 10:20 UTC | Jun 12, 10:40 UTC | 20m |
| 2026-06-12 | VJI563 | - | Jun 12, 09:15 UTC | Jun 12, 09:35 UTC | 20m |
| 2026-06-10 | VJI563 | - | Jun 10, 13:30 UTC | Jun 10, 13:55 UTC | 25m |
| 2026-06-09 | VJI563 | - | Jun 9, 02:55 UTC | Jun 9, 03:10 UTC | 15m |
| 2026-06-03 | VJI563 | - | Jun 3, 08:40 UTC | Jun 3, 08:50 UTC | 10m |
| 2026-05-27 | VJI563 | - | May 27, 16:50 UTC | May 27, 17:30 UTC | 40m |
| 2026-05-27 | VJI563 | - | May 27, 08:45 UTC | May 27, 15:30 UTC | 6h 45m |
| 2026-05-26 | VJI563 | - | May 26, 02:10 UTC | May 26, 02:44 UTC | 35m |
| 2026-05-25 | VJI563 | - | May 25, 08:25 UTC | May 25, 09:05 UTC | 40m |
| 2026-05-24 | VJI563 | - | May 24, 09:35 UTC | May 25, 09:05 UTC | 23h 30m |
| 2026-05-24 | VJI563 | - | May 24, 09:15 UTC | May 24, 09:55 UTC | 40m |
| 2026-05-24 | VJI563 | - | May 24, 02:40 UTC | May 24, 05:10 UTC | 2h 30m |
| 2026-05-22 | VJI563 | - | May 22, 15:45 UTC | May 22, 16:05 UTC | 20m |
| 2026-05-18 | VJI563 | - | May 18, 14:30 UTC | May 18, 15:05 UTC | 35m |
| 2026-05-18 | VJI563 | - | May 18, 10:50 UTC | May 18, 11:25 UTC | 35m |
| 2026-05-18 | VJI563 | - | May 18, 09:50 UTC | May 18, 10:15 UTC | 25m |
| 2026-05-16 | VJI563 | - | May 16, 12:21 UTC | May 16, 14:51 UTC | 2h 30m |
| 2026-05-16 | VJI563 | - | May 16, 10:16 UTC | May 16, 10:31 UTC | 15m |
| 2026-05-15 | VJI563 | - | May 15, 12:25 UTC | May 15, 12:55 UTC | 30m |
| 2026-05-15 | VJI563 | - | May 15, 09:30 UTC | May 15, 09:40 UTC | 10m |
| 2026-05-14 | VJI563 | - | May 14, 12:40 UTC | May 14, 12:50 UTC | 10m |
| 2026-05-14 | VJI563 | - | May 14, 10:40 UTC | May 14, 11:55 UTC | 1h 15m |
| 2026-05-14 | VJI563 | - | May 14, 09:05 UTC | May 14, 09:45 UTC | 40m |
| 2026-05-13 | VJI563 | - | May 13, 14:51 UTC | May 14, 09:45 UTC | 18h 55m |
| 2026-05-13 | VJI563 | - | May 13, 08:40 UTC | May 13, 12:45 UTC | 4h 5m |
| 2026-05-12 | VJI563 | - | May 12, 08:30 UTC | May 12, 12:35 UTC | 4h 5m |
| 2026-05-11 | VJI563 | - | May 11, 11:30 UTC | May 11, 12:00 UTC | 30m |
| 2026-05-09 | VJI563 | - | May 9, 10:35 UTC | May 9, 11:55 UTC | 1h 20m |
| 2026-05-09 | VJI563 | - | May 9, 02:25 UTC | May 9, 03:40 UTC | 1h 15m |
| 2026-05-07 | VJI563 | - | May 7, 14:30 UTC | May 7, 14:45 UTC | 15m |
| 2026-05-07 | VJI563 | - | May 7, 13:30 UTC | May 7, 13:45 UTC | 15m |
| 2026-05-05 | VJI563 | - | May 5, 09:35 UTC | May 5, 09:50 UTC | 15m |
| 2026-05-05 | VJI563 | - | May 5, 08:10 UTC | May 5, 08:25 UTC | 15m |
| 2026-05-03 | VJI563 | - | May 3, 09:25 UTC | May 3, 09:40 UTC | 15m |
| 2026-05-02 | VJI563 | - | May 2, 07:45 UTC | May 2, 09:50 UTC | 2h 5m |
| 2026-05-02 | VJI563 | - | May 2, 04:50 UTC | May 2, 06:30 UTC | 1h 40m |
| 2026-05-01 | VJI563 | - | May 1, 15:50 UTC | May 1, 20:15 UTC | 4h 25m |
| 2026-04-29 | VJI563 | - | Apr 29, 14:55 UTC | Apr 29, 17:30 UTC | 2h 35m |
| 2026-04-29 | VJI563 | - | Apr 29, 02:30 UTC | Apr 29, 04:55 UTC | 2h 25m |
| 2026-04-28 | VJI563 | - | Apr 28, 05:45 UTC | Apr 28, 08:05 UTC | 2h 20m |
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 VT-CVA page for operator, model, and routing details .