sensors Mode-S transponder
4405B2
ICAO 24-bit transponder address · allocated to Austria
Currently assigned to OE-HDU · BOMBARDIER BD-100 Challenger 300
- Hex
- 4405B2
- Octal
- 21002662
- Decimal
- 4,457,906
- Country
- AT
- Tail
- OE-HDU
- Type
- CL30
- Flights observed
- 51
- Distinct callsigns
- 1
- Country
- AT
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 4405B2 falls within the block assigned to Austria (AT) by ICAO Annex 10, Volume III. Every aircraft registered in Austria 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| LDX15 | - | 51 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | LDX15 | - | Jul 25, 07:55 UTC | Jul 25, 09:45 UTC | 1h 50m |
| 2026-07-25 | LDX15 | VIE → SKG | Jul 25, 05:20 UTC | Jul 25, 06:40 UTC | 1h 20m |
| 2026-07-20 | LDX15 | SKG → OTP | Jul 20, 10:40 UTC | Jul 20, 11:25 UTC | 45m |
| 2026-07-20 | LDX15 | - | Jul 20, 08:20 UTC | Jul 20, 09:35 UTC | 1h 15m |
| 2026-07-18 | LDX15 | - | Jul 18, 13:15 UTC | Jul 18, 14:45 UTC | 1h 30m |
| 2026-07-18 | LDX15 | - | Jul 18, 10:10 UTC | Jul 18, 10:30 UTC | 20m |
| 2026-07-15 | LDX15 | - | Jul 15, 11:55 UTC | Jul 15, 12:15 UTC | 20m |
| 2026-07-15 | LDX15 | - | Jul 15, 09:10 UTC | Jul 15, 10:55 UTC | 1h 45m |
| 2026-07-15 | LDX15 | - | Jul 15, 05:05 UTC | Jul 15, 06:50 UTC | 1h 45m |
| 2026-07-15 | LDX15 | - | Jul 15, 03:35 UTC | Jul 15, 04:00 UTC | 25m |
| 2026-07-12 | LDX15 | PSA → BLQ | Jul 12, 14:35 UTC | Jul 12, 14:55 UTC | 20m |
| 2026-07-12 | LDX15 | - | Jul 12, 11:01 UTC | Jul 12, 13:01 UTC | 2h 0m |
| 2026-07-12 | LDX15 | - | Jul 12, 08:50 UTC | Jul 12, 09:10 UTC | 20m |
| 2026-07-02 | LDX15 | - | Jul 2, 11:05 UTC | Jul 2, 15:00 UTC | 3h 55m |
| 2026-06-29 | LDX15 | - | Jun 29, 08:09 UTC | Jun 29, 10:55 UTC | 2h 45m |
| 2026-06-28 | LDX15 | - | Jun 28, 14:25 UTC | Jun 28, 16:09 UTC | 1h 45m |
| 2026-06-28 | LDX15 | - | Jun 28, 11:39 UTC | Jun 28, 12:05 UTC | 25m |
| 2026-06-25 | LDX15 | - | Jun 25, 11:15 UTC | Jun 25, 11:39 UTC | 25m |
| 2026-06-25 | LDX15 | - | Jun 25, 08:24 UTC | Jun 25, 10:15 UTC | 1h 50m |
| 2026-06-25 | LDX15 | - | Jun 25, 06:44 UTC | Jun 25, 07:09 UTC | 25m |
| 2026-06-15 | LDX15 | - | Jun 15, 11:24 UTC | Jun 15, 14:15 UTC | 2h 50m |
| 2026-06-15 | LDX15 | - | Jun 15, 09:49 UTC | Jun 15, 10:24 UTC | 35m |
| 2026-06-15 | LDX15 | - | Jun 15, 06:49 UTC | Jun 15, 08:49 UTC | 2h 0m |
| 2026-06-15 | LDX15 | - | Jun 15, 04:15 UTC | Jun 15, 04:45 UTC | 30m |
| 2026-06-12 | LDX15 | - | Jun 12, 15:35 UTC | Jun 12, 16:05 UTC | 30m |
| 2026-06-12 | LDX15 | - | Jun 12, 12:40 UTC | Jun 12, 14:20 UTC | 1h 40m |
| 2026-06-12 | LDX15 | - | Jun 12, 08:40 UTC | Jun 12, 11:20 UTC | 2h 40m |
| 2026-06-12 | LDX15 | - | Jun 12, 06:55 UTC | Jun 12, 07:15 UTC | 20m |
| 2026-06-05 | LDX15 | - | Jun 5, 09:35 UTC | Jun 5, 10:00 UTC | 25m |
| 2026-06-05 | LDX15 | - | Jun 5, 07:15 UTC | Jun 5, 08:55 UTC | 1h 40m |
| 2026-06-04 | LDX15 | - | Jun 4, 10:50 UTC | Jun 4, 12:00 UTC | 1h 10m |
| 2026-06-04 | LDX15 | - | Jun 4, 06:20 UTC | Jun 4, 09:15 UTC | 2h 55m |
| 2026-06-03 | LDX15 | - | Jun 3, 09:30 UTC | Jun 3, 11:10 UTC | 1h 40m |
| 2026-06-01 | LDX15 | - | Jun 1, 12:15 UTC | Jun 1, 14:10 UTC | 1h 55m |
| 2026-05-28 | LDX15 | - | May 28, 12:40 UTC | May 28, 14:35 UTC | 1h 55m |
| 2026-05-28 | LDX15 | - | May 28, 11:25 UTC | May 28, 11:45 UTC | 20m |
| 2026-05-24 | LDX15 | - | May 24, 11:50 UTC | May 24, 13:40 UTC | 1h 50m |
| 2026-05-24 | LDX15 | - | May 24, 09:35 UTC | May 24, 10:00 UTC | 25m |
| 2026-05-21 | LDX15 | - | May 21, 14:05 UTC | May 21, 14:30 UTC | 25m |
| 2026-05-21 | LDX15 | - | May 21, 11:15 UTC | May 21, 13:01 UTC | 1h 45m |
| 2026-05-21 | LDX15 | - | May 21, 09:00 UTC | May 21, 09:25 UTC | 25m |
| 2026-05-11 | LDX15 | - | May 11, 14:55 UTC | May 11, 15:25 UTC | 30m |
| 2026-05-11 | LDX15 | - | May 11, 12:45 UTC | May 11, 14:20 UTC | 1h 35m |
| 2026-05-10 | LDX15 | - | May 10, 09:35 UTC | May 10, 10:49 UTC | 1h 15m |
| 2026-05-07 | LDX15 | - | May 7, 06:35 UTC | May 7, 11:30 UTC | 4h 56m |
| 2026-05-07 | LDX15 | - | May 7, 04:10 UTC | May 7, 04:30 UTC | 20m |
| 2026-04-28 | LDX15 | - | Apr 28, 08:05 UTC | Apr 28, 09:30 UTC | 1h 25m |
| 2026-04-27 | LDX15 | - | Apr 27, 15:50 UTC | Apr 27, 18:15 UTC | 2h 25m |
| 2026-04-27 | LDX15 | - | Apr 27, 14:15 UTC | Apr 27, 14:35 UTC | 20m |
| 2026-04-25 | LDX15 | - | Apr 25, 07:35 UTC | Apr 25, 09:30 UTC | 1h 55m |
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 OE-HDU page for operator, model, and routing details .