sensors Mode-S transponder
744843
ICAO 24-bit transponder address · allocated to Jordan
- Hex
- 744843
- Octal
- 35044103
- Decimal
- 7,620,675
- Country
- JO
- Flights observed
- 113
- Distinct callsigns
- 20
- Country
- JO
- Last broadcast
- 32m ago
Current position
Country allocation
The ICAO 24-bit address 744843 falls within the block assigned to Jordan (JO) by ICAO Annex 10, Volume III. Every aircraft registered in Jordan 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 |
|---|---|---|---|
| RJA112 | - | 23 | 2026-07-05 |
| RJA111 | - | 23 | 2026-07-05 |
| RJA272 | - | 12 | 2026-07-06 |
| RJA271 | - | 12 | 2026-07-06 |
| RJA265 | - | 7 | 2026-07-03 |
| RJA266 | - | 6 | 2026-07-04 |
| RJA292 | - | 3 | 2026-06-06 |
| RJA291 | Royal Jordanian | 3 | 2026-06-05 |
| BOE126 | - | 3 | 2026-05-12 |
| RJA745 | Royal Jordanian | 2 | 2026-06-05 |
| RJA706 | Royal Jordanian | 2 | 2026-05-31 |
| RJA789 | Royal Jordanian | 1 | 2026-05-17 |
| RJA744 | Royal Jordanian | 1 | 2026-06-04 |
| RJA729 | Royal Jordanian | 1 | 2026-06-01 |
| RJA722 | Royal Jordanian | 1 | 2026-06-03 |
| RJA707 | Royal Jordanian | 1 | 2026-05-30 |
| RJA705 | - | 1 | 2026-07-03 |
| RJA704 | Royal Jordanian | 1 | 2026-05-30 |
| RJA703 | Royal Jordanian | 1 | 2026-05-30 |
| RJA702 | Royal Jordanian | 1 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-06 | RJA272 | - | Jul 6, 18:30 UTC | Jul 7, 00:45 UTC | 6h 15m |
| 2026-07-06 | RJA272 | - | Jul 6, 16:15 UTC | Jul 6, 17:00 UTC | 45m |
| 2026-07-06 | RJA271 | YUL → YYZ | Jul 6, 12:40 UTC | Jul 6, 13:35 UTC | 55m |
| 2026-07-06 | RJA271 | - | Jul 6, 00:35 UTC | Jul 6, 11:25 UTC | 10h 50m |
| 2026-07-05 | RJA112 | - | Jul 5, 16:35 UTC | Jul 5, 20:45 UTC | 4h 10m |
| 2026-07-05 | RJA111 | - | Jul 5, 09:20 UTC | Jul 5, 14:25 UTC | 5h 5m |
| 2026-07-04 | RJA266 | - | Jul 4, 16:25 UTC | Jul 5, 02:50 UTC | 10h 25m |
| 2026-07-03 | RJA265 | - | Jul 3, 23:30 UTC | Jul 4, 11:40 UTC | 12h 10m |
| 2026-07-03 | RJA112 | - | Jul 3, 16:40 UTC | Jul 3, 20:45 UTC | 4h 5m |
| 2026-07-03 | RJA111 | - | Jul 3, 09:25 UTC | Jul 3, 14:10 UTC | 4h 45m |
| 2026-07-03 | RJA705 | - | Jul 3, 01:35 UTC | Jul 3, 06:35 UTC | 5h 0m |
| 2026-07-02 | RJA183 | - | Jul 2, 16:15 UTC | Jul 3, 00:15 UTC | 8h 0m |
| 2026-07-02 | RJA182 | - | Jul 2, 00:10 UTC | Jul 2, 08:10 UTC | 8h 0m |
| 2026-07-01 | RJA112 | - | Jul 1, 16:45 UTC | Jul 1, 21:05 UTC | 4h 20m |
| 2026-07-01 | RJA111 | - | Jul 1, 09:35 UTC | Jul 1, 14:25 UTC | 4h 50m |
| 2026-06-30 | RJA266 | ORD → AMM | Jun 30, 16:35 UTC | Jul 1, 04:15 UTC | 11h 40m |
| 2026-06-29 | RJA265 | AMM → ORD | Jun 29, 23:49 UTC | Jun 30, 11:50 UTC | 12h 1m |
| 2026-06-29 | RJA112 | - | Jun 29, 16:50 UTC | Jun 29, 21:30 UTC | 4h 40m |
| 2026-06-29 | RJA111 | - | Jun 29, 09:29 UTC | Jun 29, 14:19 UTC | 4h 50m |
| 2026-06-28 | RJA268 | - | Jun 28, 14:54 UTC | Jun 29, 01:34 UTC | 10h 40m |
| 2026-06-27 | RJA267 | - | Jun 27, 23:34 UTC | Jun 28, 10:50 UTC | 11h 15m |
| 2026-06-27 | RJA112 | - | Jun 27, 17:09 UTC | Jun 27, 21:34 UTC | 4h 25m |
| 2026-06-27 | RJA111 | - | Jun 27, 09:29 UTC | Jun 27, 14:05 UTC | 4h 35m |
| 2026-06-26 | RJA272 | - | Jun 26, 18:34 UTC | Jun 27, 04:15 UTC | 9h 40m |
| 2026-06-26 | RJA272 | - | Jun 26, 16:00 UTC | Jun 26, 16:44 UTC | 45m |
| 2026-06-26 | RJA271 | YUL → YYZ | Jun 26, 12:14 UTC | Jun 26, 13:10 UTC | 55m |
| 2026-06-26 | RJA271 | - | Jun 26, 00:35 UTC | Jun 26, 11:09 UTC | 10h 35m |
| 2026-06-25 | RJA112 | - | Jun 25, 16:24 UTC | Jun 25, 20:49 UTC | 4h 25m |
| 2026-06-25 | RJA111 | - | Jun 25, 09:20 UTC | Jun 25, 13:50 UTC | 4h 30m |
| 2026-06-24 | RJA272 | - | Jun 24, 18:29 UTC | Jun 25, 03:59 UTC | 9h 30m |
| 2026-06-24 | RJA272 | YYZ → YUL | Jun 24, 15:54 UTC | Jun 24, 16:45 UTC | 50m |
| 2026-06-24 | RJA271 | YUL → YYZ | Jun 24, 12:25 UTC | Jun 24, 13:20 UTC | 55m |
| 2026-06-24 | RJA271 | - | Jun 24, 00:25 UTC | Jun 24, 11:09 UTC | 10h 45m |
| 2026-06-23 | RJA112 | - | Jun 23, 16:29 UTC | Jun 23, 20:49 UTC | 4h 20m |
| 2026-06-23 | RJA111 | - | Jun 23, 09:09 UTC | Jun 23, 13:50 UTC | 4h 40m |
| 2026-06-22 | RJA272 | - | Jun 22, 18:35 UTC | Jun 23, 04:09 UTC | 9h 35m |
| 2026-06-22 | RJA272 | YYZ → YUL | Jun 22, 15:45 UTC | Jun 22, 16:34 UTC | 50m |
| 2026-06-22 | RJA271 | YUL → YYZ | Jun 22, 12:30 UTC | Jun 22, 13:19 UTC | 50m |
| 2026-06-22 | RJA271 | - | Jun 22, 00:29 UTC | Jun 22, 11:04 UTC | 10h 35m |
| 2026-06-21 | RJA112 | - | Jun 21, 16:49 UTC | Jun 21, 21:10 UTC | 4h 20m |
| 2026-06-21 | RJA111 | - | Jun 21, 09:29 UTC | Jun 21, 14:15 UTC | 4h 45m |
| 2026-06-20 | RJA266 | ORD → AMM | Jun 20, 16:29 UTC | Jun 21, 03:34 UTC | 11h 5m |
| 2026-06-19 | RJA265 | AMM → ORD | Jun 19, 23:25 UTC | Jun 20, 11:05 UTC | 11h 40m |
| 2026-06-19 | RJA112 | - | Jun 19, 16:29 UTC | Jun 19, 20:55 UTC | 4h 25m |
| 2026-06-19 | RJA111 | - | Jun 19, 09:24 UTC | Jun 19, 13:54 UTC | 4h 30m |
| 2026-06-18 | RJA266 | ORD → AMM | Jun 18, 16:50 UTC | Jun 19, 04:00 UTC | 11h 9m |
| 2026-06-17 | RJA265 | AMM → ORD | Jun 17, 23:20 UTC | Jun 18, 11:40 UTC | 12h 20m |
| 2026-06-17 | RJA112 | - | Jun 17, 16:20 UTC | Jun 17, 20:50 UTC | 4h 30m |
| 2026-06-17 | RJA111 | - | Jun 17, 09:30 UTC | Jun 17, 14:20 UTC | 4h 50m |
| 2026-06-16 | RJA266 | ORD → AMM | Jun 16, 16:50 UTC | Jun 17, 03:45 UTC | 10h 56m |
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.