sensors Mode-S transponder
896213
ICAO 24-bit transponder address · allocated to United Arab Emirates
Currently assigned to A6-EGR · BOEING 777-300ER
- Hex
- 896213
- Octal
- 42261023
- Decimal
- 9,003,539
- Country
- AE
- Tail
- A6-EGR
- Type
- B77W
- Flights observed
- 56
- Distinct callsigns
- 20
- Country
- AE
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 896213 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 |
|---|---|---|---|
| UAE9967 | - | 9 | 2026-05-25 |
| UAE9968 | Emirates | 6 | 2026-05-26 |
| UAE95 | Emirates | 4 | 2026-04-14 |
| UAE9818 | - | 3 | 2026-05-27 |
| UAE96 | Emirates | 3 | 2026-04-15 |
| UAE2579 | Emirates | 3 | 2026-04-20 |
| UAE9965 | - | 2 | 2026-05-19 |
| UAE9938 | - | 2 | 2026-04-28 |
| UAE9648 | - | 2 | 2026-04-17 |
| UAE512 | Emirates | 2 | 2026-04-12 |
| UAE2578 | - | 2 | 2026-04-20 |
| UAE9978 | Emirates | 1 | 2026-05-22 |
| UAE9977 | Emirates | 1 | 2026-05-22 |
| UAE9966 | Emirates | 1 | 2026-05-20 |
| UAE9928 | Emirates | 1 | 2026-05-23 |
| UAE9869 | Emirates | 1 | 2026-05-24 |
| UAE9721 | Emirates | 1 | 2026-04-23 |
| UAE9720 | - | 1 | 2026-04-22 |
| UAE9438 | - | 1 | 2026-04-26 |
| UAE9437 | Emirates | 1 | 2026-04-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UAE510 | DXB → DEL | May 30, 03:15 UTC | May 30, 04:00 UTC | 45m |
| 2026-05-27 | UAE9818 | - | May 27, 08:20 UTC | May 27, 21:00 UTC | 12h 40m |
| 2026-05-26 | UAE9818 | - | May 26, 14:50 UTC | May 27, 13:00 UTC | 22h 11m |
| 2026-05-26 | UAE9968 | DFW → DWC | May 26, 12:50 UTC | May 27, 12:45 UTC | 23h 55m |
| 2026-05-26 | UAE9968 | DFW → DWC | May 26, 10:50 UTC | May 27, 09:10 UTC | 22h 20m |
| 2026-05-26 | UAE9968 | DFW → DWC | May 26, 10:29 UTC | May 27, 08:45 UTC | 22h 16m |
| 2026-05-26 | UAE9968 | DFW → DWC | May 26, 04:15 UTC | May 26, 15:14 UTC | 11h 0m |
| 2026-05-25 | UAE9968 | DFW → DWC | May 25, 23:24 UTC | May 26, 01:10 UTC | 1h 45m |
| 2026-05-25 | UAE9967 | - | May 25, 10:35 UTC | May 25, 20:55 UTC | 10h 20m |
| 2026-05-25 | UAE9967 | - | May 25, 03:55 UTC | May 25, 08:05 UTC | 4h 10m |
| 2026-05-24 | UAE9967 | - | May 24, 08:50 UTC | May 25, 08:05 UTC | 23h 15m |
| 2026-05-24 | UAE9967 | - | May 24, 07:55 UTC | May 25, 06:45 UTC | 22h 50m |
| 2026-05-24 | UAE9869 | HAN → DWC | May 24, 04:50 UTC | May 25, 04:45 UTC | 23h 55m |
| 2026-05-23 | UAE9928 | DWC → HKG | May 23, 21:20 UTC | May 24, 08:50 UTC | 11h 30m |
| 2026-05-22 | UAE9978 | FRA → DXB | May 22, 13:35 UTC | May 22, 20:10 UTC | 6h 35m |
| 2026-05-22 | UAE9977 | MAD → DWC | May 22, 02:45 UTC | May 22, 09:45 UTC | 7h 0m |
| 2026-05-20 | UAE9966 | JFK → DWC | May 20, 04:20 UTC | May 20, 16:20 UTC | 12h 1m |
| 2026-05-19 | UAE9965 | - | May 19, 11:35 UTC | May 19, 23:10 UTC | 11h 35m |
| 2026-05-19 | UAE9965 | - | May 19, 05:15 UTC | May 19, 09:35 UTC | 4h 20m |
| 2026-05-16 | UAE304 | DXB → PVG | May 16, 15:05 UTC | May 17, 06:45 UTC | 15h 40m |
| 2026-05-09 | UAE9818 | - | May 9, 10:50 UTC | May 9, 21:30 UTC | 10h 40m |
| 2026-04-28 | UAE9938 | - | Apr 28, 07:50 UTC | Apr 29, 00:54 UTC | 17h 5m |
| 2026-04-28 | UAE9938 | - | Apr 28, 01:10 UTC | Apr 29, 00:45 UTC | 23h 35m |
| 2026-04-26 | UAE9438 | - | Apr 26, 11:50 UTC | Apr 26, 12:40 UTC | 50m |
| 2026-04-26 | UAE9437 | ICN → DWC | Apr 26, 08:15 UTC | Apr 26, 08:55 UTC | 40m |
| 2026-04-25 | UAE72 | CDG → DXB | Apr 25, 11:10 UTC | Apr 25, 17:40 UTC | 6h 30m |
| 2026-04-24 | UAE71 | DXB → CDG | Apr 24, 23:40 UTC | Apr 25, 07:10 UTC | 7h 30m |
| 2026-04-23 | UAE9721 | KGL → NBO | Apr 23, 02:15 UTC | Apr 23, 02:35 UTC | 20m |
| 2026-04-22 | UAE9720 | - | Apr 22, 21:50 UTC | Apr 22, 22:15 UTC | 25m |
| 2026-04-20 | UAE2579 | HKG → DXB | Apr 20, 22:50 UTC | Apr 20, 23:15 UTC | 25m |
| 2026-04-20 | UAE2579 | HKG → DXB | Apr 20, 17:00 UTC | Apr 20, 19:35 UTC | 2h 35m |
| 2026-04-20 | UAE2579 | HKG → DXB | Apr 20, 15:20 UTC | Apr 20, 15:35 UTC | 15m |
| 2026-04-20 | UAE2578 | - | Apr 20, 12:35 UTC | Apr 20, 13:00 UTC | 25m |
| 2026-04-20 | UAE2578 | - | Apr 20, 06:10 UTC | Apr 20, 10:25 UTC | 4h 15m |
| 2026-04-18 | UAE9968 | DFW → DWC | Apr 18, 23:45 UTC | Apr 19, 14:20 UTC | 14h 35m |
| 2026-04-18 | UAE9967 | - | Apr 18, 10:30 UTC | Apr 18, 20:40 UTC | 10h 10m |
| 2026-04-18 | UAE9967 | - | Apr 18, 07:25 UTC | Apr 18, 08:40 UTC | 1h 15m |
| 2026-04-18 | UAE9967 | - | Apr 18, 05:30 UTC | Apr 18, 07:20 UTC | 1h 50m |
| 2026-04-18 | UAE9967 | - | Apr 18, 01:25 UTC | Apr 18, 02:05 UTC | 40m |
| 2026-04-18 | UAE9967 | - | Apr 18, 01:00 UTC | Apr 18, 01:20 UTC | 20m |
| 2026-04-17 | UAE9648 | - | Apr 17, 17:00 UTC | Apr 17, 17:15 UTC | 15m |
| 2026-04-16 | UAE9648 | - | Apr 16, 21:55 UTC | Apr 16, 22:20 UTC | 25m |
| 2026-04-16 | UAE2501 | DXB → MAN | Apr 16, 16:15 UTC | Apr 16, 16:30 UTC | 15m |
| 2026-04-16 | UAE714 | LUN → DXB | Apr 16, 01:20 UTC | Apr 16, 01:50 UTC | 30m |
| 2026-04-15 | UAE88N | DXB → LUN | Apr 15, 05:55 UTC | Apr 15, 06:25 UTC | 30m |
| 2026-04-15 | UAE96 | FCO → DXB | Apr 15, 01:10 UTC | Apr 15, 02:15 UTC | 1h 5m |
| 2026-04-14 | UAE96 | FCO → DXB | Apr 14, 20:55 UTC | Apr 14, 22:30 UTC | 1h 35m |
| 2026-04-14 | UAE96 | FCO → DXB | Apr 14, 20:35 UTC | Apr 14, 20:50 UTC | 15m |
| 2026-04-14 | UAE95 | DXB → FCO | Apr 14, 16:50 UTC | Apr 14, 18:35 UTC | 1h 45m |
| 2026-04-14 | UAE95 | DXB → FCO | Apr 14, 15:35 UTC | Apr 14, 16:45 UTC | 1h 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-EGR page for operator, model, and routing details .