Not currently tracked · last seen 5h ago
- Flights observed
- 150 showing last 50
- Avg flight time
- 2h 5m
- Typical route
- DEL → BLR
- Last seen
- 5h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-29 | PNQ → BLR | May 29, 19:20 UTC | May 29, 19:45 UTC | 25m |
| 2026-05-29 | PAT → BLR | May 29, 14:25 UTC | May 29, 14:55 UTC | 30m |
| 2026-05-29 | PAT → BLR | May 29, 12:20 UTC | May 29, 13:00 UTC | 40m |
| 2026-05-29 | - | May 29, 08:40 UTC | May 29, 11:05 UTC | 2h 25m |
| 2026-05-29 | DEL → BLR | May 29, 07:15 UTC | May 29, 07:25 UTC | 10m |
| 2026-05-29 | DEL → BLR | May 29, 05:10 UTC | May 29, 05:45 UTC | 35m |
| 2026-05-29 | CCU → BLR | May 29, 01:15 UTC | May 29, 03:55 UTC | 2h 40m |
| 2026-05-14 | DEL → BLR | May 14, 07:50 UTC | May 14, 08:00 UTC | 10m |
| 2026-05-14 | DEL → BLR | May 14, 05:40 UTC | May 14, 06:05 UTC | 25m |
| 2026-05-13 | GOI → DEL | May 13, 07:10 UTC | May 13, 12:45 UTC | 5h 35m |
| 2026-05-13 | GAU → DEL | May 13, 03:40 UTC | May 13, 05:35 UTC | 1h 55m |
| 2026-05-13 | DEL → IXB | May 13, 00:55 UTC | May 13, 02:05 UTC | 1h 10m |
| 2026-05-12 | IXR → DEL | May 12, 15:35 UTC | May 12, 17:10 UTC | 1h 35m |
| 2026-05-12 | DEL → LKO | May 12, 13:10 UTC | May 12, 14:20 UTC | 1h 10m |
| 2026-05-12 | IXJ → DEL | May 12, 05:45 UTC | May 12, 11:50 UTC | 6h 5m |
| 2026-05-12 | BLR → COK | May 12, 02:50 UTC | May 12, 03:35 UTC | 45m |
| 2026-05-11 | IXR → DEL | May 11, 12:50 UTC | May 11, 17:10 UTC | 4h 20m |
| 2026-05-11 | DEL → IXR | May 11, 03:45 UTC | May 11, 11:40 UTC | 7h 55m |
| 2026-05-11 | BOM → AUH | May 11, 00:10 UTC | May 11, 01:05 UTC | 55m |
| 2026-05-10 | DED → AMD | May 10, 03:35 UTC | May 11, 01:05 UTC | 21h 30m |
| 2026-05-10 | AMD → DED | May 10, 01:20 UTC | May 10, 02:45 UTC | 1h 25m |
| 2026-05-09 | BOM → AMD | May 9, 18:15 UTC | May 9, 18:30 UTC | 15m |
| 2026-05-09 | IXC → AMD | May 9, 08:35 UTC | May 9, 09:15 UTC | 40m |
| 2026-05-09 | AMD → IXC | May 9, 03:15 UTC | May 9, 07:25 UTC | 4h 10m |
| 2026-05-08 | AMD → DED | May 8, 16:15 UTC | May 9, 02:20 UTC | 10h 5m |
| 2026-05-08 | IDR → BLR | May 8, 15:15 UTC | May 8, 15:30 UTC | 15m |
| 2026-05-08 | IXR → BLR | May 8, 13:20 UTC | May 8, 13:35 UTC | 15m |
| 2026-05-08 | - | May 8, 08:55 UTC | May 8, 09:04 UTC | 10m |
| 2026-05-08 | DEL → BLR | May 8, 07:20 UTC | May 8, 07:39 UTC | 20m |
| 2026-05-08 | DEL → BLR | May 8, 05:14 UTC | May 8, 05:49 UTC | 35m |
| 2026-05-05 | IXR → DEL | May 5, 15:15 UTC | May 5, 17:05 UTC | 1h 50m |
| 2026-05-05 | DEL → IXR | May 5, 13:00 UTC | May 5, 14:00 UTC | 1h 0m |
| 2026-05-05 | PAT → DEL | May 5, 08:25 UTC | May 5, 10:30 UTC | 2h 5m |
| 2026-05-05 | DEL → PAT | May 5, 06:10 UTC | May 5, 07:10 UTC | 1h 0m |
| 2026-05-05 | GAU → PAT | May 5, 02:30 UTC | May 5, 03:35 UTC | 1h 5m |
| 2026-05-05 | SHJ → VNS | May 5, 00:40 UTC | May 5, 00:55 UTC | 15m |
| 2026-05-04 | SHJ → VNS | May 4, 21:20 UTC | May 4, 21:45 UTC | 25m |
| 2026-05-04 | VNS → SHJ | May 4, 19:35 UTC | May 4, 19:40 UTC | 5m |
| 2026-05-04 | VNS → SHJ | May 4, 15:50 UTC | May 4, 16:00 UTC | 10m |
| 2026-05-04 | HYD → TRZ | May 4, 12:55 UTC | May 4, 13:45 UTC | 50m |
| 2026-05-04 | BLR → PNQ | May 4, 06:20 UTC | May 4, 11:25 UTC | 5h 5m |
| 2026-05-04 | GAU → PAT | May 4, 02:45 UTC | May 4, 04:00 UTC | 1h 15m |
| 2026-05-04 | SHJ → VNS | May 4, 00:50 UTC | May 4, 01:00 UTC | 10m |
| 2026-05-03 | SHJ → VNS | May 3, 21:44 UTC | May 3, 22:15 UTC | 30m |
| 2026-05-03 | VNS → SHJ | May 3, 16:15 UTC | May 3, 20:15 UTC | 4h 0m |
| 2026-05-03 | HYD → TRZ | May 3, 13:20 UTC | May 3, 14:15 UTC | 55m |
| 2026-05-03 | DEL → IXR | May 3, 10:45 UTC | May 3, 11:30 UTC | 45m |
| 2026-05-03 | DEL → IXR | May 3, 09:50 UTC | May 3, 10:00 UTC | 10m |
| 2026-05-02 | RKT → BOM | May 2, 22:10 UTC | May 3, 00:50 UTC | 2h 40m |
| 2026-05-02 | BOM → AUH | May 2, 17:45 UTC | May 2, 18:20 UTC | 35m |
Specifications
| Registration | VT-EXE |
| Aircraft type | AIRBUS A-320 (A320) |
| Mode-S code | 800B63 · 40005543 (octal) |
Looking for transponder-level data? View the Mode-S 800B63 page for country allocation, callsign history, and ADS-B signal details.
VT-EXE frequently asked
What type of aircraft is VT-EXE?
VT-EXE is a AIRBUS A-320 (ICAO type code A320).
What is the Mode-S transponder code for VT-EXE?
VT-EXE broadcasts on Mode-S (ICAO 24-bit) address 800B63 (octal 40005543). View the transponder page.
What route does VT-EXE typically fly?
VT-EXE most frequently flies between DEL and BLR based on observed flights.
Where is VT-EXE right now?
VT-EXE is not currently being tracked; last seen 5h ago.