sensors Mode-S transponder

02009F

ICAO 24-bit transponder address · allocated to Morocco

Currently assigned to CN-ROW · BOEING 767-300

Hex
02009F
Octal
00400237
Decimal
131,231
Country
MA
Tail
CN-ROW
Type
B763
No current signal · last broadcast 6d ago
Flights observed
65
Distinct callsigns
8
Country
MA
Last broadcast
6d ago

Last known position

Most recent position reported by Mode-S 02009F.

Country allocation

The ICAO 24-bit address 02009F falls within the block assigned to Morocco (MA) by ICAO Annex 10, Volume III. Every aircraft registered in Morocco 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 8 distinct

Callsign Airline Flights Last seen
RAM352Y Royal Air Maroc 17 2026-05-20
RAM353Y Royal Air Maroc 12 2026-05-20
RAM321 Royal Air Maroc 11 2026-05-23
RAM320 Royal Air Maroc 11 2026-05-23
RAM355 Royal Air Maroc 5 2026-05-10
RAM354 Royal Air Maroc 5 2026-05-10
RAM325 Royal Air Maroc 2 2026-04-24
RAM324 Royal Air Maroc 2 2026-04-24

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-23 RAM321 IST → CMN May 23, 16:20 UTCMay 23, 20:15 UTC3h 56m
2026-05-23 RAM320 DKR → CMN May 23, 09:30 UTCMay 23, 13:20 UTC3h 50m
2026-05-20 RAM353Y BRU → CMN May 20, 13:30 UTCMay 20, 15:55 UTC2h 25m
2026-05-20 RAM352Y CMN → BRU May 20, 08:15 UTCMay 20, 11:05 UTC2h 50m
2026-05-17 RAM353Y BRU → CMN May 17, 09:45 UTCMay 17, 12:25 UTC2h 40m
2026-05-17 RAM352Y CMN → BRU May 17, 04:50 UTCMay 17, 07:30 UTC2h 40m
2026-05-16 RAM353Y BRU → CMN May 16, 18:00 UTCMay 16, 20:45 UTC2h 45m
2026-05-16 RAM352Y CMN → BRU May 16, 14:16 UTCMay 16, 14:55 UTC40m
2026-05-13 RAM352Y CMN → BRU May 13, 15:45 UTCMay 13, 18:30 UTC2h 45m
2026-05-12 RAM321 IST → CMN May 12, 16:00 UTCMay 12, 20:45 UTC4h 45m
2026-05-12 RAM320 DKR → CMN May 12, 10:10 UTCMay 12, 13:25 UTC3h 15m
2026-05-10 RAM355 BRU → BRU May 10, 19:15 UTCMay 10, 22:15 UTC3h 0m
2026-05-10 RAM354 CMN → BRU May 10, 15:05 UTCMay 10, 17:30 UTC2h 25m
2026-05-10 RAM353Y BRU → CMN May 10, 09:55 UTCMay 10, 12:54 UTC3h 0m
2026-05-10 RAM352Y CMN → BRU May 10, 05:34 UTCMay 10, 08:05 UTC2h 30m
2026-05-09 RAM321 IST → CMN May 9, 15:25 UTCMay 9, 19:35 UTC4h 10m
2026-05-09 RAM320 DKR → CMN May 9, 09:45 UTCMay 9, 13:10 UTC3h 25m
2026-05-06 RAM353Y BRU → CMN May 6, 13:25 UTCMay 6, 16:10 UTC2h 45m
2026-05-06 RAM352Y CMN → BRU May 6, 08:15 UTCMay 6, 11:00 UTC2h 45m
2026-05-05 RAM321 IST → CMN May 5, 15:01 UTCMay 5, 19:20 UTC4h 20m
2026-05-05 RAM320 DKR → CMN May 5, 09:15 UTCMay 5, 12:50 UTC3h 35m
2026-05-03 RAM355 BRU → BRU May 3, 21:05 UTCMay 4, 00:00 UTC2h 55m
2026-05-03 RAM354 CMN → BRU May 3, 16:05 UTCMay 3, 18:40 UTC2h 35m
2026-05-03 RAM353Y BRU → CMN May 3, 09:40 UTCMay 3, 12:35 UTC2h 55m
2026-05-03 RAM352Y CMN → BRU May 3, 04:15 UTCMay 3, 06:45 UTC2h 30m
2026-05-02 RAM321 IST → CMN May 2, 16:00 UTCMay 2, 20:05 UTC4h 5m
2026-05-02 RAM320 DKR → CMN May 2, 09:35 UTCMay 2, 13:15 UTC3h 40m
2026-04-29 RAM353Y BRU → CMN Apr 29, 15:40 UTCApr 29, 18:30 UTC2h 50m
2026-04-29 RAM352Y CMN → BRU Apr 29, 13:40 UTCApr 29, 14:20 UTC40m
2026-04-29 RAM352Y CMN → BRU Apr 29, 09:10 UTCApr 29, 12:00 UTC2h 50m
2026-04-28 RAM321 IST → CMN Apr 28, 15:45 UTCApr 28, 19:50 UTC4h 5m
2026-04-28 RAM320 DKR → CMN Apr 28, 09:35 UTCApr 28, 13:20 UTC3h 45m
2026-04-26 RAM355 BRU → BRU Apr 26, 19:30 UTCApr 26, 22:05 UTC2h 35m
2026-04-26 RAM354 CMN → BRU Apr 26, 14:55 UTCApr 26, 17:40 UTC2h 45m
2026-04-26 RAM353Y BRU → CMN Apr 26, 09:10 UTCApr 26, 11:45 UTC2h 35m
2026-04-26 RAM352Y CMN → BRU Apr 26, 04:20 UTCApr 26, 07:10 UTC2h 50m
2026-04-24 RAM324 DSS → CMN Apr 24, 03:35 UTCApr 24, 03:50 UTC15m
2026-04-24 RAM325 CMN → DSS Apr 24, 01:55 UTCApr 24, 02:20 UTC25m
2026-04-22 RAM353Y BRU → CMN Apr 22, 15:45 UTCApr 22, 18:35 UTC2h 50m
2026-04-22 RAM352Y CMN → BRU Apr 22, 13:40 UTCApr 22, 14:25 UTC45m
2026-04-22 RAM352Y CMN → BRU Apr 22, 08:35 UTCApr 22, 11:25 UTC2h 50m
2026-04-21 RAM321 IST → CMN Apr 21, 15:51 UTCApr 21, 20:10 UTC4h 20m
2026-04-21 RAM320 DKR → CMN Apr 21, 09:20 UTCApr 21, 12:55 UTC3h 35m
2026-04-19 RAM355 BRU → BRU Apr 19, 19:00 UTCApr 19, 21:35 UTC2h 35m
2026-04-19 RAM354 CMN → BRU Apr 19, 14:50 UTCApr 19, 17:30 UTC2h 40m
2026-04-19 RAM353Y BRU → CMN Apr 19, 09:10 UTCApr 19, 11:50 UTC2h 40m
2026-04-19 RAM352Y CMN → BRU Apr 19, 04:05 UTCApr 19, 07:00 UTC2h 55m
2026-04-18 RAM321 IST → CMN Apr 18, 15:25 UTCApr 18, 19:20 UTC3h 55m
2026-04-18 RAM320 DKR → CMN Apr 18, 09:25 UTCApr 18, 13:05 UTC3h 40m
2026-04-17 RAM324 DSS → CMN Apr 17, 05:20 UTCApr 17, 05:30 UTC10m

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

Mode-S 02009F frequently asked

What is Mode-S code 02009F?
02009F is an ICAO 24-bit transponder address. Allocated to Morocco. Assigned to CN-ROW.
Where is Mode-S 02009F registered?
Mode-S code 02009F is allocated to Morocco (MA). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 02009F broadcasting right now?
No active broadcast right now. Last signal was 6d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 02009F, octal 00400237, decimal 131,231.
What flights does 02009F operate?
Mode-S 02009F has broadcast 8 distinct callsigns, including RAM352Y, RAM353Y, RAM321, RAM320, RAM355.