sensors Mode-S transponder
344305
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-LUK · AIRBUS A-330-300
- Hex
- 344305
- Octal
- 15041405
- Decimal
- 3,425,029
- Country
- ES
- Tail
- EC-LUK
- Type
- A333
- Flights observed
- 159
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 344305 falls within the block assigned to Spain (ES) by ICAO Annex 10, Volume III. Every aircraft registered in Spain 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 |
|---|---|---|---|
| IBE03SY | - | 17 | 2026-07-03 |
| IBE03CY | - | 15 | 2026-07-04 |
| IBE0212 | - | 9 | 2026-07-13 |
| IBE03LF | Iberia Airlines | 8 | 2026-07-01 |
| IBE02DA | - | 8 | 2026-07-13 |
| IBE3272 | - | 7 | 2026-06-30 |
| IBE3271 | - | 7 | 2026-06-29 |
| IBE03TM | Iberia Airlines | 7 | 2026-07-07 |
| IBE03TH | - | 7 | 2026-07-07 |
| IBE0267 | Iberia Airlines | 7 | 2026-05-14 |
| IBE3268 | - | 6 | 2026-06-21 |
| IBE03HT | - | 6 | 2026-07-01 |
| IBE0268 | Iberia Airlines | 6 | 2026-05-15 |
| IBE3267 | - | 5 | 2026-06-19 |
| IBE02CR | Iberia Airlines | 5 | 2026-06-14 |
| IBE03LW | Iberia Airlines | 3 | 2026-05-19 |
| IBE03GR | Iberia Airlines | 3 | 2026-05-18 |
| IBE03AE | Iberia Airlines | 3 | 2026-06-07 |
| IBE02SJ | Iberia Airlines | 3 | 2026-06-14 |
| IBE0272 | Iberia Airlines | 3 | 2026-05-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | IBE0212 | - | Jul 13, 21:30 UTC | Jul 13, 22:15 UTC | 45m |
| 2026-07-13 | IBE02DA | - | Jul 13, 11:10 UTC | Jul 13, 18:25 UTC | 7h 15m |
| 2026-07-09 | IBE0212 | JFK → MAD | Jul 9, 21:30 UTC | Jul 10, 04:05 UTC | 6h 35m |
| 2026-07-09 | IBE02DA | - | Jul 9, 11:05 UTC | Jul 9, 18:40 UTC | 7h 35m |
| 2026-07-07 | IBE03TH | - | Jul 7, 21:35 UTC | Jul 8, 05:45 UTC | 8h 10m |
| 2026-07-07 | IBE03TM | MIA → MAD | Jul 7, 09:55 UTC | Jul 7, 18:45 UTC | 8h 50m |
| 2026-07-06 | IBE0212 | JFK → MAD | Jul 6, 00:25 UTC | Jul 6, 06:55 UTC | 6h 30m |
| 2026-07-05 | IBE02DA | MAD → JFK | Jul 5, 11:20 UTC | Jul 5, 18:45 UTC | 7h 25m |
| 2026-07-04 | IBE0264 | - | Jul 4, 15:00 UTC | Jul 5, 09:20 UTC | 18h 20m |
| 2026-07-04 | IBE03CY | - | Jul 4, 01:40 UTC | Jul 4, 09:05 UTC | 7h 25m |
| 2026-07-03 | IBE03SY | MAD → ORD | Jul 3, 12:40 UTC | Jul 3, 21:25 UTC | 8h 45m |
| 2026-07-02 | IBE0366 | DFW → MAD | Jul 2, 06:20 UTC | Jul 2, 15:25 UTC | 9h 5m |
| 2026-07-01 | IBE03LF | SJU → MAD | Jul 1, 18:00 UTC | Jul 2, 03:45 UTC | 9h 45m |
| 2026-07-01 | IBE03HT | DFW → MAD | Jul 1, 03:25 UTC | Jul 1, 12:35 UTC | 9h 10m |
| 2026-06-30 | IBE03LF | SJU → MAD | Jun 30, 22:00 UTC | Jul 1, 00:35 UTC | 2h 35m |
| 2026-06-30 | IBE03LF | SJU → MAD | Jun 30, 14:40 UTC | Jun 30, 21:55 UTC | 7h 15m |
| 2026-06-30 | IBE3272 | - | Jun 30, 00:00 UTC | Jun 30, 09:50 UTC | 9h 51m |
| 2026-06-29 | IBE3271 | - | Jun 29, 11:39 UTC | Jun 29, 21:54 UTC | 10h 15m |
| 2026-06-28 | IBE0212 | - | Jun 28, 21:55 UTC | Jun 29, 04:04 UTC | 6h 10m |
| 2026-06-28 | IBE02DA | MAD → JFK | Jun 28, 11:00 UTC | Jun 28, 18:55 UTC | 7h 55m |
| 2026-06-27 | IBE3272 | - | Jun 27, 22:49 UTC | Jun 28, 08:50 UTC | 10h 0m |
| 2026-06-27 | IBE3271 | - | Jun 27, 10:14 UTC | Jun 27, 20:14 UTC | 10h 0m |
| 2026-06-26 | IBE03TH | - | Jun 26, 21:15 UTC | Jun 27, 05:19 UTC | 8h 5m |
| 2026-06-26 | IBE03TM | MIA → MAD | Jun 26, 10:05 UTC | Jun 26, 18:49 UTC | 8h 45m |
| 2026-06-25 | IBE0212 | - | Jun 25, 21:50 UTC | Jun 26, 04:10 UTC | 6h 20m |
| 2026-06-25 | IBE02DA | MAD → JFK | Jun 25, 11:15 UTC | Jun 25, 18:45 UTC | 7h 30m |
| 2026-06-24 | IBE3272 | - | Jun 24, 22:39 UTC | Jun 25, 08:50 UTC | 10h 10m |
| 2026-06-24 | IBE3271 | - | Jun 24, 10:10 UTC | Jun 24, 20:30 UTC | 10h 20m |
| 2026-06-23 | IBE03CY | ORD → MAD | Jun 23, 23:05 UTC | Jun 24, 06:35 UTC | 7h 30m |
| 2026-06-23 | IBE03SY | MAD → ORD | Jun 23, 11:04 UTC | Jun 23, 19:44 UTC | 8h 40m |
| 2026-06-21 | IBE3268 | - | Jun 21, 02:35 UTC | Jun 21, 03:30 UTC | 55m |
| 2026-06-20 | IBE3268 | - | Jun 20, 17:29 UTC | Jun 21, 02:30 UTC | 9h 0m |
| 2026-06-19 | IBE3267 | - | Jun 19, 22:19 UTC | Jun 20, 08:14 UTC | 9h 55m |
| 2026-06-19 | IBE03HT | DFW → MAD | Jun 19, 03:24 UTC | Jun 19, 12:14 UTC | 8h 50m |
| 2026-06-18 | IBE03LF | SJU → MAD | Jun 18, 14:30 UTC | Jun 19, 00:49 UTC | 10h 19m |
| 2026-06-17 | IBE3272 | MAD → HAM | Jun 17, 22:35 UTC | Jun 18, 08:10 UTC | 9h 35m |
| 2026-06-17 | IBE3271 | HAM → MAD | Jun 17, 10:15 UTC | Jun 17, 20:40 UTC | 10h 25m |
| 2026-06-17 | IBE03CY | - | Jun 17, 00:05 UTC | Jun 17, 07:45 UTC | 7h 40m |
| 2026-06-16 | IBE03SY | MAD → ORD | Jun 16, 10:20 UTC | Jun 16, 19:05 UTC | 8h 45m |
| 2026-06-15 | IBE0212 | - | Jun 15, 21:25 UTC | Jun 16, 03:55 UTC | 6h 30m |
| 2026-06-15 | IBE02DA | MAD → JFK | Jun 15, 11:24 UTC | Jun 15, 19:14 UTC | 7h 50m |
| 2026-06-14 | IBE02CR | SJO → MAD | Jun 14, 20:00 UTC | Jun 15, 09:05 UTC | 13h 4m |
| 2026-06-14 | IBE02CR | SJO → MAD | Jun 14, 11:20 UTC | Jun 15, 09:05 UTC | 21h 44m |
| 2026-06-14 | IBE02SJ | MAD → SJO | Jun 14, 10:20 UTC | Jun 15, 09:05 UTC | 22h 44m |
| 2026-06-13 | IBE3268 | MAD → HAM | Jun 13, 17:30 UTC | Jun 14, 03:15 UTC | 9h 45m |
| 2026-06-12 | IBE3267 | HAM → MAD | Jun 12, 23:40 UTC | Jun 13, 10:30 UTC | 10h 49m |
| 2026-06-12 | IBE07GF | LHR → MAD | Jun 12, 19:45 UTC | Jun 12, 21:40 UTC | 1h 55m |
| 2026-06-12 | IBE07MM | MAD → MAD | Jun 12, 16:25 UTC | Jun 12, 18:15 UTC | 1h 50m |
| 2026-06-11 | IBE3272 | MAD → HAM | Jun 11, 23:15 UTC | Jun 12, 09:00 UTC | 9h 46m |
| 2026-06-11 | IBE3271 | HAM → MAD | Jun 11, 10:50 UTC | Jun 11, 21:05 UTC | 10h 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 EC-LUK page for operator, model, and routing details .