sensors Mode-S transponder
89618B
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EEL · AIRBUS A-380-800
- Hex
- 89618B
- Octal
- 42260613
- Decimal
- 9,003,403
- Country
- AE
- Tail
- A6-EEL
- Type
- A388
- Flights observed
- 99
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 4h ago
Current position
Country allocation
The ICAO 24-bit address 89618B 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UAE242 | - | 29 | 2026-06-12 |
| UAE30Y | Emirates | 24 | 2026-06-12 |
| UAE52M | Emirates | 4 | 2026-06-02 |
| UAE46 | Emirates | 4 | 2026-06-02 |
| UAE353 | Emirates | 4 | 2026-05-24 |
| UAE303 | Emirates | 4 | 2026-05-23 |
| UAE2LT | Emirates | 4 | 2026-06-11 |
| UAE2K | Emirates | 3 | 2026-06-11 |
| UAE803 | Emirates | 2 | 2026-04-15 |
| UAE71J | Emirates | 2 | 2026-05-25 |
| UAE67V | Emirates | 2 | 2026-06-03 |
| UAE54J | Emirates | 2 | 2026-06-03 |
| UAE352 | Emirates | 2 | 2026-05-24 |
| UAE323 | Emirates | 2 | 2026-06-01 |
| UAE1EW | Emirates | 2 | 2026-05-25 |
| UAE96R | Emirates | 1 | 2026-04-21 |
| UAE8UW | Emirates | 1 | 2026-05-20 |
| UAE84N | Emirates | 1 | 2026-04-21 |
| UAE804 | Emirates | 1 | 2026-04-15 |
| UAE7Q | Emirates | 1 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-12 | UAE242 | - | Jun 12, 20:10 UTC | Jun 12, 21:10 UTC | 1h 0m |
| 2026-06-12 | UAE30Y | DXB → YYZ | Jun 12, 03:20 UTC | Jun 12, 13:10 UTC | 9h 50m |
| 2026-06-11 | UAE2LT | CAI → DXB | Jun 11, 17:35 UTC | Jun 11, 20:45 UTC | 3h 10m |
| 2026-06-11 | UAE2K | DXB → CAI | Jun 11, 12:30 UTC | Jun 11, 14:55 UTC | 2h 25m |
| 2026-06-07 | UAE242 | YYZ → DXB | Jun 7, 19:10 UTC | Jun 8, 08:00 UTC | 12h 50m |
| 2026-06-07 | UAE30Y | DXB → YYZ | Jun 7, 03:15 UTC | Jun 7, 12:50 UTC | 9h 35m |
| 2026-06-06 | UAE2LT | CAI → DXB | Jun 6, 17:34 UTC | Jun 6, 20:35 UTC | 3h 0m |
| 2026-06-05 | UAE242 | YYZ → DXB | Jun 5, 19:20 UTC | Jun 6, 07:55 UTC | 12h 35m |
| 2026-06-05 | UAE30Y | DXB → YYZ | Jun 5, 00:30 UTC | Jun 5, 13:00 UTC | 12h 30m |
| 2026-06-03 | UAE54J | VIE → DXB | Jun 3, 13:55 UTC | Jun 3, 19:35 UTC | 5h 40m |
| 2026-06-03 | UAE67V | DXB → VIE | Jun 3, 05:00 UTC | Jun 3, 10:45 UTC | 5h 45m |
| 2026-06-02 | UAE46 | FRA → DXB | Jun 2, 14:20 UTC | Jun 2, 20:40 UTC | 6h 20m |
| 2026-06-02 | UAE52M | DXB → FRA | Jun 2, 08:00 UTC | Jun 2, 11:50 UTC | 3h 50m |
| 2026-06-01 | UAE323 | ICN → DXB | Jun 1, 23:45 UTC | Jun 2, 00:05 UTC | 20m |
| 2026-06-01 | UAE323 | ICN → DXB | Jun 1, 15:10 UTC | Jun 1, 22:45 UTC | 7h 35m |
| 2026-06-01 | UAE322 | DXB → ICN | Jun 1, 08:40 UTC | Jun 1, 09:05 UTC | 25m |
| 2026-05-31 | UAE46 | FRA → DXB | May 31, 14:15 UTC | May 31, 20:25 UTC | 6h 10m |
| 2026-05-30 | UAE52M | DXB → FRA | May 30, 21:35 UTC | May 31, 11:40 UTC | 14h 5m |
| 2026-05-30 | UAE7Q | KUL → DXB | May 30, 18:25 UTC | May 30, 18:45 UTC | 20m |
| 2026-05-30 | UAE15K | DXB → KUL | May 30, 01:25 UTC | May 30, 06:30 UTC | 5h 5m |
| 2026-05-25 | UAE71J | CAI → DXB | May 25, 10:55 UTC | May 25, 14:00 UTC | 3h 5m |
| 2026-05-25 | UAE1EW | DXB → CAI | May 25, 06:05 UTC | May 25, 08:20 UTC | 2h 15m |
| 2026-05-24 | UAE353 | SIN → DXB | May 24, 23:35 UTC | May 24, 23:46 UTC | 11m |
| 2026-05-24 | UAE353 | SIN → DXB | May 24, 17:15 UTC | May 24, 21:45 UTC | 4h 30m |
| 2026-05-24 | UAE352 | DXB → SIN | May 24, 08:25 UTC | May 24, 13:45 UTC | 5h 20m |
| 2026-05-23 | UAE46 | FRA → DXB | May 23, 13:50 UTC | May 23, 20:15 UTC | 6h 26m |
| 2026-05-23 | UAE52M | DXB → FRA | May 23, 04:40 UTC | May 23, 11:00 UTC | 6h 20m |
| 2026-05-23 | UAE303 | PVG → DXB | May 23, 00:40 UTC | May 23, 01:10 UTC | 30m |
| 2026-05-22 | UAE303 | PVG → DXB | May 22, 20:05 UTC | May 22, 23:35 UTC | 3h 30m |
| 2026-05-22 | UAE303 | PVG → DXB | May 22, 03:25 UTC | May 22, 23:35 UTC | 20h 10m |
| 2026-05-22 | UAE303 | PVG → DXB | May 22, 01:15 UTC | May 22, 23:35 UTC | 22h 20m |
| 2026-05-21 | UAE46 | FRA → DXB | May 21, 13:55 UTC | May 21, 20:05 UTC | 6h 10m |
| 2026-05-21 | UAE52M | DXB → FRA | May 21, 08:40 UTC | May 21, 11:05 UTC | 2h 25m |
| 2026-05-20 | UAE8UW | JFK → DXB | May 20, 03:55 UTC | May 20, 16:20 UTC | 12h 26m |
| 2026-05-19 | UAE69R | DXB → JFK | May 19, 05:30 UTC | May 19, 18:30 UTC | 13h 0m |
| 2026-05-18 | UAE353 | SIN → DXB | May 18, 23:40 UTC | May 18, 23:55 UTC | 15m |
| 2026-05-18 | UAE353 | SIN → DXB | May 18, 17:15 UTC | May 18, 22:05 UTC | 4h 49m |
| 2026-05-18 | UAE352 | DXB → SIN | May 18, 06:20 UTC | May 18, 13:20 UTC | 7h 0m |
| 2026-05-16 | UAE242 | YYZ → DXB | May 16, 19:20 UTC | May 17, 07:45 UTC | 12h 25m |
| 2026-05-16 | UAE30Y | DXB → YYZ | May 16, 00:30 UTC | May 16, 13:55 UTC | 13h 26m |
| 2026-05-15 | UAE2LT | CAI → DXB | May 15, 18:05 UTC | May 15, 21:10 UTC | 3h 5m |
| 2026-05-15 | UAE2K | DXB → CAI | May 15, 15:10 UTC | May 15, 15:30 UTC | 20m |
| 2026-05-14 | UAE242 | YYZ → DXB | May 14, 19:15 UTC | May 15, 08:00 UTC | 12h 45m |
| 2026-05-13 | UAE30Y | DXB → YYZ | May 13, 23:20 UTC | May 14, 13:25 UTC | 14h 5m |
| 2026-05-12 | UAE242 | YYZ → DXB | May 12, 19:10 UTC | May 13, 07:50 UTC | 12h 40m |
| 2026-05-12 | UAE30Y | DXB → YYZ | May 12, 02:45 UTC | May 12, 13:40 UTC | 10h 55m |
| 2026-05-11 | UAE54J | VIE → DXB | May 11, 13:55 UTC | May 11, 19:35 UTC | 5h 41m |
| 2026-05-11 | UAE67V | DXB → VIE | May 11, 04:30 UTC | May 11, 10:50 UTC | 6h 20m |
| 2026-05-01 | UAE2505 | DXB → SHJ | May 1, 23:20 UTC | May 1, 23:35 UTC | 15m |
| 2026-05-01 | UAE2LT | CAI → DXB | May 1, 18:15 UTC | May 1, 21:25 UTC | 3h 10m |
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-EEL page for operator, model, and routing details .