sensors Mode-S transponder
4CC584
ICAO 24-bit transponder address
- Hex
- 4CC584
- Octal
- 23142604
- Decimal
- 5,031,300
- Flights observed
- 33
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 3d ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TFSKY | - | 33 | 2026-07-16 |
Recent flights last 33
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | TFSKY | - | Jul 16, 16:09 UTC | Jul 16, 16:25 UTC | 15m |
| 2026-07-08 | TFSKY | - | Jul 8, 14:30 UTC | Jul 8, 14:45 UTC | 15m |
| 2026-07-04 | TFSKY | - | Jul 4, 16:45 UTC | Jul 4, 17:00 UTC | 15m |
| 2026-07-04 | TFSKY | - | Jul 4, 09:10 UTC | Jul 4, 09:15 UTC | 5m |
| 2026-06-30 | TFSKY | - | Jun 30, 11:15 UTC | Jun 30, 11:30 UTC | 15m |
| 2026-06-30 | TFSKY | - | Jun 30, 07:45 UTC | Jun 30, 08:00 UTC | 15m |
| 2026-06-16 | TFSKY | - | Jun 16, 22:20 UTC | Jun 16, 22:30 UTC | 10m |
| 2026-06-16 | TFSKY | - | Jun 16, 21:30 UTC | Jun 16, 21:40 UTC | 10m |
| 2026-06-16 | TFSKY | - | Jun 16, 19:30 UTC | Jun 16, 19:45 UTC | 15m |
| 2026-06-16 | TFSKY | RKV → RKV | Jun 16, 15:35 UTC | Jun 16, 15:50 UTC | 15m |
| 2026-06-04 | TFSKY | RKV → RKV | Jun 4, 21:15 UTC | Jun 4, 22:05 UTC | 50m |
| 2026-05-30 | TFSKY | RKV → RKV | May 30, 14:00 UTC | May 30, 14:05 UTC | 5m |
| 2026-05-28 | TFSKY | - | May 28, 21:25 UTC | May 28, 22:45 UTC | 1h 20m |
| 2026-05-28 | TFSKY | - | May 28, 19:35 UTC | May 28, 19:40 UTC | 5m |
| 2026-05-21 | TFSKY | - | May 21, 19:20 UTC | May 21, 19:30 UTC | 10m |
| 2026-05-14 | TFSKY | - | May 14, 22:25 UTC | May 14, 22:30 UTC | 5m |
| 2026-05-14 | TFSKY | - | May 14, 20:20 UTC | May 14, 20:25 UTC | 5m |
| 2026-05-07 | TFSKY | - | May 7, 22:10 UTC | May 7, 22:20 UTC | 10m |
| 2026-05-07 | TFSKY | - | May 7, 19:50 UTC | May 7, 19:55 UTC | 5m |
| 2026-05-04 | TFSKY | - | May 4, 22:00 UTC | May 4, 22:25 UTC | 25m |
| 2026-05-04 | TFSKY | - | May 4, 21:10 UTC | May 4, 21:25 UTC | 15m |
| 2026-05-03 | TFSKY | - | May 3, 17:40 UTC | May 3, 17:50 UTC | 10m |
| 2026-05-03 | TFSKY | - | May 3, 12:40 UTC | May 3, 13:10 UTC | 30m |
| 2026-05-01 | TFSKY | RKV → RKV | May 1, 19:55 UTC | May 1, 21:05 UTC | 1h 10m |
| 2026-04-30 | TFSKY | - | Apr 30, 20:25 UTC | Apr 30, 20:45 UTC | 20m |
| 2026-04-30 | TFSKY | - | Apr 30, 19:25 UTC | Apr 30, 19:30 UTC | 5m |
| 2026-04-20 | TFSKY | - | Apr 20, 21:10 UTC | Apr 20, 21:35 UTC | 25m |
| 2026-04-20 | TFSKY | - | Apr 20, 20:05 UTC | Apr 20, 20:30 UTC | 25m |
| 2026-04-20 | TFSKY | - | Apr 20, 15:15 UTC | Apr 20, 15:30 UTC | 15m |
| 2026-04-20 | TFSKY | - | Apr 20, 13:10 UTC | Apr 20, 13:20 UTC | 10m |
| 2026-04-17 | TFSKY | - | Apr 17, 17:55 UTC | Apr 17, 18:15 UTC | 20m |
| 2026-04-17 | TFSKY | - | Apr 17, 16:50 UTC | Apr 17, 17:00 UTC | 10m |
| 2026-04-17 | TFSKY | RKV → RKV | Apr 17, 13:30 UTC | Apr 17, 13:45 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.