sensors Mode-S transponder
80165F
ICAO 24-bit transponder address · allocated to India
Currently assigned to VT-NSG · EMBRAER EMB-135 Legacy
- Hex
- 80165F
- Octal
- 40013137
- Decimal
- 8,394,335
- Country
- IN
- Tail
- VT-NSG
- Type
- E35L
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- IN
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 80165F 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 |
|---|---|---|---|
| VTNSG | - | 49 | 2026-06-02 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | VTNSG | - | Jun 2, 10:30 UTC | Jun 2, 10:40 UTC | 10m |
| 2026-06-01 | VTNSG | - | Jun 1, 13:50 UTC | Jun 1, 14:15 UTC | 25m |
| 2026-06-01 | VTNSG | - | Jun 1, 12:20 UTC | Jun 1, 12:30 UTC | 10m |
| 2026-06-01 | VTNSG | - | Jun 1, 08:50 UTC | Jun 1, 09:00 UTC | 10m |
| 2026-05-31 | VTNSG | - | May 31, 18:35 UTC | May 31, 19:20 UTC | 45m |
| 2026-05-31 | VTNSG | - | May 31, 10:50 UTC | May 31, 11:00 UTC | 10m |
| 2026-05-30 | VTNSG | - | May 30, 13:10 UTC | May 30, 13:40 UTC | 30m |
| 2026-05-30 | VTNSG | - | May 30, 11:45 UTC | May 30, 12:30 UTC | 45m |
| 2026-05-30 | VTNSG | - | May 30, 00:40 UTC | May 30, 01:10 UTC | 30m |
| 2026-05-29 | VTNSG | - | May 29, 23:50 UTC | May 30, 00:00 UTC | 10m |
| 2026-05-28 | VTNSG | - | May 28, 10:45 UTC | May 28, 11:25 UTC | 40m |
| 2026-05-26 | VTNSG | - | May 26, 15:49 UTC | May 26, 16:20 UTC | 30m |
| 2026-05-25 | VTNSG | - | May 25, 15:25 UTC | May 25, 16:00 UTC | 35m |
| 2026-05-25 | VTNSG | - | May 25, 11:25 UTC | May 25, 11:45 UTC | 20m |
| 2026-05-24 | VTNSG | - | May 24, 13:15 UTC | May 24, 15:45 UTC | 2h 30m |
| 2026-05-24 | VTNSG | - | May 24, 09:15 UTC | May 24, 09:30 UTC | 15m |
| 2026-05-24 | VTNSG | - | May 24, 07:05 UTC | May 24, 07:35 UTC | 30m |
| 2026-05-20 | VTNSG | - | May 20, 12:20 UTC | May 20, 13:30 UTC | 1h 10m |
| 2026-05-18 | VTNSG | - | May 18, 09:55 UTC | May 18, 10:15 UTC | 20m |
| 2026-05-15 | VTNSG | - | May 15, 12:15 UTC | May 15, 14:05 UTC | 1h 50m |
| 2026-05-14 | VTNSG | - | May 14, 16:20 UTC | May 14, 16:55 UTC | 35m |
| 2026-05-14 | VTNSG | - | May 14, 13:15 UTC | May 14, 13:30 UTC | 15m |
| 2026-05-13 | VTNSG | - | May 13, 11:35 UTC | May 13, 11:45 UTC | 10m |
| 2026-05-13 | VTNSG | - | May 13, 07:25 UTC | May 13, 07:40 UTC | 15m |
| 2026-05-13 | VTNSG | - | May 13, 02:20 UTC | May 13, 02:50 UTC | 30m |
| 2026-05-12 | VTNSG | - | May 12, 12:30 UTC | May 12, 14:35 UTC | 2h 5m |
| 2026-05-11 | VTNSG | - | May 11, 12:50 UTC | May 11, 14:35 UTC | 1h 45m |
| 2026-05-10 | VTNSG | - | May 10, 12:00 UTC | May 10, 12:19 UTC | 20m |
| 2026-05-10 | VTNSG | - | May 10, 03:30 UTC | May 10, 04:04 UTC | 35m |
| 2026-05-10 | VTNSG | - | May 10, 01:14 UTC | May 10, 01:30 UTC | 15m |
| 2026-05-07 | VTNSG | - | May 7, 17:15 UTC | May 7, 18:15 UTC | 1h 0m |
| 2026-05-05 | VTNSG | - | May 5, 15:40 UTC | May 6, 03:40 UTC | 12h 0m |
| 2026-04-30 | VTNSG | - | Apr 30, 18:55 UTC | May 1, 09:20 UTC | 14h 25m |
| 2026-04-30 | VTNSG | - | Apr 30, 11:50 UTC | Apr 30, 12:20 UTC | 30m |
| 2026-04-30 | VTNSG | - | Apr 30, 08:55 UTC | Apr 30, 10:30 UTC | 1h 35m |
| 2026-04-29 | VTNSG | - | Apr 29, 14:10 UTC | Apr 29, 14:55 UTC | 45m |
| 2026-04-28 | VTNSG | - | Apr 28, 03:45 UTC | Apr 28, 04:05 UTC | 20m |
| 2026-04-27 | VTNSG | - | Apr 27, 19:30 UTC | Apr 27, 19:45 UTC | 15m |
| 2026-04-24 | VTNSG | - | Apr 24, 18:00 UTC | Apr 25, 03:40 UTC | 9h 40m |
| 2026-04-23 | VTNSG | - | Apr 23, 15:05 UTC | Apr 23, 15:25 UTC | 20m |
| 2026-04-18 | VTNSG | - | Apr 18, 09:00 UTC | Apr 18, 09:20 UTC | 20m |
| 2026-04-17 | VTNSG | - | Apr 17, 07:20 UTC | Apr 17, 09:15 UTC | 1h 55m |
| 2026-04-17 | VTNSG | - | Apr 17, 06:15 UTC | Apr 17, 07:15 UTC | 1h 0m |
| 2026-04-17 | VTNSG | - | Apr 17, 00:15 UTC | Apr 17, 01:15 UTC | 1h 0m |
| 2026-04-15 | VTNSG | - | Apr 15, 15:05 UTC | Apr 15, 15:20 UTC | 15m |
| 2026-04-13 | VTNSG | - | Apr 13, 14:20 UTC | Apr 13, 14:50 UTC | 30m |
| 2026-04-13 | VTNSG | - | Apr 13, 06:10 UTC | Apr 13, 06:40 UTC | 30m |
| 2026-04-13 | VTNSG | - | Apr 13, 03:30 UTC | Apr 13, 03:45 UTC | 15m |
| 2026-04-12 | VTNSG | - | Apr 12, 17:25 UTC | Apr 12, 18:05 UTC | 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-NSG page for operator, model, and routing details .