sensors Mode-S transponder
34760A
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-ODQ · AIRBUS A-330-300
- Hex
- 34760A
- Octal
- 15073012
- Decimal
- 3,438,090
- Country
- ES
- Tail
- EC-ODQ
- Type
- A333
- Flights observed
- 119
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 34760A 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 |
|---|---|---|---|
| SVA5317 | - | 6 | 2026-05-03 |
| SVA9416 | - | 5 | 2026-06-03 |
| SVA9392 | - | 5 | 2026-05-01 |
| SVA5257 | - | 5 | 2026-04-28 |
| SVA5181 | - | 5 | 2026-04-24 |
| SVA9518 | - | 4 | 2026-05-15 |
| SVA9383 | - | 4 | 2026-04-24 |
| SVA9381 | - | 4 | 2026-04-30 |
| SVA9360 | - | 4 | 2026-04-28 |
| SVA9340 | - | 4 | 2026-04-27 |
| SVA9320 | - | 4 | 2026-06-01 |
| SVA9315 | - | 4 | 2026-05-21 |
| SVA5337 | - | 4 | 2026-04-22 |
| SVA5268 | Saudi Arabian Airlines | 4 | 2026-06-06 |
| SVA5236 | - | 4 | 2026-06-05 |
| SVA5204 | - | 4 | 2026-06-04 |
| SVA9547 | - | 3 | 2026-05-18 |
| SVA9537 | - | 3 | 2026-05-17 |
| SVA9423 | - | 3 | 2026-05-05 |
| SVA9402 | - | 3 | 2026-05-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-07 | SVA5304 | - | Jun 7, 12:00 UTC | Jun 7, 21:50 UTC | 9h 50m |
| 2026-06-06 | SVA5304 | - | Jun 6, 23:30 UTC | Jun 7, 21:50 UTC | 22h 20m |
| 2026-06-06 | SVA5304 | - | Jun 6, 19:40 UTC | Jun 7, 17:50 UTC | 22h 10m |
| 2026-06-06 | SVA9505 | - | Jun 6, 14:34 UTC | Jun 7, 12:20 UTC | 21h 45m |
| 2026-06-06 | SVA5268 | JED → KJT | Jun 6, 13:39 UTC | Jun 7, 12:20 UTC | 22h 40m |
| 2026-06-06 | SVA5268 | JED → KJT | Jun 6, 05:05 UTC | Jun 7, 00:05 UTC | 19h 0m |
| 2026-06-05 | SVA5268 | JED → KJT | Jun 5, 18:35 UTC | Jun 6, 14:40 UTC | 20h 5m |
| 2026-06-05 | SVA5268 | JED → KJT | Jun 5, 18:05 UTC | Jun 6, 14:40 UTC | 20h 35m |
| 2026-06-05 | SVA9486 | - | Jun 5, 14:05 UTC | Jun 6, 09:39 UTC | 19h 35m |
| 2026-06-05 | SVA9486 | - | Jun 5, 09:20 UTC | Jun 6, 05:20 UTC | 20h 0m |
| 2026-06-05 | SVA5236 | - | Jun 5, 00:35 UTC | Jun 5, 18:40 UTC | 18h 5m |
| 2026-06-04 | SVA5236 | - | Jun 4, 15:15 UTC | Jun 5, 14:30 UTC | 23h 15m |
| 2026-06-04 | SVA5236 | - | Jun 4, 11:25 UTC | Jun 5, 10:20 UTC | 22h 55m |
| 2026-06-04 | SVA5236 | - | Jun 4, 06:35 UTC | Jun 5, 06:15 UTC | 23h 40m |
| 2026-06-04 | SVA5204 | - | Jun 4, 06:20 UTC | Jun 5, 01:00 UTC | 18h 40m |
| 2026-06-04 | SVA5204 | - | Jun 4, 01:55 UTC | Jun 5, 00:30 UTC | 22h 35m |
| 2026-06-03 | SVA5204 | - | Jun 3, 21:40 UTC | Jun 4, 15:50 UTC | 18h 10m |
| 2026-06-03 | SVA5204 | - | Jun 3, 09:00 UTC | Jun 4, 07:15 UTC | 22h 15m |
| 2026-06-03 | SVA9416 | - | Jun 3, 07:30 UTC | Jun 4, 02:20 UTC | 18h 50m |
| 2026-06-03 | SVA9416 | - | Jun 3, 03:15 UTC | Jun 4, 02:20 UTC | 23h 5m |
| 2026-06-02 | SVA9416 | - | Jun 2, 22:35 UTC | Jun 3, 21:55 UTC | 23h 20m |
| 2026-06-02 | SVA5166 | - | Jun 2, 18:00 UTC | Jun 3, 09:10 UTC | 15h 10m |
| 2026-06-02 | SVA5166 | - | Jun 2, 13:40 UTC | Jun 3, 09:10 UTC | 19h 30m |
| 2026-06-02 | SVA5166 | - | Jun 2, 00:45 UTC | Jun 2, 23:25 UTC | 22h 40m |
| 2026-06-01 | SVA9320 | - | Jun 1, 20:35 UTC | Jun 2, 19:25 UTC | 22h 50m |
| 2026-06-01 | SVA9320 | - | Jun 1, 20:20 UTC | Jun 2, 18:25 UTC | 22h 5m |
| 2026-06-01 | SVA9320 | - | Jun 1, 16:35 UTC | Jun 2, 14:00 UTC | 21h 25m |
| 2026-06-01 | SVA9320 | - | Jun 1, 15:40 UTC | Jun 2, 14:00 UTC | 22h 20m |
| 2026-06-01 | SVA5132 | - | Jun 1, 07:00 UTC | Jun 2, 02:25 UTC | 19h 25m |
| 2026-05-21 | SVA5461 | - | May 21, 20:10 UTC | May 21, 22:05 UTC | 1h 55m |
| 2026-05-21 | SVA9315 | - | May 21, 03:35 UTC | May 21, 15:40 UTC | 12h 5m |
| 2026-05-20 | SVA9315 | - | May 20, 17:00 UTC | May 21, 15:40 UTC | 22h 40m |
| 2026-05-20 | SVA9315 | - | May 20, 15:50 UTC | May 21, 14:25 UTC | 22h 35m |
| 2026-05-20 | SVA9315 | - | May 20, 10:35 UTC | May 21, 09:15 UTC | 22h 40m |
| 2026-05-20 | SVA5307 | - | May 20, 09:35 UTC | May 21, 08:30 UTC | 22h 55m |
| 2026-05-19 | SVA5307 | - | May 19, 23:05 UTC | May 20, 17:25 UTC | 18h 21m |
| 2026-05-19 | SVA9306 | - | May 19, 22:00 UTC | May 20, 17:25 UTC | 19h 26m |
| 2026-05-19 | SVA9306 | - | May 19, 09:00 UTC | May 20, 03:40 UTC | 18h 40m |
| 2026-05-19 | SVA9306 | - | May 19, 07:50 UTC | May 20, 03:40 UTC | 19h 50m |
| 2026-05-18 | SVA9547 | - | May 18, 12:55 UTC | May 19, 03:00 UTC | 14h 4m |
| 2026-05-18 | SVA9547 | - | May 18, 02:55 UTC | May 19, 02:30 UTC | 23h 34m |
| 2026-05-18 | SVA9547 | - | May 18, 01:55 UTC | May 18, 20:50 UTC | 18h 54m |
| 2026-05-17 | SVA9537 | - | May 17, 09:25 UTC | May 17, 21:05 UTC | 11h 40m |
| 2026-05-16 | SVA9537 | - | May 16, 18:35 UTC | May 17, 14:50 UTC | 20h 15m |
| 2026-05-16 | SVA9537 | - | May 16, 17:15 UTC | May 17, 14:50 UTC | 21h 35m |
| 2026-05-15 | SVA9518 | - | May 15, 22:45 UTC | May 16, 12:40 UTC | 13h 56m |
| 2026-05-15 | SVA9518 | - | May 15, 11:30 UTC | May 16, 06:45 UTC | 19h 15m |
| 2026-05-15 | SVA9518 | - | May 15, 06:35 UTC | May 16, 06:31 UTC | 23h 55m |
| 2026-05-15 | SVA9518 | - | May 15, 05:00 UTC | May 16, 02:45 UTC | 21h 44m |
| 2026-05-14 | SVA9507 | - | May 14, 19:15 UTC | May 15, 11:30 UTC | 16h 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-ODQ page for operator, model, and routing details .