sensors Mode-S transponder
4401D2
ICAO 24-bit transponder address · allocated to Austria
Currently assigned to OE-IYY · DASSAULT Falcon 900
- Hex
- 4401D2
- Octal
- 21000722
- Decimal
- 4,456,914
- Country
- AT
- Tail
- OE-IYY
- Type
- F900
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- AT
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 4401D2 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 |
|---|---|---|---|
| MOZ603 | - | 48 | 2026-07-17 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | MOZ603 | VIE → OLB | Jul 17, 08:49 UTC | Jul 17, 10:15 UTC | 1h 25m |
| 2026-07-14 | MOZ603 | - | Jul 14, 15:00 UTC | Jul 14, 16:15 UTC | 1h 15m |
| 2026-07-08 | MOZ603 | - | Jul 8, 15:20 UTC | Jul 8, 16:25 UTC | 1h 5m |
| 2026-07-07 | MOZ603 | VIE → LBG | Jul 7, 16:15 UTC | Jul 7, 17:55 UTC | 1h 40m |
| 2026-07-07 | MOZ603 | LBG → VIE | Jul 7, 07:35 UTC | Jul 7, 09:00 UTC | 1h 25m |
| 2026-07-05 | MOZ603 | VIE → LBG | Jul 5, 12:15 UTC | Jul 5, 13:55 UTC | 1h 40m |
| 2026-07-05 | MOZ603 | - | Jul 5, 09:20 UTC | Jul 5, 10:10 UTC | 50m |
| 2026-07-05 | MOZ603 | - | Jul 5, 07:25 UTC | Jul 5, 08:20 UTC | 55m |
| 2026-07-01 | MOZ603 | - | Jul 1, 09:30 UTC | Jul 1, 11:00 UTC | 1h 30m |
| 2026-06-30 | MOZ603 | ATH → BOJ | Jun 30, 09:20 UTC | Jun 30, 10:30 UTC | 1h 10m |
| 2026-06-30 | MOZ603 | - | Jun 30, 04:35 UTC | Jun 30, 05:10 UTC | 35m |
| 2026-06-27 | MOZ603 | ATH → SKG | Jun 27, 15:30 UTC | Jun 27, 16:04 UTC | 35m |
| 2026-06-27 | MOZ603 | - | Jun 27, 11:55 UTC | Jun 27, 14:20 UTC | 2h 25m |
| 2026-06-26 | MOZ603 | - | Jun 26, 08:40 UTC | Jun 26, 09:50 UTC | 1h 10m |
| 2026-06-24 | MOZ603 | ATH → VIE | Jun 24, 11:09 UTC | Jun 24, 13:10 UTC | 2h 0m |
| 2026-06-24 | MOZ603 | VIE → ATH | Jun 24, 07:10 UTC | Jun 24, 09:00 UTC | 1h 50m |
| 2026-06-14 | MOZ603 | ATH → VIE | Jun 14, 12:40 UTC | Jun 14, 14:45 UTC | 2h 5m |
| 2026-06-14 | MOZ603 | VIE → ATH | Jun 14, 09:10 UTC | Jun 14, 11:00 UTC | 1h 50m |
| 2026-06-11 | MOZ603 | - | Jun 11, 11:20 UTC | Jun 11, 12:35 UTC | 1h 15m |
| 2026-06-10 | MOZ603 | IBZ → NCE | Jun 10, 09:55 UTC | Jun 10, 11:10 UTC | 1h 15m |
| 2026-06-10 | MOZ603 | - | Jun 10, 06:10 UTC | Jun 10, 07:30 UTC | 1h 20m |
| 2026-06-03 | MOZ603 | - | Jun 3, 11:20 UTC | Jun 3, 12:45 UTC | 1h 25m |
| 2026-05-24 | MOZ603 | NCE → VIE | May 24, 11:05 UTC | May 24, 12:25 UTC | 1h 20m |
| 2026-05-19 | MOZ603 | - | May 19, 15:55 UTC | May 19, 17:30 UTC | 1h 35m |
| 2026-05-19 | MOZ603 | - | May 19, 07:00 UTC | May 19, 08:30 UTC | 1h 30m |
| 2026-05-18 | MOZ603 | VIE → NCE | May 18, 12:35 UTC | May 18, 14:05 UTC | 1h 30m |
| 2026-05-16 | MOZ603 | - | May 16, 14:51 UTC | May 16, 15:25 UTC | 35m |
| 2026-05-16 | MOZ603 | - | May 16, 13:15 UTC | May 16, 14:05 UTC | 50m |
| 2026-05-15 | MOZ603 | - | May 15, 08:00 UTC | May 15, 09:30 UTC | 1h 30m |
| 2026-05-12 | MOZ603 | - | May 12, 17:20 UTC | May 12, 19:00 UTC | 1h 40m |
| 2026-05-11 | MOZ603 | - | May 11, 14:50 UTC | May 11, 15:50 UTC | 1h 0m |
| 2026-05-10 | MOZ603 | - | May 10, 09:35 UTC | May 10, 10:30 UTC | 55m |
| 2026-05-08 | MOZ603 | - | May 8, 11:55 UTC | May 8, 12:30 UTC | 35m |
| 2026-05-04 | MOZ603 | - | May 4, 14:25 UTC | May 4, 15:20 UTC | 55m |
| 2026-05-04 | MOZ603 | VIE → NCE | May 4, 11:35 UTC | May 4, 13:00 UTC | 1h 25m |
| 2026-04-30 | MOZ603 | NCE → VIE | Apr 30, 14:40 UTC | Apr 30, 15:55 UTC | 1h 15m |
| 2026-04-30 | MOZ603 | - | Apr 30, 12:30 UTC | Apr 30, 13:45 UTC | 1h 15m |
| 2026-04-26 | MOZ603 | - | Apr 26, 17:50 UTC | Apr 26, 18:55 UTC | 1h 5m |
| 2026-04-26 | MOZ603 | VIE → NCE | Apr 26, 15:50 UTC | Apr 26, 17:20 UTC | 1h 30m |
| 2026-04-26 | MOZ603 | NCE → VIE | Apr 26, 12:45 UTC | Apr 26, 13:55 UTC | 1h 10m |
| 2026-04-22 | MOZ603 | - | Apr 22, 14:20 UTC | Apr 22, 15:05 UTC | 45m |
| 2026-04-21 | MOZ603 | - | Apr 21, 14:10 UTC | Apr 21, 14:55 UTC | 45m |
| 2026-04-21 | MOZ603 | VIE → NCE | Apr 21, 07:55 UTC | Apr 21, 09:25 UTC | 1h 30m |
| 2026-04-14 | MOZ603 | - | Apr 14, 10:50 UTC | Apr 14, 12:00 UTC | 1h 10m |
| 2026-04-14 | MOZ603 | - | Apr 14, 10:40 UTC | Apr 14, 11:05 UTC | 25m |
| 2026-04-14 | MOZ603 | - | Apr 14, 09:10 UTC | Apr 14, 09:25 UTC | 15m |
| 2026-04-14 | MOZ603 | - | Apr 14, 08:05 UTC | Apr 14, 09:05 UTC | 1h 0m |
| 2026-04-13 | MOZ603 | - | Apr 13, 16:25 UTC | Apr 13, 17:05 UTC | 40m |
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-IYY page for operator, model, and routing details .