sensors Mode-S transponder
73244B
ICAO 24-bit transponder address · allocated to Iran
Currently assigned to EP-IBK · AIRBUS A-310
- Hex
- 73244B
- Octal
- 34622113
- Decimal
- 7,545,931
- Country
- IR
- Tail
- EP-IBK
- Type
- A310
- Flights observed
- 42
- Distinct callsigns
- 14
- Country
- IR
- Last broadcast
- 25d ago
Last known position
Country allocation
The ICAO 24-bit address 73244B falls within the block assigned to Iran (IR) by ICAO Annex 10, Volume III. Every aircraft registered in Iran 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| IRA718 | Iran Air | 13 | 2026-05-05 |
| IRA719 | Iran Air | 9 | 2026-05-04 |
| IRA3633 | - | 5 | 2026-05-08 |
| IRA3681 | - | 3 | 2026-05-06 |
| IRA3585 | - | 3 | 2026-05-09 |
| IRA5329 | - | 1 | 2026-04-25 |
| IRA3679 | - | 1 | 2026-05-14 |
| IRA3635 | - | 1 | 2026-04-30 |
| IRA3604 | - | 1 | 2026-05-12 |
| IRA3599 | Iran Air | 1 | 2026-05-15 |
| IRA3584 | - | 1 | 2026-05-08 |
| IRA3580 | - | 1 | 2026-05-14 |
| IRA3539 | - | 1 | 2026-05-10 |
| IRA3538 | - | 1 | 2026-05-09 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-15 | IRA3599 | MED → MHD | May 15, 05:25 UTC | May 16, 00:25 UTC | 18h 59m |
| 2026-05-14 | IRA3580 | - | May 14, 06:55 UTC | May 15, 06:30 UTC | 23h 35m |
| 2026-05-14 | IRA3679 | - | May 14, 01:20 UTC | May 14, 07:05 UTC | 5h 45m |
| 2026-05-12 | IRA3604 | - | May 12, 18:10 UTC | May 12, 23:50 UTC | 5h 40m |
| 2026-05-10 | IRA3539 | - | May 10, 20:50 UTC | May 11, 15:40 UTC | 18h 50m |
| 2026-05-09 | IRA3538 | - | May 9, 22:49 UTC | May 10, 21:44 UTC | 22h 55m |
| 2026-05-09 | IRA3585 | - | May 9, 17:10 UTC | May 9, 23:30 UTC | 6h 20m |
| 2026-05-09 | IRA3585 | - | May 9, 02:50 UTC | May 9, 23:30 UTC | 20h 40m |
| 2026-05-09 | IRA3585 | - | May 9, 02:15 UTC | May 9, 23:30 UTC | 21h 15m |
| 2026-05-08 | IRA3584 | - | May 8, 21:15 UTC | May 9, 18:15 UTC | 21h 0m |
| 2026-05-08 | IRA3633 | - | May 8, 05:09 UTC | May 9, 03:20 UTC | 22h 10m |
| 2026-05-08 | IRA3633 | - | May 8, 01:04 UTC | May 8, 22:15 UTC | 21h 10m |
| 2026-05-08 | IRA3633 | - | May 8, 00:25 UTC | May 8, 22:15 UTC | 21h 50m |
| 2026-05-07 | IRA3633 | - | May 7, 10:50 UTC | May 8, 06:20 UTC | 19h 30m |
| 2026-05-07 | IRA3633 | - | May 7, 10:00 UTC | May 8, 06:20 UTC | 20h 20m |
| 2026-05-06 | IRA3681 | - | May 6, 22:55 UTC | May 7, 16:20 UTC | 17h 26m |
| 2026-05-06 | IRA3681 | - | May 6, 18:50 UTC | May 7, 16:20 UTC | 21h 30m |
| 2026-05-05 | IRA718 | IST → IKA | May 5, 09:30 UTC | May 5, 11:25 UTC | 1h 55m |
| 2026-05-04 | IRA719 | IKA → IST | May 4, 10:50 UTC | May 5, 06:00 UTC | 19h 11m |
| 2026-05-04 | IRA719 | IKA → IST | May 4, 09:15 UTC | May 5, 06:00 UTC | 20h 46m |
| 2026-05-04 | IRA718 | IST → IKA | May 4, 04:50 UTC | May 5, 04:45 UTC | 23h 56m |
| 2026-05-04 | IRA719 | IKA → IST | May 4, 04:15 UTC | May 4, 11:10 UTC | 6h 55m |
| 2026-05-03 | IRA718 | IST → IKA | May 3, 11:00 UTC | May 4, 10:45 UTC | 23h 45m |
| 2026-05-03 | IRA718 | IST → IKA | May 3, 10:10 UTC | May 4, 05:30 UTC | 19h 20m |
| 2026-05-02 | IRA718 | IST → IKA | May 2, 23:10 UTC | May 3, 06:35 UTC | 7h 24m |
| 2026-05-02 | IRA719 | IKA → IST | May 2, 05:25 UTC | May 2, 17:20 UTC | 11h 55m |
| 2026-05-01 | IRA718 | IST → IKA | May 1, 10:50 UTC | May 2, 10:45 UTC | 23h 55m |
| 2026-05-01 | IRA718 | IST → IKA | May 1, 10:05 UTC | May 2, 06:25 UTC | 20h 20m |
| 2026-04-30 | IRA718 | IST → IKA | Apr 30, 18:45 UTC | May 1, 11:55 UTC | 17h 10m |
| 2026-04-30 | IRA3635 | - | Apr 30, 01:20 UTC | May 1, 00:00 UTC | 22h 40m |
| 2026-04-29 | IRA3681 | - | Apr 29, 19:00 UTC | Apr 30, 18:45 UTC | 23h 44m |
| 2026-04-29 | IRA718 | IST → IKA | Apr 29, 09:15 UTC | Apr 30, 02:15 UTC | 16h 59m |
| 2026-04-28 | IRA718 | IST → IKA | Apr 28, 11:00 UTC | Apr 29, 05:40 UTC | 18h 40m |
| 2026-04-28 | IRA718 | IST → IKA | Apr 28, 10:20 UTC | Apr 29, 05:40 UTC | 19h 20m |
| 2026-04-27 | IRA719 | IKA → IST | Apr 27, 17:25 UTC | Apr 28, 07:30 UTC | 14h 5m |
| 2026-04-27 | IRA719 | IKA → IST | Apr 27, 10:50 UTC | Apr 28, 07:30 UTC | 20h 40m |
| 2026-04-27 | IRA718 | IST → IKA | Apr 27, 09:15 UTC | Apr 28, 07:30 UTC | 22h 15m |
| 2026-04-26 | IRA719 | IKA → IST | Apr 26, 13:45 UTC | Apr 27, 05:55 UTC | 16h 10m |
| 2026-04-26 | IRA719 | IKA → IST | Apr 26, 07:25 UTC | Apr 27, 05:55 UTC | 22h 30m |
| 2026-04-25 | IRA5329 | - | Apr 25, 10:50 UTC | Apr 26, 08:10 UTC | 21h 20m |
| 2026-04-25 | IRA718 | IST → IKA | Apr 25, 09:25 UTC | Apr 26, 08:10 UTC | 22h 45m |
| 2026-04-25 | IRA719 | IKA → IST | Apr 25, 04:20 UTC | Apr 25, 05:50 UTC | 1h 30m |
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 EP-IBK page for operator, model, and routing details .