sensors Mode-S transponder
0B8960
ICAO 24-bit transponder address
- Hex
- 0B8960
- Octal
- 02704540
- Decimal
- 756,064
- Flights observed
- 30
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 1d ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TGGAO | - | 30 | 2026-06-01 |
Recent flights last 30
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | TGGAO | - | Jun 1, 22:50 UTC | Jun 1, 23:00 UTC | 10m |
| 2026-06-01 | TGGAO | - | Jun 1, 19:40 UTC | Jun 1, 19:50 UTC | 10m |
| 2026-05-24 | TGGAO | GUA → GUA | May 24, 15:10 UTC | May 24, 15:25 UTC | 15m |
| 2026-05-23 | TGGAO | - | May 23, 12:55 UTC | May 23, 14:00 UTC | 1h 5m |
| 2026-05-16 | TGGAO | GUA → GUA | May 16, 16:40 UTC | May 16, 19:10 UTC | 2h 30m |
| 2026-05-16 | TGGAO | GUA → GUA | May 16, 12:55 UTC | May 16, 14:31 UTC | 1h 35m |
| 2026-05-16 | TGGAO | - | May 16, 00:20 UTC | May 16, 00:35 UTC | 15m |
| 2026-05-15 | TGGAO | - | May 15, 23:35 UTC | May 15, 23:40 UTC | 5m |
| 2026-05-10 | TGGAO | GUA → GUA | May 10, 12:40 UTC | May 10, 14:20 UTC | 1h 40m |
| 2026-05-06 | TGGAO | - | May 6, 20:55 UTC | May 6, 21:10 UTC | 15m |
| 2026-05-06 | TGGAO | - | May 6, 18:50 UTC | May 6, 19:15 UTC | 25m |
| 2026-05-05 | TGGAO | GUA → GUA | May 5, 23:35 UTC | May 6, 00:01 UTC | 25m |
| 2026-05-04 | TGGAO | - | May 4, 21:05 UTC | May 4, 21:40 UTC | 35m |
| 2026-05-04 | TGGAO | - | May 4, 14:40 UTC | May 4, 15:30 UTC | 50m |
| 2026-05-03 | TGGAO | - | May 3, 17:50 UTC | May 3, 18:09 UTC | 20m |
| 2026-05-03 | TGGAO | - | May 3, 14:25 UTC | May 3, 14:35 UTC | 10m |
| 2026-05-02 | TGGAO | - | May 2, 13:00 UTC | May 2, 14:30 UTC | 1h 30m |
| 2026-05-01 | TGGAO | - | May 1, 20:05 UTC | May 1, 20:25 UTC | 20m |
| 2026-05-01 | TGGAO | - | May 1, 17:25 UTC | May 1, 17:40 UTC | 15m |
| 2026-04-30 | TGGAO | - | Apr 30, 17:20 UTC | Apr 30, 18:05 UTC | 45m |
| 2026-04-30 | TGGAO | - | Apr 30, 12:15 UTC | Apr 30, 13:10 UTC | 55m |
| 2026-04-24 | TGGAO | - | Apr 24, 20:25 UTC | Apr 24, 20:35 UTC | 10m |
| 2026-04-24 | TGGAO | - | Apr 24, 17:15 UTC | Apr 24, 17:30 UTC | 15m |
| 2026-04-24 | TGGAO | - | Apr 24, 15:35 UTC | Apr 24, 16:40 UTC | 1h 5m |
| 2026-04-21 | TGGAO | GUA → GUA | Apr 21, 13:35 UTC | Apr 21, 14:01 UTC | 25m |
| 2026-04-18 | TGGAO | GUA → GUA | Apr 18, 15:25 UTC | Apr 18, 17:25 UTC | 2h 0m |
| 2026-04-18 | TGGAO | - | Apr 18, 14:00 UTC | Apr 18, 14:15 UTC | 15m |
| 2026-04-18 | TGGAO | - | Apr 18, 13:10 UTC | Apr 18, 13:25 UTC | 15m |
| 2026-04-15 | TGGAO | - | Apr 15, 23:35 UTC | Apr 16, 00:15 UTC | 40m |
| 2026-04-15 | TGGAO | - | Apr 15, 13:35 UTC | Apr 15, 14:30 UTC | 55m |
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.