sensors Mode-S transponder
4C8092
ICAO 24-bit transponder address · allocated to Cyprus
Currently assigned to CAF-001 · EMBRAER EMB-135 Legacy
- Hex
- 4C8092
- Octal
- 23100222
- Decimal
- 5,013,650
- Country
- CY
- Tail
- CAF-001
- Type
- E35L
- Flights observed
- 56
- Distinct callsigns
- 1
- Country
- CY
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 4C8092 falls within the block assigned to Cyprus (CY) by ICAO Annex 10, Volume III. Every aircraft registered in Cyprus 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 |
|---|---|---|---|
| CAF001 | - | 56 | 2026-07-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | CAF001 | PFO → PFO | Jul 16, 08:30 UTC | Jul 16, 10:10 UTC | 1h 40m |
| 2026-07-14 | CAF001 | - | Jul 14, 16:45 UTC | Jul 14, 17:00 UTC | 15m |
| 2026-07-14 | CAF001 | - | Jul 14, 11:55 UTC | Jul 14, 15:50 UTC | 3h 55m |
| 2026-07-13 | CAF001 | LCA → LBG | Jul 13, 13:15 UTC | Jul 13, 17:50 UTC | 4h 35m |
| 2026-07-13 | CAF001 | PFO → LCA | Jul 13, 11:05 UTC | Jul 13, 11:35 UTC | 30m |
| 2026-07-07 | CAF001 | - | Jul 7, 16:50 UTC | Jul 7, 18:00 UTC | 1h 10m |
| 2026-07-07 | CAF001 | - | Jul 7, 15:00 UTC | Jul 7, 15:45 UTC | 45m |
| 2026-07-02 | CAF001 | - | Jul 2, 14:05 UTC | Jul 2, 15:45 UTC | 1h 40m |
| 2026-07-01 | CAF001 | - | Jul 1, 08:15 UTC | Jul 1, 10:05 UTC | 1h 50m |
| 2026-06-24 | CAF001 | - | Jun 24, 06:39 UTC | Jun 24, 07:54 UTC | 1h 15m |
| 2026-06-19 | CAF001 | - | Jun 19, 21:14 UTC | Jun 19, 21:24 UTC | 10m |
| 2026-06-19 | CAF001 | - | Jun 19, 16:04 UTC | Jun 19, 20:09 UTC | 4h 5m |
| 2026-06-18 | CAF001 | - | Jun 18, 04:35 UTC | Jun 18, 08:55 UTC | 4h 20m |
| 2026-06-18 | CAF001 | - | Jun 18, 02:45 UTC | Jun 18, 03:05 UTC | 20m |
| 2026-06-15 | CAF001 | - | Jun 15, 07:20 UTC | Jun 15, 08:35 UTC | 1h 15m |
| 2026-06-15 | CAF001 | - | Jun 15, 06:15 UTC | Jun 15, 06:49 UTC | 35m |
| 2026-06-12 | CAF001 | - | Jun 12, 11:40 UTC | Jun 12, 11:55 UTC | 15m |
| 2026-06-12 | CAF001 | - | Jun 12, 06:55 UTC | Jun 12, 10:30 UTC | 3h 35m |
| 2026-06-10 | CAF001 | - | Jun 10, 06:05 UTC | Jun 10, 10:15 UTC | 4h 10m |
| 2026-06-10 | CAF001 | PFO → LCA | Jun 10, 03:45 UTC | Jun 10, 04:05 UTC | 20m |
| 2026-06-08 | CAF001 | - | Jun 8, 06:05 UTC | Jun 8, 08:20 UTC | 2h 15m |
| 2026-06-05 | CAF001 | - | Jun 5, 13:20 UTC | Jun 5, 15:10 UTC | 1h 50m |
| 2026-06-05 | CAF001 | - | Jun 5, 06:00 UTC | Jun 5, 08:15 UTC | 2h 15m |
| 2026-06-03 | CAF001 | - | Jun 3, 07:45 UTC | Jun 3, 09:30 UTC | 1h 45m |
| 2026-06-02 | CAF001 | - | Jun 2, 12:40 UTC | Jun 2, 14:00 UTC | 1h 20m |
| 2026-05-19 | CAF001 | - | May 19, 12:30 UTC | May 19, 15:15 UTC | 2h 45m |
| 2026-05-16 | CAF001 | - | May 16, 17:40 UTC | May 16, 18:00 UTC | 20m |
| 2026-05-16 | CAF001 | - | May 16, 15:05 UTC | May 16, 16:25 UTC | 1h 20m |
| 2026-05-16 | CAF001 | - | May 16, 08:51 UTC | May 16, 09:25 UTC | 35m |
| 2026-05-16 | CAF001 | - | May 16, 05:10 UTC | May 16, 06:55 UTC | 1h 46m |
| 2026-05-14 | CAF001 | - | May 14, 17:50 UTC | May 14, 19:05 UTC | 1h 15m |
| 2026-05-14 | CAF001 | - | May 14, 10:35 UTC | May 14, 12:10 UTC | 1h 35m |
| 2026-05-14 | CAF001 | - | May 14, 08:25 UTC | May 14, 08:40 UTC | 15m |
| 2026-05-09 | CAF001 | - | May 9, 22:05 UTC | May 9, 22:20 UTC | 15m |
| 2026-05-09 | CAF001 | - | May 9, 18:40 UTC | May 9, 21:00 UTC | 2h 20m |
| 2026-05-09 | CAF001 | - | May 9, 10:10 UTC | May 9, 12:45 UTC | 2h 35m |
| 2026-05-09 | CAF001 | - | May 9, 08:10 UTC | May 9, 08:30 UTC | 20m |
| 2026-05-07 | CAF001 | - | May 7, 07:45 UTC | May 7, 08:30 UTC | 45m |
| 2026-05-06 | CAF001 | - | May 6, 14:35 UTC | May 6, 15:05 UTC | 30m |
| 2026-05-06 | CAF001 | - | May 6, 06:00 UTC | May 6, 07:05 UTC | 1h 5m |
| 2026-05-06 | CAF001 | - | May 6, 03:40 UTC | May 6, 03:55 UTC | 15m |
| 2026-05-04 | CAF001 | - | May 4, 11:15 UTC | May 4, 12:00 UTC | 45m |
| 2026-05-04 | CAF001 | - | May 4, 09:55 UTC | May 4, 10:25 UTC | 30m |
| 2026-04-30 | CAF001 | - | Apr 30, 12:10 UTC | Apr 30, 12:25 UTC | 15m |
| 2026-04-30 | CAF001 | - | Apr 30, 09:50 UTC | Apr 30, 11:10 UTC | 1h 20m |
| 2026-04-30 | CAF001 | - | Apr 30, 04:45 UTC | Apr 30, 06:20 UTC | 1h 35m |
| 2026-04-30 | CAF001 | - | Apr 30, 02:50 UTC | Apr 30, 03:00 UTC | 10m |
| 2026-04-28 | CAF001 | - | Apr 28, 08:35 UTC | Apr 28, 10:00 UTC | 1h 25m |
| 2026-04-28 | CAF001 | - | Apr 28, 06:50 UTC | Apr 28, 08:15 UTC | 1h 25m |
| 2026-04-24 | CAF001 | - | Apr 24, 15:05 UTC | Apr 24, 15:20 UTC | 15m |
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 CAF-001 page for operator, model, and routing details .