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