Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

4911F3

ICAO 24-bit transponder address · allocated to Portugal

Currently assigned to CS-DOS · CESSNA 525B Citation CJ3

Hex
4911F3
Octal
22210763
Decimal
4,788,723
Country
PT
Tail
CS-DOS
Type
C25B
No current signal · last broadcast 1d ago
Flights observed
78
Distinct callsigns
20
Country
PT
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 4911F3.

Country allocation

The ICAO 24-bit address 4911F3 falls within the block assigned to Portugal (PT) by ICAO Annex 10, Volume III. Every aircraft registered in Portugal 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 20 distinct

Callsign Airline Flights Last seen
VVV351 - 11 2026-07-16
VVV321 - 10 2026-07-06
VVV361 - 8 2026-07-10
VVV371 - 6 2026-07-11
VVV341 - 6 2026-07-15
VVV331 - 5 2026-07-14
VVV372 - 4 2026-07-11
VVV362 - 4 2026-07-10
VVV352 - 4 2026-07-02
VVV342 - 3 2026-07-15
VVV312 - 3 2026-07-12
VVV311 - 3 2026-07-05
VVV332 - 2 2026-06-30
VVV353 - 1 2026-07-02
VVV343 - 1 2026-07-01
VVV322 - 1 2026-06-08
VVV314 - 1 2026-06-14
VVV313 - 1 2026-06-14
VVV232 - 1 2026-06-09
VVV231 - 1 2026-06-09

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-16 VVV351 - Jul 16, 16:19 UTCJul 16, 17:20 UTC1h 0m
2026-07-15 VVV342 - Jul 15, 15:35 UTCJul 15, 16:25 UTC50m
2026-07-15 VVV341 - Jul 15, 05:00 UTCJul 15, 05:45 UTC45m
2026-07-14 VVV331 - Jul 14, 14:30 UTCJul 14, 15:45 UTC1h 15m
2026-07-12 VVV312 - Jul 12, 12:01 UTCJul 12, 13:30 UTC1h 30m
2026-07-11 VVV372 FNC → LEI Jul 11, 14:25 UTCJul 11, 16:30 UTC2h 5m
2026-07-11 VVV371 - Jul 11, 11:10 UTCJul 11, 12:45 UTC1h 35m
2026-07-10 VVV362 - Jul 10, 19:40 UTCJul 10, 21:20 UTC1h 40m
2026-07-10 VVV361 - Jul 10, 17:55 UTCJul 10, 18:20 UTC25m
2026-07-09 VVV351 - Jul 9, 09:00 UTCJul 9, 10:35 UTC1h 35m
2026-07-06 VVV321 - Jul 6, 12:20 UTCJul 6, 15:00 UTC2h 40m
2026-07-05 VVV311 - Jul 5, 13:00 UTCJul 5, 15:40 UTC2h 40m
2026-07-03 VVV362 MAD → CAT Jul 3, 16:15 UTCJul 3, 17:20 UTC1h 5m
2026-07-03 VVV361 - Jul 3, 08:50 UTCJul 3, 09:55 UTC1h 5m
2026-07-02 VVV353 - Jul 2, 14:10 UTCJul 2, 15:05 UTC55m
2026-07-02 VVV352 - Jul 2, 09:30 UTCJul 2, 12:40 UTC3h 10m
2026-07-02 VVV351 - Jul 2, 07:05 UTCJul 2, 08:15 UTC1h 10m
2026-07-01 VVV343 CAT → BQH Jul 1, 17:25 UTCJul 1, 20:05 UTC2h 40m
2026-07-01 VVV342 - Jul 1, 13:05 UTCJul 1, 15:40 UTC2h 35m
2026-06-30 VVV332 - Jun 30, 10:35 UTCJun 30, 10:50 UTC15m
2026-06-30 VVV331 FAO → NHT Jun 30, 06:15 UTCJun 30, 08:55 UTC2h 40m
2026-06-29 VVV321 - Jun 29, 15:00 UTCJun 29, 15:30 UTC30m
2026-06-28 VVV321 - Jun 28, 14:30 UTCJun 28, 17:00 UTC2h 30m
2026-06-27 VVV372 - Jun 27, 12:19 UTCJun 27, 13:09 UTC50m
2026-06-27 VVV371 - Jun 27, 09:09 UTCJun 27, 10:00 UTC50m
2026-06-26 VVV362 - Jun 26, 18:49 UTCJun 26, 19:35 UTC45m
2026-06-26 VVV361 - Jun 26, 14:59 UTCJun 26, 17:25 UTC2h 25m
2026-06-25 VVV352 - Jun 25, 09:55 UTCJun 25, 10:15 UTC20m
2026-06-25 VVV351 - Jun 25, 05:20 UTCJun 25, 07:45 UTC2h 25m
2026-06-25 VVV342 - Jun 25, 03:29 UTCJun 25, 04:10 UTC40m
2026-06-24 VVV341 - Jun 24, 14:04 UTCJun 24, 16:34 UTC2h 30m
2026-06-22 VVV321 ATH → CAT Jun 22, 14:29 UTCJun 22, 18:49 UTC4h 20m
2026-06-21 VVV311 - Jun 21, 07:29 UTCJun 21, 11:44 UTC4h 15m
2026-06-14 VVV314 VLC → CAT Jun 14, 19:15 UTCJun 14, 20:40 UTC1h 25m
2026-06-14 VVV313 CAT → VLC Jun 14, 16:30 UTCJun 14, 17:45 UTC1h 15m
2026-06-14 VVV212 MAH → CAT Jun 14, 13:25 UTCJun 14, 15:25 UTC2h 0m
2026-06-14 VVV211 DBV → MAH Jun 14, 10:20 UTCJun 14, 12:20 UTC2h 0m
2026-06-09 VVV232 - Jun 9, 14:40 UTCJun 9, 14:55 UTC15m
2026-06-09 VVV231 - Jun 9, 10:25 UTCJun 9, 13:20 UTC2h 55m
2026-06-09 VVV331 - Jun 9, 06:25 UTCJun 9, 07:30 UTC1h 5m
2026-06-08 VVV322 - Jun 8, 15:30 UTCJun 8, 17:35 UTC2h 5m
2026-06-08 VVV321 - Jun 8, 12:05 UTCJun 8, 13:35 UTC1h 30m
2026-06-06 VVV371 FAO → LME Jun 6, 06:25 UTCJun 6, 08:30 UTC2h 5m
2026-06-04 VVV351 - Jun 4, 09:30 UTCJun 4, 12:30 UTC3h 0m
2026-06-04 VVV351 FAO → IOM Jun 4, 05:35 UTCJun 4, 08:30 UTC2h 55m
2026-06-03 VVV341 - Jun 3, 06:10 UTCJun 3, 08:55 UTC2h 45m
2026-06-01 VVV321 - Jun 1, 09:00 UTCJun 1, 11:25 UTC2h 25m
2026-05-30 VVV371 - May 30, 15:20 UTCMay 30, 17:25 UTC2h 5m
2026-05-29 VVV361 - May 29, 09:35 UTCMay 29, 12:00 UTC2h 25m
2026-05-28 VVV351 - May 28, 08:15 UTCMay 28, 10:15 UTC2h 0m

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

Mode-S 4911F3 frequently asked

What is Mode-S code 4911F3?
4911F3 is an ICAO 24-bit transponder address. Allocated to Portugal. Assigned to CS-DOS.
Where is Mode-S 4911F3 registered?
Mode-S code 4911F3 is allocated to Portugal (PT). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 4911F3 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 4911F3, octal 22210763, decimal 4,788,723.
What flights does 4911F3 operate?
Mode-S 4911F3 has broadcast 20 distinct callsigns, including VVV351, VVV321, VVV361, VVV371, VVV341.