sensors Mode-S transponder
8003C1
ICAO 24-bit transponder address · allocated to India
Currently assigned to CA-7081 · AIRBUS A-321
- Hex
- 8003C1
- Octal
- 40001701
- Decimal
- 8,389,569
- Country
- IN
- Tail
- CA-7081
- Type
- A321
- Flights observed
- 52
- Distinct callsigns
- 5
- Country
- IN
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 8003C1 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-05-26 | VUAUL | - | May 26, 05:59 UTC | May 26, 07:24 UTC | 1h 25m |
| 2026-05-26 | VUAUL | - | May 26, 04:15 UTC | May 26, 04:35 UTC | 20m |
| 2026-05-22 | VUAUO | - | May 22, 05:15 UTC | May 22, 07:35 UTC | 2h 20m |
| 2026-05-22 | VUAUO | - | May 22, 02:40 UTC | May 22, 03:20 UTC | 40m |
| 2026-05-20 | VUAUL | - | May 20, 11:40 UTC | May 20, 12:25 UTC | 45m |
| 2026-05-20 | VUAUL | - | May 20, 10:00 UTC | May 20, 10:35 UTC | 35m |
| 2026-05-16 | AF321A | DEL → HDO | May 16, 11:55 UTC | May 16, 12:16 UTC | 20m |
| 2026-05-16 | AF321A | - | May 16, 08:11 UTC | May 16, 10:16 UTC | 2h 5m |
| 2026-05-16 | AF321A | - | May 16, 06:16 UTC | May 16, 06:45 UTC | 30m |
| 2026-05-16 | AF321A | - | May 16, 04:15 UTC | May 16, 04:30 UTC | 15m |
| 2026-05-15 | AF321A | - | May 15, 08:25 UTC | May 15, 11:20 UTC | 2h 55m |
| 2026-05-15 | AF321A | - | May 15, 05:05 UTC | May 15, 06:45 UTC | 1h 40m |
| 2026-05-15 | AF321A | HDO → DEL | May 15, 03:35 UTC | May 15, 03:55 UTC | 20m |
| 2026-05-11 | AF321 | BOS → CDG | May 11, 09:25 UTC | May 11, 09:40 UTC | 15m |
| 2026-05-11 | AF321 | BOS → CDG | May 11, 03:35 UTC | May 11, 08:20 UTC | 4h 45m |
| 2026-05-11 | AF321 | BOS → CDG | May 11, 02:10 UTC | May 11, 02:25 UTC | 15m |
| 2026-05-07 | VUAUL | HDO → HDO | May 7, 06:40 UTC | May 7, 07:20 UTC | 40m |
| 2026-05-02 | AF321 | BOS → CDG | May 2, 11:35 UTC | May 2, 11:50 UTC | 15m |
| 2026-05-02 | AF321 | BOS → CDG | May 2, 08:20 UTC | May 2, 10:40 UTC | 2h 20m |
| 2026-05-02 | AF321 | BOS → CDG | May 2, 03:30 UTC | May 2, 05:20 UTC | 1h 50m |
| 2026-05-01 | AF321 | BOS → CDG | May 1, 08:55 UTC | May 1, 10:50 UTC | 1h 55m |
| 2026-05-01 | AF321 | BOS → CDG | May 1, 06:45 UTC | May 1, 07:00 UTC | 15m |
| 2026-05-01 | AF321 | BOS → CDG | May 1, 03:25 UTC | May 1, 05:05 UTC | 1h 40m |
| 2026-05-01 | AF321 | BOS → CDG | May 1, 02:05 UTC | May 1, 02:20 UTC | 15m |
| 2026-04-28 | AF321 | BOS → CDG | Apr 28, 07:40 UTC | Apr 28, 11:45 UTC | 4h 5m |
| 2026-04-28 | AF321 | BOS → CDG | Apr 28, 04:30 UTC | Apr 28, 06:30 UTC | 2h 0m |
| 2026-04-28 | AF321 | BOS → CDG | Apr 28, 02:45 UTC | Apr 28, 02:55 UTC | 10m |
| 2026-04-27 | AF321 | BOS → CDG | Apr 27, 13:05 UTC | Apr 27, 13:15 UTC | 10m |
| 2026-04-27 | AF321 | BOS → CDG | Apr 27, 10:20 UTC | Apr 27, 11:40 UTC | 1h 20m |
| 2026-04-27 | AF321 | BOS → CDG | Apr 27, 03:20 UTC | Apr 27, 07:15 UTC | 3h 55m |
| 2026-04-25 | AF321 | BOS → CDG | Apr 25, 10:00 UTC | Apr 25, 10:25 UTC | 25m |
| 2026-04-25 | AF321 | BOS → CDG | Apr 25, 07:05 UTC | Apr 25, 09:00 UTC | 1h 55m |
| 2026-04-25 | AF321 | BOS → CDG | Apr 25, 05:00 UTC | Apr 25, 05:45 UTC | 45m |
| 2026-04-24 | AF321 | BOS → CDG | Apr 24, 07:00 UTC | Apr 25, 05:45 UTC | 22h 45m |
| 2026-04-24 | AF321 | BOS → CDG | Apr 24, 03:30 UTC | Apr 24, 05:20 UTC | 1h 50m |
| 2026-04-24 | AF321 | BOS → CDG | Apr 24, 02:15 UTC | Apr 24, 02:30 UTC | 15m |
| 2026-04-22 | VUAUL | HDO → HDO | Apr 22, 05:30 UTC | Apr 22, 10:15 UTC | 4h 45m |
| 2026-04-18 | AF321A | - | Apr 18, 14:15 UTC | Apr 18, 14:35 UTC | 20m |
| 2026-04-18 | AF321A | - | Apr 18, 11:10 UTC | Apr 18, 13:15 UTC | 2h 5m |
| 2026-04-18 | AF321A | - | Apr 18, 08:30 UTC | Apr 18, 09:35 UTC | 1h 5m |
| 2026-04-18 | AF321A | - | Apr 18, 06:55 UTC | Apr 18, 07:15 UTC | 20m |
| 2026-04-17 | AF321A | - | Apr 17, 09:55 UTC | Apr 17, 10:05 UTC | 10m |
| 2026-04-17 | AF321A | - | Apr 17, 07:20 UTC | Apr 17, 08:55 UTC | 1h 35m |
| 2026-04-17 | AF321A | - | Apr 17, 05:20 UTC | Apr 17, 05:45 UTC | 25m |
| 2026-04-17 | AF321A | - | Apr 17, 04:05 UTC | Apr 17, 05:15 UTC | 1h 11m |
| 2026-04-17 | AF321A | HDO → DEL | Apr 17, 02:45 UTC | Apr 17, 02:55 UTC | 10m |
| 2026-04-15 | VUAUP | - | Apr 15, 09:00 UTC | Apr 15, 09:30 UTC | 30m |
| 2026-04-15 | VUAUP | - | Apr 15, 08:45 UTC | Apr 15, 08:55 UTC | 10m |
| 2026-04-15 | VUAUP | - | Apr 15, 07:01 UTC | Apr 15, 07:20 UTC | 20m |
| 2026-04-15 | VUAUP | - | Apr 15, 05:00 UTC | Apr 15, 05:10 UTC | 10m |
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-7081 page for operator, model, and routing details .