sensors Mode-S transponder
4B1F4D
ICAO 24-bit transponder address · allocated to Switzerland
Currently assigned to HB-LWF · DIAMOND DA-42 Guardian
- Hex
- 4B1F4D
- Octal
- 22617515
- Decimal
- 4,923,213
- Country
- CH
- Tail
- HB-LWF
- Type
- DA42
- Flights observed
- 57
- Distinct callsigns
- 1
- Country
- CH
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 4B1F4D falls within the block assigned to Switzerland (CH) by ICAO Annex 10, Volume III. Every aircraft registered in Switzerland 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 |
|---|---|---|---|
| HBLWF | - | 57 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | HBLWF | - | Jul 24, 11:25 UTC | Jul 24, 12:30 UTC | 1h 5m |
| 2026-07-23 | HBLWF | - | Jul 23, 11:05 UTC | Jul 23, 12:10 UTC | 1h 5m |
| 2026-07-21 | HBLWF | BSL → JER | Jul 21, 12:20 UTC | Jul 21, 15:00 UTC | 2h 40m |
| 2026-07-16 | HBLWF | - | Jul 16, 14:50 UTC | Jul 16, 15:19 UTC | 30m |
| 2026-07-13 | HBLWF | ZRH → ZRH | Jul 13, 13:20 UTC | Jul 13, 13:30 UTC | 10m |
| 2026-07-12 | HBLWF | - | Jul 12, 14:01 UTC | Jul 12, 16:50 UTC | 2h 50m |
| 2026-07-12 | HBLWF | - | Jul 12, 07:45 UTC | Jul 12, 10:15 UTC | 2h 30m |
| 2026-07-09 | HBLWF | - | Jul 9, 17:35 UTC | Jul 9, 19:35 UTC | 2h 0m |
| 2026-07-09 | HBLWF | - | Jul 9, 11:20 UTC | Jul 9, 12:20 UTC | 1h 0m |
| 2026-07-06 | HBLWF | - | Jul 6, 13:10 UTC | Jul 6, 14:20 UTC | 1h 10m |
| 2026-07-04 | HBLWF | - | Jul 4, 11:10 UTC | Jul 4, 12:55 UTC | 1h 45m |
| 2026-07-04 | HBLWF | - | Jul 4, 06:40 UTC | Jul 4, 09:40 UTC | 3h 0m |
| 2026-07-03 | HBLWF | - | Jul 3, 11:10 UTC | Jul 3, 12:10 UTC | 1h 0m |
| 2026-07-03 | HBLWF | - | Jul 3, 07:40 UTC | Jul 3, 09:05 UTC | 1h 25m |
| 2026-07-02 | HBLWF | - | Jul 2, 11:20 UTC | Jul 2, 11:30 UTC | 10m |
| 2026-06-30 | HBLWF | - | Jun 30, 08:35 UTC | Jun 30, 09:55 UTC | 1h 20m |
| 2026-06-29 | HBLWF | - | Jun 29, 10:04 UTC | Jun 29, 10:15 UTC | 10m |
| 2026-06-29 | HBLWF | - | Jun 29, 08:44 UTC | Jun 29, 09:20 UTC | 35m |
| 2026-06-29 | HBLWF | - | Jun 29, 07:55 UTC | Jun 29, 08:04 UTC | 10m |
| 2026-06-28 | HBLWF | - | Jun 28, 12:55 UTC | Jun 28, 14:14 UTC | 1h 20m |
| 2026-06-28 | HBLWF | BSL → GWT | Jun 28, 07:20 UTC | Jun 28, 10:00 UTC | 2h 40m |
| 2026-06-27 | HBLWF | - | Jun 27, 12:29 UTC | Jun 27, 13:35 UTC | 1h 5m |
| 2026-06-25 | HBLWF | - | Jun 25, 07:45 UTC | Jun 25, 08:55 UTC | 1h 10m |
| 2026-06-24 | HBLWF | BRN → BSL | Jun 24, 07:44 UTC | Jun 24, 08:20 UTC | 35m |
| 2026-06-22 | HBLWF | BRN → BRN | Jun 22, 10:00 UTC | Jun 22, 11:39 UTC | 1h 40m |
| 2026-06-22 | HBLWF | - | Jun 22, 08:35 UTC | Jun 22, 09:00 UTC | 25m |
| 2026-06-20 | HBLWF | - | Jun 20, 08:14 UTC | Jun 20, 10:15 UTC | 2h 0m |
| 2026-06-19 | HBLWF | - | Jun 19, 14:59 UTC | Jun 19, 16:44 UTC | 1h 45m |
| 2026-06-18 | HBLWF | - | Jun 18, 08:20 UTC | Jun 18, 09:45 UTC | 1h 25m |
| 2026-06-15 | HBLWF | - | Jun 15, 08:54 UTC | Jun 15, 10:24 UTC | 1h 30m |
| 2026-06-12 | HBLWF | - | Jun 12, 16:20 UTC | Jun 12, 17:35 UTC | 1h 15m |
| 2026-06-10 | HBLWF | BRN → LUG | Jun 10, 16:35 UTC | Jun 10, 17:30 UTC | 55m |
| 2026-06-10 | HBLWF | BSL → BRN | Jun 10, 15:25 UTC | Jun 10, 15:55 UTC | 30m |
| 2026-06-10 | HBLWF | - | Jun 10, 07:50 UTC | Jun 10, 09:25 UTC | 1h 35m |
| 2026-06-08 | HBLWF | - | Jun 8, 13:20 UTC | Jun 8, 14:50 UTC | 1h 30m |
| 2026-06-07 | HBLWF | PRG → BSL | Jun 7, 12:10 UTC | Jun 7, 14:40 UTC | 2h 30m |
| 2026-06-05 | HBLWF | BSL → PRG | Jun 5, 13:20 UTC | Jun 5, 15:30 UTC | 2h 10m |
| 2026-05-26 | HBLWF | - | May 26, 16:59 UTC | May 26, 18:05 UTC | 1h 5m |
| 2026-05-26 | HBLWF | - | May 26, 12:24 UTC | May 26, 13:24 UTC | 1h 0m |
| 2026-05-26 | HBLWF | - | May 26, 08:59 UTC | May 26, 09:59 UTC | 1h 0m |
| 2026-05-24 | HBLWF | - | May 24, 11:40 UTC | May 24, 14:10 UTC | 2h 30m |
| 2026-05-22 | HBLWF | - | May 22, 07:20 UTC | May 22, 09:40 UTC | 2h 20m |
| 2026-05-21 | HBLWF | - | May 21, 15:10 UTC | May 21, 16:50 UTC | 1h 40m |
| 2026-05-17 | HBLWF | - | May 17, 14:45 UTC | May 17, 16:45 UTC | 2h 0m |
| 2026-05-16 | HBLWF | - | May 16, 07:16 UTC | May 16, 09:21 UTC | 2h 5m |
| 2026-05-10 | HBLWF | LEJ → BSL | May 10, 12:44 UTC | May 10, 14:45 UTC | 2h 0m |
| 2026-05-08 | HBLWF | - | May 8, 16:05 UTC | May 8, 18:00 UTC | 1h 55m |
| 2026-05-01 | HBLWF | - | May 1, 12:00 UTC | May 1, 12:15 UTC | 15m |
| 2026-05-01 | HBLWF | - | May 1, 09:20 UTC | May 1, 10:40 UTC | 1h 20m |
| 2026-05-01 | HBLWF | - | May 1, 08:20 UTC | May 1, 08:50 UTC | 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 HB-LWF page for operator, model, and routing details .