sensors Mode-S transponder
3F22CC
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-LZBW
- Hex
- 3F22CC
- Octal
- 17621314
- Decimal
- 4,137,676
- Country
- DE
- Tail
- D-LZBW
- Type
- SHIP
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- DE
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 3F22CC 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 |
|---|---|---|---|
| DLZBW | - | 49 | 2026-06-02 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | DLZBW | FDH → FDH | Jun 2, 06:35 UTC | Jun 2, 10:00 UTC | 3h 25m |
| 2026-06-01 | DLZBW | FDH → FDH | Jun 1, 06:35 UTC | Jun 1, 17:10 UTC | 10h 35m |
| 2026-05-30 | DLZBW | FDH → FDH | May 30, 06:40 UTC | May 30, 17:15 UTC | 10h 35m |
| 2026-05-28 | DLZBW | FDH → FDH | May 28, 09:45 UTC | May 28, 13:55 UTC | 4h 10m |
| 2026-05-28 | DLZBW | FDH → FDH | May 28, 07:25 UTC | May 28, 07:35 UTC | 10m |
| 2026-05-28 | DLZBW | FDH → FDH | May 28, 06:10 UTC | May 28, 06:20 UTC | 10m |
| 2026-05-27 | DLZBW | FDH → FDH | May 27, 06:40 UTC | May 27, 14:45 UTC | 8h 5m |
| 2026-05-26 | DLZBW | FDH → FDH | May 26, 06:44 UTC | May 26, 17:05 UTC | 10h 20m |
| 2026-05-25 | DLZBW | FDH → FDH | May 25, 06:40 UTC | May 25, 17:05 UTC | 10h 25m |
| 2026-05-24 | DLZBW | FDH → FDH | May 24, 06:40 UTC | May 24, 17:05 UTC | 10h 25m |
| 2026-05-23 | DLZBW | FDH → FDH | May 23, 06:35 UTC | May 23, 17:10 UTC | 10h 35m |
| 2026-05-22 | DLZBW | FDH → FDH | May 22, 06:40 UTC | May 22, 17:05 UTC | 10h 25m |
| 2026-05-21 | DLZBW | FDH → FDH | May 21, 06:40 UTC | May 21, 17:05 UTC | 10h 25m |
| 2026-05-20 | DLZBW | FDH → FDH | May 20, 06:10 UTC | May 20, 06:20 UTC | 10m |
| 2026-05-19 | DLZBW | FDH → FDH | May 19, 06:40 UTC | May 19, 17:15 UTC | 10h 35m |
| 2026-05-17 | DLZBW | FDH → FDH | May 17, 06:35 UTC | May 17, 17:05 UTC | 10h 30m |
| 2026-05-15 | DLZBW | FDH → FDH | May 15, 10:45 UTC | May 15, 13:05 UTC | 2h 20m |
| 2026-05-10 | DLZBW | FDH → FDH | May 10, 06:30 UTC | May 10, 14:25 UTC | 7h 55m |
| 2026-05-09 | DLZBW | FDH → FDH | May 9, 06:40 UTC | May 9, 17:30 UTC | 10h 50m |
| 2026-05-08 | DLZBW | FDH → FDH | May 8, 08:59 UTC | May 8, 17:05 UTC | 8h 5m |
| 2026-05-08 | DLZBW | FDH → FDH | May 8, 06:35 UTC | May 8, 07:44 UTC | 1h 10m |
| 2026-05-07 | DLZBW | FDH → FDH | May 7, 08:05 UTC | May 7, 16:40 UTC | 8h 35m |
| 2026-05-06 | DLZBW | FDH → FDH | May 6, 06:40 UTC | May 6, 11:40 UTC | 5h 0m |
| 2026-05-05 | DLZBW | FDH → FDH | May 5, 06:25 UTC | May 5, 13:20 UTC | 6h 55m |
| 2026-05-04 | DLZBW | - | May 4, 06:35 UTC | May 4, 14:40 UTC | 8h 5m |
| 2026-05-03 | DLZBW | - | May 3, 07:00 UTC | May 3, 17:00 UTC | 10h 0m |
| 2026-05-02 | DLZBW | - | May 2, 06:55 UTC | May 2, 17:00 UTC | 10h 5m |
| 2026-05-01 | DLZBW | - | May 1, 10:45 UTC | May 1, 17:15 UTC | 6h 30m |
| 2026-04-28 | DLZBW | FDH → FDH | Apr 28, 06:15 UTC | Apr 28, 10:25 UTC | 4h 10m |
| 2026-04-27 | DLZBW | FDH → FDH | Apr 27, 06:55 UTC | Apr 27, 17:15 UTC | 10h 20m |
| 2026-04-27 | DLZBW | FDH → FDH | Apr 27, 05:45 UTC | Apr 27, 06:05 UTC | 20m |
| 2026-04-26 | DLZBW | FDH → FDH | Apr 26, 06:40 UTC | Apr 26, 17:00 UTC | 10h 20m |
| 2026-04-25 | DLZBW | FDH → FDH | Apr 25, 06:35 UTC | Apr 25, 17:20 UTC | 10h 45m |
| 2026-04-24 | DLZBW | FDH → FDH | Apr 24, 06:55 UTC | Apr 24, 17:05 UTC | 10h 10m |
| 2026-04-23 | DLZBW | FDH → FDH | Apr 23, 06:30 UTC | Apr 23, 17:20 UTC | 10h 50m |
| 2026-04-20 | DLZBW | - | Apr 20, 07:05 UTC | Apr 20, 16:25 UTC | 9h 20m |
| 2026-04-19 | DLZBW | FDH → FDH | Apr 19, 06:35 UTC | Apr 19, 07:55 UTC | 1h 20m |
| 2026-04-18 | DLZBW | FDH → FDH | Apr 18, 18:10 UTC | Apr 18, 18:25 UTC | 15m |
| 2026-04-16 | DLZBW | - | Apr 16, 13:15 UTC | Apr 16, 14:35 UTC | 1h 20m |
| 2026-04-16 | DLZBW | - | Apr 16, 11:09 UTC | Apr 16, 13:05 UTC | 1h 55m |
| 2026-04-16 | DLZBW | - | Apr 16, 09:10 UTC | Apr 16, 11:04 UTC | 1h 55m |
| 2026-04-16 | DLZBW | - | Apr 16, 08:40 UTC | Apr 16, 09:05 UTC | 25m |
| 2026-04-15 | DLZBW | - | Apr 15, 15:05 UTC | Apr 15, 16:10 UTC | 1h 5m |
| 2026-04-15 | DLZBW | - | Apr 15, 13:01 UTC | Apr 15, 14:55 UTC | 1h 54m |
| 2026-04-15 | DLZBW | - | Apr 15, 11:00 UTC | Apr 15, 12:55 UTC | 1h 55m |
| 2026-04-15 | DLZBW | - | Apr 15, 09:00 UTC | Apr 15, 10:55 UTC | 1h 55m |
| 2026-04-15 | DLZBW | - | Apr 15, 07:10 UTC | Apr 15, 08:55 UTC | 1h 45m |
| 2026-04-14 | DLZBW | - | Apr 14, 12:50 UTC | Apr 14, 13:50 UTC | 1h 0m |
| 2026-04-14 | DLZBW | - | Apr 14, 11:40 UTC | Apr 14, 12:45 UTC | 1h 5m |
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-LZBW page for operator, model, and routing details .