sensors Mode-S transponder
733493
ICAO 24-bit transponder address · allocated to Iran
Currently assigned to EP-MDS · AIRBUS A-320
- Hex
- 733493
- Octal
- 34632223
- Decimal
- 7,550,099
- Country
- IR
- Tail
- EP-MDS
- Type
- A320
- Flights observed
- 61
- Distinct callsigns
- 4
- Country
- IR
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 733493 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-25 | IRB9747 | - | Jun 25, 11:50 UTC | Jun 25, 13:00 UTC | 1h 10m |
| 2026-06-25 | IRB9746 | - | Jun 25, 08:40 UTC | Jun 25, 10:25 UTC | 1h 45m |
| 2026-06-24 | IRB9746 | - | Jun 24, 11:39 UTC | Jun 25, 10:25 UTC | 22h 45m |
| 2026-06-24 | IRB9709 | - | Jun 24, 08:45 UTC | Jun 24, 10:14 UTC | 1h 30m |
| 2026-06-22 | IRB9747 | - | Jun 22, 14:05 UTC | Jun 22, 15:14 UTC | 1h 10m |
| 2026-06-22 | IRB9746 | - | Jun 22, 11:00 UTC | Jun 22, 12:25 UTC | 1h 25m |
| 2026-06-21 | IRB9708 | - | Jun 21, 11:24 UTC | Jun 21, 12:35 UTC | 1h 10m |
| 2026-06-21 | IRB9709 | - | Jun 21, 08:15 UTC | Jun 21, 09:44 UTC | 1h 30m |
| 2026-06-20 | IRB9709 | - | Jun 20, 11:05 UTC | Jun 21, 09:44 UTC | 22h 40m |
| 2026-06-20 | IRB9709 | - | Jun 20, 07:39 UTC | Jun 20, 09:14 UTC | 1h 35m |
| 2026-06-19 | IRB9709 | - | Jun 19, 12:49 UTC | Jun 20, 09:14 UTC | 20h 25m |
| 2026-06-19 | IRB9708 | - | Jun 19, 11:54 UTC | Jun 19, 13:04 UTC | 1h 10m |
| 2026-06-19 | IRB9709 | - | Jun 19, 08:29 UTC | Jun 19, 09:59 UTC | 1h 30m |
| 2026-06-18 | IRB9709 | - | Jun 18, 12:50 UTC | Jun 19, 09:59 UTC | 21h 9m |
| 2026-06-18 | IRB9709 | - | Jun 18, 11:50 UTC | Jun 19, 09:59 UTC | 22h 9m |
| 2026-06-18 | IRB9746 | - | Jun 18, 08:40 UTC | Jun 18, 10:10 UTC | 1h 30m |
| 2026-06-17 | IRB9746 | - | Jun 17, 12:50 UTC | Jun 18, 10:10 UTC | 21h 20m |
| 2026-06-17 | IRB9746 | - | Jun 17, 11:50 UTC | Jun 18, 10:10 UTC | 22h 20m |
| 2026-06-17 | IRB9709 | - | Jun 17, 08:50 UTC | Jun 17, 10:15 UTC | 1h 25m |
| 2026-06-15 | IRB9747 | - | Jun 15, 11:45 UTC | Jun 15, 12:55 UTC | 1h 10m |
| 2026-06-15 | IRB9746 | - | Jun 15, 08:29 UTC | Jun 15, 09:49 UTC | 1h 20m |
| 2026-06-14 | IRB9746 | - | Jun 14, 11:20 UTC | Jun 15, 09:49 UTC | 22h 29m |
| 2026-06-14 | IRB9709 | - | Jun 14, 08:15 UTC | Jun 14, 09:40 UTC | 1h 25m |
| 2026-06-13 | IRB9709 | - | Jun 13, 12:50 UTC | Jun 14, 09:40 UTC | 20h 50m |
| 2026-06-13 | IRB9709 | - | Jun 13, 11:40 UTC | Jun 14, 09:40 UTC | 22h 0m |
| 2026-06-13 | IRB9709 | - | Jun 13, 08:10 UTC | Jun 13, 09:50 UTC | 1h 40m |
| 2026-06-12 | IRB9709 | - | Jun 12, 13:00 UTC | Jun 13, 09:50 UTC | 20h 49m |
| 2026-06-12 | IRB9709 | - | Jun 12, 12:05 UTC | Jun 13, 09:50 UTC | 21h 44m |
| 2026-06-12 | IRB9709 | - | Jun 12, 08:55 UTC | Jun 12, 10:20 UTC | 1h 25m |
| 2026-06-11 | IRB9709 | - | Jun 11, 11:50 UTC | Jun 12, 10:20 UTC | 22h 31m |
| 2026-06-11 | IRB9746 | - | Jun 11, 09:05 UTC | Jun 11, 10:25 UTC | 1h 20m |
| 2026-06-04 | IRB9747 | - | Jun 4, 10:20 UTC | Jun 4, 11:35 UTC | 1h 15m |
| 2026-06-04 | IRB9746 | - | Jun 4, 07:30 UTC | Jun 4, 08:45 UTC | 1h 15m |
| 2026-06-02 | IRB9747 | - | Jun 2, 10:30 UTC | Jun 2, 11:40 UTC | 1h 10m |
| 2026-06-02 | IRB9746 | - | Jun 2, 07:25 UTC | Jun 2, 09:00 UTC | 1h 35m |
| 2026-06-01 | IRB9746 | - | Jun 1, 10:50 UTC | Jun 2, 09:00 UTC | 22h 10m |
| 2026-06-01 | IRB9746 | - | Jun 1, 10:35 UTC | Jun 2, 08:45 UTC | 22h 10m |
| 2026-06-01 | IRB9746 | - | Jun 1, 07:35 UTC | Jun 1, 09:15 UTC | 1h 40m |
| 2026-05-30 | IRB9747 | - | May 30, 11:55 UTC | May 30, 13:05 UTC | 1h 10m |
| 2026-05-30 | IRB9746 | - | May 30, 08:55 UTC | May 30, 10:20 UTC | 1h 25m |
| 2026-05-29 | IRB9746 | - | May 29, 10:50 UTC | May 30, 10:20 UTC | 23h 30m |
| 2026-05-29 | IRB9747 | - | May 29, 10:30 UTC | May 29, 11:30 UTC | 1h 0m |
| 2026-05-29 | IRB9746 | - | May 29, 07:30 UTC | May 29, 09:10 UTC | 1h 40m |
| 2026-05-28 | IRB9746 | - | May 28, 10:50 UTC | May 29, 09:10 UTC | 22h 20m |
| 2026-05-28 | IRB9747 | - | May 28, 10:20 UTC | May 29, 08:45 UTC | 22h 25m |
| 2026-05-28 | IRB9746 | - | May 28, 07:25 UTC | May 28, 08:50 UTC | 1h 25m |
| 2026-05-25 | IRB9746 | - | May 25, 07:35 UTC | May 25, 07:55 UTC | 20m |
| 2026-05-22 | IRB9747 | - | May 22, 10:30 UTC | May 22, 10:45 UTC | 15m |
| 2026-05-22 | IRB9746 | - | May 22, 08:40 UTC | May 22, 08:50 UTC | 10m |
| 2026-05-22 | IRB9746 | - | May 22, 07:30 UTC | May 22, 07:55 UTC | 25m |
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-MDS page for operator, model, and routing details .