sensors Mode-S transponder
801593
ICAO 24-bit transponder address · allocated to India
Currently assigned to VT-PRI · BOMBARDIER BD-700 Global 7000/7500
- Hex
- 801593
- Octal
- 40012623
- Decimal
- 8,394,131
- Country
- IN
- Tail
- VT-PRI
- Type
- GL7T
- Flights observed
- 56
- Distinct callsigns
- 1
- Country
- IN
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 801593 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 |
|---|---|---|---|
| VTPRI | - | 56 | 2026-07-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | VTPRI | LTN → BQH | Jul 15, 15:50 UTC | Jul 15, 16:15 UTC | 25m |
| 2026-07-15 | VTPRI | NCE → LTN | Jul 15, 12:35 UTC | Jul 15, 14:10 UTC | 1h 35m |
| 2026-07-14 | VTPRI | - | Jul 14, 01:05 UTC | Jul 14, 09:05 UTC | 8h 0m |
| 2026-07-07 | VTPRI | - | Jul 7, 03:45 UTC | Jul 7, 06:30 UTC | 2h 45m |
| 2026-07-06 | VTPRI | - | Jul 6, 21:10 UTC | Jul 7, 03:40 UTC | 6h 30m |
| 2026-07-05 | VTPRI | BOM → LTN | Jul 5, 04:40 UTC | Jul 5, 14:05 UTC | 9h 25m |
| 2026-07-02 | VTPRI | - | Jul 2, 15:50 UTC | Jul 2, 16:05 UTC | 15m |
| 2026-07-02 | VTPRI | - | Jul 2, 11:10 UTC | Jul 2, 11:20 UTC | 10m |
| 2026-07-01 | VTPRI | - | Jul 1, 22:05 UTC | Jul 2, 07:35 UTC | 9h 30m |
| 2026-06-26 | VTPRI | BOM → LTN | Jun 26, 21:04 UTC | Jun 27, 06:19 UTC | 9h 15m |
| 2026-06-24 | VTPRI | - | Jun 24, 07:15 UTC | Jun 24, 16:34 UTC | 9h 20m |
| 2026-06-22 | VTPRI | BOM → LTN | Jun 22, 21:00 UTC | Jun 23, 06:24 UTC | 9h 25m |
| 2026-06-19 | VTPRI | - | Jun 19, 23:00 UTC | Jun 20, 08:34 UTC | 9h 35m |
| 2026-06-18 | VTPRI | BED → LTN | Jun 18, 00:35 UTC | Jun 18, 06:45 UTC | 6h 10m |
| 2026-06-15 | VTPRI | BOS → BED | Jun 15, 10:00 UTC | Jun 15, 10:20 UTC | 20m |
| 2026-06-15 | VTPRI | VIE → BOS | Jun 15, 00:40 UTC | Jun 15, 08:25 UTC | 7h 45m |
| 2026-06-14 | VTPRI | BOM → VIE | Jun 14, 15:40 UTC | Jun 14, 23:35 UTC | 7h 55m |
| 2026-06-14 | VTPRI | - | Jun 14, 02:20 UTC | Jun 14, 10:10 UTC | 7h 51m |
| 2026-06-13 | VTPRI | BED → VIE | Jun 13, 17:55 UTC | Jun 14, 01:05 UTC | 7h 10m |
| 2026-06-11 | VTPRI | BOS → BED | Jun 11, 13:05 UTC | Jun 11, 13:20 UTC | 15m |
| 2026-06-11 | VTPRI | VIE → BOS | Jun 11, 03:55 UTC | Jun 11, 11:20 UTC | 7h 25m |
| 2026-06-10 | VTPRI | BOM → VIE | Jun 10, 18:35 UTC | Jun 11, 02:35 UTC | 8h 0m |
| 2026-05-30 | VTPRI | - | May 30, 21:35 UTC | May 31, 00:10 UTC | 2h 35m |
| 2026-05-30 | VTPRI | - | May 30, 17:25 UTC | May 30, 17:45 UTC | 20m |
| 2026-05-30 | VTPRI | BUD → VIE | May 30, 08:05 UTC | May 30, 08:40 UTC | 35m |
| 2026-05-29 | VTPRI | - | May 29, 22:45 UTC | May 30, 06:45 UTC | 8h 0m |
| 2026-05-27 | VTPRI | - | May 27, 10:00 UTC | May 27, 11:05 UTC | 1h 5m |
| 2026-05-27 | VTPRI | - | May 27, 08:45 UTC | May 27, 09:05 UTC | 20m |
| 2026-05-26 | VTPRI | LIN → BOM | May 26, 22:15 UTC | May 27, 06:49 UTC | 8h 35m |
| 2026-05-24 | VTPRI | - | May 24, 20:20 UTC | May 25, 04:35 UTC | 8h 15m |
| 2026-05-22 | VTPRI | - | May 22, 08:55 UTC | May 22, 09:55 UTC | 1h 0m |
| 2026-05-22 | VTPRI | - | May 22, 07:40 UTC | May 22, 08:10 UTC | 30m |
| 2026-05-18 | VTPRI | - | May 18, 22:35 UTC | May 19, 07:20 UTC | 8h 45m |
| 2026-05-17 | VTPRI | - | May 17, 20:40 UTC | May 18, 06:35 UTC | 9h 55m |
| 2026-05-14 | VTPRI | - | May 14, 11:05 UTC | May 14, 11:35 UTC | 30m |
| 2026-05-14 | VTPRI | - | May 14, 07:40 UTC | May 14, 08:55 UTC | 1h 15m |
| 2026-05-09 | VTPRI | - | May 9, 20:00 UTC | May 10, 02:39 UTC | 6h 40m |
| 2026-05-07 | VTPRI | - | May 7, 10:50 UTC | May 7, 11:45 UTC | 55m |
| 2026-05-07 | VTPRI | - | May 7, 06:40 UTC | May 7, 07:20 UTC | 40m |
| 2026-05-06 | VTPRI | - | May 6, 11:40 UTC | May 6, 12:20 UTC | 40m |
| 2026-05-06 | VTPRI | - | May 6, 02:15 UTC | May 6, 07:55 UTC | 5h 40m |
| 2026-05-01 | VTPRI | - | May 1, 14:10 UTC | May 1, 15:00 UTC | 50m |
| 2026-05-01 | VTPRI | - | May 1, 04:45 UTC | May 1, 07:05 UTC | 2h 20m |
| 2026-04-26 | VTPRI | - | Apr 26, 09:35 UTC | Apr 26, 10:10 UTC | 35m |
| 2026-04-26 | VTPRI | - | Apr 26, 06:55 UTC | Apr 26, 07:05 UTC | 10m |
| 2026-04-25 | VTPRI | - | Apr 25, 14:45 UTC | Apr 25, 15:20 UTC | 35m |
| 2026-04-25 | VTPRI | - | Apr 25, 12:40 UTC | Apr 25, 12:50 UTC | 10m |
| 2026-04-24 | VTPRI | - | Apr 24, 17:55 UTC | Apr 24, 18:25 UTC | 30m |
| 2026-04-24 | VTPRI | - | Apr 24, 16:20 UTC | Apr 24, 16:35 UTC | 15m |
| 2026-04-22 | VTPRI | - | Apr 22, 17:15 UTC | Apr 22, 17:30 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-PRI page for operator, model, and routing details .