sensors Mode-S transponder
4B18EE
ICAO 24-bit transponder address · allocated to Switzerland
Currently assigned to HB-JLM · BOMBARDIER BD-100 Challenger 350
- Hex
- 4B18EE
- Octal
- 22614356
- Decimal
- 4,921,582
- Country
- CH
- Tail
- HB-JLM
- Type
- CL35
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- CH
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4B18EE 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 |
|---|---|---|---|
| HBJLM | - | 48 | 2026-06-01 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | HBJLM | - | Jun 1, 08:50 UTC | Jun 1, 09:35 UTC | 45m |
| 2026-06-01 | HBJLM | - | Jun 1, 06:15 UTC | Jun 1, 07:00 UTC | 45m |
| 2026-05-30 | HBJLM | MXP → GVA | May 30, 07:05 UTC | May 30, 07:35 UTC | 30m |
| 2026-05-28 | HBJLM | - | May 28, 19:25 UTC | May 29, 10:45 UTC | 15h 20m |
| 2026-05-27 | HBJLM | - | May 27, 21:25 UTC | May 27, 23:45 UTC | 2h 20m |
| 2026-05-26 | HBJLM | - | May 26, 08:45 UTC | May 27, 02:54 UTC | 18h 10m |
| 2026-05-26 | HBJLM | - | May 26, 05:20 UTC | May 27, 01:29 UTC | 20h 10m |
| 2026-05-24 | HBJLM | - | May 24, 19:00 UTC | May 24, 21:45 UTC | 2h 45m |
| 2026-05-23 | HBJLM | - | May 23, 21:00 UTC | May 23, 21:35 UTC | 35m |
| 2026-05-23 | HBJLM | - | May 23, 19:15 UTC | May 23, 19:25 UTC | 10m |
| 2026-05-23 | HBJLM | - | May 23, 14:55 UTC | May 23, 16:45 UTC | 1h 50m |
| 2026-05-22 | HBJLM | - | May 22, 21:35 UTC | May 22, 21:45 UTC | 10m |
| 2026-05-22 | HBJLM | - | May 22, 19:25 UTC | May 22, 19:40 UTC | 15m |
| 2026-05-22 | HBJLM | - | May 22, 14:30 UTC | May 22, 14:45 UTC | 15m |
| 2026-05-21 | HBJLM | - | May 21, 17:35 UTC | May 22, 14:45 UTC | 21h 10m |
| 2026-05-21 | HBJLM | - | May 21, 16:20 UTC | May 22, 14:45 UTC | 22h 25m |
| 2026-05-21 | HBJLM | - | May 21, 13:40 UTC | May 21, 14:15 UTC | 35m |
| 2026-05-20 | HBJLM | - | May 20, 19:25 UTC | May 20, 19:40 UTC | 15m |
| 2026-05-20 | HBJLM | - | May 20, 15:20 UTC | May 20, 16:20 UTC | 1h 0m |
| 2026-05-19 | HBJLM | - | May 19, 21:05 UTC | May 19, 22:30 UTC | 1h 25m |
| 2026-05-19 | HBJLM | - | May 19, 19:00 UTC | May 19, 19:15 UTC | 15m |
| 2026-05-19 | HBJLM | - | May 19, 15:30 UTC | May 19, 16:50 UTC | 1h 20m |
| 2026-05-19 | HBJLM | - | May 19, 13:20 UTC | May 19, 13:40 UTC | 20m |
| 2026-05-18 | HBJLM | - | May 18, 14:10 UTC | May 18, 15:10 UTC | 1h 0m |
| 2026-05-18 | HBJLM | - | May 18, 08:05 UTC | May 18, 13:30 UTC | 5h 25m |
| 2026-05-18 | HBJLM | - | May 18, 05:20 UTC | May 18, 07:20 UTC | 2h 0m |
| 2026-05-17 | HBJLM | - | May 17, 09:55 UTC | May 17, 11:55 UTC | 2h 0m |
| 2026-05-14 | HBJLM | - | May 14, 10:10 UTC | May 14, 12:00 UTC | 1h 50m |
| 2026-05-08 | HBJLM | LIN → GVA | May 8, 08:09 UTC | May 8, 08:44 UTC | 35m |
| 2026-05-07 | HBJLM | CPT → LIN | May 7, 18:45 UTC | May 8, 07:04 UTC | 12h 20m |
| 2026-05-07 | HBJLM | - | May 7, 06:10 UTC | May 7, 11:10 UTC | 5h 0m |
| 2026-05-05 | HBJLM | GVA → JNB | May 5, 19:15 UTC | May 6, 07:10 UTC | 11h 55m |
| 2026-04-29 | HBJLM | LCY → GVA | Apr 29, 14:25 UTC | Apr 29, 15:45 UTC | 1h 20m |
| 2026-04-28 | HBJLM | GVA → LCY | Apr 28, 06:05 UTC | Apr 28, 07:25 UTC | 1h 20m |
| 2026-04-26 | HBJLM | - | Apr 26, 16:30 UTC | Apr 26, 18:50 UTC | 2h 20m |
| 2026-04-26 | HBJLM | - | Apr 26, 12:10 UTC | Apr 26, 14:10 UTC | 2h 0m |
| 2026-04-23 | HBJLM | - | Apr 23, 15:40 UTC | Apr 23, 16:25 UTC | 45m |
| 2026-04-23 | HBJLM | - | Apr 23, 13:50 UTC | Apr 23, 15:00 UTC | 1h 10m |
| 2026-04-23 | HBJLM | - | Apr 23, 06:01 UTC | Apr 23, 07:20 UTC | 1h 20m |
| 2026-04-21 | HBJLM | - | Apr 21, 08:25 UTC | Apr 21, 10:40 UTC | 2h 15m |
| 2026-04-21 | HBJLM | - | Apr 21, 05:40 UTC | Apr 21, 07:50 UTC | 2h 10m |
| 2026-04-16 | HBJLM | - | Apr 16, 16:40 UTC | Apr 16, 17:10 UTC | 30m |
| 2026-04-16 | HBJLM | - | Apr 16, 14:10 UTC | Apr 16, 14:40 UTC | 30m |
| 2026-04-16 | HBJLM | ZRH → GVA | Apr 16, 08:19 UTC | Apr 16, 08:54 UTC | 35m |
| 2026-04-16 | HBJLM | GVA → ZRH | Apr 16, 06:15 UTC | Apr 16, 06:45 UTC | 30m |
| 2026-04-14 | HBJLM | - | Apr 14, 10:50 UTC | Apr 14, 12:15 UTC | 1h 25m |
| 2026-04-14 | HBJLM | - | Apr 14, 09:30 UTC | Apr 14, 11:05 UTC | 1h 35m |
| 2026-04-14 | HBJLM | - | Apr 14, 05:15 UTC | Apr 14, 07:10 UTC | 1h 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 HB-JLM page for operator, model, and routing details .