sensors Mode-S transponder
500527
ICAO 24-bit transponder address
- Hex
- 500527
- Octal
- 24002447
- Decimal
- 5,244,199
- Flights observed
- 29
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 11d ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| T7KPS | - | 29 | 2026-07-17 |
Recent flights last 29
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | T7KPS | - | Jul 17, 16:04 UTC | Jul 17, 18:44 UTC | 2h 40m |
| 2026-07-16 | T7KPS | - | Jul 16, 12:09 UTC | Jul 16, 15:30 UTC | 3h 20m |
| 2026-07-16 | T7KPS | - | Jul 16, 09:45 UTC | Jul 16, 10:40 UTC | 55m |
| 2026-07-13 | T7KPS | ATH → ISL | Jul 13, 06:20 UTC | Jul 13, 07:10 UTC | 50m |
| 2026-07-13 | T7KPS | - | Jul 13, 05:10 UTC | Jul 13, 05:31 UTC | 20m |
| 2026-07-13 | T7KPS | - | Jul 13, 03:30 UTC | Jul 13, 04:20 UTC | 50m |
| 2026-07-11 | T7KPS | JMK → ISL | Jul 11, 16:50 UTC | Jul 11, 17:35 UTC | 45m |
| 2026-07-11 | T7KPS | - | Jul 11, 14:55 UTC | Jul 11, 16:00 UTC | 1h 5m |
| 2026-07-10 | T7KPS | - | Jul 10, 21:10 UTC | Jul 10, 22:15 UTC | 1h 5m |
| 2026-07-10 | T7KPS | - | Jul 10, 19:15 UTC | Jul 10, 20:15 UTC | 1h 0m |
| 2026-07-05 | T7KPS | - | Jul 5, 14:20 UTC | Jul 5, 16:30 UTC | 2h 10m |
| 2026-07-04 | T7KPS | - | Jul 4, 08:35 UTC | Jul 4, 10:55 UTC | 2h 20m |
| 2026-06-30 | T7KPS | - | Jun 30, 18:20 UTC | Jul 1, 04:55 UTC | 10h 35m |
| 2026-06-30 | T7KPS | - | Jun 30, 14:55 UTC | Jun 30, 15:45 UTC | 50m |
| 2026-06-30 | T7KPS | - | Jun 30, 02:35 UTC | Jun 30, 04:50 UTC | 2h 15m |
| 2026-06-28 | T7KPS | - | Jun 28, 21:24 UTC | Jun 28, 22:29 UTC | 1h 5m |
| 2026-06-28 | T7KPS | - | Jun 28, 14:54 UTC | Jun 28, 16:35 UTC | 1h 40m |
| 2026-06-26 | T7KPS | - | Jun 26, 07:35 UTC | Jun 26, 12:00 UTC | 4h 25m |
| 2026-06-25 | T7KPS | - | Jun 25, 14:44 UTC | Jun 25, 17:39 UTC | 2h 55m |
| 2026-06-22 | T7KPS | - | Jun 22, 22:59 UTC | Jun 23, 06:49 UTC | 7h 50m |
| 2026-06-22 | T7KPS | - | Jun 22, 16:34 UTC | Jun 22, 21:40 UTC | 5h 5m |
| 2026-06-20 | T7KPS | - | Jun 20, 12:14 UTC | Jun 20, 13:44 UTC | 1h 30m |
| 2026-06-19 | T7KPS | - | Jun 19, 02:35 UTC | Jun 19, 03:15 UTC | 40m |
| 2026-06-13 | T7KPS | - | Jun 13, 23:10 UTC | Jun 13, 23:35 UTC | 25m |
| 2026-06-13 | T7KPS | - | Jun 13, 14:35 UTC | Jun 13, 16:25 UTC | 1h 50m |
| 2026-06-12 | T7KPS | - | Jun 12, 15:25 UTC | Jun 12, 16:00 UTC | 35m |
| 2026-06-12 | T7KPS | - | Jun 12, 14:35 UTC | Jun 12, 15:05 UTC | 30m |
| 2026-06-11 | T7KPS | - | Jun 11, 21:35 UTC | Jun 11, 22:10 UTC | 35m |
| 2026-06-11 | T7KPS | - | Jun 11, 20:35 UTC | Jun 11, 21:15 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.