sensors Mode-S transponder
4D240F
ICAO 24-bit transponder address
Currently assigned to 9H-EUX · AIRBUS A-320
- Hex
- 4D240F
- Octal
- 23222017
- Decimal
- 5,055,503
- Tail
- 9H-EUX
- Type
- A320
- Flights observed
- 19
- Distinct callsigns
- 17
- Country
- -
- Last broadcast
- 11m ago
Current position
Callsign history 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| EWG8KP | Eurowings | 2 | 2026-06-08 |
| EWG5Q | - | 2 | 2026-06-13 |
| EWG9F | Eurowings | 1 | 2026-06-10 |
| EWG8VB | Eurowings | 1 | 2026-06-10 |
| EWG8J | Eurowings | 1 | 2026-06-12 |
| EWG82Y | Eurowings | 1 | 2026-06-12 |
| EWG7U | Eurowings | 1 | 2026-06-12 |
| EWG70A | - | 1 | 2026-06-09 |
| EWG6DM | - | 1 | 2026-06-12 |
| EWG4UY | - | 1 | 2026-06-12 |
| EWG47B | Eurowings | 1 | 2026-06-13 |
| EWG3Y | Eurowings | 1 | 2026-06-12 |
| EWG2YR | Eurowings | 1 | 2026-06-13 |
| EWG2J | Eurowings | 1 | 2026-06-11 |
| EWG28N | Eurowings | 1 | 2026-06-11 |
| EWG21F | Eurowings | 1 | 2026-06-10 |
| EWG11S | Eurowings | 1 | 2026-06-09 |
Recent flights last 19
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-13 | EWG5Q | - | Jun 13, 10:25 UTC | Jun 13, 11:45 UTC | 1h 20m |
| 2026-06-13 | EWG2YR | NCE → DUS | Jun 13, 07:45 UTC | Jun 13, 09:10 UTC | 1h 25m |
| 2026-06-13 | EWG47B | DUS → NCE | Jun 13, 05:20 UTC | Jun 13, 06:40 UTC | 1h 20m |
| 2026-06-12 | EWG8J | OPO → BER | Jun 12, 17:15 UTC | Jun 12, 18:40 UTC | 1h 25m |
| 2026-06-12 | EWG82Y | DUS → VIE | Jun 12, 15:00 UTC | Jun 12, 16:15 UTC | 1h 15m |
| 2026-06-12 | EWG6DM | - | Jun 12, 12:20 UTC | Jun 12, 14:10 UTC | 1h 50m |
| 2026-06-12 | EWG4UY | - | Jun 12, 09:35 UTC | Jun 12, 11:10 UTC | 1h 35m |
| 2026-06-12 | EWG7U | MXP → DUS | Jun 12, 07:05 UTC | Jun 12, 08:00 UTC | 55m |
| 2026-06-12 | EWG3Y | HAM → TFS | Jun 12, 04:55 UTC | Jun 12, 06:05 UTC | 1h 10m |
| 2026-06-11 | EWG28N | VIE → DUS | Jun 11, 18:55 UTC | Jun 11, 21:00 UTC | 2h 5m |
| 2026-06-11 | EWG2J | HAJ → BGY | Jun 11, 14:45 UTC | Jun 11, 16:55 UTC | 2h 10m |
| 2026-06-10 | EWG9F | CGN → PMI | Jun 10, 14:30 UTC | Jun 10, 16:25 UTC | 1h 55m |
| 2026-06-10 | EWG5Q | - | Jun 10, 10:50 UTC | Jun 10, 13:00 UTC | 2h 10m |
| 2026-06-10 | EWG21F | MAN → DUS | Jun 10, 07:20 UTC | Jun 10, 08:35 UTC | 1h 15m |
| 2026-06-10 | EWG8VB | GOT → DUS | Jun 10, 04:55 UTC | Jun 10, 06:00 UTC | 1h 5m |
| 2026-06-09 | EWG11S | PMI → DUS | Jun 9, 08:20 UTC | Jun 9, 10:20 UTC | 2h 0m |
| 2026-06-09 | EWG70A | - | Jun 9, 04:40 UTC | Jun 9, 06:40 UTC | 2h 0m |
| 2026-06-08 | EWG8KP | SZG → HAM | Jun 8, 17:50 UTC | Jun 8, 18:50 UTC | 1h 0m |
| 2026-06-08 | EWG8KP | SZG → HAM | Jun 8, 16:30 UTC | Jun 8, 17:05 UTC | 35m |
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 9H-EUX page for operator, model, and routing details .