sensors Mode-S transponder
020163
ICAO 24-bit transponder address · allocated to Morocco
Currently assigned to CN-TMB · HAWKER BEECHCRAFT Hawker 750/850
- Hex
- 020163
- Octal
- 00400543
- Decimal
- 131,427
- Country
- MA
- Tail
- CN-TMB
- Type
- H25B
- Flights observed
- 24
- Distinct callsigns
- 6
- Country
- MA
- Last broadcast
- 8d ago
Current position
Country allocation
The ICAO 24-bit address 020163 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 6 distinct
Recent flights last 24
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-21 | AOM129M | - | May 21, 22:00 UTC | May 21, 23:30 UTC | 1h 30m |
| 2026-05-21 | AOM129M | - | May 21, 17:55 UTC | May 21, 19:30 UTC | 1h 35m |
| 2026-05-21 | AOM129M | - | May 21, 12:05 UTC | May 21, 15:00 UTC | 2h 55m |
| 2026-05-20 | AOM129M | - | May 20, 18:00 UTC | May 20, 21:45 UTC | 3h 45m |
| 2026-05-20 | AOM129M | - | May 20, 15:00 UTC | May 20, 15:15 UTC | 15m |
| 2026-05-09 | AOM123M | - | May 9, 16:25 UTC | May 9, 19:35 UTC | 3h 10m |
| 2026-05-09 | AOM123M | FAO → MAN | May 9, 12:35 UTC | May 9, 15:10 UTC | 2h 35m |
| 2026-05-09 | AOM123M | - | May 9, 09:25 UTC | May 9, 10:05 UTC | 40m |
| 2026-05-07 | AOM117M | - | May 7, 12:45 UTC | May 7, 15:45 UTC | 3h 0m |
| 2026-05-07 | AOM117M | - | May 7, 07:00 UTC | May 7, 10:55 UTC | 3h 55m |
| 2026-05-06 | AOM117M | - | May 6, 12:55 UTC | May 7, 10:55 UTC | 22h 0m |
| 2026-05-06 | AOM117M | - | May 6, 12:40 UTC | May 7, 10:45 UTC | 22h 5m |
| 2026-04-21 | AOM107M | - | Apr 21, 12:10 UTC | Apr 21, 20:55 UTC | 8h 45m |
| 2026-04-17 | AOM102M | - | Apr 17, 17:25 UTC | Apr 17, 18:30 UTC | 1h 5m |
| 2026-04-17 | AOM102M | - | Apr 17, 15:35 UTC | Apr 17, 17:15 UTC | 1h 40m |
| 2026-04-17 | AOM102M | - | Apr 17, 11:20 UTC | Apr 17, 12:45 UTC | 1h 25m |
| 2026-04-17 | AOM102M | - | Apr 17, 09:55 UTC | Apr 17, 11:15 UTC | 1h 20m |
| 2026-04-14 | AOM100M | - | Apr 14, 12:50 UTC | Apr 14, 14:45 UTC | 1h 55m |
| 2026-04-14 | AOM100M | - | Apr 14, 12:05 UTC | Apr 14, 12:45 UTC | 40m |
| 2026-04-13 | AOM100M | - | Apr 13, 16:15 UTC | Apr 13, 18:55 UTC | 2h 40m |
| 2026-04-13 | AOM100M | - | Apr 13, 15:50 UTC | Apr 13, 18:55 UTC | 3h 5m |
| 2026-04-13 | AOM100M | - | Apr 13, 15:25 UTC | Apr 13, 16:15 UTC | 50m |
| 2026-04-13 | AOM100M | - | Apr 13, 11:35 UTC | Apr 13, 11:50 UTC | 15m |
| 2026-04-13 | AOM100M | - | Apr 13, 10:10 UTC | Apr 13, 10:40 UTC | 30m |
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-TMB page for operator, model, and routing details .