sensors Mode-S transponder
3463DA
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-NHM · AIRBUS A-330-300
- Hex
- 3463DA
- Octal
- 15061732
- Decimal
- 3,433,434
- Country
- ES
- Tail
- EC-NHM
- Type
- A333
- Flights observed
- 65
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 3463DA 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 |
|---|---|---|---|
| SVA9544 | - | 5 | 2026-05-18 |
| SVA9351 | - | 5 | 2026-04-28 |
| SVA9461 | - | 4 | 2026-05-09 |
| SVA5358 | Saudi Arabian Airlines | 4 | 2026-06-09 |
| SVA5135 | - | 4 | 2026-04-27 |
| SVA9525 | - | 3 | 2026-05-16 |
| SVA9457 | - | 3 | 2026-05-08 |
| SVA9448 | - | 3 | 2026-05-07 |
| SVA9302 | - | 3 | 2026-05-18 |
| SVA5347 | - | 3 | 2026-05-10 |
| SVA5188 | - | 3 | 2026-06-03 |
| SVA9534 | - | 2 | 2026-05-17 |
| SVA5232 | - | 2 | 2026-06-04 |
| SVA5220 | - | 2 | 2026-06-04 |
| SVA5113 | - | 2 | 2026-06-03 |
| SVA9528 | - | 1 | 2026-06-08 |
| SVA9516 | - | 1 | 2026-05-15 |
| SVA9495 | - | 1 | 2026-06-05 |
| SVA9493 | - | 1 | 2026-05-12 |
| SVA9471 | - | 1 | 2026-05-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-11 | SVA9402 | - | Jun 11, 03:10 UTC | Jun 11, 03:45 UTC | 35m |
| 2026-06-10 | SVA5107 | - | Jun 10, 14:20 UTC | Jun 11, 01:10 UTC | 10h 50m |
| 2026-06-09 | SVA5106 | - | Jun 9, 20:35 UTC | Jun 10, 12:15 UTC | 15h 40m |
| 2026-06-09 | SVA5358 | JED → BLR | Jun 9, 14:35 UTC | Jun 10, 12:15 UTC | 21h 40m |
| 2026-06-09 | SVA5358 | JED → BLR | Jun 9, 09:55 UTC | Jun 10, 04:10 UTC | 18h 15m |
| 2026-06-08 | SVA5358 | JED → BLR | Jun 8, 19:20 UTC | Jun 9, 15:40 UTC | 20h 20m |
| 2026-06-08 | SVA5358 | JED → BLR | Jun 8, 16:40 UTC | Jun 9, 15:40 UTC | 23h 0m |
| 2026-06-08 | SVA9528 | - | Jun 8, 12:35 UTC | Jun 9, 10:20 UTC | 21h 45m |
| 2026-06-08 | SVA5310 | - | Jun 8, 10:55 UTC | Jun 9, 10:20 UTC | 23h 25m |
| 2026-06-07 | SVA5380 | - | Jun 7, 04:35 UTC | Jun 7, 11:20 UTC | 6h 45m |
| 2026-06-05 | SVA9495 | - | Jun 5, 09:50 UTC | Jun 5, 12:30 UTC | 2h 40m |
| 2026-06-04 | SVA5232 | - | Jun 4, 12:50 UTC | Jun 5, 08:15 UTC | 19h 25m |
| 2026-06-04 | SVA5232 | - | Jun 4, 12:10 UTC | Jun 5, 08:15 UTC | 20h 5m |
| 2026-06-04 | SVA5220 | - | Jun 4, 02:20 UTC | Jun 4, 19:00 UTC | 16h 40m |
| 2026-06-03 | SVA5220 | - | Jun 3, 22:35 UTC | Jun 4, 19:00 UTC | 20h 25m |
| 2026-06-03 | SVA5188 | - | Jun 3, 21:50 UTC | Jun 4, 19:00 UTC | 21h 10m |
| 2026-06-03 | SVA5188 | - | Jun 3, 08:35 UTC | Jun 4, 03:55 UTC | 19h 20m |
| 2026-06-03 | SVA5188 | - | Jun 3, 08:15 UTC | Jun 4, 03:55 UTC | 19h 40m |
| 2026-06-03 | SVA5113 | - | Jun 3, 02:40 UTC | Jun 3, 05:55 UTC | 3h 15m |
| 2026-06-02 | SVA5113 | - | Jun 2, 04:35 UTC | Jun 3, 03:05 UTC | 22h 30m |
| 2026-06-01 | SVA9379 | - | Jun 1, 22:10 UTC | Jun 2, 05:25 UTC | 7h 15m |
| 2026-05-20 | SVA9314 | - | May 20, 20:05 UTC | May 21, 02:30 UTC | 6h 25m |
| 2026-05-18 | SVA9302 | - | May 18, 16:35 UTC | May 19, 12:20 UTC | 19h 44m |
| 2026-05-18 | SVA9302 | - | May 18, 16:20 UTC | May 19, 12:20 UTC | 19h 59m |
| 2026-05-18 | SVA9302 | - | May 18, 10:35 UTC | May 19, 10:30 UTC | 23h 54m |
| 2026-05-18 | SVA9544 | - | May 18, 10:10 UTC | May 19, 07:45 UTC | 21h 34m |
| 2026-05-17 | SVA9544 | - | May 17, 20:45 UTC | May 18, 17:40 UTC | 20h 55m |
| 2026-05-17 | SVA9544 | - | May 17, 19:30 UTC | May 18, 17:40 UTC | 22h 10m |
| 2026-05-17 | SVA9544 | - | May 17, 16:35 UTC | May 18, 16:30 UTC | 23h 55m |
| 2026-05-17 | SVA9544 | - | May 17, 14:50 UTC | May 18, 12:15 UTC | 21h 25m |
| 2026-05-17 | SVA9534 | - | May 17, 02:35 UTC | May 17, 20:50 UTC | 18h 15m |
| 2026-05-17 | SVA9534 | - | May 17, 00:35 UTC | May 17, 20:50 UTC | 20h 15m |
| 2026-05-16 | SVA9525 | - | May 16, 04:55 UTC | May 16, 22:35 UTC | 17h 40m |
| 2026-05-16 | SVA9525 | - | May 16, 00:35 UTC | May 16, 22:35 UTC | 22h 0m |
| 2026-05-16 | SVA9525 | - | May 16, 00:10 UTC | May 16, 22:30 UTC | 22h 20m |
| 2026-05-15 | SVA9516 | - | May 15, 11:35 UTC | May 16, 06:01 UTC | 18h 25m |
| 2026-05-15 | SVA9326 | - | May 15, 06:20 UTC | May 15, 08:55 UTC | 2h 35m |
| 2026-05-12 | SVA9493 | - | May 12, 20:55 UTC | May 13, 04:30 UTC | 7h 35m |
| 2026-05-10 | SVA5347 | - | May 10, 10:49 UTC | May 10, 19:15 UTC | 8h 25m |
| 2026-05-09 | SVA5347 | - | May 9, 22:55 UTC | May 10, 19:15 UTC | 20h 20m |
| 2026-05-09 | SVA5347 | - | May 9, 20:34 UTC | May 10, 19:15 UTC | 22h 40m |
| 2026-05-09 | SVA9471 | - | May 9, 16:35 UTC | May 10, 12:44 UTC | 20h 10m |
| 2026-05-09 | SVA9461 | - | May 9, 15:35 UTC | May 10, 12:44 UTC | 21h 10m |
| 2026-05-09 | SVA9461 | - | May 9, 04:45 UTC | May 9, 23:05 UTC | 18h 20m |
| 2026-05-09 | SVA9461 | - | May 9, 02:35 UTC | May 9, 23:05 UTC | 20h 30m |
| 2026-05-09 | SVA9461 | - | May 9, 01:25 UTC | May 9, 23:05 UTC | 21h 40m |
| 2026-05-08 | SVA9457 | - | May 8, 07:34 UTC | May 8, 23:30 UTC | 15h 55m |
| 2026-05-08 | SVA9457 | - | May 8, 02:35 UTC | May 8, 23:30 UTC | 20h 55m |
| 2026-05-08 | SVA9457 | - | May 8, 00:49 UTC | May 8, 23:30 UTC | 22h 40m |
| 2026-05-07 | SVA9448 | - | May 7, 12:50 UTC | May 8, 09:49 UTC | 21h 0m |
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-NHM page for operator, model, and routing details .