sensors Mode-S transponder
C07B3C
ICAO 24-bit transponder address · allocated to Canada
Currently assigned to C-GURJ · BOMBARDIER CL-600 Challenger · operated by Anderson Air Ltd
- Hex
- C07B3C
- Octal
- 60075474
- Decimal
- 12,614,460
- Country
- CA
- Tail
- C-GURJ
- Type
- CL60
- Flights observed
- 53
- Distinct callsigns
- 2
- Country
- CA
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address C07B3C 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | ADS605 | - | Jul 25, 23:45 UTC | Jul 26, 01:20 UTC | 1h 35m |
| 2026-07-25 | ADS605 | - | Jul 25, 19:30 UTC | Jul 25, 21:10 UTC | 1h 40m |
| 2026-07-25 | ADS605 | YVR → BFI | Jul 25, 18:15 UTC | Jul 25, 18:40 UTC | 25m |
| 2026-07-24 | ADS605 | - | Jul 24, 13:35 UTC | Jul 24, 17:10 UTC | 3h 35m |
| 2026-07-16 | ADS605 | - | Jul 16, 21:19 UTC | Jul 16, 23:20 UTC | 2h 0m |
| 2026-07-16 | ADS605 | CLD → SMX | Jul 16, 16:30 UTC | Jul 16, 17:05 UTC | 35m |
| 2026-07-15 | ADS605 | - | Jul 15, 21:35 UTC | Jul 15, 22:20 UTC | 45m |
| 2026-07-15 | ADS605 | - | Jul 15, 14:45 UTC | Jul 15, 16:20 UTC | 1h 35m |
| 2026-07-14 | ADS605 | - | Jul 14, 17:00 UTC | Jul 14, 17:25 UTC | 25m |
| 2026-07-14 | ADS605 | - | Jul 14, 15:55 UTC | Jul 14, 16:25 UTC | 30m |
| 2026-07-14 | ADS605 | - | Jul 14, 01:35 UTC | Jul 14, 02:50 UTC | 1h 15m |
| 2026-07-13 | ADS605 | - | Jul 13, 16:20 UTC | Jul 13, 17:20 UTC | 1h 0m |
| 2026-07-13 | ADS605 | - | Jul 13, 15:10 UTC | Jul 13, 15:40 UTC | 30m |
| 2026-07-12 | ADS605 | - | Jul 12, 21:40 UTC | Jul 13, 00:15 UTC | 2h 35m |
| 2026-07-12 | ADS605 | - | Jul 12, 17:01 UTC | Jul 12, 19:50 UTC | 2h 50m |
| 2026-07-07 | ADS605 | YYC → YVR | Jul 7, 23:50 UTC | Jul 8, 00:55 UTC | 1h 5m |
| 2026-07-06 | ADS605 | YVR → YYC | Jul 6, 19:00 UTC | Jul 6, 20:05 UTC | 1h 5m |
| 2026-07-04 | ADS605 | - | Jul 4, 18:15 UTC | Jul 4, 22:45 UTC | 4h 30m |
| 2026-07-04 | ADS605 | - | Jul 4, 15:05 UTC | Jul 4, 17:15 UTC | 2h 10m |
| 2026-07-01 | ADS605 | - | Jul 1, 18:30 UTC | Jul 1, 20:30 UTC | 2h 0m |
| 2026-07-01 | ADS605 | - | Jul 1, 13:10 UTC | Jul 1, 17:20 UTC | 4h 10m |
| 2026-06-24 | ADS605 | - | Jun 24, 15:00 UTC | Jun 24, 16:05 UTC | 1h 5m |
| 2026-06-23 | ADS605 | - | Jun 23, 13:59 UTC | Jun 23, 14:59 UTC | 1h 0m |
| 2026-06-21 | ADS605 | - | Jun 21, 18:44 UTC | Jun 21, 19:20 UTC | 35m |
| 2026-06-21 | ADS605 | - | Jun 21, 15:34 UTC | Jun 21, 16:04 UTC | 30m |
| 2026-06-11 | ADS605 | - | Jun 11, 20:40 UTC | Jun 11, 23:30 UTC | 2h 50m |
| 2026-06-10 | ADS605 | - | Jun 10, 13:25 UTC | Jun 10, 16:30 UTC | 3h 5m |
| 2026-06-04 | ADS605 | - | Jun 4, 22:30 UTC | Jun 5, 02:10 UTC | 3h 40m |
| 2026-06-02 | ADS605 | - | Jun 2, 15:55 UTC | Jun 2, 19:30 UTC | 3h 35m |
| 2026-05-31 | ADS605 | - | May 31, 17:10 UTC | May 31, 21:30 UTC | 4h 20m |
| 2026-05-14 | CGURJ | - | May 14, 19:25 UTC | May 15, 02:20 UTC | 6h 55m |
| 2026-05-13 | ADS605 | - | May 13, 19:30 UTC | May 13, 21:55 UTC | 2h 25m |
| 2026-05-12 | ADS605 | - | May 12, 16:20 UTC | May 12, 21:35 UTC | 5h 15m |
| 2026-05-08 | ADS605 | - | May 8, 19:25 UTC | May 9, 00:00 UTC | 4h 35m |
| 2026-05-08 | ADS605 | - | May 8, 13:10 UTC | May 8, 18:30 UTC | 5h 20m |
| 2026-05-04 | ADS605 | - | May 4, 21:10 UTC | May 4, 21:35 UTC | 25m |
| 2026-05-04 | ADS605 | - | May 4, 18:55 UTC | May 4, 19:05 UTC | 10m |
| 2026-05-03 | ADS605 | - | May 3, 22:54 UTC | May 3, 23:04 UTC | 10m |
| 2026-05-03 | ADS605 | - | May 3, 21:05 UTC | May 3, 21:35 UTC | 30m |
| 2026-05-02 | ADS605 | - | May 2, 18:10 UTC | May 2, 23:55 UTC | 5h 45m |
| 2026-05-02 | ADS605 | - | May 2, 12:50 UTC | May 2, 16:55 UTC | 4h 5m |
| 2026-04-27 | ADS605 | SJC → YVR | Apr 27, 22:25 UTC | Apr 28, 00:30 UTC | 2h 5m |
| 2026-04-27 | ADS605 | - | Apr 27, 19:40 UTC | Apr 27, 21:30 UTC | 1h 50m |
| 2026-04-27 | ADS605 | - | Apr 27, 02:35 UTC | Apr 27, 05:00 UTC | 2h 25m |
| 2026-04-25 | ADS605 | - | Apr 25, 18:15 UTC | Apr 25, 20:35 UTC | 2h 20m |
| 2026-04-24 | ADS605 | - | Apr 24, 20:20 UTC | Apr 24, 22:55 UTC | 2h 35m |
| 2026-04-24 | ADS605 | - | Apr 24, 14:05 UTC | Apr 24, 15:30 UTC | 1h 25m |
| 2026-04-23 | ADS605 | - | Apr 23, 16:15 UTC | Apr 23, 17:05 UTC | 50m |
| 2026-04-23 | ADS605 | YVR → BLI | Apr 23, 15:15 UTC | Apr 23, 15:30 UTC | 15m |
| 2026-04-22 | ADS605 | - | Apr 22, 03:10 UTC | Apr 22, 03:30 UTC | 20m |
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 C-GURJ page for operator, model, and routing details .