sensors Mode-S transponder
7380C1
ICAO 24-bit transponder address · allocated to Israel
Currently assigned to 4X-EDB · BOEING 787-9 Dreamliner
- Hex
- 7380C1
- Octal
- 34700301
- Decimal
- 7,569,601
- Country
- IL
- Tail
- 4X-EDB
- Type
- B789
- Flights observed
- 156
- Distinct callsigns
- 20
- Country
- IL
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address 7380C1 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 |
|---|---|---|---|
| ELY1009 | El Al Israel Airlines | 11 | 2026-04-15 |
| ELY315 | - | 10 | 2026-07-01 |
| ELY316 | - | 9 | 2026-07-01 |
| ELY1014 | El Al Israel Airlines | 8 | 2026-04-16 |
| ELY018 | - | 8 | 2026-06-30 |
| ELY318 | - | 6 | 2026-07-12 |
| ELY317 | - | 6 | 2026-07-12 |
| ELY1010 | El Al Israel Airlines | 5 | 2026-04-15 |
| ELY028 | - | 5 | 2026-07-07 |
| ELY027 | - | 5 | 2026-07-06 |
| ELY026 | - | 5 | 2026-07-14 |
| ELY017 | - | 5 | 2026-06-29 |
| ELY1011 | El Al Israel Airlines | 4 | 2026-04-21 |
| ELY006 | - | 4 | 2026-07-02 |
| ELY005 | - | 4 | 2026-07-01 |
| ELY323 | El Al Israel Airlines | 3 | 2026-05-21 |
| ELY106 | - | 3 | 2026-07-09 |
| ELY105 | - | 3 | 2026-07-08 |
| ELY025 | - | 3 | 2026-06-27 |
| ELY023 | - | 3 | 2026-07-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | ELY026 | - | Jul 14, 01:15 UTC | Jul 14, 06:15 UTC | 5h 0m |
| 2026-07-13 | ELY023 | TLV → EWR | Jul 13, 04:35 UTC | Jul 13, 15:40 UTC | 11h 5m |
| 2026-07-12 | ELY318 | - | Jul 12, 21:45 UTC | Jul 13, 01:45 UTC | 4h 0m |
| 2026-07-12 | ELY317 | TLV → LHR | Jul 12, 14:30 UTC | Jul 12, 19:10 UTC | 4h 40m |
| 2026-07-11 | ELY088 | - | Jul 11, 18:00 UTC | Jul 12, 01:20 UTC | 7h 20m |
| 2026-07-10 | ELY087 | - | Jul 10, 02:55 UTC | Jul 10, 07:00 UTC | 4h 5m |
| 2026-07-09 | ELY087 | - | Jul 9, 20:20 UTC | Jul 9, 20:40 UTC | 20m |
| 2026-07-09 | ELY106 | - | Jul 9, 03:30 UTC | Jul 9, 16:55 UTC | 13h 25m |
| 2026-07-08 | ELY105 | TLV → LAX | Jul 8, 08:00 UTC | Jul 8, 22:25 UTC | 14h 25m |
| 2026-07-07 | ELY028 | EWR → TLV | Jul 7, 18:20 UTC | Jul 8, 04:05 UTC | 9h 45m |
| 2026-07-06 | ELY027 | TLV → EWR | Jul 6, 21:50 UTC | Jul 7, 08:50 UTC | 11h 0m |
| 2026-07-06 | ELY012 | JFK → TLV | Jul 6, 08:20 UTC | Jul 6, 18:00 UTC | 9h 40m |
| 2026-07-05 | ELY011 | TLV → JFK | Jul 5, 17:05 UTC | Jul 6, 04:50 UTC | 11h 45m |
| 2026-07-02 | ELY006 | - | Jul 2, 21:15 UTC | Jul 3, 09:55 UTC | 12h 40m |
| 2026-07-01 | ELY005 | TLV → LAX | Jul 1, 22:25 UTC | Jul 2, 12:40 UTC | 14h 15m |
| 2026-07-01 | ELY316 | - | Jul 1, 14:45 UTC | Jul 1, 19:05 UTC | 4h 20m |
| 2026-07-01 | ELY315 | TLV → LHR | Jul 1, 07:40 UTC | Jul 1, 12:00 UTC | 4h 20m |
| 2026-06-30 | ELY018 | - | Jun 30, 16:15 UTC | Jul 1, 03:25 UTC | 11h 10m |
| 2026-06-29 | ELY017 | TLV → MIA | Jun 29, 21:44 UTC | Jun 30, 10:00 UTC | 12h 16m |
| 2026-06-29 | ELY316 | - | Jun 29, 15:04 UTC | Jun 29, 19:20 UTC | 4h 15m |
| 2026-06-29 | ELY315 | TLV → LHR | Jun 29, 07:34 UTC | Jun 29, 11:55 UTC | 4h 20m |
| 2026-06-28 | ELY028 | EWR → TLV | Jun 28, 17:39 UTC | Jun 29, 03:29 UTC | 9h 50m |
| 2026-06-27 | ELY025 | - | Jun 27, 22:40 UTC | Jun 28, 09:30 UTC | 10h 50m |
| 2026-06-25 | ELY318 | - | Jun 25, 22:14 UTC | Jun 26, 02:30 UTC | 4h 15m |
| 2026-06-25 | ELY317 | - | Jun 25, 14:50 UTC | Jun 25, 19:09 UTC | 4h 20m |
| 2026-06-25 | ELY026 | EWR → TLV | Jun 25, 01:54 UTC | Jun 25, 11:39 UTC | 9h 45m |
| 2026-06-23 | ELY027 | TLV → EWR | Jun 23, 21:54 UTC | Jun 24, 09:15 UTC | 11h 20m |
| 2026-06-23 | ELY106 | - | Jun 23, 03:54 UTC | Jun 23, 17:30 UTC | 13h 35m |
| 2026-06-22 | ELY105 | TLV → LAX | Jun 22, 07:04 UTC | Jun 22, 21:14 UTC | 14h 10m |
| 2026-06-21 | ELY082 | - | Jun 21, 19:50 UTC | Jun 22, 03:10 UTC | 7h 20m |
| 2026-06-21 | ELY082 | - | Jun 21, 17:15 UTC | Jun 21, 17:35 UTC | 20m |
| 2026-06-21 | ELY083 | - | Jun 21, 06:04 UTC | Jun 21, 09:35 UTC | 3h 30m |
| 2026-06-20 | ELY083 | - | Jun 20, 22:25 UTC | Jun 20, 22:50 UTC | 25m |
| 2026-06-19 | ELY320 | - | Jun 19, 10:24 UTC | Jun 19, 14:24 UTC | 4h 0m |
| 2026-06-19 | ELY319 | - | Jun 19, 03:20 UTC | Jun 19, 07:29 UTC | 4h 10m |
| 2026-06-18 | ELY004 | JFK → TLV | Jun 18, 15:20 UTC | Jun 19, 01:04 UTC | 9h 44m |
| 2026-06-17 | ELY001 | TLV → JFK | Jun 17, 22:15 UTC | Jun 18, 09:05 UTC | 10h 50m |
| 2026-06-17 | ELY316 | LHR → TLV | Jun 17, 14:50 UTC | Jun 17, 18:50 UTC | 4h 0m |
| 2026-06-17 | ELY315 | TLV → LHR | Jun 17, 07:25 UTC | Jun 17, 12:00 UTC | 4h 35m |
| 2026-06-16 | ELY028 | EWR → TLV | Jun 16, 17:49 UTC | Jun 17, 03:35 UTC | 9h 46m |
| 2026-06-15 | ELY027 | TLV → EWR | Jun 15, 21:50 UTC | Jun 16, 09:10 UTC | 11h 20m |
| 2026-06-14 | ELY006 | - | Jun 14, 21:35 UTC | Jun 15, 10:55 UTC | 13h 20m |
| 2026-06-13 | ELY005 | - | Jun 13, 22:40 UTC | Jun 14, 12:45 UTC | 14h 5m |
| 2026-06-12 | ELY026 | EWR → TLV | Jun 12, 01:35 UTC | Jun 12, 11:10 UTC | 9h 35m |
| 2026-06-11 | ELY023 | TLV → EWR | Jun 11, 10:50 UTC | Jun 11, 21:45 UTC | 10h 55m |
| 2026-06-10 | ELY002 | JFK → TLV | Jun 10, 22:30 UTC | Jun 11, 08:10 UTC | 9h 40m |
| 2026-06-10 | ELY007 | TLV → JFK | Jun 10, 07:35 UTC | Jun 10, 18:30 UTC | 10h 55m |
| 2026-06-09 | ELY318 | LHR → TLV | Jun 9, 21:35 UTC | Jun 10, 01:40 UTC | 4h 5m |
| 2026-06-09 | ELY317 | TLV → LHR | Jun 9, 14:25 UTC | Jun 9, 19:10 UTC | 4h 45m |
| 2026-06-09 | ELY026 | EWR → TLV | Jun 9, 01:55 UTC | Jun 9, 11:40 UTC | 9h 45m |
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-EDB page for operator, model, and routing details .