sensors Mode-S transponder
800414
ICAO 24-bit transponder address · allocated to India
Currently assigned to CA-7084 · AIRBUS A-321
- Hex
- 800414
- Octal
- 40002024
- Decimal
- 8,389,652
- Country
- IN
- Tail
- CA-7084
- Type
- A321
- Flights observed
- 65
- Distinct callsigns
- 5
- Country
- IN
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 800414 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 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | VUAUO | - | Jul 20, 12:45 UTC | Jul 20, 17:45 UTC | 5h 0m |
| 2026-07-14 | VUAUM | - | Jul 14, 08:25 UTC | Jul 14, 09:05 UTC | 40m |
| 2026-07-14 | VUAUM | - | Jul 14, 05:35 UTC | Jul 14, 06:40 UTC | 1h 5m |
| 2026-07-13 | AF321 | - | Jul 13, 09:05 UTC | Jul 13, 09:20 UTC | 15m |
| 2026-07-13 | AF321 | - | Jul 13, 04:00 UTC | Jul 13, 07:55 UTC | 3h 55m |
| 2026-07-13 | AF321 | HDO → DEL | Jul 13, 02:20 UTC | Jul 13, 02:40 UTC | 20m |
| 2026-07-11 | AF321 | DEL → HDO | Jul 11, 10:20 UTC | Jul 11, 10:35 UTC | 15m |
| 2026-07-11 | AF321 | - | Jul 11, 07:50 UTC | Jul 11, 08:30 UTC | 40m |
| 2026-07-10 | AF321 | - | Jul 10, 03:25 UTC | Jul 10, 04:00 UTC | 35m |
| 2026-07-09 | AF321 | - | Jul 9, 04:30 UTC | Jul 9, 08:20 UTC | 3h 50m |
| 2026-07-09 | AF321 | - | Jul 9, 03:10 UTC | Jul 9, 03:25 UTC | 15m |
| 2026-07-07 | VUAUO | HDO → HDO | Jul 7, 05:00 UTC | Jul 7, 09:10 UTC | 4h 10m |
| 2026-06-27 | AF321 | - | Jun 27, 11:39 UTC | Jun 27, 11:59 UTC | 20m |
| 2026-06-27 | AF321 | CCU → DEL | Jun 27, 07:55 UTC | Jun 27, 09:50 UTC | 1h 55m |
| 2026-06-27 | AF321 | - | Jun 27, 06:05 UTC | Jun 27, 06:54 UTC | 50m |
| 2026-06-26 | AF321 | - | Jun 26, 07:00 UTC | Jun 26, 07:39 UTC | 40m |
| 2026-06-26 | AF321 | - | Jun 26, 03:39 UTC | Jun 26, 05:30 UTC | 1h 50m |
| 2026-06-25 | VUAUO | - | Jun 25, 09:50 UTC | Jun 25, 12:19 UTC | 2h 30m |
| 2026-06-25 | VUAUO | - | Jun 25, 04:35 UTC | Jun 25, 04:49 UTC | 15m |
| 2026-06-25 | VUAUO | - | Jun 25, 02:30 UTC | Jun 25, 02:59 UTC | 30m |
| 2026-06-25 | VUAUO | - | Jun 25, 00:59 UTC | Jun 25, 01:14 UTC | 15m |
| 2026-06-20 | VUAUO | DEL → HDO | Jun 20, 17:10 UTC | Jun 20, 17:24 UTC | 15m |
| 2026-06-20 | VUAUO | - | Jun 20, 13:55 UTC | Jun 20, 16:19 UTC | 2h 25m |
| 2026-06-20 | VUAUO | - | Jun 20, 08:55 UTC | Jun 20, 09:44 UTC | 50m |
| 2026-06-20 | VUAUO | - | Jun 20, 03:19 UTC | Jun 20, 07:44 UTC | 4h 25m |
| 2026-06-19 | VUAUO | HDO → DEL | Jun 19, 02:19 UTC | Jun 19, 02:35 UTC | 15m |
| 2026-06-17 | VUAUO | - | Jun 17, 09:55 UTC | Jun 17, 10:20 UTC | 25m |
| 2026-06-17 | VUAUO | - | Jun 17, 06:20 UTC | Jun 17, 08:30 UTC | 2h 10m |
| 2026-06-16 | VUAUO | - | Jun 16, 11:05 UTC | Jun 17, 08:30 UTC | 21h 26m |
| 2026-06-16 | VUAUO | - | Jun 16, 09:04 UTC | Jun 17, 08:30 UTC | 23h 26m |
| 2026-06-10 | VUAUO | - | Jun 10, 16:40 UTC | Jun 10, 17:25 UTC | 45m |
| 2026-06-10 | VUAUO | - | Jun 10, 12:45 UTC | Jun 10, 14:55 UTC | 2h 10m |
| 2026-06-08 | VUAUO | - | Jun 8, 16:55 UTC | Jun 8, 17:40 UTC | 45m |
| 2026-06-08 | VUAUO | - | Jun 8, 12:50 UTC | Jun 8, 14:45 UTC | 1h 55m |
| 2026-06-05 | VUAUO | - | Jun 5, 07:35 UTC | Jun 5, 11:55 UTC | 4h 20m |
| 2026-05-29 | VUAUO | - | May 29, 10:15 UTC | May 29, 10:35 UTC | 20m |
| 2026-05-29 | VUAUO | - | May 29, 06:50 UTC | May 29, 09:10 UTC | 2h 20m |
| 2026-05-29 | VUAUO | - | May 29, 04:15 UTC | May 29, 05:25 UTC | 1h 10m |
| 2026-05-27 | VUAUO | - | May 27, 10:05 UTC | May 27, 11:30 UTC | 1h 25m |
| 2026-05-27 | VUAUO | - | May 27, 06:49 UTC | May 27, 08:15 UTC | 1h 25m |
| 2026-05-25 | VUAUO | - | May 25, 16:05 UTC | May 25, 16:35 UTC | 30m |
| 2026-05-25 | VUAUO | - | May 25, 11:55 UTC | May 25, 14:20 UTC | 2h 25m |
| 2026-05-19 | VUAUO | - | May 19, 04:10 UTC | May 19, 07:25 UTC | 3h 15m |
| 2026-05-19 | VUAUO | HDO → DEL | May 19, 01:30 UTC | May 19, 01:45 UTC | 15m |
| 2026-05-18 | VUAUO | - | May 18, 04:30 UTC | May 18, 06:50 UTC | 2h 20m |
| 2026-05-18 | VUAUO | - | May 18, 02:00 UTC | May 18, 02:35 UTC | 35m |
| 2026-05-08 | VUAUO | DEL → HDO | May 8, 13:15 UTC | May 8, 15:05 UTC | 1h 50m |
| 2026-05-08 | VUAUO | - | May 8, 11:25 UTC | May 8, 12:04 UTC | 40m |
| 2026-05-08 | VUAUO | - | May 8, 08:59 UTC | May 8, 09:30 UTC | 30m |
| 2026-05-06 | VUAUO | - | May 6, 12:40 UTC | May 6, 16:10 UTC | 3h 30m |
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 CA-7084 page for operator, model, and routing details .