sensors Mode-S transponder
346206
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-NCK · AIRBUS A-330-200
- Hex
- 346206
- Octal
- 15061006
- Decimal
- 3,432,966
- Country
- ES
- Tail
- EC-NCK
- Type
- A332
- Flights observed
- 67
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 346206 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 |
|---|---|---|---|
| TAI301 | - | 9 | 2026-06-28 |
| TAI300 | - | 9 | 2026-06-29 |
| TAI523 | Avianca El Salvador | 6 | 2026-06-27 |
| TAI522 | - | 6 | 2026-06-27 |
| RAM208 | - | 5 | 2026-07-04 |
| RAM209 | - | 2 | 2026-07-05 |
| IBE0126 | Iberia Airlines | 2 | 2026-06-13 |
| IBE0124 | Iberia Airlines | 2 | 2026-06-09 |
| IBE0121 | Iberia Airlines | 2 | 2026-06-08 |
| GRL940 | Air Greenland | 2 | 2026-06-06 |
| TOM976P | TUI Airways | 1 | 2026-05-30 |
| TOM975P | TUI Airways | 1 | 2026-05-30 |
| TOM937P | TUI Airways | 1 | 2026-05-26 |
| TOM6JE | TUI Airways | 1 | 2026-05-25 |
| TOM4757 | TUI Airways | 1 | 2026-05-24 |
| TOM4756 | TUI Airways | 1 | 2026-05-24 |
| TOM4685 | TUI Airways | 1 | 2026-05-23 |
| TOM4684 | TUI Airways | 1 | 2026-05-23 |
| TOM3XE | TUI Airways | 1 | 2026-05-30 |
| TOM28A | TUI Airways | 1 | 2026-05-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-05 | RAM209 | - | Jul 5, 02:50 UTC | Jul 5, 08:45 UTC | 5h 55m |
| 2026-07-04 | RAM208 | - | Jul 4, 17:05 UTC | Jul 5, 00:05 UTC | 7h 0m |
| 2026-07-04 | RAM209 | - | Jul 4, 03:05 UTC | Jul 4, 09:35 UTC | 6h 30m |
| 2026-07-03 | RAM208 | - | Jul 3, 08:55 UTC | Jul 4, 00:25 UTC | 15h 30m |
| 2026-07-03 | RAM208 | - | Jul 3, 03:35 UTC | Jul 4, 00:25 UTC | 20h 50m |
| 2026-07-03 | RAM208 | YUL → YUL | Jul 3, 03:25 UTC | Jul 4, 00:25 UTC | 21h 0m |
| 2026-07-02 | RAM208 | - | Jul 2, 17:25 UTC | Jul 3, 01:05 UTC | 7h 40m |
| 2026-07-01 | RAM8961 | - | Jul 1, 13:35 UTC | Jul 1, 14:35 UTC | 1h 0m |
| 2026-06-29 | TAI300 | - | Jun 29, 11:29 UTC | Jun 29, 21:24 UTC | 9h 55m |
| 2026-06-28 | TAI301 | - | Jun 28, 18:34 UTC | Jun 29, 04:50 UTC | 10h 15m |
| 2026-06-28 | TAI300 | - | Jun 28, 05:34 UTC | Jun 28, 15:14 UTC | 9h 40m |
| 2026-06-27 | TAI523 | LAX → SAL | Jun 27, 21:59 UTC | Jun 28, 02:20 UTC | 4h 20m |
| 2026-06-27 | TAI522 | - | Jun 27, 14:25 UTC | Jun 27, 19:00 UTC | 4h 35m |
| 2026-06-27 | TAI301 | - | Jun 27, 00:29 UTC | Jun 27, 10:50 UTC | 10h 20m |
| 2026-06-26 | TAI300 | - | Jun 26, 06:50 UTC | Jun 26, 16:20 UTC | 9h 30m |
| 2026-06-25 | TAI523 | LAX → SAL | Jun 25, 21:59 UTC | Jun 26, 02:24 UTC | 4h 25m |
| 2026-06-25 | TAI522 | - | Jun 25, 14:29 UTC | Jun 25, 18:59 UTC | 4h 30m |
| 2026-06-25 | TAI301 | - | Jun 25, 00:24 UTC | Jun 25, 10:50 UTC | 10h 25m |
| 2026-06-24 | TAI300 | - | Jun 24, 05:40 UTC | Jun 24, 15:35 UTC | 9h 55m |
| 2026-06-23 | TAI523 | LAX → SAL | Jun 23, 22:05 UTC | Jun 24, 02:24 UTC | 4h 20m |
| 2026-06-23 | TAI522 | - | Jun 23, 14:35 UTC | Jun 23, 19:15 UTC | 4h 40m |
| 2026-06-23 | TAI301 | - | Jun 23, 00:35 UTC | Jun 23, 10:39 UTC | 10h 5m |
| 2026-06-22 | TAI300 | - | Jun 22, 11:39 UTC | Jun 22, 21:30 UTC | 9h 50m |
| 2026-06-21 | TAI301 | - | Jun 21, 18:29 UTC | Jun 22, 05:04 UTC | 10h 35m |
| 2026-06-21 | TAI300 | - | Jun 21, 05:35 UTC | Jun 21, 15:05 UTC | 9h 30m |
| 2026-06-20 | TAI523 | LAX → SAL | Jun 20, 22:00 UTC | Jun 21, 02:20 UTC | 4h 20m |
| 2026-06-20 | TAI522 | - | Jun 20, 14:14 UTC | Jun 20, 18:54 UTC | 4h 40m |
| 2026-06-20 | TAI301 | - | Jun 20, 00:39 UTC | Jun 20, 11:14 UTC | 10h 35m |
| 2026-06-19 | TAI300 | - | Jun 19, 05:40 UTC | Jun 19, 15:24 UTC | 9h 45m |
| 2026-06-18 | TAI523 | LAX → SAL | Jun 18, 22:15 UTC | Jun 19, 02:35 UTC | 4h 19m |
| 2026-06-18 | TAI522 | - | Jun 18, 14:25 UTC | Jun 18, 19:00 UTC | 4h 35m |
| 2026-06-18 | TAI301 | - | Jun 18, 00:25 UTC | Jun 18, 10:30 UTC | 10h 5m |
| 2026-06-17 | TAI300 | - | Jun 17, 07:40 UTC | Jun 17, 16:05 UTC | 8h 25m |
| 2026-06-16 | TAI523 | LAX → SAL | Jun 16, 22:20 UTC | Jun 17, 02:45 UTC | 4h 25m |
| 2026-06-16 | TAI522 | - | Jun 16, 14:20 UTC | Jun 16, 19:00 UTC | 4h 40m |
| 2026-06-16 | TAI301 | - | Jun 16, 00:24 UTC | Jun 16, 10:25 UTC | 10h 0m |
| 2026-06-15 | TAI300 | - | Jun 15, 11:45 UTC | Jun 15, 21:45 UTC | 10h 0m |
| 2026-06-14 | TAI301 | - | Jun 14, 19:55 UTC | Jun 15, 06:15 UTC | 10h 19m |
| 2026-06-13 | IBE0126 | LIM → MAD | Jun 13, 21:35 UTC | Jun 14, 12:50 UTC | 15h 15m |
| 2026-06-13 | IBE0126 | LIM → MAD | Jun 13, 13:35 UTC | Jun 14, 12:50 UTC | 23h 15m |
| 2026-06-13 | IBE0125 | - | Jun 13, 11:50 UTC | Jun 14, 11:30 UTC | 23h 40m |
| 2026-06-11 | IBE07GF | LHR → MAD | Jun 11, 18:30 UTC | Jun 11, 20:15 UTC | 1h 45m |
| 2026-06-11 | IBE07MM | MAD → MAD | Jun 11, 14:35 UTC | Jun 11, 16:20 UTC | 1h 45m |
| 2026-06-09 | IBE0124 | LIM → MAD | Jun 9, 17:50 UTC | Jun 10, 03:50 UTC | 10h 0m |
| 2026-06-09 | IBE0124 | LIM → MAD | Jun 9, 08:35 UTC | Jun 10, 03:50 UTC | 19h 15m |
| 2026-06-08 | IBE0121 | MAD → BCN | Jun 8, 23:35 UTC | Jun 9, 18:35 UTC | 19h 0m |
| 2026-06-08 | IBE0121 | MAD → BCN | Jun 8, 22:30 UTC | Jun 9, 18:35 UTC | 20h 5m |
| 2026-06-06 | GRL940 | MAD → CPH | Jun 6, 15:15 UTC | Jun 6, 18:00 UTC | 2h 45m |
| 2026-06-05 | GRL3782 | GOH → GOH | Jun 5, 09:45 UTC | Jun 5, 20:40 UTC | 10h 55m |
| 2026-06-04 | GRL940 | MAD → CPH | Jun 4, 15:05 UTC | Jun 4, 17:30 UTC | 2h 25m |
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-NCK page for operator, model, and routing details .