sensors Mode-S transponder
738074
ICAO 24-bit transponder address · allocated to Israel
Currently assigned to 4X-ECD · BOEING 777-200
- Hex
- 738074
- Octal
- 34700164
- Decimal
- 7,569,524
- Country
- IL
- Tail
- 4X-ECD
- Type
- B772
- Flights observed
- 129
- Distinct callsigns
- 20
- Country
- IL
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 738074 falls within the block assigned to Israel (IL) by ICAO Annex 10, Volume III. Every aircraft registered in Israel 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 |
|---|---|---|---|
| ELY082 | - | 30 | 2026-07-16 |
| ELY083 | - | 20 | 2026-07-16 |
| ELY325 | El Al Israel Airlines | 10 | 2026-07-26 |
| ELY338 | - | 8 | 2026-07-14 |
| ELY337 | - | 8 | 2026-07-14 |
| ELY326 | - | 8 | 2026-07-09 |
| ELY080 | El Al Israel Airlines | 7 | 2026-07-19 |
| ELY085 | El Al Israel Airlines | 6 | 2026-07-18 |
| ELY087 | - | 3 | 2026-07-15 |
| ELY574 | El Al Israel Airlines | 2 | 2026-07-24 |
| ELY573 | El Al Israel Airlines | 2 | 2026-07-24 |
| ELY084 | - | 2 | 2026-06-22 |
| ELY611 | El Al Israel Airlines | 1 | 2026-04-30 |
| ELY5132 | El Al Israel Airlines | 1 | 2026-05-28 |
| ELY5131 | El Al Israel Airlines | 1 | 2026-05-28 |
| ELY328 | El Al Israel Airlines | 1 | 2026-06-15 |
| ELY327 | El Al Israel Airlines | 1 | 2026-06-15 |
| ELY324 | - | 1 | 2026-06-21 |
| ELY323 | - | 1 | 2026-06-21 |
| ELY320 | - | 1 | 2026-07-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | ELY325 | TLV → CDG | Jul 26, 14:25 UTC | Jul 26, 18:45 UTC | 4h 20m |
| 2026-07-24 | ELY574 | OTP → TLV | Jul 24, 08:45 UTC | Jul 24, 11:00 UTC | 2h 15m |
| 2026-07-24 | ELY573 | TLV → OTP | Jul 24, 04:20 UTC | Jul 24, 06:30 UTC | 2h 10m |
| 2026-07-23 | ELY2368 | BUD → TLV | Jul 23, 22:10 UTC | Jul 24, 00:45 UTC | 2h 35m |
| 2026-07-23 | ELY2367 | TLV → BUD | Jul 23, 16:55 UTC | Jul 23, 19:50 UTC | 2h 55m |
| 2026-07-22 | ELY320 | - | Jul 22, 11:40 UTC | Jul 22, 15:35 UTC | 3h 55m |
| 2026-07-22 | ELY319 | - | Jul 22, 04:15 UTC | Jul 22, 05:25 UTC | 1h 10m |
| 2026-07-19 | ELY080 | BKK → TLV | Jul 19, 16:00 UTC | Jul 19, 23:30 UTC | 7h 30m |
| 2026-07-19 | ELY080 | BKK → TLV | Jul 19, 13:25 UTC | Jul 19, 14:50 UTC | 1h 25m |
| 2026-07-18 | ELY085 | TLV → BKK | Jul 18, 21:20 UTC | Jul 19, 08:25 UTC | 11h 5m |
| 2026-07-16 | ELY082 | - | Jul 16, 20:00 UTC | Jul 17, 03:34 UTC | 7h 35m |
| 2026-07-16 | ELY082 | - | Jul 16, 17:20 UTC | Jul 16, 17:40 UTC | 20m |
| 2026-07-16 | ELY083 | - | Jul 16, 09:15 UTC | Jul 16, 09:40 UTC | 25m |
| 2026-07-15 | ELY083 | - | Jul 15, 22:30 UTC | Jul 16, 06:30 UTC | 8h 0m |
| 2026-07-15 | ELY087 | - | Jul 15, 02:10 UTC | Jul 15, 19:20 UTC | 17h 10m |
| 2026-07-14 | ELY087 | - | Jul 14, 19:10 UTC | Jul 15, 19:00 UTC | 23h 49m |
| 2026-07-14 | ELY338 | AMS → TLV | Jul 14, 10:55 UTC | Jul 14, 14:50 UTC | 3h 55m |
| 2026-07-14 | ELY337 | TLV → AMS | Jul 14, 04:15 UTC | Jul 14, 08:40 UTC | 4h 25m |
| 2026-07-13 | ELY338 | AMS → TLV | Jul 13, 10:40 UTC | Jul 13, 14:35 UTC | 3h 55m |
| 2026-07-13 | ELY337 | TLV → AMS | Jul 13, 04:15 UTC | Jul 13, 08:40 UTC | 4h 25m |
| 2026-07-12 | ELY080 | - | Jul 12, 16:01 UTC | Jul 12, 23:40 UTC | 7h 40m |
| 2026-07-12 | ELY080 | - | Jul 12, 13:25 UTC | Jul 12, 14:45 UTC | 1h 20m |
| 2026-07-11 | ELY085 | - | Jul 11, 21:25 UTC | Jul 12, 08:40 UTC | 11h 15m |
| 2026-07-09 | ELY326 | - | Jul 9, 21:15 UTC | Jul 10, 01:05 UTC | 3h 50m |
| 2026-07-09 | ELY325 | TLV → CDG | Jul 9, 14:45 UTC | Jul 9, 19:05 UTC | 4h 20m |
| 2026-07-08 | ELY082 | - | Jul 8, 20:00 UTC | Jul 9, 03:30 UTC | 7h 30m |
| 2026-07-08 | ELY082 | - | Jul 8, 17:30 UTC | Jul 8, 17:45 UTC | 15m |
| 2026-07-07 | ELY083 | TLV → BKK | Jul 7, 22:25 UTC | Jul 8, 09:40 UTC | 11h 15m |
| 2026-07-07 | ELY574 | - | Jul 7, 09:00 UTC | Jul 7, 11:05 UTC | 2h 5m |
| 2026-07-07 | ELY573 | - | Jul 7, 03:45 UTC | Jul 7, 05:55 UTC | 2h 10m |
| 2026-07-06 | ELY338 | AMS → TLV | Jul 6, 11:20 UTC | Jul 6, 15:15 UTC | 3h 55m |
| 2026-07-06 | ELY337 | - | Jul 6, 04:20 UTC | Jul 6, 08:45 UTC | 4h 25m |
| 2026-07-05 | ELY080 | - | Jul 5, 13:25 UTC | Jul 5, 23:20 UTC | 9h 55m |
| 2026-07-04 | ELY085 | - | Jul 4, 21:35 UTC | Jul 5, 08:30 UTC | 10h 55m |
| 2026-07-02 | ELY326 | - | Jul 2, 21:35 UTC | Jul 3, 01:20 UTC | 3h 45m |
| 2026-07-02 | ELY325 | - | Jul 2, 14:20 UTC | Jul 2, 18:40 UTC | 4h 20m |
| 2026-07-01 | ELY082 | - | Jul 1, 20:15 UTC | Jul 2, 03:35 UTC | 7h 20m |
| 2026-07-01 | ELY082 | - | Jul 1, 17:45 UTC | Jul 1, 17:55 UTC | 10m |
| 2026-06-30 | ELY083 | - | Jun 30, 22:10 UTC | Jul 1, 09:25 UTC | 11h 15m |
| 2026-06-28 | ELY080 | - | Jun 28, 13:49 UTC | Jun 28, 23:50 UTC | 10h 0m |
| 2026-06-28 | ELY085 | - | Jun 28, 08:19 UTC | Jun 28, 08:39 UTC | 20m |
| 2026-06-27 | ELY085 | - | Jun 27, 21:25 UTC | Jun 28, 05:24 UTC | 8h 0m |
| 2026-06-25 | ELY326 | - | Jun 25, 21:40 UTC | Jun 26, 01:34 UTC | 3h 55m |
| 2026-06-25 | ELY325 | - | Jun 25, 14:44 UTC | Jun 25, 18:55 UTC | 4h 10m |
| 2026-06-24 | ELY082 | - | Jun 24, 17:25 UTC | Jun 25, 03:29 UTC | 10h 5m |
| 2026-06-24 | ELY083 | - | Jun 24, 08:49 UTC | Jun 24, 09:15 UTC | 25m |
| 2026-06-24 | ELY083 | - | Jun 24, 05:49 UTC | Jun 24, 06:15 UTC | 25m |
| 2026-06-23 | ELY083 | - | Jun 23, 22:19 UTC | Jun 23, 22:40 UTC | 20m |
| 2026-06-22 | ELY084 | - | Jun 22, 20:10 UTC | Jun 22, 20:39 UTC | 30m |
| 2026-06-22 | ELY084 | - | Jun 22, 10:34 UTC | Jun 22, 13:39 UTC | 3h 5m |
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 4X-ECD page for operator, model, and routing details .