sensors Mode-S transponder
800C9C
ICAO 24-bit transponder address · allocated to India
Currently assigned to VT-ARO · DASSAULT Falcon 2000
- Hex
- 800C9C
- Octal
- 40006234
- Decimal
- 8,391,836
- Country
- IN
- Tail
- VT-ARO
- Type
- F2TH
- Flights observed
- 76
- Distinct callsigns
- 1
- Country
- IN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 800C9C 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 |
|---|---|---|---|
| VTARO | - | 76 | 2026-07-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | VTARO | CCU → DEL | Jul 14, 07:45 UTC | Jul 14, 09:35 UTC | 1h 50m |
| 2026-07-13 | VTARO | - | Jul 13, 11:50 UTC | Jul 13, 12:10 UTC | 20m |
| 2026-07-12 | VTARO | - | Jul 12, 03:35 UTC | Jul 12, 05:40 UTC | 2h 5m |
| 2026-07-12 | VTARO | - | Jul 12, 01:50 UTC | Jul 12, 02:10 UTC | 20m |
| 2026-07-11 | VTARO | - | Jul 11, 23:45 UTC | Jul 12, 00:25 UTC | 40m |
| 2026-07-09 | VTARO | - | Jul 9, 08:55 UTC | Jul 9, 09:25 UTC | 30m |
| 2026-07-09 | VTARO | - | Jul 9, 04:50 UTC | Jul 9, 05:10 UTC | 20m |
| 2026-07-06 | VTARO | - | Jul 6, 03:15 UTC | Jul 6, 03:55 UTC | 40m |
| 2026-07-06 | VTARO | - | Jul 6, 01:05 UTC | Jul 6, 01:20 UTC | 15m |
| 2026-07-05 | VTARO | - | Jul 5, 16:40 UTC | Jul 5, 17:25 UTC | 45m |
| 2026-07-04 | VTARO | - | Jul 4, 14:05 UTC | Jul 4, 14:45 UTC | 40m |
| 2026-07-03 | VTARO | - | Jul 3, 02:40 UTC | Jul 3, 11:15 UTC | 8h 35m |
| 2026-06-30 | VTARO | - | Jun 30, 06:45 UTC | Jun 30, 07:15 UTC | 30m |
| 2026-06-30 | VTARO | - | Jun 30, 05:45 UTC | Jun 30, 06:05 UTC | 20m |
| 2026-06-29 | VTARO | - | Jun 29, 06:24 UTC | Jun 29, 06:54 UTC | 30m |
| 2026-06-28 | VTARO | - | Jun 28, 05:34 UTC | Jun 28, 05:55 UTC | 20m |
| 2026-06-21 | VTARO | - | Jun 21, 08:20 UTC | Jun 21, 09:49 UTC | 1h 30m |
| 2026-06-20 | VTARO | - | Jun 20, 16:44 UTC | Jun 20, 16:59 UTC | 15m |
| 2026-06-19 | VTARO | - | Jun 19, 10:54 UTC | Jun 19, 11:09 UTC | 15m |
| 2026-06-19 | VTARO | - | Jun 19, 07:25 UTC | Jun 19, 08:44 UTC | 1h 20m |
| 2026-06-15 | VTARO | - | Jun 15, 02:55 UTC | Jun 15, 13:40 UTC | 10h 45m |
| 2026-06-14 | VTARO | - | Jun 14, 03:55 UTC | Jun 14, 12:10 UTC | 8h 15m |
| 2026-06-12 | VTARO | - | Jun 12, 13:25 UTC | Jun 12, 17:00 UTC | 3h 35m |
| 2026-06-03 | VTARO | - | Jun 3, 19:30 UTC | Jun 3, 20:05 UTC | 35m |
| 2026-06-03 | VTARO | - | Jun 3, 11:35 UTC | Jun 3, 11:55 UTC | 20m |
| 2026-05-17 | VTARO | - | May 17, 12:40 UTC | May 17, 13:15 UTC | 35m |
| 2026-05-17 | VTARO | - | May 17, 10:30 UTC | May 17, 11:15 UTC | 45m |
| 2026-05-15 | VTARO | - | May 15, 07:45 UTC | May 15, 14:35 UTC | 6h 50m |
| 2026-05-14 | VTARO | - | May 14, 15:15 UTC | May 14, 18:15 UTC | 3h 0m |
| 2026-05-14 | VTARO | - | May 14, 09:05 UTC | May 14, 12:05 UTC | 3h 0m |
| 2026-05-12 | VTARO | - | May 12, 13:51 UTC | May 12, 14:25 UTC | 35m |
| 2026-05-12 | VTARO | - | May 12, 11:00 UTC | May 12, 13:15 UTC | 2h 15m |
| 2026-05-12 | VTARO | - | May 12, 06:40 UTC | May 12, 08:20 UTC | 1h 40m |
| 2026-05-10 | VTARO | - | May 10, 11:10 UTC | May 10, 13:40 UTC | 2h 30m |
| 2026-05-09 | VTARO | - | May 9, 12:50 UTC | May 9, 13:50 UTC | 1h 0m |
| 2026-05-09 | VTARO | - | May 9, 11:45 UTC | May 9, 12:25 UTC | 40m |
| 2026-05-09 | VTARO | - | May 9, 09:20 UTC | May 9, 09:50 UTC | 30m |
| 2026-05-09 | VTARO | - | May 9, 02:30 UTC | May 9, 03:05 UTC | 35m |
| 2026-05-08 | VTARO | - | May 8, 09:25 UTC | May 8, 10:19 UTC | 55m |
| 2026-05-07 | VTARO | - | May 7, 06:50 UTC | May 7, 07:30 UTC | 40m |
| 2026-05-06 | VTARO | - | May 6, 06:25 UTC | May 6, 06:45 UTC | 20m |
| 2026-05-04 | VTARO | - | May 4, 07:15 UTC | May 4, 08:10 UTC | 55m |
| 2026-05-04 | VTARO | - | May 4, 05:40 UTC | May 4, 05:50 UTC | 10m |
| 2026-05-04 | VTARO | - | May 4, 04:00 UTC | May 4, 04:15 UTC | 15m |
| 2026-05-04 | VTARO | - | May 4, 02:00 UTC | May 4, 02:39 UTC | 40m |
| 2026-05-03 | VTARO | - | May 3, 07:05 UTC | May 3, 09:30 UTC | 2h 25m |
| 2026-05-03 | VTARO | - | May 3, 04:15 UTC | May 3, 06:00 UTC | 1h 45m |
| 2026-05-01 | VTARO | - | May 1, 09:35 UTC | May 1, 10:10 UTC | 35m |
| 2026-05-01 | VTARO | - | May 1, 04:15 UTC | May 1, 04:35 UTC | 20m |
| 2026-04-30 | VTARO | - | Apr 30, 13:10 UTC | Apr 30, 15:50 UTC | 2h 40m |
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-ARO page for operator, model, and routing details .