sensors Mode-S transponder
738100
ICAO 24-bit transponder address · allocated to Israel
Currently assigned to 4X-ERA · BOEING 787-8 Dreamliner
- Hex
- 738100
- Octal
- 34700400
- Decimal
- 7,569,664
- Country
- IL
- Tail
- 4X-ERA
- Type
- B788
- Flights observed
- 120
- Distinct callsigns
- 20
- Country
- IL
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address 738100 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 |
|---|---|---|---|
| ELY015 | - | 11 | 2026-06-23 |
| ELY082 | - | 10 | 2026-06-30 |
| ELY016 | - | 10 | 2026-06-24 |
| ELY083 | - | 8 | 2026-06-30 |
| ELY017 | El Al Israel Airlines | 7 | 2026-07-16 |
| ELY122 | - | 5 | 2026-07-12 |
| ELY121 | - | 5 | 2026-07-02 |
| ELY318 | - | 4 | 2026-07-15 |
| ELY317 | - | 4 | 2026-07-15 |
| ELY118 | El Al Israel Airlines | 4 | 2026-06-21 |
| ELY086 | - | 4 | 2026-06-27 |
| ELY085 | - | 4 | 2026-06-26 |
| ELY084 | - | 4 | 2026-06-29 |
| ELY018 | - | 4 | 2026-07-13 |
| ELY416 | El Al Israel Airlines | 3 | 2026-04-17 |
| ELY328 | El Al Israel Airlines | 3 | 2026-06-02 |
| ELY327 | El Al Israel Airlines | 3 | 2026-06-02 |
| ELY081 | - | 3 | 2026-06-28 |
| ELY004 | - | 3 | 2026-07-08 |
| ELY003 | - | 3 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | ELY017 | TLV → MIA | Jul 16, 22:30 UTC | Jul 17, 11:15 UTC | 12h 45m |
| 2026-07-15 | ELY318 | - | Jul 15, 21:50 UTC | Jul 16, 01:45 UTC | 3h 55m |
| 2026-07-15 | ELY317 | TLV → LHR | Jul 15, 14:20 UTC | Jul 15, 19:00 UTC | 4h 40m |
| 2026-07-15 | ELY026 | EWR → TLV | Jul 15, 01:20 UTC | Jul 15, 11:20 UTC | 10h 0m |
| 2026-07-14 | ELY023 | TLV → EWR | Jul 14, 10:30 UTC | Jul 14, 21:35 UTC | 11h 5m |
| 2026-07-13 | ELY018 | - | Jul 13, 16:25 UTC | Jul 14, 03:50 UTC | 11h 25m |
| 2026-07-12 | ELY017 | - | Jul 12, 21:55 UTC | Jul 13, 10:25 UTC | 12h 30m |
| 2026-07-12 | ELY122 | - | Jul 12, 06:35 UTC | Jul 12, 18:10 UTC | 11h 35m |
| 2026-07-09 | ELY1017 | - | Jul 9, 22:35 UTC | Jul 10, 11:15 UTC | 12h 40m |
| 2026-07-08 | ELY004 | JFK → TLV | Jul 8, 14:45 UTC | Jul 9, 00:45 UTC | 10h 0m |
| 2026-07-07 | ELY003 | TLV → JFK | Jul 7, 21:45 UTC | Jul 8, 08:35 UTC | 10h 50m |
| 2026-07-06 | ELY018 | - | Jul 6, 16:30 UTC | Jul 7, 03:40 UTC | 11h 10m |
| 2026-07-05 | ELY017 | - | Jul 5, 21:30 UTC | Jul 6, 09:55 UTC | 12h 25m |
| 2026-07-05 | ELY122 | MIA → TLV | Jul 5, 06:10 UTC | Jul 5, 17:35 UTC | 11h 25m |
| 2026-07-02 | ELY121 | TLV → MIA | Jul 2, 21:55 UTC | Jul 3, 10:10 UTC | 12h 15m |
| 2026-07-01 | ELY318 | - | Jul 1, 22:10 UTC | Jul 2, 02:20 UTC | 4h 10m |
| 2026-07-01 | ELY317 | TLV → LHR | Jul 1, 16:05 UTC | Jul 1, 20:30 UTC | 4h 25m |
| 2026-06-30 | ELY082 | - | Jun 30, 19:35 UTC | Jul 1, 02:40 UTC | 7h 5m |
| 2026-06-30 | ELY082 | - | Jun 30, 17:05 UTC | Jun 30, 17:20 UTC | 15m |
| 2026-06-30 | ELY083 | - | Jun 30, 08:55 UTC | Jun 30, 09:15 UTC | 20m |
| 2026-06-30 | ELY083 | - | Jun 30, 05:50 UTC | Jun 30, 06:10 UTC | 20m |
| 2026-06-29 | ELY083 | - | Jun 29, 22:10 UTC | Jun 29, 22:30 UTC | 20m |
| 2026-06-29 | ELY084 | - | Jun 29, 11:50 UTC | Jun 29, 19:15 UTC | 7h 25m |
| 2026-06-29 | ELY084 | - | Jun 29, 09:20 UTC | Jun 29, 10:34 UTC | 1h 15m |
| 2026-06-28 | ELY081 | TLV → BKK | Jun 28, 19:40 UTC | Jun 29, 07:05 UTC | 11h 25m |
| 2026-06-27 | ELY086 | - | Jun 27, 18:24 UTC | Jun 28, 01:40 UTC | 7h 15m |
| 2026-06-27 | ELY086 | - | Jun 27, 15:55 UTC | Jun 27, 16:14 UTC | 20m |
| 2026-06-26 | ELY085 | - | Jun 26, 04:45 UTC | Jun 26, 08:15 UTC | 3h 30m |
| 2026-06-25 | ELY085 | - | Jun 25, 21:20 UTC | Jun 25, 21:40 UTC | 20m |
| 2026-06-24 | ELY016 | BOS → TLV | Jun 24, 17:40 UTC | Jun 25, 03:04 UTC | 9h 25m |
| 2026-06-23 | ELY015 | TLV → BOS | Jun 23, 22:40 UTC | Jun 24, 09:39 UTC | 11h 0m |
| 2026-06-22 | ELY018 | - | Jun 22, 16:10 UTC | Jun 23, 03:25 UTC | 11h 15m |
| 2026-06-21 | ELY017 | - | Jun 21, 21:29 UTC | Jun 22, 10:25 UTC | 12h 55m |
| 2026-06-21 | ELY118 | MIA → TLV | Jun 21, 04:24 UTC | Jun 21, 15:40 UTC | 11h 15m |
| 2026-06-18 | ELY017 | TLV → MIA | Jun 18, 22:55 UTC | Jun 19, 11:39 UTC | 12h 44m |
| 2026-06-17 | ELY004 | JFK → TLV | Jun 17, 16:15 UTC | Jun 18, 02:10 UTC | 9h 55m |
| 2026-06-16 | ELY003 | TLV → JFK | Jun 16, 21:30 UTC | Jun 17, 08:25 UTC | 10h 55m |
| 2026-06-16 | ELY324 | CDG → TLV | Jun 16, 14:00 UTC | Jun 16, 17:59 UTC | 4h 0m |
| 2026-06-16 | ELY323 | TLV → CDG | Jun 16, 07:09 UTC | Jun 16, 11:40 UTC | 4h 30m |
| 2026-06-15 | ELY018 | MIA → TLV | Jun 15, 16:15 UTC | Jun 16, 03:35 UTC | 11h 20m |
| 2026-06-14 | ELY017 | TLV → MIA | Jun 14, 21:40 UTC | Jun 15, 10:20 UTC | 12h 40m |
| 2026-06-14 | ELY122 | MIA → TLV | Jun 14, 06:25 UTC | Jun 14, 17:45 UTC | 11h 20m |
| 2026-06-11 | ELY121 | TLV → MIA | Jun 11, 21:25 UTC | Jun 12, 09:55 UTC | 12h 31m |
| 2026-06-10 | ELY318 | LHR → TLV | Jun 10, 21:40 UTC | Jun 11, 01:50 UTC | 4h 10m |
| 2026-06-10 | ELY317 | TLV → LHR | Jun 10, 14:40 UTC | Jun 10, 19:40 UTC | 5h 0m |
| 2026-06-09 | ELY116 | BOS → TLV | Jun 9, 17:50 UTC | Jun 10, 03:20 UTC | 9h 30m |
| 2026-06-09 | ELY115 | TLV → BOS | Jun 9, 02:45 UTC | Jun 9, 13:05 UTC | 10h 20m |
| 2026-06-07 | ELY122 | MIA → TLV | Jun 7, 06:30 UTC | Jun 7, 17:45 UTC | 11h 15m |
| 2026-06-04 | ELY121 | TLV → MIA | Jun 4, 21:35 UTC | Jun 5, 10:20 UTC | 12h 45m |
| 2026-06-03 | ELY016 | BOS → TLV | Jun 3, 18:00 UTC | Jun 4, 03:05 UTC | 9h 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-ERA page for operator, model, and routing details .