sensors Mode-S transponder
4B18E4
ICAO 24-bit transponder address · allocated to Switzerland
Currently assigned to HB-JLC · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4B18E4
- Octal
- 22614344
- Decimal
- 4,921,572
- Country
- CH
- Tail
- HB-JLC
- Type
- GLEX
- Flights observed
- 53
- Distinct callsigns
- 1
- Country
- CH
- Last broadcast
- 5d ago
Last known position
Country allocation
The ICAO 24-bit address 4B18E4 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 |
|---|---|---|---|
| SWW1C | - | 53 | 2026-07-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | SWW1C | RBA → GVA | Jul 20, 13:25 UTC | Jul 20, 15:35 UTC | 2h 10m |
| 2026-07-20 | SWW1C | GVA → RBA | Jul 20, 10:00 UTC | Jul 20, 12:35 UTC | 2h 35m |
| 2026-07-18 | SWW1C | - | Jul 18, 11:15 UTC | Jul 18, 12:35 UTC | 1h 20m |
| 2026-07-17 | SWW1C | - | Jul 17, 16:10 UTC | Jul 17, 18:29 UTC | 2h 20m |
| 2026-07-11 | SWW1C | - | Jul 11, 18:45 UTC | Jul 11, 20:25 UTC | 1h 40m |
| 2026-07-10 | SWW1C | - | Jul 10, 16:45 UTC | Jul 10, 17:30 UTC | 45m |
| 2026-07-10 | SWW1C | - | Jul 10, 09:45 UTC | Jul 10, 15:15 UTC | 5h 30m |
| 2026-07-02 | SWW1C | - | Jul 2, 11:50 UTC | Jul 2, 17:00 UTC | 5h 10m |
| 2026-07-02 | SWW1C | - | Jul 2, 08:40 UTC | Jul 2, 09:20 UTC | 40m |
| 2026-06-26 | SWW1C | KGS → GVA | Jun 26, 16:09 UTC | Jun 26, 18:39 UTC | 2h 30m |
| 2026-06-26 | SWW1C | - | Jun 26, 12:44 UTC | Jun 26, 15:25 UTC | 2h 40m |
| 2026-06-26 | SWW1C | - | Jun 26, 08:00 UTC | Jun 26, 08:40 UTC | 40m |
| 2026-06-25 | SWW1C | ZRH → NCE | Jun 25, 19:20 UTC | Jun 25, 20:05 UTC | 45m |
| 2026-06-23 | SWW1C | - | Jun 23, 18:04 UTC | Jun 23, 19:34 UTC | 1h 30m |
| 2026-06-22 | SWW1C | - | Jun 22, 09:04 UTC | Jun 22, 10:15 UTC | 1h 10m |
| 2026-06-21 | SWW1C | - | Jun 21, 15:59 UTC | Jun 21, 16:59 UTC | 1h 0m |
| 2026-06-21 | SWW1C | - | Jun 21, 13:44 UTC | Jun 21, 14:44 UTC | 1h 0m |
| 2026-06-19 | SWW1C | - | Jun 19, 18:05 UTC | Jun 19, 19:14 UTC | 1h 10m |
| 2026-06-19 | SWW1C | - | Jun 19, 15:49 UTC | Jun 19, 16:55 UTC | 1h 5m |
| 2026-06-18 | SWW1C | LBG → GVA | Jun 18, 18:15 UTC | Jun 18, 19:10 UTC | 55m |
| 2026-06-17 | SWW1C | - | Jun 17, 14:25 UTC | Jun 17, 15:15 UTC | 50m |
| 2026-06-11 | SWW1C | - | Jun 11, 18:40 UTC | Jun 11, 19:30 UTC | 50m |
| 2026-06-10 | SWW1C | - | Jun 10, 15:50 UTC | Jun 10, 16:40 UTC | 50m |
| 2026-06-08 | SWW1C | LBG → GVA | Jun 8, 08:15 UTC | Jun 8, 09:00 UTC | 45m |
| 2026-06-05 | SWW1C | - | Jun 5, 15:35 UTC | Jun 5, 16:20 UTC | 45m |
| 2026-06-05 | SWW1C | - | Jun 5, 11:00 UTC | Jun 5, 13:25 UTC | 2h 25m |
| 2026-06-04 | SWW1C | - | Jun 4, 11:05 UTC | Jun 5, 11:00 UTC | 23h 55m |
| 2026-06-04 | SWW1C | - | Jun 4, 10:35 UTC | Jun 4, 12:55 UTC | 2h 20m |
| 2026-06-02 | SWW1C | GVA → LBG | Jun 2, 15:50 UTC | Jun 3, 02:25 UTC | 10h 35m |
| 2026-06-01 | SWW1C | BER → GVA | Jun 1, 15:05 UTC | Jun 1, 16:20 UTC | 1h 15m |
| 2026-05-31 | SWW1C | GVA → BER | May 31, 17:55 UTC | May 31, 19:10 UTC | 1h 15m |
| 2026-05-28 | SWW1C | - | May 28, 03:00 UTC | May 28, 05:00 UTC | 2h 0m |
| 2026-05-22 | SWW1C | - | May 22, 11:55 UTC | May 22, 15:30 UTC | 3h 35m |
| 2026-05-21 | SWW1C | BSL → GVA | May 21, 11:20 UTC | May 21, 11:55 UTC | 35m |
| 2026-05-15 | SWW1C | GVA → BSL | May 15, 05:00 UTC | May 15, 05:35 UTC | 35m |
| 2026-05-15 | SWW1C | - | May 15, 02:40 UTC | May 15, 04:05 UTC | 1h 25m |
| 2026-05-13 | SWW1C | - | May 13, 20:00 UTC | May 13, 21:55 UTC | 1h 55m |
| 2026-05-13 | SWW1C | GVA → FAB | May 13, 07:15 UTC | May 13, 08:30 UTC | 1h 15m |
| 2026-05-11 | SWW1C | - | May 11, 14:50 UTC | May 11, 15:35 UTC | 45m |
| 2026-05-11 | SWW1C | - | May 11, 08:10 UTC | May 11, 08:55 UTC | 45m |
| 2026-05-10 | SWW1C | - | May 10, 12:59 UTC | May 10, 13:40 UTC | 40m |
| 2026-05-10 | SWW1C | - | May 10, 09:05 UTC | May 10, 09:45 UTC | 40m |
| 2026-05-06 | SWW1C | - | May 6, 13:10 UTC | May 6, 15:10 UTC | 2h 0m |
| 2026-05-06 | SWW1C | GVA → LIS | May 6, 09:45 UTC | May 6, 11:45 UTC | 2h 0m |
| 2026-05-05 | SWW1C | - | May 5, 02:30 UTC | May 5, 06:15 UTC | 3h 45m |
| 2026-05-02 | SWW1C | - | May 2, 17:45 UTC | May 2, 20:05 UTC | 2h 20m |
| 2026-04-30 | SWW1C | - | Apr 30, 15:55 UTC | May 1, 04:10 UTC | 12h 15m |
| 2026-04-27 | SWW1C | - | Apr 27, 05:10 UTC | Apr 27, 05:25 UTC | 15m |
| 2026-04-26 | SWW1C | - | Apr 26, 19:30 UTC | Apr 26, 23:25 UTC | 3h 55m |
| 2026-04-17 | SWW1C | - | Apr 17, 03:40 UTC | Apr 17, 05:00 UTC | 1h 21m |
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-JLC page for operator, model, and routing details .