sensors Mode-S transponder
896423
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-RJD · BOMBARDIER BD-700 Global 5000/5500
- Hex
- 896423
- Octal
- 42262043
- Decimal
- 9,004,067
- Country
- AE
- Tail
- A6-RJD
- Type
- GL5T
- Flights observed
- 22
- Distinct callsigns
- 1
- Country
- AE
- Last broadcast
- Jul 21, 14:25 UTC
Last known position
Country allocation
The ICAO 24-bit address 896423 falls within the block assigned to United Arab Emirates (AE) by ICAO Annex 10, Volume III. Every aircraft registered in United Arab Emirates 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ROJ023 | - | 22 | 2026-07-21 |
Recent flights last 22
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | ROJ023 | AUH → AUH | Jul 21, 14:05 UTC | Jul 21, 14:10 UTC | 5m |
| 2026-07-21 | ROJ023 | AUH → AUH | Jul 21, 13:50 UTC | Jul 21, 14:00 UTC | 10m |
| 2026-07-02 | ROJ023 | - | Jul 2, 10:25 UTC | Jul 2, 14:40 UTC | 4h 15m |
| 2026-07-02 | ROJ023 | - | Jul 2, 08:00 UTC | Jul 2, 09:20 UTC | 1h 20m |
| 2026-07-01 | ROJ023 | - | Jul 1, 08:20 UTC | Jul 1, 17:55 UTC | 9h 35m |
| 2026-06-30 | ROJ023 | - | Jun 30, 09:40 UTC | Jun 30, 09:50 UTC | 10m |
| 2026-06-30 | ROJ023 | - | Jun 30, 08:35 UTC | Jun 30, 09:00 UTC | 25m |
| 2026-06-30 | ROJ023 | - | Jun 30, 05:20 UTC | Jun 30, 05:40 UTC | 20m |
| 2026-06-29 | ROJ023 | - | Jun 29, 17:34 UTC | Jun 29, 17:55 UTC | 20m |
| 2026-06-28 | ROJ023 | - | Jun 28, 19:34 UTC | Jun 29, 17:55 UTC | 22h 20m |
| 2026-06-28 | ROJ023 | - | Jun 28, 18:05 UTC | Jun 28, 19:34 UTC | 1h 30m |
| 2026-06-28 | ROJ023 | - | Jun 28, 12:44 UTC | Jun 28, 15:44 UTC | 3h 0m |
| 2026-06-26 | ROJ023 | - | Jun 26, 08:50 UTC | Jun 26, 15:39 UTC | 6h 50m |
| 2026-06-11 | ROJ023 | - | Jun 11, 18:15 UTC | Jun 11, 22:05 UTC | 3h 50m |
| 2026-06-10 | ROJ023 | - | Jun 10, 20:35 UTC | Jun 11, 00:05 UTC | 3h 30m |
| 2026-06-08 | ROJ023 | - | Jun 8, 14:15 UTC | Jun 8, 14:45 UTC | 30m |
| 2026-05-23 | ROJ023 | - | May 23, 16:35 UTC | May 23, 19:55 UTC | 3h 20m |
| 2026-05-23 | ROJ023 | - | May 23, 13:55 UTC | May 23, 14:05 UTC | 10m |
| 2026-05-20 | ROJ023 | - | May 20, 16:25 UTC | May 20, 16:35 UTC | 10m |
| 2026-05-20 | ROJ023 | - | May 20, 11:05 UTC | May 20, 14:10 UTC | 3h 5m |
| 2026-05-04 | ROJ023 | - | May 4, 11:40 UTC | May 4, 12:05 UTC | 25m |
| 2026-05-04 | ROJ023 | - | May 4, 06:25 UTC | May 4, 06:45 UTC | 20m |
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 A6-RJD page for operator, model, and routing details .