sensors Mode-S transponder
801743
ICAO 24-bit transponder address · allocated to India
Currently assigned to VT-PVV · CESSNA 525A Citation CJ2
- Hex
- 801743
- Octal
- 40013503
- Decimal
- 8,394,563
- Country
- IN
- Tail
- VT-PVV
- Type
- C25A
- Flights observed
- 64
- Distinct callsigns
- 1
- Country
- IN
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 801743 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 |
|---|---|---|---|
| VTPVV | - | 64 | 2026-07-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | VTPVV | - | Jul 18, 01:30 UTC | Jul 18, 01:50 UTC | 20m |
| 2026-07-12 | VTPVV | - | Jul 12, 05:15 UTC | Jul 12, 05:50 UTC | 35m |
| 2026-07-12 | VTPVV | - | Jul 12, 01:50 UTC | Jul 12, 02:20 UTC | 30m |
| 2026-07-08 | VTPVV | - | Jul 8, 05:10 UTC | Jul 8, 14:25 UTC | 9h 15m |
| 2026-07-02 | VTPVV | - | Jul 2, 07:10 UTC | Jul 2, 16:25 UTC | 9h 15m |
| 2026-06-27 | VTPVV | - | Jun 27, 08:14 UTC | Jun 27, 09:04 UTC | 50m |
| 2026-06-26 | VTPVV | - | Jun 26, 06:15 UTC | Jun 26, 06:54 UTC | 40m |
| 2026-06-24 | VTPVV | - | Jun 24, 09:49 UTC | Jun 24, 11:24 UTC | 1h 35m |
| 2026-06-24 | VTPVV | - | Jun 24, 06:39 UTC | Jun 24, 07:54 UTC | 1h 15m |
| 2026-06-20 | VTPVV | - | Jun 20, 13:34 UTC | Jun 20, 14:05 UTC | 30m |
| 2026-06-20 | VTPVV | - | Jun 20, 11:05 UTC | Jun 20, 11:54 UTC | 50m |
| 2026-06-19 | VTPVV | - | Jun 19, 08:14 UTC | Jun 19, 08:44 UTC | 30m |
| 2026-06-19 | VTPVV | - | Jun 19, 04:04 UTC | Jun 19, 05:19 UTC | 1h 15m |
| 2026-06-18 | VTPVV | - | Jun 18, 02:50 UTC | Jun 18, 05:35 UTC | 2h 45m |
| 2026-06-16 | VTPVV | - | Jun 16, 07:09 UTC | Jun 16, 09:15 UTC | 2h 5m |
| 2026-06-06 | VTPVV | - | Jun 6, 13:09 UTC | Jun 6, 13:39 UTC | 30m |
| 2026-06-06 | VTPVV | - | Jun 6, 05:10 UTC | Jun 6, 05:30 UTC | 20m |
| 2026-06-06 | VTPVV | - | Jun 6, 04:20 UTC | Jun 6, 04:35 UTC | 15m |
| 2026-06-04 | VTPVV | - | Jun 4, 04:30 UTC | Jun 4, 05:15 UTC | 45m |
| 2026-06-04 | VTPVV | - | Jun 4, 01:45 UTC | Jun 4, 02:15 UTC | 30m |
| 2026-06-01 | VTPVV | - | Jun 1, 13:00 UTC | Jun 1, 14:35 UTC | 1h 35m |
| 2026-06-01 | VTPVV | - | Jun 1, 10:25 UTC | Jun 1, 11:40 UTC | 1h 15m |
| 2026-05-31 | VTPVV | - | May 31, 12:10 UTC | May 31, 13:05 UTC | 55m |
| 2026-05-23 | VTPVV | - | May 23, 12:35 UTC | May 23, 13:20 UTC | 45m |
| 2026-05-23 | VTPVV | - | May 23, 07:10 UTC | May 23, 08:00 UTC | 50m |
| 2026-05-21 | VTPVV | - | May 21, 14:55 UTC | May 21, 16:01 UTC | 1h 5m |
| 2026-05-21 | VTPVV | - | May 21, 05:50 UTC | May 21, 06:45 UTC | 55m |
| 2026-05-20 | VTPVV | - | May 20, 08:40 UTC | May 20, 09:15 UTC | 35m |
| 2026-05-20 | VTPVV | - | May 20, 04:45 UTC | May 20, 05:10 UTC | 25m |
| 2026-05-19 | VTPVV | - | May 19, 12:05 UTC | May 19, 12:35 UTC | 30m |
| 2026-05-19 | VTPVV | - | May 19, 06:05 UTC | May 19, 06:25 UTC | 20m |
| 2026-05-13 | VTPVV | - | May 13, 12:30 UTC | May 13, 13:00 UTC | 30m |
| 2026-05-12 | VTPVV | - | May 12, 11:20 UTC | May 12, 14:00 UTC | 2h 40m |
| 2026-05-12 | VTPVV | - | May 12, 02:45 UTC | May 12, 03:25 UTC | 40m |
| 2026-05-11 | VTPVV | - | May 11, 07:55 UTC | May 11, 08:35 UTC | 40m |
| 2026-05-09 | VTPVV | - | May 9, 13:00 UTC | May 9, 14:10 UTC | 1h 10m |
| 2026-05-09 | VTPVV | - | May 9, 09:00 UTC | May 9, 09:30 UTC | 30m |
| 2026-05-08 | VTPVV | - | May 8, 00:34 UTC | May 8, 07:34 UTC | 7h 0m |
| 2026-05-06 | VTPVV | - | May 6, 12:50 UTC | May 6, 13:20 UTC | 30m |
| 2026-05-06 | VTPVV | - | May 6, 02:15 UTC | May 6, 02:45 UTC | 30m |
| 2026-05-05 | VTPVV | - | May 5, 01:55 UTC | May 5, 06:40 UTC | 4h 45m |
| 2026-05-04 | VTPVV | - | May 4, 09:55 UTC | May 4, 10:35 UTC | 40m |
| 2026-05-04 | VTPVV | - | May 4, 05:05 UTC | May 4, 05:45 UTC | 40m |
| 2026-05-02 | VTPVV | - | May 2, 13:30 UTC | May 2, 14:25 UTC | 55m |
| 2026-05-02 | VTPVV | - | May 2, 11:45 UTC | May 2, 11:55 UTC | 10m |
| 2026-05-01 | VTPVV | - | May 1, 20:00 UTC | May 1, 20:30 UTC | 30m |
| 2026-05-01 | VTPVV | - | May 1, 19:05 UTC | May 1, 19:15 UTC | 10m |
| 2026-04-30 | VTPVV | - | Apr 30, 18:05 UTC | Apr 30, 18:35 UTC | 30m |
| 2026-04-30 | VTPVV | - | Apr 30, 17:05 UTC | Apr 30, 17:25 UTC | 20m |
| 2026-04-29 | VTPVV | - | Apr 29, 10:45 UTC | Apr 29, 11:00 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 VT-PVV page for operator, model, and routing details .