sensors Mode-S transponder
096023
ICAO 24-bit transponder address · allocated to Cape Verde
Currently assigned to D4-CCI · BOEING 737-700
- Hex
- 096023
- Octal
- 02260043
- Decimal
- 614,435
- Country
- CV
- Tail
- D4-CCI
- Type
- B737
- Flights observed
- 83
- Distinct callsigns
- 10
- Country
- CV
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 096023 falls within the block assigned to Cape Verde (CV) by ICAO Annex 10, Volume III. Every aircraft registered in Cape Verde 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 10 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TCV606 | - | 26 | 2026-06-23 |
| TCV607 | TACV Cabo Verde Airlines | 13 | 2026-06-24 |
| TCV612 | TACV Cabo Verde Airlines | 10 | 2026-06-19 |
| TCV601 | TACV Cabo Verde Airlines | 8 | 2026-06-13 |
| TCV640 | TACV Cabo Verde Airlines | 7 | 2026-06-20 |
| TCV641 | TACV Cabo Verde Airlines | 6 | 2026-06-15 |
| TCV611 | TACV Cabo Verde Airlines | 5 | 2026-06-18 |
| TCV605 | TACV Cabo Verde Airlines | 5 | 2026-06-23 |
| TCV631 | TACV Cabo Verde Airlines | 1 | 2026-05-30 |
| TCV630 | TACV Cabo Verde Airlines | 1 | 2026-05-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-24 | TCV607 | LIS → RAI | Jun 24, 15:24 UTC | Jun 24, 16:45 UTC | 1h 20m |
| 2026-06-23 | TCV605 | OPO → SID | Jun 23, 21:49 UTC | Jun 24, 13:20 UTC | 15h 30m |
| 2026-06-23 | TCV606 | - | Jun 23, 18:04 UTC | Jun 23, 19:55 UTC | 1h 50m |
| 2026-06-22 | - | - | Jun 22, 11:04 UTC | Jun 22, 14:49 UTC | 3h 45m |
| 2026-06-20 | TCV640 | SID → CDG | Jun 20, 18:14 UTC | Jun 21, 16:25 UTC | 22h 10m |
| 2026-06-20 | TCV606 | - | Jun 20, 14:29 UTC | Jun 20, 16:19 UTC | 1h 50m |
| 2026-06-19 | TCV607 | LIS → RAI | Jun 19, 15:19 UTC | Jun 19, 17:04 UTC | 1h 45m |
| 2026-06-19 | TCV612 | VXE → LIS | Jun 19, 11:34 UTC | Jun 19, 13:39 UTC | 2h 5m |
| 2026-06-18 | TCV612 | VXE → LIS | Jun 18, 14:50 UTC | Jun 19, 13:39 UTC | 22h 49m |
| 2026-06-18 | TCV611 | LIS → VXE | Jun 18, 14:15 UTC | Jun 19, 12:44 UTC | 22h 29m |
| 2026-06-18 | TCV606 | - | Jun 18, 10:55 UTC | Jun 18, 12:40 UTC | 1h 45m |
| 2026-06-17 | TCV607 | LIS → RAI | Jun 17, 15:10 UTC | Jun 17, 17:05 UTC | 1h 55m |
| 2026-06-17 | TCV606 | - | Jun 17, 11:15 UTC | Jun 17, 13:15 UTC | 2h 0m |
| 2026-06-16 | TCV605 | OPO → SID | Jun 16, 21:45 UTC | Jun 16, 23:30 UTC | 1h 45m |
| 2026-06-16 | TCV606 | - | Jun 16, 18:20 UTC | Jun 16, 20:10 UTC | 1h 51m |
| 2026-06-15 | TCV641 | CDG → VXE | Jun 15, 10:35 UTC | Jun 15, 14:00 UTC | 3h 25m |
| 2026-06-14 | TCV640 | SID → CDG | Jun 14, 12:55 UTC | Jun 14, 16:30 UTC | 3h 35m |
| 2026-06-13 | TCV601 | LIS → SID | Jun 13, 20:40 UTC | Jun 13, 21:10 UTC | 30m |
| 2026-06-13 | TCV601 | LIS → SID | Jun 13, 15:25 UTC | Jun 13, 17:15 UTC | 1h 50m |
| 2026-06-13 | TCV606 | - | Jun 13, 11:25 UTC | Jun 13, 13:30 UTC | 2h 5m |
| 2026-06-12 | TCV607 | LIS → RAI | Jun 12, 15:00 UTC | Jun 12, 16:50 UTC | 1h 50m |
| 2026-06-12 | TCV612 | VXE → LIS | Jun 12, 11:45 UTC | Jun 12, 13:30 UTC | 1h 45m |
| 2026-06-11 | TCV612 | VXE → LIS | Jun 11, 15:20 UTC | Jun 12, 13:30 UTC | 22h 11m |
| 2026-06-11 | TCV611 | LIS → VXE | Jun 11, 14:15 UTC | Jun 12, 12:45 UTC | 22h 31m |
| 2026-06-11 | TCV606 | RAI → LIS | Jun 11, 11:00 UTC | Jun 11, 12:55 UTC | 1h 55m |
| 2026-06-10 | TCV607 | LIS → RAI | Jun 10, 15:15 UTC | Jun 10, 17:05 UTC | 1h 50m |
| 2026-06-09 | TCV605 | OPO → SID | Jun 9, 21:05 UTC | Jun 10, 12:50 UTC | 15h 45m |
| 2026-06-09 | TCV606 | RAI → LIS | Jun 9, 18:20 UTC | Jun 9, 19:45 UTC | 1h 25m |
| 2026-06-08 | TCV641 | CDG → VXE | Jun 8, 10:55 UTC | Jun 8, 14:40 UTC | 3h 45m |
| 2026-06-07 | TCV640 | SID → CDG | Jun 7, 12:40 UTC | Jun 7, 16:30 UTC | 3h 50m |
| 2026-06-06 | TCV601 | LIS → SID | Jun 6, 15:34 UTC | Jun 6, 17:19 UTC | 1h 45m |
| 2026-06-06 | TCV606 | RAI → LIS | Jun 6, 11:19 UTC | Jun 6, 13:20 UTC | 2h 0m |
| 2026-06-05 | TCV606 | RAI → LIS | Jun 5, 16:50 UTC | Jun 6, 13:20 UTC | 20h 30m |
| 2026-06-05 | TCV606 | RAI → LIS | Jun 5, 15:25 UTC | Jun 6, 13:20 UTC | 21h 55m |
| 2026-06-05 | TCV612 | VXE → LIS | Jun 5, 11:55 UTC | Jun 5, 13:50 UTC | 1h 55m |
| 2026-06-04 | TCV611 | LIS → VXE | Jun 4, 14:55 UTC | Jun 5, 13:50 UTC | 22h 55m |
| 2026-06-04 | TCV606 | RAI → LIS | Jun 4, 11:15 UTC | Jun 4, 13:15 UTC | 2h 0m |
| 2026-06-03 | TCV606 | RAI → LIS | Jun 3, 14:50 UTC | Jun 4, 13:15 UTC | 22h 25m |
| 2026-06-03 | TCV607 | LIS → RAI | Jun 3, 14:35 UTC | Jun 4, 12:45 UTC | 22h 10m |
| 2026-06-03 | TCV606 | RAI → LIS | Jun 3, 10:55 UTC | Jun 3, 12:45 UTC | 1h 50m |
| 2026-06-03 | TCV605 | OPO → SID | Jun 3, 02:00 UTC | Jun 3, 02:15 UTC | 15m |
| 2026-06-02 | TCV605 | OPO → SID | Jun 2, 22:05 UTC | Jun 2, 23:55 UTC | 1h 50m |
| 2026-06-02 | TCV606 | RAI → LIS | Jun 2, 18:20 UTC | Jun 2, 20:15 UTC | 1h 55m |
| 2026-06-01 | TCV641 | CDG → VXE | Jun 1, 10:35 UTC | Jun 1, 14:15 UTC | 3h 40m |
| 2026-05-31 | TCV640 | SID → CDG | May 31, 12:35 UTC | May 31, 16:30 UTC | 3h 55m |
| 2026-05-30 | TCV631 | BGY → SID | May 30, 18:40 UTC | May 30, 22:25 UTC | 3h 45m |
| 2026-05-30 | TCV630 | SID → BGY | May 30, 13:15 UTC | May 30, 16:55 UTC | 3h 40m |
| 2026-05-29 | TCV607 | LIS → RAI | May 29, 15:10 UTC | May 29, 17:00 UTC | 1h 51m |
| 2026-05-29 | TCV612 | VXE → LIS | May 29, 11:30 UTC | May 29, 13:30 UTC | 2h 0m |
| 2026-05-28 | TCV612 | VXE → LIS | May 28, 14:50 UTC | May 29, 13:30 UTC | 22h 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 D4-CCI page for operator, model, and routing details .