sensors Mode-S transponder
72866B
ICAO 24-bit transponder address · allocated to Iraq
Currently assigned to YI-ASK · BOEING 737-800
- Hex
- 72866B
- Octal
- 34503153
- Decimal
- 7,505,515
- Country
- IQ
- Tail
- YI-ASK
- Type
- B738
- Flights observed
- 50
- Distinct callsigns
- 20
- Country
- IQ
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 72866B falls within the block assigned to Iraq (IQ) by ICAO Annex 10, Volume III. Every aircraft registered in Iraq 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 |
|---|---|---|---|
| IAW123 | Iraqi Airways | 14 | 2026-06-04 |
| IAW216 | Iraqi Airways | 6 | 2026-06-03 |
| IAW124 | Iraqi Airways | 5 | 2026-05-05 |
| IAW102 | Iraqi Airways | 3 | 2026-05-11 |
| IAW422 | - | 2 | 2026-06-01 |
| IAW3023 | - | 2 | 2026-06-02 |
| IAW251 | Iraqi Airways | 2 | 2026-06-01 |
| IAW163 | Iraqi Airways | 2 | 2026-05-12 |
| IAW101 | Iraqi Airways | 2 | 2026-05-11 |
| IAW494 | - | 1 | 2026-05-29 |
| IAW492 | - | 1 | 2026-05-26 |
| IAW491 | - | 1 | 2026-05-26 |
| IAW3024 | - | 1 | 2026-05-23 |
| IAW215 | Iraqi Airways | 1 | 2026-06-02 |
| IAW214 | - | 1 | 2026-05-22 |
| IAW213 | - | 1 | 2026-05-22 |
| IAW210 | Iraqi Airways | 1 | 2026-05-25 |
| IAW209 | Iraqi Airways | 1 | 2026-05-25 |
| IAW164 | Iraqi Airways | 1 | 2026-05-12 |
| IAW110 | Iraqi Airways | 1 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-04 | IAW123 | BGW → DXB | Jun 4, 08:40 UTC | Jun 4, 09:05 UTC | 25m |
| 2026-06-03 | IAW216 | IST → BGW | Jun 3, 08:50 UTC | Jun 4, 08:45 UTC | 23h 55m |
| 2026-06-03 | IAW216 | IST → BGW | Jun 3, 08:20 UTC | Jun 3, 09:25 UTC | 1h 5m |
| 2026-06-02 | IAW215 | BGW → IST | Jun 2, 17:50 UTC | Jun 3, 06:50 UTC | 13h 0m |
| 2026-06-02 | IAW3023 | - | Jun 2, 08:20 UTC | Jun 2, 16:35 UTC | 8h 15m |
| 2026-06-01 | IAW422 | - | Jun 1, 20:25 UTC | Jun 2, 06:35 UTC | 10h 10m |
| 2026-06-01 | IAW422 | - | Jun 1, 09:25 UTC | Jun 2, 06:35 UTC | 21h 10m |
| 2026-06-01 | IAW251 | KIK → IST | Jun 1, 07:15 UTC | Jun 1, 07:50 UTC | 35m |
| 2026-05-31 | IAW251 | KIK → IST | May 31, 08:50 UTC | Jun 1, 07:50 UTC | 23h 0m |
| 2026-05-31 | IAW123 | BGW → DXB | May 31, 08:25 UTC | May 31, 09:10 UTC | 45m |
| 2026-05-29 | IAW494 | - | May 29, 21:00 UTC | May 29, 21:40 UTC | 40m |
| 2026-05-29 | IAW123 | BGW → DXB | May 29, 08:20 UTC | May 29, 19:25 UTC | 11h 6m |
| 2026-05-28 | IAW123 | BGW → DXB | May 28, 08:50 UTC | May 29, 08:45 UTC | 23h 55m |
| 2026-05-28 | IAW123 | BGW → DXB | May 28, 08:20 UTC | May 28, 09:05 UTC | 45m |
| 2026-05-26 | IAW492 | - | May 26, 09:25 UTC | May 26, 09:45 UTC | 20m |
| 2026-05-26 | IAW491 | - | May 26, 08:15 UTC | May 26, 08:24 UTC | 10m |
| 2026-05-25 | IAW210 | AYT → BGW | May 25, 18:55 UTC | May 25, 19:15 UTC | 20m |
| 2026-05-25 | IAW209 | BGW → AYT | May 25, 16:55 UTC | May 25, 17:25 UTC | 30m |
| 2026-05-23 | IAW3024 | - | May 23, 17:25 UTC | May 23, 17:45 UTC | 20m |
| 2026-05-23 | IAW3023 | - | May 23, 15:55 UTC | May 23, 16:15 UTC | 20m |
| 2026-05-22 | IAW214 | - | May 22, 23:55 UTC | May 23, 10:15 UTC | 10h 19m |
| 2026-05-22 | IAW213 | - | May 22, 22:30 UTC | May 22, 22:40 UTC | 10m |
| 2026-05-22 | IAW105 | ISU → DXB | May 22, 08:15 UTC | May 22, 08:25 UTC | 10m |
| 2026-05-12 | IAW164 | AMM → BGW | May 12, 16:50 UTC | May 12, 17:05 UTC | 15m |
| 2026-05-12 | IAW163 | BGW → AMM | May 12, 05:35 UTC | May 12, 15:20 UTC | 9h 45m |
| 2026-05-11 | IAW102 | CAI → BGW | May 11, 10:50 UTC | May 12, 05:35 UTC | 18h 45m |
| 2026-05-11 | IAW102 | CAI → BGW | May 11, 10:40 UTC | May 12, 05:35 UTC | 18h 56m |
| 2026-05-11 | IAW101 | BGW → CAI | May 11, 08:10 UTC | May 11, 09:05 UTC | 55m |
| 2026-05-06 | IAW216 | IST → BGW | May 6, 09:30 UTC | May 6, 15:15 UTC | 5h 45m |
| 2026-05-05 | IAW124 | DXB → BGW | May 5, 11:55 UTC | May 5, 13:05 UTC | 1h 10m |
| 2026-05-05 | IAW123 | BGW → DXB | May 5, 08:45 UTC | May 5, 09:10 UTC | 25m |
| 2026-05-03 | IAW102 | CAI → BGW | May 3, 11:25 UTC | May 3, 11:50 UTC | 25m |
| 2026-05-02 | IAW101 | BGW → CAI | May 2, 17:00 UTC | May 3, 09:20 UTC | 16h 19m |
| 2026-05-02 | IAW163 | BGW → AMM | May 2, 15:05 UTC | May 2, 15:15 UTC | 10m |
| 2026-04-30 | IAW124 | DXB → BGW | Apr 30, 12:35 UTC | Apr 30, 13:40 UTC | 1h 5m |
| 2026-04-30 | IAW123 | BGW → DXB | Apr 30, 08:35 UTC | Apr 30, 09:45 UTC | 1h 10m |
| 2026-04-29 | IAW123 | BGW → DXB | Apr 29, 12:50 UTC | Apr 30, 09:45 UTC | 20h 54m |
| 2026-04-29 | IAW123 | BGW → DXB | Apr 29, 11:55 UTC | Apr 30, 09:45 UTC | 21h 49m |
| 2026-04-29 | IAW123 | BGW → DXB | Apr 29, 08:34 UTC | Apr 29, 09:35 UTC | 1h 1m |
| 2026-04-28 | IAW216 | IST → BGW | Apr 28, 08:20 UTC | Apr 28, 08:30 UTC | 10m |
| 2026-04-26 | IAW124 | DXB → BGW | Apr 26, 12:00 UTC | Apr 26, 13:10 UTC | 1h 10m |
| 2026-04-26 | IAW123 | BGW → DXB | Apr 26, 08:20 UTC | Apr 26, 09:25 UTC | 1h 5m |
| 2026-04-25 | IAW123 | BGW → DXB | Apr 25, 12:50 UTC | Apr 26, 09:25 UTC | 20h 35m |
| 2026-04-25 | IAW124 | DXB → BGW | Apr 25, 12:20 UTC | Apr 26, 09:25 UTC | 21h 5m |
| 2026-04-25 | IAW123 | BGW → DXB | Apr 25, 08:25 UTC | Apr 25, 09:30 UTC | 1h 5m |
| 2026-04-22 | IAW216 | IST → BGW | Apr 22, 09:05 UTC | Apr 22, 15:00 UTC | 5h 55m |
| 2026-04-20 | IAW124 | DXB → BGW | Apr 20, 10:40 UTC | Apr 20, 11:55 UTC | 1h 15m |
| 2026-04-20 | IAW123 | BGW → DXB | Apr 20, 07:20 UTC | Apr 20, 08:30 UTC | 1h 10m |
| 2026-04-17 | IAW110 | CAI → BGW | Apr 17, 18:15 UTC | Apr 17, 19:10 UTC | 55m |
| 2026-04-16 | IAW216 | IST → BGW | Apr 16, 09:10 UTC | Apr 16, 09:29 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 YI-ASK page for operator, model, and routing details .