sensors Mode-S transponder

C04FFF

ICAO 24-bit transponder address · allocated to Canada

Currently assigned to C-GEHQ · BOEING 737 MAX 8 · operated by Air Canada

Hex
C04FFF
Octal
60047777
Decimal
12,603,391
Country
CA
Tail
C-GEHQ
Type
B38M
No current signal · last broadcast 4h ago
Flights observed
211
Distinct callsigns
20
Country
CA
Last broadcast
4h ago

Last known position

Most recent position reported by Mode-S C04FFF.

Country allocation

The ICAO 24-bit address C04FFF 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 20 distinct

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 ROU2083 YEG → YVR May 30, 04:20 UTCMay 30, 05:35 UTC1h 15m
2026-05-30 ROU2080 YVR → YYC May 30, 01:55 UTCMay 30, 03:00 UTC1h 5m
2026-05-29 ROU2081 YEG → YVR May 29, 23:05 UTCMay 29, 23:45 UTC40m
2026-05-29 ROU2081 YEG → YVR May 29, 23:00 UTCMay 30, 00:08 UTC1h 8m
2026-05-29 ROU2078 YVR → YEG May 29, 20:15 UTCMay 29, 21:30 UTC1h 15m
2026-05-29 ROU2078 YVR → YEG May 29, 20:15 UTCMay 29, 21:25 UTC1h 10m
2026-05-29 ROU1765 SNU → YYZ May 29, 13:40 UTCMay 29, 15:40 UTC2h 0m
2026-05-29 ROU1765 SNU → YYZ May 29, 13:40 UTCMay 29, 17:34 UTC3h 54m
2026-05-28 ROU1764 YYZ → SNU May 28, 20:40 UTCMay 29, 00:55 UTC4h 15m
2026-05-28 ROU2097 MEX → YVR May 28, 15:45 UTCMay 28, 18:30 UTC2h 45m
2026-05-28 ROU2097 MEX → YVR May 28, 13:25 UTCMay 28, 13:35 UTC10m
2026-05-28 ROU2096 YVR → MEX May 28, 04:55 UTCMay 28, 05:00 UTC5m
2026-05-28 ROU2096 YVR → MEX May 28, 00:05 UTCMay 28, 02:55 UTC2h 50m
2026-05-27 ROU2097 MEX → YVR May 27, 15:30 UTCMay 27, 15:45 UTC15m
2026-05-27 ROU2097 MEX → YVR May 27, 15:30 UTCMay 27, 20:43 UTC5h 13m
2026-05-27 ROU2096 YVR → MEX May 27, 05:04 UTCMay 27, 05:14 UTC10m
2026-05-27 ROU2096 YVR → MEX May 27, 00:14 UTCMay 27, 03:04 UTC2h 50m
2026-05-26 ROU2025 YYC → YVR May 26, 20:09 UTCMay 26, 21:14 UTC1h 5m
2026-05-26 ROU2022 YVR → YYC May 26, 17:55 UTCMay 26, 18:55 UTC1h 0m
2026-05-26 ROU2022 YVR → YYC May 26, 17:50 UTCMay 26, 18:46 UTC56m
2026-05-26 ROU2019 YFC → YYZ May 26, 14:33 UTCMay 26, 15:27 UTC54m
2026-05-26 ROU2019 YFC → YYZ May 26, 14:35 UTCMay 26, 15:39 UTC1h 5m
2026-05-26 ROU2072 YVR → YYC May 26, 04:35 UTCMay 26, 05:34 UTC1h 0m
2026-05-26 ROU2029 YYC → YVR May 26, 01:55 UTCMay 26, 03:05 UTC1h 10m
2026-05-25 ROU2026 YVR → YYC May 25, 23:14 UTCMay 26, 00:14 UTC1h 0m
2026-05-25 ROU2025 YYC → YVR May 25, 20:30 UTCMay 25, 21:40 UTC1h 10m
2026-05-25 ROU2022 YVR → YYC May 25, 17:50 UTCMay 25, 18:55 UTC1h 5m
2026-05-25 ROU2019 YFC → YYZ May 25, 14:40 UTCMay 25, 15:50 UTC1h 10m
2026-05-25 ROU2072 YVR → YYC May 25, 04:40 UTCMay 25, 05:40 UTC1h 0m
2026-05-25 ROU2029 YYC → YVR May 25, 02:05 UTCMay 25, 03:20 UTC1h 15m
2026-05-24 ROU2026 YVR → YYC May 24, 23:00 UTCMay 24, 23:46 UTC46m
2026-05-24 ROU2025 YYC → YVR May 24, 20:20 UTCMay 24, 21:30 UTC1h 10m
2026-05-24 ROU2022 YVR → YYC May 24, 17:55 UTCMay 24, 18:55 UTC1h 0m
2026-05-24 ROU2019 YFC → YYZ May 24, 14:30 UTCMay 24, 15:40 UTC1h 10m
2026-05-24 ROU2072 YVR → YYC May 24, 04:40 UTCMay 24, 05:35 UTC55m
2026-05-24 ROU2072 YVR → YYC May 24, 04:38 UTCMay 24, 05:32 UTC54m
2026-05-23 ROU1766 ANC → YVR May 23, 23:15 UTCMay 24, 01:50 UTC2h 35m
2026-05-23 ROU1767 YVR → ANC May 23, 18:15 UTCMay 23, 21:10 UTC2h 55m
2026-05-23 ROU1773 LAS → YVR May 23, 13:50 UTCMay 23, 16:10 UTC2h 20m
2026-05-23 ROU1773 LAS → YVR May 23, 13:50 UTCMay 23, 16:06 UTC2h 16m
2026-05-23 ROU1774 YYZ → AZS May 23, 04:46 UTCMay 23, 06:49 UTC2h 3m
2026-05-23 ROU1774 YYZ → AZS May 23, 04:50 UTCMay 23, 07:00 UTC2h 10m
2026-05-22 ROU1766 ANC → YVR May 22, 23:55 UTCMay 23, 02:40 UTC2h 44m
2026-05-22 ROU1767 YVR → ANC May 22, 18:15 UTCMay 22, 21:15 UTC3h 0m
2026-05-22 ROU1773 LAS → YVR May 22, 13:55 UTCMay 22, 16:20 UTC2h 25m
2026-05-22 ROU1773 LAS → YVR May 22, 13:55 UTCMay 22, 16:24 UTC2h 29m
2026-05-22 ROU1774 YYZ → AZS May 22, 04:40 UTCMay 22, 06:45 UTC2h 5m
2026-05-22 ROU1771 HUX → YYZ May 22, 00:10 UTCMay 22, 03:00 UTC2h 50m
2026-05-21 ROU1770 YYZ → HUX May 21, 20:15 UTCMay 21, 22:45 UTC2h 30m
2026-05-21 ROU1773 LAS → YVR May 21, 13:55 UTCMay 21, 15:45 UTC1h 50m

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-GEHQ page for operator, model, and routing details .

Mode-S C04FFF frequently asked

What is Mode-S code C04FFF?
C04FFF is an ICAO 24-bit transponder address. Allocated to Canada. Assigned to C-GEHQ.
Where is Mode-S C04FFF registered?
Mode-S code C04FFF is allocated to Canada (CA). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is C04FFF broadcasting right now?
No active broadcast right now. Last signal was 4h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex C04FFF, octal 60047777, decimal 12,603,391.
What flights does C04FFF operate?
Mode-S C04FFF has broadcast 20 distinct callsigns, including ROU1773, ROU1774, ROU2081, ROU2097, ROU2080.