sensors Mode-S transponder
4C8074
ICAO 24-bit transponder address · allocated to Cyprus
Currently assigned to 5B-CLY · PACIFIC AEROSPACE Cresco
- Hex
- 4C8074
- Octal
- 23100164
- Decimal
- 5,013,620
- Country
- CY
- Tail
- 5B-CLY
- Type
- CRES
- Flights observed
- 86
- Distinct callsigns
- 1
- Country
- CY
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 4C8074 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 |
|---|---|---|---|
| 5BCLY | - | 86 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | 5BCLY | - | Jul 17, 17:40 UTC | Jul 17, 18:00 UTC | 20m |
| 2026-07-17 | 5BCLY | - | Jul 17, 16:24 UTC | Jul 17, 17:05 UTC | 40m |
| 2026-07-17 | 5BCLY | - | Jul 17, 14:04 UTC | Jul 17, 15:20 UTC | 1h 15m |
| 2026-07-17 | 5BCLY | - | Jul 17, 09:50 UTC | Jul 17, 13:29 UTC | 3h 40m |
| 2026-07-15 | 5BCLY | - | Jul 15, 15:00 UTC | Jul 15, 15:10 UTC | 10m |
| 2026-07-15 | 5BCLY | - | Jul 15, 13:30 UTC | Jul 15, 14:05 UTC | 35m |
| 2026-07-15 | 5BCLY | - | Jul 15, 11:55 UTC | Jul 15, 12:40 UTC | 45m |
| 2026-07-15 | 5BCLY | - | Jul 15, 10:00 UTC | Jul 15, 11:15 UTC | 1h 15m |
| 2026-07-11 | 5BCLY | - | Jul 11, 17:00 UTC | Jul 11, 17:45 UTC | 45m |
| 2026-07-11 | 5BCLY | - | Jul 11, 09:10 UTC | Jul 11, 16:20 UTC | 7h 10m |
| 2026-07-10 | 5BCLY | - | Jul 10, 16:50 UTC | Jul 10, 17:40 UTC | 50m |
| 2026-07-10 | 5BCLY | - | Jul 10, 15:05 UTC | Jul 10, 15:55 UTC | 50m |
| 2026-07-10 | 5BCLY | - | Jul 10, 11:35 UTC | Jul 10, 14:15 UTC | 2h 40m |
| 2026-07-10 | 5BCLY | - | Jul 10, 09:55 UTC | Jul 10, 11:00 UTC | 1h 5m |
| 2026-07-08 | 5BCLY | - | Jul 8, 11:45 UTC | Jul 8, 15:50 UTC | 4h 5m |
| 2026-07-07 | 5BCLY | - | Jul 7, 18:50 UTC | Jul 7, 19:05 UTC | 15m |
| 2026-07-05 | 5BCLY | - | Jul 5, 11:50 UTC | Jul 5, 18:00 UTC | 6h 10m |
| 2026-07-03 | 5BCLY | - | Jul 3, 10:50 UTC | Jul 3, 11:35 UTC | 45m |
| 2026-07-03 | 5BCLY | - | Jul 3, 09:35 UTC | Jul 3, 10:20 UTC | 45m |
| 2026-07-02 | 5BCLY | - | Jul 2, 17:50 UTC | Jul 2, 18:10 UTC | 20m |
| 2026-07-02 | 5BCLY | - | Jul 2, 16:20 UTC | Jul 2, 16:40 UTC | 20m |
| 2026-07-02 | 5BCLY | - | Jul 2, 14:50 UTC | Jul 2, 15:10 UTC | 20m |
| 2026-07-02 | 5BCLY | - | Jul 2, 12:00 UTC | Jul 2, 12:20 UTC | 20m |
| 2026-06-29 | 5BCLY | - | Jun 29, 13:19 UTC | Jun 29, 15:49 UTC | 2h 30m |
| 2026-06-26 | 5BCLY | - | Jun 26, 12:10 UTC | Jun 26, 14:35 UTC | 2h 25m |
| 2026-06-26 | 5BCLY | - | Jun 26, 09:50 UTC | Jun 26, 11:09 UTC | 1h 20m |
| 2026-06-24 | 5BCLY | - | Jun 24, 17:45 UTC | Jun 24, 18:09 UTC | 25m |
| 2026-06-24 | 5BCLY | - | Jun 24, 15:14 UTC | Jun 24, 16:40 UTC | 1h 25m |
| 2026-06-24 | 5BCLY | - | Jun 24, 13:50 UTC | Jun 24, 14:39 UTC | 50m |
| 2026-06-24 | 5BCLY | - | Jun 24, 11:59 UTC | Jun 24, 13:05 UTC | 1h 5m |
| 2026-06-21 | 5BCLY | - | Jun 21, 15:09 UTC | Jun 21, 16:19 UTC | 1h 10m |
| 2026-06-21 | 5BCLY | - | Jun 21, 08:15 UTC | Jun 21, 14:19 UTC | 6h 5m |
| 2026-06-20 | 5BCLY | - | Jun 20, 15:04 UTC | Jun 20, 17:24 UTC | 2h 20m |
| 2026-06-20 | 5BCLY | - | Jun 20, 08:25 UTC | Jun 20, 14:19 UTC | 5h 55m |
| 2026-06-14 | 5BCLY | - | Jun 14, 08:30 UTC | Jun 14, 18:20 UTC | 9h 50m |
| 2026-06-13 | 5BCLY | - | Jun 13, 12:15 UTC | Jun 13, 18:35 UTC | 6h 20m |
| 2026-06-10 | 5BCLY | - | Jun 10, 11:45 UTC | Jun 10, 13:00 UTC | 1h 15m |
| 2026-06-05 | 5BCLY | - | Jun 5, 13:15 UTC | Jun 5, 13:35 UTC | 20m |
| 2026-06-05 | 5BCLY | - | Jun 5, 11:45 UTC | Jun 5, 12:35 UTC | 50m |
| 2026-05-31 | 5BCLY | - | May 31, 15:05 UTC | May 31, 15:30 UTC | 25m |
| 2026-05-31 | 5BCLY | - | May 31, 10:05 UTC | May 31, 14:30 UTC | 4h 25m |
| 2026-05-31 | 5BCLY | - | May 31, 08:50 UTC | May 31, 09:15 UTC | 25m |
| 2026-05-30 | 5BCLY | - | May 30, 15:15 UTC | May 30, 15:30 UTC | 15m |
| 2026-05-30 | 5BCLY | - | May 30, 13:30 UTC | May 30, 14:30 UTC | 1h 0m |
| 2026-05-30 | 5BCLY | - | May 30, 11:55 UTC | May 30, 12:40 UTC | 45m |
| 2026-05-30 | 5BCLY | - | May 30, 08:25 UTC | May 30, 10:20 UTC | 1h 55m |
| 2026-05-27 | 5BCLY | - | May 27, 13:50 UTC | May 27, 16:30 UTC | 2h 40m |
| 2026-05-27 | 5BCLY | - | May 27, 11:55 UTC | May 27, 13:15 UTC | 1h 20m |
| 2026-05-27 | 5BCLY | - | May 27, 09:45 UTC | May 27, 10:00 UTC | 15m |
| 2026-05-24 | 5BCLY | - | May 24, 14:35 UTC | May 24, 15:40 UTC | 1h 5m |
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 5B-CLY page for operator, model, and routing details .