sensors Mode-S transponder
750574
ICAO 24-bit transponder address · allocated to Malaysia
Currently assigned to 9M-LFJ · AIRBUS A-330-300
- Hex
- 750574
- Octal
- 35202564
- Decimal
- 7,669,108
- Country
- MY
- Tail
- 9M-LFJ
- Type
- A333
- Flights observed
- 98
- Distinct callsigns
- 20
- Country
- MY
- Last broadcast
- 4d ago
Last known position
Country allocation
The ICAO 24-bit address 750574 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 |
|---|---|---|---|
| MXD702 | Malindo Air | 6 | 2026-07-25 |
| KNE9276 | - | 4 | 2026-06-20 |
| MXD161 | Malindo Air | 3 | 2026-07-25 |
| KNE9342 | - | 3 | 2026-06-08 |
| KNE9242 | Nas Air | 3 | 2026-06-13 |
| KNE8099 | - | 3 | 2026-05-19 |
| KNE8077 | - | 3 | 2026-05-06 |
| KNE8074 | - | 3 | 2026-05-05 |
| MXD706 | Malindo Air | 2 | 2026-07-19 |
| MXD162 | Malindo Air | 2 | 2026-07-24 |
| KNE9068 | - | 2 | 2026-06-14 |
| KNE9062 | - | 2 | 2026-06-01 |
| KNE9060 | - | 2 | 2026-06-10 |
| KNE9041 | Nas Air | 2 | 2026-05-30 |
| KNE8103 | - | 2 | 2026-05-20 |
| KNE8095 | - | 2 | 2026-05-13 |
| KNE8091 | - | 2 | 2026-05-11 |
| KNE8083 | - | 2 | 2026-05-08 |
| KNE8072 | - | 2 | 2026-05-04 |
| MXD705 | Malindo Air | 1 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | MXD705 | KUL → JED | Jul 26, 10:20 UTC | Jul 26, 16:30 UTC | 6h 10m |
| 2026-07-25 | MXD702 | JED → KUL | Jul 25, 13:15 UTC | Jul 26, 08:00 UTC | 18h 46m |
| 2026-07-25 | MXD702 | JED → KUL | Jul 25, 12:25 UTC | Jul 26, 08:00 UTC | 19h 36m |
| 2026-07-25 | MXD702 | JED → KUL | Jul 25, 09:10 UTC | Jul 26, 08:00 UTC | 22h 51m |
| 2026-07-25 | MXD161 | DAC → KUL | Jul 25, 00:25 UTC | Jul 25, 00:45 UTC | 20m |
| 2026-07-24 | MXD161 | DAC → KUL | Jul 24, 21:10 UTC | Jul 24, 23:30 UTC | 2h 20m |
| 2026-07-24 | MXD162 | KUL → DAC | Jul 24, 15:20 UTC | Jul 24, 18:45 UTC | 3h 25m |
| 2026-07-23 | MXD161 | DAC → KUL | Jul 23, 20:40 UTC | Jul 23, 22:25 UTC | 1h 45m |
| 2026-07-23 | MXD162 | - | Jul 23, 15:20 UTC | Jul 23, 18:45 UTC | 3h 25m |
| 2026-07-22 | MXD702 | JED → KUL | Jul 22, 11:10 UTC | Jul 23, 06:25 UTC | 19h 15m |
| 2026-07-20 | MXD702 | - | Jul 20, 11:05 UTC | Jul 21, 06:25 UTC | 19h 19m |
| 2026-07-20 | MXD702 | - | Jul 20, 10:45 UTC | Jul 21, 06:25 UTC | 19h 39m |
| 2026-07-19 | MXD706 | JED → KUL | Jul 19, 13:40 UTC | Jul 20, 08:05 UTC | 18h 25m |
| 2026-07-19 | MXD706 | JED → KUL | Jul 19, 10:25 UTC | Jul 20, 08:05 UTC | 21h 40m |
| 2026-07-18 | MXD132 | - | Jul 18, 18:10 UTC | Jul 18, 19:10 UTC | 1h 0m |
| 2026-07-18 | MXD131 | - | Jul 18, 10:55 UTC | Jul 18, 15:45 UTC | 4h 50m |
| 2026-07-17 | MXD161D | DAC → KUL | Jul 17, 20:29 UTC | Jul 18, 00:10 UTC | 3h 40m |
| 2026-07-17 | MXD162D | - | Jul 17, 15:10 UTC | Jul 17, 17:40 UTC | 2h 30m |
| 2026-06-30 | MXD5714 | - | Jun 30, 19:35 UTC | Jul 1, 03:05 UTC | 7h 30m |
| 2026-06-29 | KNE9091 | - | Jun 29, 12:34 UTC | Jun 29, 16:10 UTC | 3h 35m |
| 2026-06-29 | KNE9090 | - | Jun 29, 05:24 UTC | Jun 29, 09:29 UTC | 4h 5m |
| 2026-06-21 | KNE9037 | - | Jun 21, 07:04 UTC | Jun 21, 10:44 UTC | 3h 40m |
| 2026-06-20 | KNE9277 | - | Jun 20, 06:05 UTC | Jun 21, 00:40 UTC | 18h 35m |
| 2026-06-20 | KNE9276 | - | Jun 20, 01:05 UTC | Jun 21, 00:40 UTC | 23h 35m |
| 2026-06-19 | KNE9276 | - | Jun 19, 23:04 UTC | Jun 20, 08:49 UTC | 9h 45m |
| 2026-06-19 | KNE9276 | - | Jun 19, 05:05 UTC | Jun 20, 02:04 UTC | 21h 0m |
| 2026-06-19 | KNE9276 | - | Jun 19, 04:00 UTC | Jun 20, 02:04 UTC | 22h 5m |
| 2026-06-18 | KNE9082 | - | Jun 18, 21:30 UTC | Jun 19, 01:24 UTC | 3h 54m |
| 2026-06-17 | KNE9077 | - | Jun 17, 10:25 UTC | Jun 17, 14:10 UTC | 3h 45m |
| 2026-06-16 | KNE9075 | - | Jun 16, 15:15 UTC | Jun 17, 07:55 UTC | 16h 41m |
| 2026-06-15 | KNE9074 | - | Jun 15, 20:04 UTC | Jun 16, 12:10 UTC | 16h 5m |
| 2026-06-15 | KNE9072 | - | Jun 15, 00:35 UTC | Jun 15, 16:55 UTC | 16h 20m |
| 2026-06-14 | KNE9070 | - | Jun 14, 06:50 UTC | Jun 14, 21:25 UTC | 14h 35m |
| 2026-06-14 | KNE9068 | - | Jun 14, 00:10 UTC | Jun 14, 04:15 UTC | 4h 5m |
| 2026-06-13 | KNE9068 | - | Jun 13, 07:30 UTC | Jun 14, 04:15 UTC | 20h 45m |
| 2026-06-13 | KNE9242 | JED → ALG | Jun 13, 01:45 UTC | Jun 14, 00:35 UTC | 22h 49m |
| 2026-06-12 | KNE9242 | JED → ALG | Jun 12, 23:45 UTC | Jun 13, 08:10 UTC | 8h 24m |
| 2026-06-12 | KNE9242 | JED → ALG | Jun 12, 03:35 UTC | Jun 13, 02:40 UTC | 23h 5m |
| 2026-06-11 | KNE9061 | - | Jun 11, 09:25 UTC | Jun 12, 04:00 UTC | 18h 36m |
| 2026-06-10 | KNE9060 | - | Jun 10, 13:30 UTC | Jun 11, 07:15 UTC | 17h 45m |
| 2026-06-10 | KNE9060 | - | Jun 10, 11:35 UTC | Jun 11, 07:15 UTC | 19h 40m |
| 2026-06-09 | KNE9183 | - | Jun 9, 04:45 UTC | Jun 9, 08:30 UTC | 3h 45m |
| 2026-06-08 | KNE9343 | - | Jun 8, 12:40 UTC | Jun 9, 02:05 UTC | 13h 25m |
| 2026-06-08 | KNE9342 | - | Jun 8, 06:25 UTC | Jun 8, 08:45 UTC | 2h 20m |
| 2026-06-07 | KNE9342 | - | Jun 7, 11:05 UTC | Jun 8, 08:45 UTC | 21h 40m |
| 2026-06-07 | KNE9342 | - | Jun 7, 09:05 UTC | Jun 8, 08:45 UTC | 23h 40m |
| 2026-06-07 | KNE9339 | - | Jun 7, 08:40 UTC | Jun 8, 07:00 UTC | 22h 20m |
| 2026-06-06 | KNE9337 | - | Jun 6, 09:09 UTC | Jun 7, 04:20 UTC | 19h 10m |
| 2026-06-05 | KNE9053 | - | Jun 5, 00:35 UTC | Jun 5, 01:30 UTC | 55m |
| 2026-06-04 | KNE9052 | - | Jun 4, 05:20 UTC | Jun 4, 21:35 UTC | 16h 15m |
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-LFJ page for operator, model, and routing details .