sensors Mode-S transponder
096028
ICAO 24-bit transponder address · allocated to Cape Verde
Currently assigned to D4-CCJ · BOEING 737 MAX 8
- Hex
- 096028
- Octal
- 02260050
- Decimal
- 614,440
- Country
- CV
- Tail
- D4-CCJ
- Type
- B38M
- Flights observed
- 56
- Distinct callsigns
- 13
- Country
- CV
- Last broadcast
- 22d ago
Last known position
Country allocation
The ICAO 24-bit address 096028 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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TCV607 | TACV Cabo Verde Airlines | 10 | 2026-04-30 |
| TCV606 | TACV Cabo Verde Airlines | 10 | 2026-04-30 |
| TCV630 | TACV Cabo Verde Airlines | 9 | 2026-05-02 |
| TCV642 | TACV Cabo Verde Airlines | 5 | 2026-05-01 |
| TCV643 | TACV Cabo Verde Airlines | 4 | 2026-05-01 |
| TCV641 | TACV Cabo Verde Airlines | 3 | 2026-05-05 |
| TCV640 | TACV Cabo Verde Airlines | 3 | 2026-05-04 |
| TCV631 | TACV Cabo Verde Airlines | 3 | 2026-05-02 |
| TCV612 | TACV Cabo Verde Airlines | 3 | 2026-04-23 |
| TCV611 | TACV Cabo Verde Airlines | 3 | 2026-04-30 |
| TCV7000 | - | 1 | 2026-05-07 |
| TCV690 | TACV Cabo Verde Airlines | 1 | 2026-05-04 |
| TCV601 | TACV Cabo Verde Airlines | 1 | 2026-05-03 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-07 | TCV7000 | - | May 7, 10:00 UTC | May 7, 11:15 UTC | 1h 15m |
| 2026-05-05 | TCV641 | CDG → VXE | May 5, 16:30 UTC | May 5, 20:20 UTC | 3h 50m |
| 2026-05-04 | TCV640 | SID → CDG | May 4, 23:10 UTC | May 5, 14:50 UTC | 15h 40m |
| 2026-05-04 | TCV690 | RAI → PVD | May 4, 18:25 UTC | May 4, 19:05 UTC | 41m |
| 2026-05-03 | TCV601 | LIS → SID | May 3, 15:10 UTC | May 3, 17:00 UTC | 1h 50m |
| 2026-05-02 | TCV631 | BGY → SID | May 2, 18:25 UTC | May 3, 13:35 UTC | 19h 9m |
| 2026-05-02 | TCV630 | SID → BGY | May 2, 12:55 UTC | May 2, 16:40 UTC | 3h 45m |
| 2026-05-01 | TCV630 | SID → BGY | May 1, 20:05 UTC | May 2, 16:40 UTC | 20h 35m |
| 2026-05-01 | TCV630 | SID → BGY | May 1, 18:05 UTC | May 2, 16:40 UTC | 22h 36m |
| 2026-05-01 | TCV643 | CDG → SID | May 1, 17:30 UTC | May 2, 16:00 UTC | 22h 31m |
| 2026-05-01 | TCV642 | VXE → CDG | May 1, 12:05 UTC | May 1, 15:35 UTC | 3h 30m |
| 2026-04-30 | TCV607 | LIS → RAI | Apr 30, 20:10 UTC | Apr 30, 22:00 UTC | 1h 50m |
| 2026-04-30 | TCV611 | LIS → VXE | Apr 30, 08:40 UTC | Apr 30, 18:30 UTC | 9h 50m |
| 2026-04-30 | TCV606 | RAI → LIS | Apr 30, 05:10 UTC | Apr 30, 07:15 UTC | 2h 5m |
| 2026-04-29 | TCV607 | LIS → RAI | Apr 29, 15:30 UTC | Apr 29, 17:20 UTC | 1h 50m |
| 2026-04-29 | TCV606 | RAI → LIS | Apr 29, 11:40 UTC | Apr 29, 13:35 UTC | 1h 55m |
| 2026-04-27 | TCV641 | CDG → VXE | Apr 27, 10:45 UTC | Apr 27, 14:35 UTC | 3h 50m |
| 2026-04-26 | TCV640 | SID → CDG | Apr 26, 12:55 UTC | Apr 26, 16:20 UTC | 3h 25m |
| 2026-04-25 | TCV631 | BGY → SID | Apr 25, 18:40 UTC | Apr 25, 22:15 UTC | 3h 35m |
| 2026-04-25 | TCV630 | SID → BGY | Apr 25, 13:35 UTC | Apr 25, 17:05 UTC | 3h 30m |
| 2026-04-24 | TCV630 | SID → BGY | Apr 24, 20:35 UTC | Apr 25, 17:05 UTC | 20h 30m |
| 2026-04-24 | TCV630 | SID → BGY | Apr 24, 18:05 UTC | Apr 25, 17:05 UTC | 23h 0m |
| 2026-04-24 | TCV643 | CDG → SID | Apr 24, 17:30 UTC | Apr 25, 16:00 UTC | 22h 30m |
| 2026-04-24 | TCV642 | VXE → CDG | Apr 24, 12:00 UTC | Apr 24, 15:30 UTC | 3h 30m |
| 2026-04-23 | TCV607 | LIS → RAI | Apr 23, 20:15 UTC | Apr 23, 22:05 UTC | 1h 50m |
| 2026-04-23 | TCV612 | VXE → LIS | Apr 23, 08:15 UTC | Apr 23, 18:30 UTC | 10h 15m |
| 2026-04-23 | TCV606 | RAI → LIS | Apr 23, 05:10 UTC | Apr 23, 07:01 UTC | 1h 50m |
| 2026-04-22 | TCV607 | LIS → RAI | Apr 22, 14:50 UTC | Apr 22, 17:00 UTC | 2h 10m |
| 2026-04-22 | TCV606 | RAI → LIS | Apr 22, 11:25 UTC | Apr 22, 13:10 UTC | 1h 45m |
| 2026-04-20 | TCV641 | CDG → VXE | Apr 20, 10:45 UTC | Apr 20, 14:45 UTC | 4h 0m |
| 2026-04-19 | TCV640 | SID → CDG | Apr 19, 13:00 UTC | Apr 19, 16:40 UTC | 3h 40m |
| 2026-04-18 | TCV631 | BGY → SID | Apr 18, 19:10 UTC | Apr 18, 23:05 UTC | 3h 55m |
| 2026-04-18 | TCV630 | - | Apr 18, 13:10 UTC | Apr 18, 16:50 UTC | 3h 40m |
| 2026-04-17 | TCV630 | - | Apr 17, 20:40 UTC | Apr 18, 16:50 UTC | 20h 10m |
| 2026-04-17 | TCV643 | - | Apr 17, 19:25 UTC | Apr 17, 21:05 UTC | 1h 40m |
| 2026-04-17 | TCV630 | - | Apr 17, 18:05 UTC | Apr 18, 16:50 UTC | 22h 45m |
| 2026-04-17 | TCV643 | - | Apr 17, 17:20 UTC | Apr 18, 16:00 UTC | 22h 40m |
| 2026-04-17 | TCV642 | - | Apr 17, 15:20 UTC | Apr 17, 15:30 UTC | 10m |
| 2026-04-17 | TCV642 | - | Apr 17, 13:20 UTC | Apr 17, 15:15 UTC | 1h 54m |
| 2026-04-17 | TCV642 | - | Apr 17, 11:55 UTC | Apr 17, 13:15 UTC | 1h 20m |
| 2026-04-16 | TCV607 | - | Apr 16, 21:24 UTC | Apr 16, 22:05 UTC | 40m |
| 2026-04-16 | TCV607 | - | Apr 16, 20:15 UTC | Apr 16, 20:50 UTC | 35m |
| 2026-04-16 | TCV612 | - | Apr 16, 17:15 UTC | Apr 16, 18:35 UTC | 1h 20m |
| 2026-04-16 | TCV612 | - | Apr 16, 16:55 UTC | Apr 16, 17:10 UTC | 15m |
| 2026-04-16 | TCV611 | - | Apr 16, 09:15 UTC | Apr 16, 09:59 UTC | 45m |
| 2026-04-16 | TCV611 | - | Apr 16, 08:04 UTC | Apr 16, 08:35 UTC | 30m |
| 2026-04-16 | TCV606 | RAI → LIS | Apr 16, 05:09 UTC | Apr 16, 06:45 UTC | 1h 35m |
| 2026-04-16 | TCV606 | RAI → LIS | Apr 16, 04:54 UTC | Apr 16, 05:05 UTC | 10m |
| 2026-04-15 | TCV607 | - | Apr 15, 15:05 UTC | Apr 15, 16:40 UTC | 1h 35m |
| 2026-04-15 | TCV606 | RAI → LIS | Apr 15, 11:15 UTC | Apr 15, 12:55 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 D4-CCJ page for operator, model, and routing details .