sensors Mode-S transponder
C2B585
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to 130610 · Lockheed Martin CC-130J-30 Hercules · operated by ROYAL CANADIAN AIR FORCE
- Hex
- C2B585
- Octal
- 60532605
- Decimal
- 12,760,453
- Country
- CA
- Tail
- 130610
- Type
- C30J
- Flights observed
- 52
- Distinct callsigns
- 11
- Country
- CA
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address C2B585 falls within the block assigned to Canada (CA) by ICAO Annex 10, Volume III. Every aircraft registered in Canada 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 11 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-13 | CFC2949 | - | Jun 13, 12:20 UTC | Jun 13, 17:30 UTC | 5h 10m |
| 2026-06-13 | CFC2949 | CPH → RZE | Jun 13, 07:55 UTC | Jun 13, 09:25 UTC | 1h 30m |
| 2026-06-11 | CFC2949 | - | Jun 11, 13:35 UTC | Jun 11, 15:25 UTC | 1h 50m |
| 2026-06-11 | CFC2949 | - | Jun 11, 09:35 UTC | Jun 11, 12:40 UTC | 3h 5m |
| 2026-06-11 | CFC2949 | - | Jun 11, 07:35 UTC | Jun 11, 08:50 UTC | 1h 15m |
| 2026-06-09 | CFC2952 | - | Jun 9, 18:40 UTC | Jun 9, 20:15 UTC | 1h 35m |
| 2026-06-09 | CFC2952 | - | Jun 9, 16:45 UTC | Jun 9, 17:40 UTC | 55m |
| 2026-06-09 | CFC2952 | - | Jun 9, 14:30 UTC | Jun 9, 15:50 UTC | 1h 20m |
| 2026-06-09 | CFC2952 | - | Jun 9, 11:30 UTC | Jun 9, 13:30 UTC | 2h 0m |
| 2026-06-08 | CFC2952 | - | Jun 8, 15:20 UTC | Jun 8, 15:45 UTC | 25m |
| 2026-06-08 | CFC2952 | - | Jun 8, 12:10 UTC | Jun 8, 14:20 UTC | 2h 10m |
| 2026-06-08 | CFC2952 | VIE → RZE | Jun 8, 09:15 UTC | Jun 8, 10:15 UTC | 1h 0m |
| 2026-06-06 | CFC2952 | - | Jun 6, 13:20 UTC | Jun 6, 15:39 UTC | 2h 20m |
| 2026-06-06 | CFC2952 | - | Jun 6, 12:24 UTC | Jun 6, 12:49 UTC | 25m |
| 2026-06-06 | CFC2952 | - | Jun 6, 11:45 UTC | Jun 6, 12:20 UTC | 35m |
| 2026-06-05 | CFC2952 | - | Jun 5, 10:25 UTC | Jun 5, 11:05 UTC | 40m |
| 2026-05-29 | CFC2931 | RZE → PIK | May 29, 16:30 UTC | May 29, 20:15 UTC | 3h 45m |
| 2026-05-29 | CFC2931 | - | May 29, 10:40 UTC | May 29, 15:55 UTC | 5h 15m |
| 2026-05-28 | CFC2931 | - | May 28, 12:25 UTC | May 28, 16:15 UTC | 3h 50m |
| 2026-05-27 | CFC2931 | RZE → NUE | May 27, 16:25 UTC | May 27, 18:10 UTC | 1h 45m |
| 2026-05-27 | CFC2931 | - | May 27, 10:45 UTC | May 27, 15:35 UTC | 4h 50m |
| 2026-05-26 | CFC2931 | - | May 26, 08:59 UTC | May 26, 12:40 UTC | 3h 40m |
| 2026-05-22 | CFC2937 | - | May 22, 11:15 UTC | May 22, 14:25 UTC | 3h 10m |
| 2026-05-21 | CFC2937 | - | May 21, 14:15 UTC | May 21, 18:15 UTC | 4h 0m |
| 2026-05-21 | CFC2937 | - | May 21, 07:55 UTC | May 21, 12:35 UTC | 4h 40m |
| 2026-05-18 | CFC2938 | - | May 18, 17:10 UTC | May 18, 20:00 UTC | 2h 49m |
| 2026-05-18 | CFC2938 | RZE → PUF | May 18, 12:20 UTC | May 18, 16:15 UTC | 3h 55m |
| 2026-05-18 | CFC2938 | - | May 18, 08:35 UTC | May 18, 11:20 UTC | 2h 45m |
| 2026-05-16 | CFC2938 | - | May 16, 15:31 UTC | May 16, 18:20 UTC | 2h 50m |
| 2026-05-16 | CFC2938 | - | May 16, 11:46 UTC | May 16, 14:35 UTC | 2h 50m |
| 2026-05-16 | CFC2938 | - | May 16, 08:20 UTC | May 16, 10:05 UTC | 1h 45m |
| 2026-05-13 | CFC2946 | RZE → PIK | May 13, 15:00 UTC | May 13, 19:15 UTC | 4h 15m |
| 2026-05-13 | CFC2946 | - | May 13, 13:40 UTC | May 13, 13:45 UTC | 5m |
| 2026-05-13 | CFC2946 | - | May 13, 12:20 UTC | May 13, 12:45 UTC | 25m |
| 2026-05-12 | CFC2946 | - | May 12, 17:40 UTC | May 12, 18:55 UTC | 1h 15m |
| 2026-05-12 | CFC2946 | - | May 12, 15:40 UTC | May 12, 16:55 UTC | 1h 15m |
| 2026-05-12 | CFC2946 | - | May 12, 09:25 UTC | May 12, 13:05 UTC | 3h 40m |
| 2026-05-10 | CFC2939 | - | May 10, 13:49 UTC | May 10, 17:34 UTC | 3h 45m |
| 2026-05-10 | CFC2939 | - | May 10, 10:19 UTC | May 10, 12:54 UTC | 2h 35m |
| 2026-05-09 | CFC2939 | - | May 9, 13:00 UTC | May 9, 16:20 UTC | 3h 20m |
| 2026-05-09 | CFC2939 | - | May 9, 10:15 UTC | May 9, 12:15 UTC | 2h 0m |
| 2026-05-09 | CFC2939 | - | May 9, 07:05 UTC | May 9, 09:10 UTC | 2h 5m |
| 2026-05-08 | CFC4248 | BRU → PIK | May 8, 12:55 UTC | May 8, 14:25 UTC | 1h 30m |
| 2026-05-08 | CFC4248 | - | May 8, 10:14 UTC | May 8, 11:49 UTC | 1h 35m |
| 2026-05-07 | CFC4248 | - | May 7, 01:55 UTC | May 7, 02:40 UTC | 45m |
| 2026-05-06 | CFC4248 | - | May 6, 15:25 UTC | May 6, 17:20 UTC | 1h 55m |
| 2026-05-04 | TRKR5 | - | May 4, 19:25 UTC | May 4, 21:20 UTC | 1h 55m |
| 2026-04-19 | CFC2573 | - | Apr 19, 17:05 UTC | Apr 19, 23:00 UTC | 5h 55m |
| 2026-04-18 | CFC2573 | - | Apr 18, 20:00 UTC | Apr 18, 23:00 UTC | 3h 0m |
| 2026-04-18 | CFC2573 | - | Apr 18, 15:45 UTC | Apr 18, 19:30 UTC | 3h 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 130610 page for operator, model, and routing details .