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