sensors Mode-S transponder
800B60
ICAO 24-bit transponder address · allocated to India
Currently assigned to VT-SDK · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 800B60
- Octal
- 40005540
- Decimal
- 8,391,520
- Country
- IN
- Tail
- VT-SDK
- Type
- GLEX
- Flights observed
- 34
- Distinct callsigns
- 1
- Country
- IN
- Last broadcast
- Jul 20, 13:30 UTC
Last known position
Country allocation
The ICAO 24-bit address 800B60 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 |
|---|---|---|---|
| VTSDK | - | 34 | 2026-07-20 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | VTSDK | - | Jul 20, 03:30 UTC | Jul 20, 12:50 UTC | 9h 20m |
| 2026-07-18 | VTSDK | - | Jul 18, 15:30 UTC | Jul 18, 16:50 UTC | 1h 20m |
| 2026-07-17 | VTSDK | - | Jul 17, 11:30 UTC | Jul 17, 13:10 UTC | 1h 40m |
| 2026-07-02 | VTSDK | - | Jul 2, 12:55 UTC | Jul 2, 13:25 UTC | 30m |
| 2026-07-01 | VTSDK | - | Jul 1, 11:05 UTC | Jul 1, 12:50 UTC | 1h 45m |
| 2026-06-29 | VTSDK | - | Jun 29, 17:14 UTC | Jun 29, 17:30 UTC | 15m |
| 2026-06-29 | VTSDK | - | Jun 29, 15:24 UTC | Jun 29, 15:34 UTC | 10m |
| 2026-06-24 | VTSDK | - | Jun 24, 16:19 UTC | Jun 24, 16:34 UTC | 15m |
| 2026-06-24 | VTSDK | - | Jun 24, 15:09 UTC | Jun 24, 15:24 UTC | 15m |
| 2026-06-20 | VTSDK | - | Jun 20, 14:59 UTC | Jun 20, 15:14 UTC | 15m |
| 2026-06-20 | VTSDK | - | Jun 20, 04:34 UTC | Jun 20, 04:49 UTC | 15m |
| 2026-06-19 | VTSDK | - | Jun 19, 11:04 UTC | Jun 19, 11:20 UTC | 15m |
| 2026-06-19 | VTSDK | - | Jun 19, 09:30 UTC | Jun 19, 09:40 UTC | 10m |
| 2026-06-18 | VTSDK | - | Jun 18, 13:10 UTC | Jun 18, 13:25 UTC | 15m |
| 2026-06-17 | VTSDK | - | Jun 17, 13:10 UTC | Jun 17, 21:35 UTC | 8h 25m |
| 2026-06-16 | VTSDK | - | Jun 16, 15:15 UTC | Jun 16, 16:35 UTC | 1h 20m |
| 2026-06-12 | VTSDK | - | Jun 12, 20:25 UTC | Jun 13, 06:00 UTC | 9h 34m |
| 2026-06-09 | VTSDK | - | Jun 9, 09:30 UTC | Jun 9, 10:00 UTC | 30m |
| 2026-06-07 | VTSDK | - | Jun 7, 16:45 UTC | Jun 7, 17:05 UTC | 20m |
| 2026-06-07 | VTSDK | - | Jun 7, 14:40 UTC | Jun 7, 14:50 UTC | 10m |
| 2026-06-07 | VTSDK | - | Jun 7, 13:15 UTC | Jun 7, 13:50 UTC | 35m |
| 2026-06-07 | VTSDK | - | Jun 7, 10:50 UTC | Jun 7, 12:25 UTC | 1h 35m |
| 2026-05-31 | VTSDK | - | May 31, 11:05 UTC | May 31, 11:35 UTC | 30m |
| 2026-05-14 | VTSDK | - | May 14, 11:05 UTC | May 14, 11:15 UTC | 10m |
| 2026-05-13 | VTSDK | - | May 13, 12:30 UTC | May 13, 13:00 UTC | 30m |
| 2026-05-12 | VTSDK | - | May 12, 14:05 UTC | May 13, 13:00 UTC | 22h 55m |
| 2026-05-12 | VTSDK | - | May 12, 13:05 UTC | May 12, 14:10 UTC | 1h 5m |
| 2026-05-11 | VTSDK | - | May 11, 18:25 UTC | May 11, 19:40 UTC | 1h 15m |
| 2026-04-24 | VTSDK | - | Apr 24, 11:50 UTC | Apr 24, 12:30 UTC | 40m |
| 2026-04-23 | VTSDK | - | Apr 23, 08:50 UTC | Apr 23, 09:15 UTC | 25m |
| 2026-04-22 | VTSDK | - | Apr 22, 06:15 UTC | Apr 22, 07:05 UTC | 50m |
| 2026-04-22 | VTSDK | - | Apr 22, 03:05 UTC | Apr 22, 04:55 UTC | 1h 50m |
| 2026-04-15 | VTSDK | - | Apr 15, 17:15 UTC | Apr 15, 17:40 UTC | 25m |
| 2026-04-15 | VTSDK | - | Apr 15, 09:05 UTC | Apr 15, 09:50 UTC | 45m |
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-SDK page for operator, model, and routing details .