sensors Mode-S transponder
3C450F
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-AAHO · EMBRAER EMB-135 Legacy
- Hex
- 3C450F
- Octal
- 17042417
- Decimal
- 3,949,839
- Country
- DE
- Tail
- D-AAHO
- Type
- E35L
- Flights observed
- 81
- Distinct callsigns
- 5
- Country
- DE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 3C450F 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 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | VJH763 | TLL → BTS | May 29, 13:10 UTC | May 29, 14:45 UTC | 1h 35m |
| 2026-05-28 | VJH763 | BUD → TLL | May 28, 15:55 UTC | May 28, 17:55 UTC | 2h 0m |
| 2026-05-28 | VJH763 | - | May 28, 10:55 UTC | May 28, 14:35 UTC | 3h 40m |
| 2026-05-27 | VJH763 | - | May 27, 09:10 UTC | May 27, 11:30 UTC | 2h 20m |
| 2026-05-26 | VJH763 | - | May 26, 04:04 UTC | May 26, 10:54 UTC | 6h 50m |
| 2026-05-25 | VJH763 | - | May 25, 11:50 UTC | May 26, 10:54 UTC | 23h 4m |
| 2026-05-25 | VJH763 | - | May 25, 09:50 UTC | May 26, 09:45 UTC | 23h 55m |
| 2026-05-25 | VJH763 | - | May 25, 08:40 UTC | May 26, 07:19 UTC | 22h 39m |
| 2026-05-24 | VJH763 | - | May 24, 14:00 UTC | May 24, 14:20 UTC | 20m |
| 2026-05-24 | VJH763 | - | May 24, 09:25 UTC | May 24, 13:00 UTC | 3h 35m |
| 2026-05-23 | VJH763 | - | May 23, 14:20 UTC | May 24, 13:00 UTC | 22h 40m |
| 2026-05-21 | VJH763 | - | May 21, 11:45 UTC | May 21, 17:40 UTC | 5h 55m |
| 2026-05-20 | VJH763 | - | May 20, 11:50 UTC | May 21, 11:45 UTC | 23h 55m |
| 2026-05-20 | VJH763 | - | May 20, 08:40 UTC | May 20, 12:50 UTC | 4h 10m |
| 2026-05-20 | VJH763 | NUE → NCE | May 20, 06:00 UTC | May 20, 07:10 UTC | 1h 10m |
| 2026-05-19 | VJH763 | - | May 19, 13:50 UTC | May 19, 17:10 UTC | 3h 20m |
| 2026-05-18 | VJH763 | - | May 18, 18:30 UTC | May 18, 22:10 UTC | 3h 40m |
| 2026-05-18 | VJH763 | - | May 18, 14:25 UTC | May 18, 16:10 UTC | 1h 45m |
| 2026-05-18 | VJH763 | BWE → BTS | May 18, 12:10 UTC | May 18, 13:15 UTC | 1h 5m |
| 2026-05-17 | VJH763 | - | May 17, 15:01 UTC | May 17, 16:15 UTC | 1h 15m |
| 2026-05-17 | VJH763 | - | May 17, 12:15 UTC | May 17, 13:50 UTC | 1h 35m |
| 2026-05-17 | VJH763 | - | May 17, 08:35 UTC | May 17, 09:50 UTC | 1h 15m |
| 2026-05-16 | VJH763 | LYN → PRG | May 16, 12:05 UTC | May 16, 13:21 UTC | 1h 15m |
| 2026-05-16 | VJH763 | MXP → LYN | May 16, 09:10 UTC | May 16, 09:45 UTC | 35m |
| 2026-05-15 | VJH042Y | BEG → MXP | May 15, 14:20 UTC | May 15, 15:55 UTC | 1h 34m |
| 2026-05-14 | VJH050T | ATH → BEG | May 14, 18:30 UTC | May 14, 19:50 UTC | 1h 20m |
| 2026-05-14 | VJH763 | - | May 14, 10:00 UTC | May 14, 12:05 UTC | 2h 5m |
| 2026-05-13 | VJH763 | - | May 13, 11:50 UTC | May 14, 11:45 UTC | 23h 55m |
| 2026-05-13 | VJH763 | - | May 13, 09:30 UTC | May 13, 12:55 UTC | 3h 25m |
| 2026-05-13 | VJH763 | - | May 13, 06:20 UTC | May 13, 07:15 UTC | 55m |
| 2026-05-10 | VJH763 | - | May 10, 09:24 UTC | May 10, 13:05 UTC | 3h 40m |
| 2026-05-09 | VJH763 | TBS → AMM | May 9, 09:10 UTC | May 9, 11:40 UTC | 2h 30m |
| 2026-05-03 | VJH763 | - | May 3, 18:34 UTC | May 3, 19:00 UTC | 25m |
| 2026-05-03 | VJH369K | - | May 3, 12:25 UTC | May 3, 16:40 UTC | 4h 15m |
| 2026-05-02 | VJH763 | FAO → STN | May 2, 16:40 UTC | May 2, 18:55 UTC | 2h 15m |
| 2026-05-02 | VJH763 | MLA → FAO | May 2, 12:40 UTC | May 2, 15:40 UTC | 3h 0m |
| 2026-05-01 | VJH763 | SVQ → MLA | May 1, 15:50 UTC | May 1, 18:05 UTC | 2h 15m |
| 2026-05-01 | VJH763 | BCN → SVQ | May 1, 13:30 UTC | May 1, 14:50 UTC | 1h 20m |
| 2026-04-30 | VJH763 | - | Apr 30, 18:45 UTC | Apr 30, 19:20 UTC | 35m |
| 2026-04-30 | VJH763 | - | Apr 30, 15:50 UTC | Apr 30, 17:25 UTC | 1h 35m |
| 2026-04-30 | VJH763 | BUD → FKB | Apr 30, 12:40 UTC | Apr 30, 13:55 UTC | 1h 15m |
| 2026-04-30 | VJH438H | - | Apr 30, 10:25 UTC | Apr 30, 11:00 UTC | 35m |
| 2026-04-29 | VJH763 | ZRH → KRK | Apr 29, 18:20 UTC | Apr 29, 19:35 UTC | 1h 15m |
| 2026-04-29 | VJH763 | - | Apr 29, 15:15 UTC | Apr 29, 16:50 UTC | 1h 35m |
| 2026-04-29 | VJH763 | FDH → FAB | Apr 29, 12:10 UTC | Apr 29, 13:40 UTC | 1h 30m |
| 2026-04-29 | VJH763 | - | Apr 29, 09:35 UTC | Apr 29, 11:15 UTC | 1h 40m |
| 2026-04-28 | VJH763 | - | Apr 28, 14:15 UTC | Apr 28, 17:15 UTC | 3h 0m |
| 2026-04-28 | VJH763 | - | Apr 28, 06:35 UTC | Apr 28, 11:25 UTC | 4h 50m |
| 2026-04-26 | VJH763 | - | Apr 26, 13:20 UTC | Apr 26, 14:20 UTC | 1h 0m |
| 2026-04-25 | VJH763 | - | Apr 25, 13:50 UTC | Apr 26, 13:45 UTC | 23h 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 D-AAHO page for operator, model, and routing details .