sensors Mode-S transponder

0201B5

ICAO 24-bit transponder address · allocated to Morocco

Currently assigned to CN-RHG · BOEING 737 MAX 8

Hex
0201B5
Octal
00400665
Decimal
131,509
Country
MA
Tail
CN-RHG
Type
B38M
Transponder active on ground
Flights observed
280
Distinct callsigns
14
Country
MA
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 0201B5.

Country allocation

The ICAO 24-bit address 0201B5 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 14 distinct

Callsign Airline Flights Last seen
RAM650E - 87 2026-07-14
RAM651U - 84 2026-07-13
RAM665Z - 68 2026-07-13
RAM664Y - 24 2026-07-11
RAM1400 - 5 2026-07-11
RAM1401 - 4 2026-07-06
RAM965Y Royal Air Maroc 1 2026-04-21
RAM964Y Royal Air Maroc 1 2026-04-21
RAM8667 - 1 2026-04-20
RAM789H - 1 2026-07-10
RAM788H - 1 2026-07-10
RAM667H Royal Air Maroc 1 2026-04-20
RAM653D Royal Air Maroc 1 2026-04-20
RAM652D Royal Air Maroc 1 2026-04-20

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 RAM650E - Jul 14, 08:10 UTCJul 14, 09:15 UTC1h 5m
2026-07-13 RAM651U - Jul 13, 19:50 UTCJul 13, 22:00 UTC2h 10m
2026-07-13 RAM665Z ORY → ORY Jul 13, 11:20 UTCJul 13, 18:20 UTC7h 0m
2026-07-13 RAM650E - Jul 13, 07:15 UTCJul 13, 09:20 UTC2h 5m
2026-07-12 RAM651U - Jul 12, 19:50 UTCJul 12, 22:10 UTC2h 20m
2026-07-12 RAM665Z ORY → ORY Jul 12, 11:05 UTCJul 12, 18:10 UTC7h 5m
2026-07-12 RAM650E - Jul 12, 07:10 UTCJul 12, 09:10 UTC2h 0m
2026-07-11 RAM651U - Jul 11, 19:50 UTCJul 11, 22:05 UTC2h 15m
2026-07-11 RAM664Y ORY → ORY Jul 11, 10:50 UTCJul 11, 18:10 UTC7h 20m
2026-07-11 RAM650E - Jul 11, 07:15 UTCJul 11, 09:20 UTC2h 5m
2026-07-11 RAM1400 - Jul 11, 00:40 UTCJul 11, 01:15 UTC35m
2026-07-10 RAM789H - Jul 10, 20:15 UTCJul 10, 22:50 UTC2h 35m
2026-07-10 RAM788H - Jul 10, 15:20 UTCJul 10, 17:40 UTC2h 20m
2026-07-06 RAM1401 - Jul 6, 06:30 UTCJul 6, 07:15 UTC45m
2026-07-05 RAM651U - Jul 5, 19:35 UTCJul 5, 21:40 UTC2h 5m
2026-07-05 RAM665Z ORY → ORY Jul 5, 11:00 UTCJul 5, 18:10 UTC7h 10m
2026-07-05 RAM650E - Jul 5, 07:00 UTCJul 5, 09:20 UTC2h 20m
2026-07-04 RAM651U - Jul 4, 19:45 UTCJul 4, 21:50 UTC2h 5m
2026-07-04 RAM665Z ORY → ORY Jul 4, 11:20 UTCJul 4, 18:30 UTC7h 10m
2026-07-04 RAM650E - Jul 4, 07:15 UTCJul 4, 09:35 UTC2h 20m
2026-07-03 RAM651U - Jul 3, 20:10 UTCJul 3, 22:15 UTC2h 5m
2026-07-03 RAM665Z ORY → ORY Jul 3, 11:25 UTCJul 3, 18:45 UTC7h 20m
2026-07-03 RAM650E - Jul 3, 07:05 UTCJul 3, 09:35 UTC2h 30m
2026-07-02 RAM651U - Jul 2, 19:50 UTCJul 2, 21:50 UTC2h 0m
2026-07-02 RAM664Y AGA → ORY Jul 2, 11:05 UTCJul 2, 18:25 UTC7h 20m
2026-07-02 RAM650E - Jul 2, 07:05 UTCJul 2, 09:35 UTC2h 30m
2026-07-01 RAM651U - Jul 1, 20:00 UTCJul 1, 22:05 UTC2h 5m
2026-07-01 RAM664Y AGA → ORY Jul 1, 11:00 UTCJul 1, 18:25 UTC7h 25m
2026-07-01 RAM650E - Jul 1, 07:05 UTCJul 1, 09:40 UTC2h 35m
2026-06-30 RAM651U - Jun 30, 19:45 UTCJun 30, 21:50 UTC2h 5m
2026-06-30 RAM665Z ORY → ORY Jun 30, 11:00 UTCJun 30, 18:25 UTC7h 25m
2026-06-30 RAM650E - Jun 30, 07:00 UTCJun 30, 09:20 UTC2h 20m
2026-06-29 RAM651U - Jun 29, 20:00 UTCJun 29, 22:00 UTC2h 0m
2026-06-29 RAM665Z ORY → ORY Jun 29, 10:59 UTCJun 29, 18:19 UTC7h 20m
2026-06-29 RAM650E - Jun 29, 07:05 UTCJun 29, 09:20 UTC2h 15m
2026-06-28 RAM651U - Jun 28, 20:19 UTCJun 28, 22:29 UTC2h 10m
2026-06-28 RAM665Z ORY → ORY Jun 28, 11:04 UTCJun 28, 18:55 UTC7h 50m
2026-06-28 RAM650E - Jun 28, 07:25 UTCJun 28, 09:34 UTC2h 10m
2026-06-28 RAM651U - Jun 28, 01:50 UTCJun 28, 02:14 UTC25m
2026-06-27 RAM651U - Jun 27, 21:19 UTCJun 27, 23:50 UTC2h 30m
2026-06-27 RAM665Z ORY → ORY Jun 27, 11:00 UTCJun 27, 19:09 UTC8h 10m
2026-06-27 RAM650E - Jun 27, 07:04 UTCJun 27, 09:09 UTC2h 5m
2026-06-26 RAM651U - Jun 26, 19:55 UTCJun 26, 22:05 UTC2h 10m
2026-06-26 RAM665Z ORY → ORY Jun 26, 11:20 UTCJun 26, 18:29 UTC7h 10m
2026-06-26 RAM650E - Jun 26, 07:05 UTCJun 26, 09:20 UTC2h 15m
2026-06-25 RAM651U - Jun 25, 19:34 UTCJun 25, 21:44 UTC2h 10m
2026-06-25 RAM665Z ORY → ORY Jun 25, 10:55 UTCJun 25, 18:10 UTC7h 15m
2026-06-25 RAM650E - Jun 25, 07:05 UTCJun 25, 09:14 UTC2h 10m
2026-06-24 RAM1400 - Jun 24, 23:10 UTCJun 24, 23:45 UTC35m
2026-06-22 RAM1401 - Jun 22, 06:19 UTCJun 22, 06:49 UTC30m

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

Mode-S 0201B5 frequently asked

What is Mode-S code 0201B5?
0201B5 is an ICAO 24-bit transponder address. Allocated to Morocco. Assigned to CN-RHG.
Where is Mode-S 0201B5 registered?
Mode-S code 0201B5 is allocated to Morocco (MA). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 0201B5 broadcasting right now?
Mode-S 0201B5 is currently broadcasting from the ground.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 0201B5, octal 00400665, decimal 131,509.
What flights does 0201B5 operate?
Mode-S 0201B5 has broadcast 14 distinct callsigns, including RAM650E, RAM651U, RAM665Z, RAM664Y, RAM1400.