sensors Mode-S transponder
732541
ICAO 24-bit transponder address · allocated to Iran
Currently assigned to EP-IJA · AIRBUS A-330-200
- Hex
- 732541
- Octal
- 34622501
- Decimal
- 7,546,177
- Country
- IR
- Tail
- EP-IJA
- Type
- A332
- Flights observed
- 41
- Distinct callsigns
- 15
- Country
- IR
- Last broadcast
- 22d ago
Last known position
Country allocation
The ICAO 24-bit address 732541 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| IRA719 | Iran Air | 8 | 2026-05-22 |
| IRA718 | Iran Air | 5 | 2026-05-22 |
| IRA3687 | - | 5 | 2026-04-30 |
| IRA3507 | - | 4 | 2026-05-02 |
| IRA3609 | - | 3 | 2026-04-29 |
| IRA3561 | Iran Air | 3 | 2026-04-28 |
| IRA3527 | - | 3 | 2026-05-03 |
| IRA3613 | - | 2 | 2026-05-05 |
| IRA3581 | - | 2 | 2026-05-02 |
| IRA5393 | - | 1 | 2026-04-27 |
| IRA5392 | - | 1 | 2026-04-27 |
| IRA3582 | - | 1 | 2026-05-15 |
| IRA3560 | - | 1 | 2026-04-27 |
| IRA3537 | - | 1 | 2026-05-04 |
| IRA3506 | - | 1 | 2026-05-01 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-22 | IRA718 | IST → IKA | May 22, 10:00 UTC | May 22, 11:40 UTC | 1h 40m |
| 2026-05-22 | IRA719 | IKA → IST | May 22, 07:30 UTC | May 22, 07:45 UTC | 15m |
| 2026-05-22 | IRA719 | IKA → IST | May 22, 06:00 UTC | May 22, 06:45 UTC | 45m |
| 2026-05-21 | IRA719 | IKA → IST | May 21, 10:20 UTC | May 22, 06:45 UTC | 20h 25m |
| 2026-05-21 | IRA718 | IST → IKA | May 21, 09:10 UTC | May 22, 06:45 UTC | 21h 35m |
| 2026-05-21 | IRA719 | IKA → IST | May 21, 06:00 UTC | May 21, 06:15 UTC | 15m |
| 2026-05-21 | IRA719 | IKA → IST | May 21, 04:45 UTC | May 21, 05:10 UTC | 25m |
| 2026-05-18 | IRA718 | IST → IKA | May 18, 09:25 UTC | May 18, 10:55 UTC | 1h 30m |
| 2026-05-18 | IRA719 | IKA → IST | May 18, 06:50 UTC | May 18, 07:00 UTC | 10m |
| 2026-05-18 | IRA719 | IKA → IST | May 18, 05:10 UTC | May 18, 06:05 UTC | 55m |
| 2026-05-17 | IRA719 | IKA → IST | May 17, 10:10 UTC | May 18, 06:05 UTC | 19h 55m |
| 2026-05-17 | IRA718 | IST → IKA | May 17, 09:10 UTC | May 17, 09:25 UTC | 15m |
| 2026-05-15 | IRA3582 | - | May 15, 07:30 UTC | May 15, 07:45 UTC | 15m |
| 2026-05-06 | IRA718 | IST → IKA | May 6, 12:01 UTC | May 6, 12:45 UTC | 45m |
| 2026-05-05 | IRA3613 | - | May 5, 20:15 UTC | May 6, 08:25 UTC | 12h 10m |
| 2026-05-05 | IRA3613 | - | May 5, 05:35 UTC | May 6, 01:50 UTC | 20h 15m |
| 2026-05-04 | IRA3537 | - | May 4, 08:55 UTC | May 5, 06:05 UTC | 21h 11m |
| 2026-05-03 | IRA3527 | - | May 3, 17:29 UTC | May 4, 10:05 UTC | 16h 35m |
| 2026-05-03 | IRA3527 | - | May 3, 12:30 UTC | May 4, 10:05 UTC | 21h 35m |
| 2026-05-03 | IRA3527 | - | May 3, 00:20 UTC | May 3, 18:40 UTC | 18h 19m |
| 2026-05-02 | IRA3581 | - | May 2, 19:10 UTC | May 3, 18:09 UTC | 22h 59m |
| 2026-05-02 | IRA3581 | - | May 2, 06:20 UTC | May 3, 01:30 UTC | 19h 10m |
| 2026-05-02 | IRA3507 | - | May 2, 05:30 UTC | May 3, 01:30 UTC | 20h 0m |
| 2026-05-02 | IRA3507 | - | May 2, 00:20 UTC | May 2, 19:15 UTC | 18h 55m |
| 2026-05-01 | IRA3507 | - | May 1, 12:35 UTC | May 2, 06:45 UTC | 18h 10m |
| 2026-05-01 | IRA3507 | - | May 1, 11:55 UTC | May 2, 06:45 UTC | 18h 50m |
| 2026-05-01 | IRA3506 | - | May 1, 03:00 UTC | May 2, 01:30 UTC | 22h 30m |
| 2026-04-30 | IRA3687 | - | Apr 30, 09:50 UTC | May 1, 04:05 UTC | 18h 15m |
| 2026-04-30 | IRA3687 | - | Apr 30, 04:35 UTC | May 1, 04:05 UTC | 23h 30m |
| 2026-04-29 | IRA3687 | - | Apr 29, 18:50 UTC | Apr 30, 11:00 UTC | 16h 9m |
| 2026-04-29 | IRA3687 | - | Apr 29, 14:20 UTC | Apr 30, 11:00 UTC | 20h 39m |
| 2026-04-29 | IRA3687 | - | Apr 29, 13:10 UTC | Apr 30, 11:00 UTC | 21h 49m |
| 2026-04-29 | IRA3609 | - | Apr 29, 03:15 UTC | Apr 29, 19:55 UTC | 16h 41m |
| 2026-04-28 | IRA3609 | - | Apr 28, 22:40 UTC | Apr 29, 19:55 UTC | 21h 16m |
| 2026-04-28 | IRA3609 | - | Apr 28, 21:55 UTC | Apr 29, 19:55 UTC | 22h 1m |
| 2026-04-28 | IRA3561 | MED → ZAH | Apr 28, 14:20 UTC | Apr 29, 14:15 UTC | 23h 55m |
| 2026-04-28 | IRA3561 | MED → ZAH | Apr 28, 08:20 UTC | Apr 29, 04:20 UTC | 20h 0m |
| 2026-04-28 | IRA3561 | MED → ZAH | Apr 28, 07:10 UTC | Apr 29, 04:20 UTC | 21h 10m |
| 2026-04-27 | IRA3560 | - | Apr 27, 12:20 UTC | Apr 28, 08:20 UTC | 20h 0m |
| 2026-04-27 | IRA5392 | - | Apr 27, 11:50 UTC | Apr 28, 08:20 UTC | 20h 30m |
| 2026-04-27 | IRA5393 | - | Apr 27, 08:35 UTC | Apr 27, 09:35 UTC | 1h 0m |
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-IJA page for operator, model, and routing details .