sensors Mode-S transponder
495066
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TCF · AIRBUS A-330-900
- Hex
- 495066
- Octal
- 22250146
- Decimal
- 4,804,710
- Country
- PT
- Tail
- CS-TCF
- Type
- A339
- Flights observed
- 118
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 495066 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 |
|---|---|---|---|
| OBS864 | - | 19 | 2026-07-13 |
| OBS851 | - | 19 | 2026-07-13 |
| OBS863 | - | 17 | 2026-07-12 |
| OBS852 | - | 14 | 2026-07-14 |
| OBS153P | Orbest | 9 | 2026-06-16 |
| OBS130P | - | 7 | 2026-07-10 |
| OBS162P | - | 6 | 2026-05-24 |
| OBS832 | - | 4 | 2026-07-10 |
| OBS831 | - | 3 | 2026-07-03 |
| OBS835 | - | 2 | 2026-07-08 |
| OBS137P | - | 2 | 2026-07-09 |
| EVE806 | - | 2 | 2026-06-11 |
| EVE804 | - | 2 | 2026-06-10 |
| EVE802 | Air Evex | 2 | 2026-05-03 |
| EVE801 | Air Evex | 2 | 2026-05-02 |
| ETR895 | Aerolíneas Estelar | 2 | 2026-05-01 |
| OBS832R | - | 1 | 2026-07-11 |
| OBS136P | - | 1 | 2026-06-24 |
| OBS125P | - | 1 | 2026-04-14 |
| EVE805 | - | 1 | 2026-06-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | OBS852 | - | Jul 14, 02:05 UTC | Jul 14, 02:25 UTC | 20m |
| 2026-07-13 | OBS851 | - | Jul 13, 15:10 UTC | Jul 13, 22:00 UTC | 6h 50m |
| 2026-07-13 | OBS864 | CUN → LIS | Jul 13, 02:50 UTC | Jul 13, 11:40 UTC | 8h 50m |
| 2026-07-12 | OBS863 | LIS → CUN | Jul 12, 15:25 UTC | Jul 13, 00:25 UTC | 9h 0m |
| 2026-07-11 | OBS832R | - | Jul 11, 14:35 UTC | Jul 11, 15:20 UTC | 45m |
| 2026-07-10 | OBS832 | LIS → OPO | Jul 10, 19:45 UTC | Jul 11, 12:55 UTC | 17h 10m |
| 2026-07-10 | OBS130P | - | Jul 10, 15:35 UTC | Jul 10, 16:30 UTC | 55m |
| 2026-07-09 | OBS137P | LIS → MAD | Jul 9, 14:05 UTC | Jul 9, 15:05 UTC | 1h 0m |
| 2026-07-08 | OBS835 | LIS → LIS | Jul 8, 13:05 UTC | Jul 9, 07:15 UTC | 18h 10m |
| 2026-07-08 | OBS864 | CUN → LIS | Jul 8, 00:40 UTC | Jul 8, 09:20 UTC | 8h 40m |
| 2026-07-07 | OBS863 | LIS → CUN | Jul 7, 12:50 UTC | Jul 7, 21:55 UTC | 9h 5m |
| 2026-07-06 | OBS852 | LIS → LIS | Jul 6, 15:25 UTC | Jul 7, 08:25 UTC | 17h 0m |
| 2026-07-06 | OBS864 | CUN → LIS | Jul 6, 02:40 UTC | Jul 6, 11:35 UTC | 8h 55m |
| 2026-07-05 | OBS863 | LIS → CUN | Jul 5, 14:55 UTC | Jul 5, 23:45 UTC | 8h 50m |
| 2026-07-03 | OBS831 | LIS → LIS | Jul 3, 19:50 UTC | Jul 4, 12:05 UTC | 16h 15m |
| 2026-07-03 | OBS130P | MAD → LIS | Jul 3, 15:15 UTC | Jul 3, 16:15 UTC | 1h 0m |
| 2026-07-02 | OBS137P | - | Jul 2, 11:15 UTC | Jul 2, 12:10 UTC | 55m |
| 2026-07-01 | OBS835 | LIS → LIS | Jul 1, 14:40 UTC | Jul 2, 07:35 UTC | 16h 55m |
| 2026-07-01 | OBS864 | CUN → LIS | Jul 1, 01:35 UTC | Jul 1, 10:30 UTC | 8h 55m |
| 2026-06-30 | OBS863 | LIS → CUN | Jun 30, 13:30 UTC | Jun 30, 22:40 UTC | 9h 10m |
| 2026-06-30 | OBS852 | - | Jun 30, 01:35 UTC | Jun 30, 08:35 UTC | 7h 0m |
| 2026-06-29 | OBS851 | - | Jun 29, 15:00 UTC | Jun 29, 22:00 UTC | 7h 0m |
| 2026-06-29 | OBS864 | CUN → LIS | Jun 29, 02:35 UTC | Jun 29, 11:25 UTC | 8h 50m |
| 2026-06-28 | OBS863 | LIS → CUN | Jun 28, 14:39 UTC | Jun 28, 23:39 UTC | 9h 0m |
| 2026-06-26 | OBS832 | AZS → LIS | Jun 26, 19:39 UTC | Jun 27, 12:09 UTC | 16h 30m |
| 2026-06-26 | OBS130P | MAD → LIS | Jun 26, 15:45 UTC | Jun 26, 16:39 UTC | 55m |
| 2026-06-24 | OBS136P | LIS → MAD | Jun 24, 13:40 UTC | Jun 25, 07:54 UTC | 18h 15m |
| 2026-06-24 | OBS864 | CUN → LIS | Jun 24, 01:09 UTC | Jun 24, 09:49 UTC | 8h 40m |
| 2026-06-23 | OBS863 | LIS → CUN | Jun 23, 13:45 UTC | Jun 23, 22:44 UTC | 9h 0m |
| 2026-06-23 | OBS852 | PUJ → LIS | Jun 23, 01:40 UTC | Jun 23, 08:25 UTC | 6h 45m |
| 2026-06-22 | OBS851 | LIS → PUJ | Jun 22, 14:45 UTC | Jun 22, 21:45 UTC | 7h 0m |
| 2026-06-22 | OBS864 | CUN → LIS | Jun 22, 03:30 UTC | Jun 22, 12:05 UTC | 8h 35m |
| 2026-06-21 | OBS863 | LIS → CUN | Jun 21, 15:09 UTC | Jun 22, 00:20 UTC | 9h 10m |
| 2026-06-21 | OBS852 | PUJ → LIS | Jun 21, 04:34 UTC | Jun 21, 11:24 UTC | 6h 50m |
| 2026-06-20 | OBS851 | LIS → PUJ | Jun 20, 17:10 UTC | Jun 21, 00:25 UTC | 7h 15m |
| 2026-06-19 | OBS832 | AZS → LIS | Jun 19, 17:34 UTC | Jun 20, 10:29 UTC | 16h 55m |
| 2026-06-19 | OBS130P | - | Jun 19, 14:59 UTC | Jun 19, 15:59 UTC | 1h 0m |
| 2026-06-16 | OBS153P | PUJ → MAD | Jun 16, 11:00 UTC | Jun 16, 11:55 UTC | 55m |
| 2026-06-16 | OBS852 | PUJ → LIS | Jun 16, 01:40 UTC | Jun 16, 08:44 UTC | 7h 5m |
| 2026-06-15 | OBS851 | LIS → PUJ | Jun 15, 16:19 UTC | Jun 15, 23:25 UTC | 7h 5m |
| 2026-06-14 | OBS864 | CUN → LIS | Jun 14, 15:35 UTC | Jun 15, 11:15 UTC | 19h 40m |
| 2026-06-14 | OBS863 | LIS → CUN | Jun 14, 14:55 UTC | Jun 15, 11:15 UTC | 20h 20m |
| 2026-06-13 | OBS851 | LIS → PUJ | Jun 13, 17:25 UTC | Jun 14, 11:20 UTC | 17h 55m |
| 2026-06-12 | OBS832 | AZS → LIS | Jun 12, 17:20 UTC | Jun 13, 10:10 UTC | 16h 49m |
| 2026-06-12 | OBS130P | - | Jun 12, 14:05 UTC | Jun 12, 15:05 UTC | 1h 0m |
| 2026-06-11 | EVE806 | - | Jun 11, 03:40 UTC | Jun 11, 18:25 UTC | 14h 45m |
| 2026-06-10 | EVE806 | - | Jun 10, 19:35 UTC | Jun 11, 18:25 UTC | 22h 50m |
| 2026-06-10 | EVE803 | - | Jun 10, 19:15 UTC | Jun 11, 17:30 UTC | 22h 15m |
| 2026-06-10 | EVE804 | - | Jun 10, 15:05 UTC | Jun 10, 16:40 UTC | 1h 35m |
| 2026-06-09 | EVE804 | - | Jun 9, 19:35 UTC | Jun 10, 16:40 UTC | 21h 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 CS-TCF page for operator, model, and routing details .