sensors Mode-S transponder
801694
ICAO 24-bit transponder address · allocated to India
Currently assigned to VT-AFO · BOEING 737-800
- Hex
- 801694
- Octal
- 40013224
- Decimal
- 8,394,388
- Country
- IN
- Tail
- VT-AFO
- Type
- B738
- Flights observed
- 50
- Distinct callsigns
- 7
- Country
- IN
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 801694 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 7 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-31 | O9708 | - | May 31, 17:25 UTC | May 31, 20:25 UTC | 3h 0m |
| 2026-05-31 | O9707 | - | May 31, 14:15 UTC | May 31, 15:30 UTC | 1h 15m |
| 2026-05-31 | O9707 | - | May 31, 12:10 UTC | May 31, 12:50 UTC | 40m |
| 2026-05-28 | O9708 | - | May 28, 17:45 UTC | May 28, 20:55 UTC | 3h 10m |
| 2026-05-28 | O9707 | - | May 28, 15:20 UTC | May 28, 15:30 UTC | 10m |
| 2026-05-28 | O9707 | - | May 28, 13:55 UTC | May 28, 14:50 UTC | 55m |
| 2026-05-28 | O9707 | - | May 28, 11:15 UTC | May 28, 13:00 UTC | 1h 45m |
| 2026-05-27 | O9102 | - | May 27, 01:19 UTC | May 27, 07:10 UTC | 5h 50m |
| 2026-05-24 | O9707 | - | May 24, 20:20 UTC | May 25, 02:35 UTC | 6h 15m |
| 2026-05-24 | O9707 | - | May 24, 16:55 UTC | May 24, 18:45 UTC | 1h 50m |
| 2026-05-24 | O9102 | - | May 24, 00:55 UTC | May 24, 06:45 UTC | 5h 50m |
| 2026-05-23 | O9102 | - | May 23, 01:10 UTC | May 23, 07:10 UTC | 5h 59m |
| 2026-05-21 | O9708 | - | May 21, 18:35 UTC | May 21, 23:50 UTC | 5h 15m |
| 2026-05-21 | O9707 | - | May 21, 16:50 UTC | May 21, 17:20 UTC | 30m |
| 2026-05-20 | O9101 | - | May 20, 01:30 UTC | May 20, 11:40 UTC | 10h 11m |
| 2026-05-17 | O9708 | - | May 17, 16:55 UTC | May 17, 21:25 UTC | 4h 30m |
| 2026-05-17 | O9707 | - | May 17, 15:05 UTC | May 17, 15:25 UTC | 20m |
| 2026-05-17 | O9102 | - | May 17, 04:30 UTC | May 17, 07:40 UTC | 3h 10m |
| 2026-05-16 | O9102 | - | May 16, 12:05 UTC | May 17, 07:40 UTC | 19h 35m |
| 2026-05-16 | O9102 | - | May 16, 09:25 UTC | May 17, 07:40 UTC | 22h 15m |
| 2026-05-16 | O9102 | - | May 16, 07:05 UTC | May 17, 07:00 UTC | 23h 55m |
| 2026-05-16 | O9101 | - | May 16, 03:45 UTC | May 16, 12:40 UTC | 8h 56m |
| 2026-05-14 | O9102 | - | May 14, 04:40 UTC | May 14, 07:45 UTC | 3h 5m |
| 2026-05-13 | O9102 | - | May 13, 11:05 UTC | May 14, 07:45 UTC | 20h 40m |
| 2026-05-13 | O9102 | - | May 13, 10:40 UTC | May 14, 07:45 UTC | 21h 5m |
| 2026-05-13 | O9102 | - | May 13, 08:05 UTC | May 14, 07:00 UTC | 22h 55m |
| 2026-05-13 | O9102 | - | May 13, 05:55 UTC | May 14, 04:50 UTC | 22h 55m |
| 2026-05-13 | O9102 | - | May 13, 00:35 UTC | May 13, 11:30 UTC | 10h 55m |
| 2026-05-10 | O9708 | - | May 10, 16:10 UTC | May 10, 23:15 UTC | 7h 5m |
| 2026-05-10 | O9707 | - | May 10, 13:35 UTC | May 10, 15:15 UTC | 1h 40m |
| 2026-05-10 | O9102 | - | May 10, 02:20 UTC | May 10, 07:50 UTC | 5h 30m |
| 2026-05-09 | O9102 | - | May 9, 01:25 UTC | May 9, 07:15 UTC | 5h 50m |
| 2026-05-08 | O9102 | - | May 8, 11:44 UTC | May 9, 07:15 UTC | 19h 30m |
| 2026-05-08 | O9102 | - | May 8, 09:34 UTC | May 9, 07:15 UTC | 21h 40m |
| 2026-05-08 | O9102 | - | May 8, 07:24 UTC | May 9, 07:00 UTC | 23h 35m |
| 2026-05-08 | O9102 | - | May 8, 04:29 UTC | May 9, 01:30 UTC | 21h 0m |
| 2026-05-07 | O9708 | - | May 7, 17:50 UTC | May 8, 12:30 UTC | 18h 40m |
| 2026-05-07 | O9708 | - | May 7, 15:05 UTC | May 8, 12:30 UTC | 21h 25m |
| 2026-05-07 | O9708 | - | May 7, 13:05 UTC | May 8, 12:30 UTC | 23h 25m |
| 2026-05-07 | O9707 | - | May 7, 12:40 UTC | May 8, 09:44 UTC | 21h 5m |
| 2026-05-02 | O9102 | - | May 2, 09:35 UTC | May 2, 13:35 UTC | 4h 0m |
| 2026-04-27 | O9102 | - | Apr 27, 01:20 UTC | Apr 27, 07:15 UTC | 5h 55m |
| 2026-04-23 | O9101 | - | Apr 23, 02:05 UTC | Apr 23, 10:45 UTC | 8h 40m |
| 2026-04-18 | O9309 | - | Apr 18, 11:55 UTC | Apr 18, 16:00 UTC | 4h 5m |
| 2026-04-18 | O9304 | - | Apr 18, 09:05 UTC | Apr 18, 09:20 UTC | 15m |
| 2026-04-18 | O9303 | - | Apr 18, 05:40 UTC | Apr 18, 10:05 UTC | 4h 25m |
| 2026-04-16 | O9708 | - | Apr 16, 17:25 UTC | Apr 16, 18:25 UTC | 1h 0m |
| 2026-04-16 | O9708 | - | Apr 16, 16:10 UTC | Apr 16, 16:55 UTC | 45m |
| 2026-04-15 | O9707 | - | Apr 15, 05:20 UTC | Apr 15, 05:35 UTC | 15m |
| 2026-04-15 | O9707 | - | Apr 15, 01:45 UTC | Apr 15, 02:35 UTC | 50m |
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-AFO page for operator, model, and routing details .