sensors Mode-S transponder
800C3D
ICAO 24-bit transponder address · allocated to India
Currently assigned to K7067 · BOEING 777-300ER
- Hex
- 800C3D
- Octal
- 40006075
- Decimal
- 8,391,741
- Country
- IN
- Tail
- K7067
- Type
- B77W
- Flights observed
- 44
- Distinct callsigns
- 4
- Country
- IN
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 800C3D 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 4 distinct
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | VUAVF | - | Jul 14, 13:10 UTC | Jul 14, 16:10 UTC | 3h 0m |
| 2026-07-14 | VUAVF | - | Jul 14, 09:55 UTC | Jul 14, 12:30 UTC | 2h 35m |
| 2026-07-11 | INDIA1 | - | Jul 11, 12:30 UTC | Jul 12, 01:05 UTC | 12h 35m |
| 2026-07-11 | INDIA1 | - | Jul 11, 10:10 UTC | Jul 11, 10:25 UTC | 15m |
| 2026-07-10 | INDIA1 | - | Jul 10, 07:55 UTC | Jul 10, 08:20 UTC | 25m |
| 2026-07-10 | INDIA1 | - | Jul 10, 05:10 UTC | Jul 10, 05:40 UTC | 30m |
| 2026-07-08 | INDIA1 | - | Jul 8, 11:40 UTC | Jul 8, 12:50 UTC | 1h 10m |
| 2026-07-08 | INDIA1 | - | Jul 8, 02:40 UTC | Jul 8, 03:00 UTC | 20m |
| 2026-07-06 | INDIA1 | - | Jul 6, 10:15 UTC | Jul 6, 10:25 UTC | 10m |
| 2026-07-06 | INDIA1 | - | Jul 6, 04:10 UTC | Jul 6, 09:25 UTC | 5h 15m |
| 2026-07-02 | VUAVF | - | Jul 2, 12:35 UTC | Jul 2, 18:05 UTC | 5h 30m |
| 2026-06-30 | VUAVF | DEL → DEL | Jun 30, 05:55 UTC | Jun 30, 11:25 UTC | 5h 30m |
| 2026-06-29 | INDIA1 | - | Jun 29, 10:55 UTC | Jun 29, 12:39 UTC | 1h 45m |
| 2026-06-27 | INDIA1 | - | Jun 27, 03:55 UTC | Jun 27, 05:25 UTC | 1h 30m |
| 2026-06-24 | VUAVF | - | Jun 24, 08:49 UTC | Jun 24, 11:20 UTC | 2h 30m |
| 2026-06-21 | INDIA3 | CCU → DEL | Jun 21, 06:04 UTC | Jun 21, 07:45 UTC | 1h 40m |
| 2026-06-20 | VUAVF | DEL → CCU | Jun 20, 06:29 UTC | Jun 20, 08:14 UTC | 1h 45m |
| 2026-06-10 | VUAVF | - | Jun 10, 09:20 UTC | Jun 10, 14:30 UTC | 5h 10m |
| 2026-06-04 | VUAVF | - | Jun 4, 02:55 UTC | Jun 4, 05:35 UTC | 2h 40m |
| 2026-06-01 | VUAVF | - | Jun 1, 10:50 UTC | Jun 1, 17:55 UTC | 7h 5m |
| 2026-05-20 | INDIA1 | - | May 20, 17:05 UTC | May 21, 03:45 UTC | 10h 40m |
| 2026-05-19 | INDIA1 | - | May 19, 14:40 UTC | May 19, 17:15 UTC | 2h 35m |
| 2026-05-18 | INDIA1 | - | May 18, 06:20 UTC | May 18, 07:00 UTC | 40m |
| 2026-05-17 | INDIA1 | - | May 17, 10:40 UTC | May 17, 11:45 UTC | 1h 5m |
| 2026-05-15 | INDIA1 | - | May 15, 10:15 UTC | May 15, 17:50 UTC | 7h 34m |
| 2026-05-15 | INDIA1 | - | May 15, 03:25 UTC | May 15, 05:05 UTC | 1h 40m |
| 2026-05-12 | VUAVF | - | May 12, 13:40 UTC | May 12, 14:50 UTC | 1h 10m |
| 2026-05-12 | VUAVF | - | May 12, 11:05 UTC | May 12, 11:15 UTC | 10m |
| 2026-05-12 | VUAVF | - | May 12, 07:55 UTC | May 12, 10:15 UTC | 2h 20m |
| 2026-05-09 | INDIA1 | CCU → DEL | May 9, 07:45 UTC | May 9, 09:40 UTC | 1h 55m |
| 2026-05-09 | INDIA1 | - | May 9, 02:45 UTC | May 9, 04:25 UTC | 1h 40m |
| 2026-05-06 | VUAVF | - | May 6, 10:01 UTC | May 6, 12:20 UTC | 2h 20m |
| 2026-05-06 | VUAVF | - | May 6, 05:35 UTC | May 6, 07:05 UTC | 1h 30m |
| 2026-05-05 | VUAVF | DEL → DEL | May 5, 10:20 UTC | May 5, 16:30 UTC | 6h 10m |
| 2026-04-29 | VUAVF | DEL → DEL | Apr 29, 03:30 UTC | Apr 29, 05:45 UTC | 2h 15m |
| 2026-04-24 | INDIA1 | CCU → DEL | Apr 24, 10:20 UTC | Apr 24, 12:10 UTC | 1h 50m |
| 2026-04-23 | INDIA2 | - | Apr 23, 03:55 UTC | Apr 23, 05:40 UTC | 1h 45m |
| 2026-04-21 | VUAVF | CCU → DEL | Apr 21, 09:35 UTC | Apr 21, 11:30 UTC | 1h 55m |
| 2026-04-21 | VUAVF | DEL → CCU | Apr 21, 05:55 UTC | Apr 21, 07:35 UTC | 1h 40m |
| 2026-04-17 | VUAVF | - | Apr 17, 12:10 UTC | Apr 17, 13:00 UTC | 50m |
| 2026-04-17 | VUAVF | - | Apr 17, 09:20 UTC | Apr 17, 09:55 UTC | 35m |
| 2026-04-13 | VUAVF | - | Apr 13, 09:10 UTC | Apr 13, 11:30 UTC | 2h 20m |
| 2026-04-13 | VUAVF | - | Apr 13, 08:10 UTC | Apr 13, 08:20 UTC | 10m |
| 2026-04-13 | VUAVF | - | Apr 13, 06:10 UTC | Apr 13, 06:40 UTC | 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 K7067 page for operator, model, and routing details .