sensors Mode-S transponder
3E23C7
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-IETB · RAYTHEON 390 Premier 1
- Hex
- 3E23C7
- Octal
- 17421707
- Decimal
- 4,072,391
- Country
- DE
- Tail
- D-IETB
- Type
- PRM1
- Flights observed
- 60
- Distinct callsigns
- 1
- Country
- DE
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 3E23C7 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| DIETB | - | 60 | 2026-07-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-22 | DIETB | - | Jul 22, 11:10 UTC | Jul 22, 12:45 UTC | 1h 35m |
| 2026-07-20 | DIETB | - | Jul 20, 14:50 UTC | Jul 20, 15:00 UTC | 10m |
| 2026-07-20 | DIETB | - | Jul 20, 12:55 UTC | Jul 20, 13:55 UTC | 1h 0m |
| 2026-07-20 | DIETB | - | Jul 20, 10:05 UTC | Jul 20, 11:05 UTC | 1h 0m |
| 2026-07-17 | DIETB | - | Jul 17, 16:15 UTC | Jul 17, 16:55 UTC | 40m |
| 2026-07-17 | DIETB | - | Jul 17, 14:15 UTC | Jul 17, 15:25 UTC | 1h 10m |
| 2026-07-16 | DIETB | - | Jul 16, 15:49 UTC | Jul 16, 16:35 UTC | 45m |
| 2026-07-16 | DIETB | - | Jul 16, 14:05 UTC | Jul 16, 14:50 UTC | 45m |
| 2026-07-15 | DIETB | BWE → SXB | Jul 15, 11:00 UTC | Jul 15, 11:55 UTC | 55m |
| 2026-07-14 | DIETB | - | Jul 14, 14:50 UTC | Jul 14, 15:35 UTC | 45m |
| 2026-07-14 | DIETB | WRO → BWE | Jul 14, 09:05 UTC | Jul 14, 09:55 UTC | 50m |
| 2026-07-13 | DIETB | - | Jul 13, 14:40 UTC | Jul 13, 16:25 UTC | 1h 45m |
| 2026-07-09 | DIETB | WRO → BQH | Jul 9, 09:10 UTC | Jul 9, 11:05 UTC | 1h 55m |
| 2026-07-09 | DIETB | - | Jul 9, 07:20 UTC | Jul 9, 07:50 UTC | 30m |
| 2026-07-03 | DIETB | - | Jul 3, 14:05 UTC | Jul 3, 15:05 UTC | 1h 0m |
| 2026-06-12 | DIETB | CGN → AGB | Jun 12, 17:50 UTC | Jun 12, 18:30 UTC | 40m |
| 2026-06-12 | DIETB | HAM → CGN | Jun 12, 15:45 UTC | Jun 12, 16:25 UTC | 40m |
| 2026-06-11 | DIETB | - | Jun 11, 09:20 UTC | Jun 11, 09:50 UTC | 30m |
| 2026-06-11 | DIETB | - | Jun 11, 07:00 UTC | Jun 11, 07:40 UTC | 40m |
| 2026-06-10 | DIETB | - | Jun 10, 11:20 UTC | Jun 10, 12:20 UTC | 1h 0m |
| 2026-06-08 | DIETB | - | Jun 8, 10:30 UTC | Jun 8, 11:35 UTC | 1h 5m |
| 2026-06-06 | DIETB | - | Jun 6, 15:39 UTC | Jun 6, 16:45 UTC | 1h 5m |
| 2026-06-03 | DIETB | - | Jun 3, 10:20 UTC | Jun 3, 11:15 UTC | 55m |
| 2026-05-29 | DIETB | POZ → BER | May 29, 16:50 UTC | May 29, 17:15 UTC | 25m |
| 2026-05-29 | DIETB | - | May 29, 14:40 UTC | May 29, 15:30 UTC | 50m |
| 2026-05-29 | DIETB | POZ → LNZ | May 29, 11:25 UTC | May 29, 12:20 UTC | 55m |
| 2026-05-29 | DIETB | - | May 29, 09:40 UTC | May 29, 10:10 UTC | 30m |
| 2026-05-25 | DIETB | - | May 25, 12:00 UTC | May 25, 12:10 UTC | 10m |
| 2026-05-25 | DIETB | MUC → BER | May 25, 10:20 UTC | May 25, 11:10 UTC | 50m |
| 2026-05-22 | DIETB | - | May 22, 13:00 UTC | May 22, 14:20 UTC | 1h 20m |
| 2026-05-22 | DIETB | - | May 22, 10:30 UTC | May 22, 11:50 UTC | 1h 20m |
| 2026-05-21 | DIETB | - | May 21, 09:05 UTC | May 21, 09:50 UTC | 45m |
| 2026-05-20 | DIETB | HAM → BER | May 20, 12:15 UTC | May 20, 12:45 UTC | 30m |
| 2026-05-20 | DIETB | NCE → HAM | May 20, 09:30 UTC | May 20, 11:15 UTC | 1h 45m |
| 2026-05-17 | DIETB | MAN → NCE | May 17, 15:05 UTC | May 17, 17:05 UTC | 2h 0m |
| 2026-05-17 | DIETB | NCE → MAN | May 17, 08:30 UTC | May 17, 10:35 UTC | 2h 5m |
| 2026-05-14 | DIETB | HAM → NCE | May 14, 09:20 UTC | May 14, 11:20 UTC | 2h 0m |
| 2026-05-12 | DIETB | NUE → HAM | May 12, 15:15 UTC | May 12, 16:10 UTC | 55m |
| 2026-05-12 | DIETB | - | May 12, 05:05 UTC | May 12, 05:55 UTC | 50m |
| 2026-05-11 | DIETB | - | May 11, 14:20 UTC | May 11, 14:55 UTC | 35m |
| 2026-05-06 | DIETB | - | May 6, 14:25 UTC | May 6, 14:55 UTC | 30m |
| 2026-05-06 | DIETB | - | May 6, 12:50 UTC | May 6, 13:50 UTC | 1h 0m |
| 2026-05-06 | DIETB | - | May 6, 11:00 UTC | May 6, 11:50 UTC | 50m |
| 2026-05-04 | DIETB | - | May 4, 18:00 UTC | May 4, 19:20 UTC | 1h 21m |
| 2026-05-04 | DIETB | - | May 4, 15:10 UTC | May 4, 16:35 UTC | 1h 25m |
| 2026-05-02 | DIETB | GWT → BER | May 2, 10:25 UTC | May 2, 11:15 UTC | 50m |
| 2026-05-02 | DIETB | - | May 2, 08:45 UTC | May 2, 09:40 UTC | 55m |
| 2026-05-02 | DIETB | - | May 2, 07:25 UTC | May 2, 08:05 UTC | 40m |
| 2026-05-01 | DIETB | - | May 1, 16:20 UTC | May 1, 17:50 UTC | 1h 30m |
| 2026-05-01 | DIETB | - | May 1, 13:25 UTC | May 1, 14:45 UTC | 1h 20m |
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-IETB page for operator, model, and routing details .