Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

096030

ICAO 24-bit transponder address · allocated to Cape Verde

Currently assigned to C9-AUV

Hex
096030
Octal
02260060
Decimal
614,448
Country
CV
Tail
C9-AUV
Type
DH8D
No current signal · last broadcast 8d ago
Flights observed
66
Distinct callsigns
7
Country
CV
Last broadcast
8d ago

Last known position

Most recent position reported by Mode-S 096030.

Country allocation

The ICAO 24-bit address 096030 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 7 distinct

Callsign Airline Flights Last seen
LAM305 LAM Mozambique Airlines 16 2026-07-25
LAM306 LAM Mozambique Airlines 14 2026-07-25
LAM302 - 13 2026-07-20
LAM301 - 13 2026-07-20
LAM122 - 2 2026-06-27
TM306 - 1 2026-06-22
TM305 - 1 2026-06-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-25 LAM306 JNB → MPM Jul 25, 17:40 UTCJul 25, 18:05 UTC25m
2026-07-25 LAM305 MPM → JNB Jul 25, 16:00 UTCJul 25, 16:20 UTC20m
2026-07-20 LAM305 MPM → JNB Jul 20, 19:10 UTCJul 20, 19:30 UTC20m
2026-07-20 LAM305 MPM → JNB Jul 20, 17:25 UTCJul 20, 17:55 UTC30m
2026-07-20 LAM302 - Jul 20, 10:45 UTCJul 20, 11:05 UTC20m
2026-07-20 LAM301 - Jul 20, 09:05 UTCJul 20, 09:35 UTC30m
2026-07-19 LAM306 JNB → MPM Jul 19, 19:00 UTCJul 19, 19:25 UTC25m
2026-07-19 LAM305 MPM → JNB Jul 19, 17:30 UTCJul 19, 18:00 UTC30m
2026-07-11 LAM306 JNB → MPM Jul 11, 18:00 UTCJul 11, 18:20 UTC20m
2026-07-11 LAM305 - Jul 11, 16:40 UTCJul 11, 17:05 UTC25m
2026-07-10 LAM306 JNB → MPM Jul 10, 18:25 UTCJul 10, 18:50 UTC25m
2026-07-10 LAM305 - Jul 10, 17:15 UTCJul 10, 17:40 UTC25m
2026-07-10 - - Jul 10, 10:35 UTCJul 10, 10:55 UTC20m
2026-07-10 - - Jul 10, 08:30 UTCJul 10, 09:00 UTC30m
2026-07-07 LAM306 JNB → MPM Jul 7, 17:50 UTCJul 7, 18:15 UTC25m
2026-07-07 LAM305 - Jul 7, 16:35 UTCJul 7, 16:55 UTC20m
2026-07-06 LAM306 JNB → MPM Jul 6, 19:45 UTCJul 6, 20:10 UTC25m
2026-07-06 LAM305 - Jul 6, 18:20 UTCJul 6, 18:45 UTC25m
2026-07-05 LAM306 JNB → MPM Jul 5, 17:50 UTCJul 5, 18:15 UTC25m
2026-07-05 LAM305 - Jul 5, 16:05 UTCJul 5, 16:35 UTC30m
2026-07-05 LAM302 - Jul 5, 07:00 UTCJul 5, 07:20 UTC20m
2026-07-05 LAM301 - Jul 5, 05:40 UTCJul 5, 06:00 UTC20m
2026-07-04 LAM306 JNB → MPM Jul 4, 18:10 UTCJul 4, 18:30 UTC20m
2026-07-04 LAM305 - Jul 4, 16:20 UTCJul 4, 16:45 UTC25m
2026-07-04 LAM302 - Jul 4, 06:55 UTCJul 4, 07:20 UTC25m
2026-07-04 LAM301 - Jul 4, 05:25 UTCJul 4, 05:55 UTC30m
2026-07-03 LAM306 JNB → MPM Jul 3, 18:15 UTCJul 3, 18:40 UTC25m
2026-07-03 LAM305 - Jul 3, 16:50 UTCJul 3, 17:20 UTC30m
2026-07-03 LAM302 - Jul 3, 07:20 UTCJul 3, 07:40 UTC20m
2026-07-03 LAM301 - Jul 3, 05:40 UTCJul 3, 06:10 UTC30m
2026-07-02 LAM302 - Jul 2, 07:20 UTCJul 2, 07:40 UTC20m
2026-07-02 LAM301 - Jul 2, 05:40 UTCJul 2, 06:00 UTC20m
2026-07-01 LAM302 JNB → MPM Jul 1, 09:55 UTCJul 1, 10:20 UTC25m
2026-07-01 LAM301 - Jul 1, 08:05 UTCJul 1, 08:35 UTC30m
2026-06-30 LAM306 JNB → MPM Jun 30, 17:50 UTCJun 30, 18:15 UTC25m
2026-06-30 LAM305 - Jun 30, 16:25 UTCJun 30, 16:55 UTC30m
2026-06-30 LAM302 JNB → MPM Jun 30, 07:05 UTCJun 30, 07:30 UTC25m
2026-06-30 LAM301 MPM → JNB Jun 30, 05:20 UTCJun 30, 05:50 UTC30m
2026-06-29 LAM306 JNB → MPM Jun 29, 17:55 UTCJun 29, 18:19 UTC25m
2026-06-29 LAM305 MPM → JNB Jun 29, 16:19 UTCJun 29, 16:50 UTC30m
2026-06-29 LAM302 JNB → MPM Jun 29, 07:05 UTCJun 29, 07:30 UTC25m
2026-06-29 LAM301 MPM → JNB Jun 29, 05:34 UTCJun 29, 06:05 UTC30m
2026-06-28 LAM306 JNB → MPM Jun 28, 18:05 UTCJun 28, 18:29 UTC25m
2026-06-28 LAM305 MPM → JNB Jun 28, 16:19 UTCJun 28, 16:45 UTC25m
2026-06-28 LAM302 JNB → MPM Jun 28, 08:09 UTCJun 28, 08:29 UTC20m
2026-06-28 LAM301 MPM → JNB Jun 28, 06:40 UTCJun 28, 07:09 UTC30m
2026-06-27 LAM122 - Jun 27, 17:59 UTCJun 27, 18:24 UTC25m
2026-06-27 LAM122 - Jun 27, 16:35 UTCJun 27, 17:09 UTC35m
2026-06-27 LAM302 JNB → MPM Jun 27, 09:40 UTCJun 27, 10:05 UTC25m
2026-06-27 LAM301 MPM → JNB Jun 27, 07:45 UTCJun 27, 08:14 UTC30m

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 C9-AUV page for operator, model, and routing details .

Mode-S 096030 frequently asked

What is Mode-S code 096030?
096030 is an ICAO 24-bit transponder address. Allocated to Cape Verde. Assigned to C9-AUV.
Where is Mode-S 096030 registered?
Mode-S code 096030 is allocated to Cape Verde (CV). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 096030 broadcasting right now?
No active broadcast right now. Last signal was 8d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 096030, octal 02260060, decimal 614,448.
What flights does 096030 operate?
Mode-S 096030 has broadcast 7 distinct callsigns, including LAM305, LAM306, LAM302, LAM301, LAM122.