sensors Mode-S transponder
3E0A42
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-HVBU · AIRBUS HELICOPTERS EC-135/635
- Hex
- 3E0A42
- Octal
- 17405102
- Decimal
- 4,065,858
- Country
- DE
- Tail
- D-HVBU
- Type
- EC35
- Flights observed
- 25
- Distinct callsigns
- 5
- Country
- DE
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 3E0A42 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 25
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-19 | BPO861 | - | Jun 19, 04:00 UTC | Jun 19, 04:39 UTC | 40m |
| 2026-06-19 | BPO861 | - | Jun 19, 03:20 UTC | Jun 19, 03:29 UTC | 10m |
| 2026-06-18 | BPO861 | - | Jun 18, 06:45 UTC | Jun 18, 07:05 UTC | 20m |
| 2026-06-16 | BPO861 | - | Jun 16, 07:15 UTC | Jun 16, 07:34 UTC | 20m |
| 2026-06-15 | BPO861 | - | Jun 15, 09:05 UTC | Jun 15, 09:30 UTC | 25m |
| 2026-06-12 | BPO861 | - | Jun 12, 04:35 UTC | Jun 12, 04:45 UTC | 10m |
| 2026-06-11 | BPO861 | - | Jun 11, 04:50 UTC | Jun 11, 05:10 UTC | 20m |
| 2026-06-05 | BPO861 | - | Jun 5, 03:05 UTC | Jun 5, 04:25 UTC | 1h 20m |
| 2026-06-04 | BPO861 | - | Jun 4, 04:05 UTC | Jun 4, 04:50 UTC | 45m |
| 2026-06-03 | BPO861 | - | Jun 3, 08:35 UTC | Jun 3, 09:40 UTC | 1h 5m |
| 2026-06-03 | BPO861 | - | Jun 3, 06:35 UTC | Jun 3, 07:30 UTC | 55m |
| 2026-06-03 | BPO861 | - | Jun 3, 03:25 UTC | Jun 3, 04:10 UTC | 45m |
| 2026-06-01 | BPO840 | - | Jun 1, 05:45 UTC | Jun 1, 06:40 UTC | 55m |
| 2026-05-30 | BPO860 | - | May 30, 19:40 UTC | May 30, 20:55 UTC | 1h 15m |
| 2026-05-28 | BPO860 | - | May 28, 19:15 UTC | May 28, 20:35 UTC | 1h 20m |
| 2026-05-28 | BPO843 | - | May 28, 08:20 UTC | May 28, 09:45 UTC | 1h 25m |
| 2026-05-27 | BPO860 | - | May 27, 23:10 UTC | May 27, 23:40 UTC | 30m |
| 2026-05-27 | BPO860 | - | May 27, 21:05 UTC | May 27, 22:25 UTC | 1h 20m |
| 2026-05-27 | BPO860 | - | May 27, 11:10 UTC | May 27, 11:25 UTC | 15m |
| 2026-05-27 | BPO860 | - | May 27, 07:45 UTC | May 27, 09:10 UTC | 1h 25m |
| 2026-05-26 | BPO860 | - | May 26, 19:10 UTC | May 26, 20:34 UTC | 1h 25m |
| 2026-04-24 | BPO820 | - | Apr 24, 08:40 UTC | Apr 24, 08:55 UTC | 15m |
| 2026-04-23 | BPO820 | - | Apr 23, 11:20 UTC | Apr 23, 12:30 UTC | 1h 10m |
| 2026-04-22 | BPO820 | - | Apr 22, 10:55 UTC | Apr 22, 11:15 UTC | 20m |
| 2026-04-22 | BPO820 | - | Apr 22, 06:01 UTC | Apr 22, 06:10 UTC | 10m |
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-HVBU page for operator, model, and routing details .