sensors Mode-S transponder
4B15CA
ICAO 24-bit transponder address · allocated to Switzerland
Currently assigned to HB-IGO · DASSAULT Falcon 2000
- Hex
- 4B15CA
- Octal
- 22612712
- Decimal
- 4,920,778
- Country
- CH
- Tail
- HB-IGO
- Type
- F2TH
- Flights observed
- 54
- Distinct callsigns
- 2
- Country
- CH
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 4B15CA 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-17 | CAZ401 | - | Jun 17, 09:45 UTC | Jun 17, 11:00 UTC | 1h 15m |
| 2026-06-17 | CAZ401 | - | Jun 17, 07:25 UTC | Jun 17, 08:00 UTC | 35m |
| 2026-06-12 | CAZ401 | VIP → ZRH | Jun 12, 12:45 UTC | Jun 12, 13:15 UTC | 30m |
| 2026-06-12 | CAZ401 | - | Jun 12, 11:05 UTC | Jun 12, 12:10 UTC | 1h 5m |
| 2026-06-12 | CAZ401 | NCE → STN | Jun 12, 08:15 UTC | Jun 12, 10:05 UTC | 1h 50m |
| 2026-06-11 | CAZ401 | - | Jun 11, 17:25 UTC | Jun 11, 18:00 UTC | 35m |
| 2026-06-11 | CAZ401 | - | Jun 11, 14:45 UTC | Jun 11, 15:20 UTC | 35m |
| 2026-06-07 | CAZ401 | - | Jun 7, 12:15 UTC | Jun 7, 13:20 UTC | 1h 5m |
| 2026-06-06 | CAZ401 | - | Jun 6, 16:10 UTC | Jun 6, 16:39 UTC | 30m |
| 2026-06-06 | CAZ401 | - | Jun 6, 14:59 UTC | Jun 6, 15:39 UTC | 40m |
| 2026-06-06 | CAZ401 | - | Jun 6, 09:55 UTC | Jun 6, 10:39 UTC | 45m |
| 2026-06-06 | CAZ401 | ZRH → PSA | Jun 6, 08:30 UTC | Jun 6, 09:15 UTC | 45m |
| 2026-06-05 | CAZ401 | - | Jun 5, 14:25 UTC | Jun 5, 15:55 UTC | 1h 30m |
| 2026-06-05 | CAZ401 | - | Jun 5, 09:50 UTC | Jun 5, 11:25 UTC | 1h 35m |
| 2026-06-03 | CAZ401 | - | Jun 3, 16:15 UTC | Jun 3, 17:25 UTC | 1h 10m |
| 2026-06-03 | CAZ401 | - | Jun 3, 14:00 UTC | Jun 3, 14:30 UTC | 30m |
| 2026-06-03 | CAZ401 | - | Jun 3, 08:35 UTC | Jun 3, 09:25 UTC | 50m |
| 2026-06-02 | CAZ401 | - | Jun 2, 07:00 UTC | Jun 2, 07:45 UTC | 45m |
| 2026-06-02 | CAZ401 | ZRH → LJU | Jun 2, 04:45 UTC | Jun 2, 05:30 UTC | 45m |
| 2026-06-01 | CAZ401 | - | Jun 1, 09:30 UTC | Jun 1, 10:45 UTC | 1h 15m |
| 2026-06-01 | CAZ401 | ZRH → CIA | Jun 1, 06:35 UTC | Jun 1, 07:35 UTC | 1h 0m |
| 2026-05-31 | CAZ401 | - | May 31, 15:05 UTC | May 31, 16:25 UTC | 1h 20m |
| 2026-05-31 | CAZ401 | - | May 31, 11:00 UTC | May 31, 12:40 UTC | 1h 40m |
| 2026-05-30 | CAZ401 | - | May 30, 12:20 UTC | May 30, 14:05 UTC | 1h 45m |
| 2026-05-30 | CAZ401 | - | May 30, 08:25 UTC | May 30, 09:10 UTC | 45m |
| 2026-05-30 | CAZ401 | ZRH → SOU | May 30, 06:15 UTC | May 30, 07:35 UTC | 1h 20m |
| 2026-05-29 | CAZ401 | FAB → ZRH | May 29, 10:10 UTC | May 29, 11:20 UTC | 1h 10m |
| 2026-05-29 | CAZ401 | ZRH → FAB | May 29, 08:10 UTC | May 29, 09:30 UTC | 1h 20m |
| 2026-05-27 | CAZ401 | - | May 27, 10:15 UTC | May 27, 12:50 UTC | 2h 35m |
| 2026-05-27 | CAZ401 | - | May 27, 04:24 UTC | May 27, 06:49 UTC | 2h 25m |
| 2026-05-24 | CAZ401 | - | May 24, 12:25 UTC | May 24, 15:25 UTC | 3h 0m |
| 2026-05-20 | CAZ401 | - | May 20, 15:35 UTC | May 20, 17:45 UTC | 2h 10m |
| 2026-05-20 | CAZ401 | ZRH → GVA | May 20, 14:10 UTC | May 20, 14:40 UTC | 30m |
| 2026-05-17 | CAZ401 | - | May 17, 15:15 UTC | May 17, 16:25 UTC | 1h 10m |
| 2026-05-17 | CAZ401 | ZRH → FAB | May 17, 13:05 UTC | May 17, 14:25 UTC | 1h 20m |
| 2026-05-15 | CAZ401 | - | May 15, 09:05 UTC | May 15, 11:05 UTC | 2h 0m |
| 2026-05-14 | CAZ401 | - | May 14, 18:40 UTC | May 14, 20:40 UTC | 2h 0m |
| 2026-05-14 | CAZ401 | - | May 14, 14:55 UTC | May 14, 16:20 UTC | 1h 25m |
| 2026-05-14 | CAZ401 | ZRH → FAB | May 14, 12:10 UTC | May 14, 13:30 UTC | 1h 20m |
| 2026-05-12 | CAZ402 | LEJ → ZRH | May 12, 16:55 UTC | May 12, 17:50 UTC | 55m |
| 2026-05-12 | CAZ402 | ZRH → LEJ | May 12, 15:05 UTC | May 12, 16:00 UTC | 55m |
| 2026-05-12 | CAZ401 | - | May 12, 11:50 UTC | May 12, 12:35 UTC | 45m |
| 2026-05-12 | CAZ401 | ZRH → GOA | May 12, 09:40 UTC | May 12, 10:15 UTC | 35m |
| 2026-05-09 | CAZ401 | - | May 9, 09:05 UTC | May 9, 11:25 UTC | 2h 20m |
| 2026-05-08 | CAZ401 | - | May 8, 11:14 UTC | May 8, 13:35 UTC | 2h 20m |
| 2026-05-07 | CAZ401 | ZRH → BER | May 7, 15:05 UTC | May 7, 16:10 UTC | 1h 5m |
| 2026-05-07 | CAZ401 | - | May 7, 08:05 UTC | May 7, 08:45 UTC | 40m |
| 2026-05-06 | CAZ401 | VIE → MUC | May 6, 13:55 UTC | May 6, 14:40 UTC | 45m |
| 2026-05-05 | CAZ401 | ZRH → VIE | May 5, 18:35 UTC | May 5, 19:35 UTC | 1h 0m |
| 2026-05-03 | CAZ401 | - | May 3, 16:20 UTC | May 3, 18:00 UTC | 1h 40m |
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-IGO page for operator, model, and routing details .