sensors Mode-S transponder
3C0F0B
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-AUSC · AIRBUS A-340-300
- Hex
- 3C0F0B
- Octal
- 17007413
- Decimal
- 3,936,011
- Country
- DE
- Tail
- D-AUSC
- Type
- A343
- Flights observed
- 47
- Distinct callsigns
- 16
- Country
- DE
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 3C0F0B falls within the block assigned to Germany (DE) by ICAO Annex 10, Volume III. Every aircraft registered in Germany 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SLM994 | - | 8 | 2026-06-17 |
| USY99P | - | 7 | 2026-06-18 |
| USY099P | USC GmbH | 7 | 2026-05-10 |
| SLM993 | - | 5 | 2026-06-17 |
| USY5091 | USC GmbH | 4 | 2026-05-13 |
| USY9778 | - | 3 | 2026-05-11 |
| USY521 | - | 2 | 2026-06-06 |
| USY273 | - | 2 | 2026-06-02 |
| USY271 | - | 2 | 2026-06-19 |
| USY9777 | - | 1 | 2026-05-10 |
| USY9775 | - | 1 | 2026-05-09 |
| USY9773 | - | 1 | 2026-05-08 |
| USY9772 | - | 1 | 2026-05-07 |
| USY9771 | - | 1 | 2026-05-06 |
| USY272 | USC GmbH | 1 | 2026-05-26 |
| SLM3001 | - | 1 | 2026-06-15 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-19 | USY271 | - | Jun 19, 05:40 UTC | Jun 19, 07:39 UTC | 2h 0m |
| 2026-06-18 | USY271 | - | Jun 18, 14:45 UTC | Jun 19, 01:50 UTC | 11h 4m |
| 2026-06-18 | USY99P | AMS → DUB | Jun 18, 09:30 UTC | Jun 18, 10:45 UTC | 1h 15m |
| 2026-06-17 | SLM994 | - | Jun 17, 10:50 UTC | Jun 18, 05:50 UTC | 19h 0m |
| 2026-06-17 | SLM993 | - | Jun 17, 08:55 UTC | Jun 18, 05:50 UTC | 20h 55m |
| 2026-06-16 | SLM994 | - | Jun 16, 16:15 UTC | Jun 16, 18:05 UTC | 1h 50m |
| 2026-06-15 | SLM3001 | - | Jun 15, 20:50 UTC | Jun 16, 18:05 UTC | 21h 15m |
| 2026-06-15 | SLM994 | - | Jun 15, 07:35 UTC | Jun 15, 09:05 UTC | 1h 30m |
| 2026-06-14 | SLM994 | - | Jun 14, 10:50 UTC | Jun 15, 09:05 UTC | 22h 15m |
| 2026-06-14 | SLM993 | AMS → PBM | Jun 14, 09:25 UTC | Jun 15, 08:45 UTC | 23h 19m |
| 2026-06-13 | SLM994 | - | Jun 13, 04:45 UTC | Jun 13, 06:15 UTC | 1h 30m |
| 2026-06-12 | SLM993 | AMS → PBM | Jun 12, 09:05 UTC | Jun 13, 06:15 UTC | 21h 9m |
| 2026-06-12 | USY99P | CHR → RZE | Jun 12, 05:40 UTC | Jun 12, 06:30 UTC | 50m |
| 2026-06-08 | USY99P | CHR → RZE | Jun 8, 09:10 UTC | Jun 8, 22:40 UTC | 13h 30m |
| 2026-06-06 | USY521 | - | Jun 6, 23:00 UTC | Jun 7, 12:05 UTC | 13h 5m |
| 2026-06-06 | USY521 | - | Jun 6, 15:39 UTC | Jun 6, 20:10 UTC | 4h 30m |
| 2026-06-06 | USY99P | CHR → RZE | Jun 6, 09:39 UTC | Jun 6, 12:35 UTC | 2h 55m |
| 2026-06-06 | SLM994 | PBM → AMS | Jun 6, 05:35 UTC | Jun 6, 06:50 UTC | 1h 15m |
| 2026-06-05 | SLM993 | AMS → PBM | Jun 5, 09:15 UTC | Jun 6, 06:50 UTC | 21h 35m |
| 2026-06-04 | SLM994 | PBM → AMS | Jun 4, 06:10 UTC | Jun 4, 07:30 UTC | 1h 20m |
| 2026-06-03 | SLM994 | PBM → AMS | Jun 3, 10:50 UTC | Jun 4, 07:30 UTC | 20h 40m |
| 2026-06-03 | SLM993 | AMS → PBM | Jun 3, 10:35 UTC | Jun 4, 07:30 UTC | 20h 55m |
| 2026-06-02 | USY99P | CHR → RZE | Jun 2, 19:50 UTC | Jun 3, 07:30 UTC | 11h 40m |
| 2026-06-02 | USY273 | - | Jun 2, 03:45 UTC | Jun 2, 16:30 UTC | 12h 45m |
| 2026-06-01 | USY273 | - | Jun 1, 23:45 UTC | Jun 1, 23:55 UTC | 10m |
| 2026-05-26 | USY272 | JNB → MAN | May 26, 15:20 UTC | May 27, 07:55 UTC | 16h 35m |
| 2026-05-25 | USY99P | CHR → RZE | May 25, 10:35 UTC | May 25, 21:04 UTC | 10h 30m |
| 2026-05-15 | USY99P | CHR → RZE | May 15, 04:15 UTC | May 15, 13:00 UTC | 8h 45m |
| 2026-05-13 | USY5091 | NDJ → SDQ | May 13, 17:55 UTC | May 13, 21:00 UTC | 3h 5m |
| 2026-05-13 | USY5091 | NDJ → SDQ | May 13, 11:40 UTC | May 13, 15:15 UTC | 3h 35m |
| 2026-05-11 | USY9778 | - | May 11, 08:50 UTC | May 12, 03:10 UTC | 18h 20m |
| 2026-05-11 | USY9778 | - | May 11, 04:50 UTC | May 12, 03:10 UTC | 22h 21m |
| 2026-05-11 | USY9778 | - | May 11, 03:40 UTC | May 12, 02:45 UTC | 23h 6m |
| 2026-05-10 | USY9777 | - | May 10, 11:20 UTC | May 10, 16:04 UTC | 4h 45m |
| 2026-05-10 | USY099P | PAP → MTY | May 10, 02:14 UTC | May 10, 02:30 UTC | 15m |
| 2026-05-09 | USY9775 | - | May 9, 01:25 UTC | May 9, 17:45 UTC | 16h 20m |
| 2026-05-08 | USY9773 | - | May 8, 13:10 UTC | May 8, 18:20 UTC | 5h 10m |
| 2026-05-08 | USY099P | PAP → MTY | May 8, 06:45 UTC | May 8, 06:54 UTC | 10m |
| 2026-05-07 | USY099P | PAP → MTY | May 7, 12:30 UTC | May 7, 12:40 UTC | 10m |
| 2026-05-07 | USY9772 | - | May 7, 03:40 UTC | May 7, 09:45 UTC | 6h 5m |
| 2026-05-06 | USY9771 | - | May 6, 10:15 UTC | May 6, 15:30 UTC | 5h 15m |
| 2026-05-06 | USY099P | PAP → MTY | May 6, 06:45 UTC | May 6, 06:55 UTC | 10m |
| 2026-05-05 | USY099P | PAP → MTY | May 5, 12:45 UTC | May 5, 16:06 UTC | 3h 20m |
| 2026-04-24 | USY099P | PAP → MTY | Apr 24, 18:55 UTC | Apr 25, 03:10 UTC | 8h 15m |
| 2026-04-24 | USY5091 | NDJ → SDQ | Apr 24, 15:10 UTC | Apr 24, 15:20 UTC | 10m |
| 2026-04-24 | USY5091 | NDJ → SDQ | Apr 24, 11:05 UTC | Apr 24, 11:35 UTC | 30m |
| 2026-04-23 | USY099P | PAP → MTY | Apr 23, 01:05 UTC | Apr 23, 02:35 UTC | 1h 30m |
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 D-AUSC page for operator, model, and routing details .