sensors Mode-S transponder
4CAFF4
ICAO 24-bit transponder address · allocated to Ireland
Currently assigned to EI-LKD · AIRBUS A-330-300
- Hex
- 4CAFF4
- Octal
- 23127764
- Decimal
- 5,025,780
- Country
- IE
- Tail
- EI-LKD
- Type
- A333
- Flights observed
- 64
- Distinct callsigns
- 11
- Country
- IE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4CAFF4 falls within the block assigned to Ireland (IE) by ICAO Annex 10, Volume III. Every aircraft registered in Ireland 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 11 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SVA933 | Saudi Arabian Airlines | 20 | 2026-06-05 |
| SVA934 | Saudi Arabian Airlines | 16 | 2026-06-05 |
| SVA913 | Saudi Arabian Airlines | 7 | 2026-06-05 |
| SVA922 | Saudi Arabian Airlines | 4 | 2026-06-07 |
| SVA921 | Saudi Arabian Airlines | 4 | 2026-06-06 |
| SVA915 | Saudi Arabian Airlines | 4 | 2026-05-19 |
| SVA947 | Saudi Arabian Airlines | 2 | 2026-05-05 |
| SVA916 | Saudi Arabian Airlines | 2 | 2026-05-18 |
| SVA914 | Saudi Arabian Airlines | 2 | 2026-05-30 |
| SVA3916 | Saudi Arabian Airlines | 2 | 2026-05-05 |
| SVA953 | Saudi Arabian Airlines | 1 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-07 | SVA922 | BRU → JED | Jun 7, 07:50 UTC | Jun 7, 19:35 UTC | 11h 45m |
| 2026-06-06 | SVA921 | RUH → LGG | Jun 6, 13:25 UTC | Jun 7, 03:55 UTC | 14h 30m |
| 2026-06-05 | SVA913 | RUH → FRA | Jun 5, 15:05 UTC | Jun 6, 10:55 UTC | 19h 50m |
| 2026-06-05 | SVA934 | AMS → JED | Jun 5, 14:10 UTC | Jun 6, 10:55 UTC | 20h 45m |
| 2026-06-05 | SVA933 | JED → AMS | Jun 5, 05:30 UTC | Jun 5, 09:30 UTC | 4h 0m |
| 2026-06-03 | SVA934 | AMS → JED | Jun 3, 15:05 UTC | Jun 3, 19:15 UTC | 4h 10m |
| 2026-06-03 | SVA933 | JED → AMS | Jun 3, 04:40 UTC | Jun 3, 08:35 UTC | 3h 55m |
| 2026-06-01 | SVA934 | AMS → JED | Jun 1, 13:55 UTC | Jun 1, 17:50 UTC | 3h 55m |
| 2026-06-01 | SVA933 | JED → AMS | Jun 1, 05:20 UTC | Jun 1, 09:15 UTC | 3h 55m |
| 2026-05-30 | SVA914 | FRA → RUH | May 30, 14:40 UTC | May 31, 09:00 UTC | 18h 20m |
| 2026-05-29 | SVA913 | RUH → FRA | May 29, 17:05 UTC | May 30, 11:35 UTC | 18h 30m |
| 2026-05-29 | SVA934 | AMS → JED | May 29, 15:05 UTC | May 30, 11:35 UTC | 20h 30m |
| 2026-05-29 | SVA934 | AMS → JED | May 29, 14:25 UTC | May 30, 11:35 UTC | 21h 10m |
| 2026-05-29 | SVA933 | JED → AMS | May 29, 04:50 UTC | May 29, 09:05 UTC | 4h 15m |
| 2026-05-27 | SVA934 | AMS → JED | May 27, 15:15 UTC | May 27, 19:25 UTC | 4h 10m |
| 2026-05-27 | SVA933 | JED → AMS | May 27, 05:29 UTC | May 27, 09:05 UTC | 3h 36m |
| 2026-05-25 | SVA934 | AMS → JED | May 25, 13:55 UTC | May 25, 17:00 UTC | 3h 5m |
| 2026-05-25 | SVA933 | JED → AMS | May 25, 05:25 UTC | May 25, 09:05 UTC | 3h 40m |
| 2026-05-24 | SVA922 | BRU → JED | May 24, 06:10 UTC | May 24, 09:40 UTC | 3h 30m |
| 2026-05-23 | SVA921 | RUH → LGG | May 23, 15:00 UTC | May 24, 03:55 UTC | 12h 55m |
| 2026-05-22 | SVA913 | RUH → FRA | May 22, 17:05 UTC | May 23, 11:35 UTC | 18h 29m |
| 2026-05-22 | SVA913 | RUH → FRA | May 22, 15:05 UTC | May 23, 11:35 UTC | 20h 29m |
| 2026-05-22 | SVA934 | AMS → JED | May 22, 14:20 UTC | May 23, 11:35 UTC | 21h 14m |
| 2026-05-22 | SVA933 | JED → AMS | May 22, 05:25 UTC | May 22, 09:15 UTC | 3h 50m |
| 2026-05-20 | SVA934 | AMS → JED | May 20, 15:00 UTC | May 20, 19:20 UTC | 4h 20m |
| 2026-05-19 | SVA933 | JED → AMS | May 19, 15:05 UTC | May 20, 10:15 UTC | 19h 11m |
| 2026-05-19 | SVA933 | JED → AMS | May 19, 13:05 UTC | May 20, 10:15 UTC | 21h 11m |
| 2026-05-19 | SVA933 | JED → AMS | May 19, 12:05 UTC | May 20, 10:15 UTC | 22h 11m |
| 2026-05-19 | SVA915 | RUH → BRU | May 19, 05:10 UTC | May 19, 08:55 UTC | 3h 45m |
| 2026-05-18 | SVA916 | BRU → RUH | May 18, 06:55 UTC | May 18, 09:55 UTC | 3h 0m |
| 2026-05-17 | SVA915 | RUH → BRU | May 17, 23:55 UTC | May 18, 03:30 UTC | 3h 35m |
| 2026-05-14 | SVA934 | AMS → JED | May 14, 15:10 UTC | May 14, 19:15 UTC | 4h 5m |
| 2026-05-14 | SVA933 | JED → AMS | May 14, 05:30 UTC | May 14, 09:10 UTC | 3h 40m |
| 2026-05-12 | SVA916 | BRU → RUH | May 12, 14:55 UTC | May 12, 17:35 UTC | 2h 40m |
| 2026-05-12 | SVA915 | RUH → BRU | May 12, 07:25 UTC | May 12, 11:35 UTC | 4h 10m |
| 2026-05-11 | SVA914 | FRA → RUH | May 11, 10:00 UTC | May 11, 13:00 UTC | 3h 0m |
| 2026-05-10 | SVA913 | RUH → FRA | May 10, 17:40 UTC | May 11, 07:05 UTC | 13h 25m |
| 2026-05-10 | SVA915 | RUH → BRU | May 10, 08:40 UTC | May 10, 12:49 UTC | 4h 10m |
| 2026-05-09 | SVA934 | AMS → JED | May 9, 11:55 UTC | May 9, 15:55 UTC | 4h 0m |
| 2026-05-09 | SVA933 | JED → AMS | May 9, 04:05 UTC | May 9, 08:35 UTC | 4h 30m |
| 2026-05-08 | SVA953 | RUH → SHJ | May 8, 16:00 UTC | May 8, 16:10 UTC | 10m |
| 2026-05-07 | SVA934 | AMS → JED | May 7, 15:25 UTC | May 7, 19:50 UTC | 4h 25m |
| 2026-05-06 | SVA933 | JED → AMS | May 6, 15:20 UTC | May 7, 08:45 UTC | 17h 25m |
| 2026-05-06 | SVA933 | JED → AMS | May 6, 05:55 UTC | May 6, 09:35 UTC | 3h 40m |
| 2026-05-05 | SVA947 | RUH → NBO | May 5, 18:25 UTC | May 5, 18:40 UTC | 15m |
| 2026-05-05 | SVA3916 | JED → IST | May 5, 06:45 UTC | May 5, 08:25 UTC | 1h 40m |
| 2026-05-04 | SVA934 | AMS → JED | May 4, 14:30 UTC | May 5, 02:55 UTC | 12h 26m |
| 2026-05-04 | SVA933 | JED → AMS | May 4, 07:00 UTC | May 4, 10:35 UTC | 3h 35m |
| 2026-05-03 | SVA922 | BRU → JED | May 3, 08:20 UTC | May 3, 10:55 UTC | 2h 35m |
| 2026-05-02 | SVA921 | RUH → LGG | May 2, 13:55 UTC | May 3, 03:45 UTC | 13h 49m |
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 EI-LKD page for operator, model, and routing details .