sensors Mode-S transponder

750549

ICAO 24-bit transponder address · allocated to Malaysia

Currently assigned to 9M-BZC · AIRBUS A-321

Hex
750549
Octal
35202511
Decimal
7,669,065
Country
MY
Tail
9M-BZC
Type
A321
No current signal · last broadcast Jul 26, 19:15 UTC
Flights observed
316
Distinct callsigns
20
Country
MY
Last broadcast
Jul 26, 19:15 UTC

Last known position

Most recent position reported by Mode-S 750549.

Country allocation

The ICAO 24-bit address 750549 falls within the block assigned to Malaysia (MY) by ICAO Annex 10, Volume III. Every aircraft registered in Malaysia 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

Callsign Airline Flights Last seen
RMY3508 Raya Airways 105 2026-07-26
RMY3507 Raya Airways 104 2026-07-26
RMY7862 - 14 2026-07-24
RMY641 - 13 2026-07-26
RMY640 Raya Airways 12 2026-07-24
RMY6825 - 8 2026-06-08
RMY6824 Raya Airways 8 2026-06-08
RMY1863 - 8 2026-06-30
RMY383 - 6 2026-07-14
RMY1869 - 6 2026-06-23
RMY641D - 4 2026-07-03
RMY382 - 4 2026-07-14
RMY1862 - 3 2026-06-05
RMY9123 - 2 2026-06-26
RMY671 - 2 2026-07-16
RMY651 - 2 2026-06-23
RMY650 - 2 2026-06-23
RMY642 - 2 2026-07-16
RMY640D - 2 2026-07-03
RMY1868 - 2 2026-07-26

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 RMY641 - Jul 26, 19:05 UTCJul 26, 19:15 UTC10m
2026-07-26 RMY670 - Jul 26, 17:20 UTCJul 26, 17:30 UTC10m
2026-07-26 RMY1868 - Jul 26, 11:25 UTCJul 26, 15:25 UTC4h 0m
2026-07-26 RMY3508 HKG → SZB Jul 26, 09:45 UTCJul 26, 10:05 UTC20m
2026-07-26 RMY3508 HKG → SZB Jul 26, 06:45 UTCJul 26, 06:50 UTC5m
2026-07-26 RMY3507 SZB → HKG Jul 26, 03:55 UTCJul 26, 04:10 UTC15m
2026-07-26 RMY3507 SZB → HKG Jul 26, 00:40 UTCJul 26, 00:50 UTC10m
2026-07-24 RMY641 - Jul 24, 13:50 UTCJul 24, 14:10 UTC20m
2026-07-24 RMY641 - Jul 24, 10:45 UTCJul 24, 11:00 UTC15m
2026-07-24 RMY640 BKI → HKG Jul 24, 08:50 UTCJul 24, 09:05 UTC15m
2026-07-24 RMY640 BKI → HKG Jul 24, 06:25 UTCJul 24, 06:55 UTC30m
2026-07-24 RMY7862 - Jul 24, 02:55 UTCJul 24, 05:05 UTC2h 10m
2026-07-23 RMY3508 HKG → SZB Jul 23, 23:10 UTCJul 23, 23:30 UTC20m
2026-07-23 RMY3508 HKG → SZB Jul 23, 20:15 UTCJul 23, 20:30 UTC15m
2026-07-23 RMY3507 SZB → HKG Jul 23, 16:50 UTCJul 23, 17:10 UTC20m
2026-07-23 RMY3507 SZB → HKG Jul 23, 13:45 UTCJul 23, 13:55 UTC10m
2026-07-22 RMY3508 HKG → SZB Jul 22, 23:25 UTCJul 22, 23:50 UTC25m
2026-07-22 RMY3508 HKG → SZB Jul 22, 20:25 UTCJul 22, 20:35 UTC10m
2026-07-22 RMY3507 SZB → HKG Jul 22, 16:45 UTCJul 22, 17:05 UTC20m
2026-07-22 RMY3507 SZB → HKG Jul 22, 13:40 UTCJul 22, 13:50 UTC10m
2026-07-21 RMY3508 HKG → SZB Jul 21, 23:00 UTCJul 21, 23:35 UTC35m
2026-07-21 RMY3508 HKG → SZB Jul 21, 20:10 UTCJul 21, 20:20 UTC10m
2026-07-21 RMY3507 SZB → HKG Jul 21, 16:55 UTCJul 21, 17:20 UTC25m
2026-07-21 RMY3507 SZB → HKG Jul 21, 13:45 UTCJul 21, 13:55 UTC10m
2026-07-20 RMY3508 HKG → SZB Jul 20, 23:05 UTCJul 20, 23:40 UTC35m
2026-07-20 RMY3508 HKG → SZB Jul 20, 20:00 UTCJul 20, 20:15 UTC15m
2026-07-20 RMY3507 SZB → HKG Jul 20, 16:50 UTCJul 20, 17:05 UTC15m
2026-07-20 RMY3507 SZB → HKG Jul 20, 13:40 UTCJul 20, 13:55 UTC15m
2026-07-19 RMY3508 HKG → SZB Jul 19, 00:30 UTCJul 19, 00:45 UTC15m
2026-07-18 RMY3508 HKG → SZB Jul 18, 21:20 UTCJul 18, 21:35 UTC15m
2026-07-18 RMY3507 SZB → HKG Jul 18, 16:25 UTCJul 18, 16:40 UTC15m
2026-07-18 RMY3507 SZB → HKG Jul 18, 13:15 UTCJul 18, 13:25 UTC10m
2026-07-16 RMY671 - Jul 16, 20:15 UTCJul 16, 20:39 UTC25m
2026-07-16 RMY671 - Jul 16, 17:20 UTCJul 16, 17:35 UTC15m
2026-07-16 RMY642 - Jul 16, 15:14 UTCJul 16, 15:35 UTC20m
2026-07-16 RMY642 - Jul 16, 12:49 UTCJul 16, 13:15 UTC25m
2026-07-16 RMY7862 - Jul 16, 04:45 UTCJul 16, 06:55 UTC2h 10m
2026-07-15 RMY641 - Jul 15, 14:40 UTCJul 15, 15:20 UTC40m
2026-07-15 RMY641 - Jul 15, 11:45 UTCJul 15, 12:00 UTC15m
2026-07-15 RMY640 - Jul 15, 09:05 UTCJul 15, 09:20 UTC15m
2026-07-15 RMY640 - Jul 15, 06:30 UTCJul 15, 07:00 UTC30m
2026-07-15 RMY7862 - Jul 15, 02:50 UTCJul 15, 05:05 UTC2h 15m
2026-07-14 RMY383 - Jul 14, 22:25 UTCJul 14, 23:10 UTC44m
2026-07-14 RMY382 - Jul 14, 16:15 UTCJul 14, 16:45 UTC30m
2026-07-14 RMY641 - Jul 14, 14:15 UTCJul 14, 14:45 UTC30m
2026-07-14 RMY641 - Jul 14, 11:15 UTCJul 14, 11:30 UTC15m
2026-07-14 RMY640 - Jul 14, 09:00 UTCJul 14, 09:15 UTC15m
2026-07-14 RMY640 - Jul 14, 06:25 UTCJul 14, 06:55 UTC30m
2026-07-14 RMY7862 - Jul 14, 02:40 UTCJul 14, 04:55 UTC2h 15m
2026-07-13 RMY641 - Jul 13, 13:35 UTCJul 13, 13:50 UTC15m

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

Mode-S 750549 frequently asked

What is Mode-S code 750549?
750549 is an ICAO 24-bit transponder address. Allocated to Malaysia. Assigned to 9M-BZC.
Where is Mode-S 750549 registered?
Mode-S code 750549 is allocated to Malaysia (MY). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 750549 broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 19:15 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 750549, octal 35202511, decimal 7,669,065.
What flights does 750549 operate?
Mode-S 750549 has broadcast 20 distinct callsigns, including RMY3508, RMY3507, RMY7862, RMY641, RMY640.