sensors Mode-S transponder
495065
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-TCE · AIRBUS A-330-200
- Hex
- 495065
- Octal
- 22250145
- Decimal
- 4,804,709
- Country
- PT
- Tail
- CS-TCE
- Type
- A332
- Flights observed
- 47
- Distinct callsigns
- 20
- Country
- PT
- Last broadcast
- 37m ago
Last known position
Country allocation
The ICAO 24-bit address 495065 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 |
|---|---|---|---|
| AIZ992 | Arkia Israel Airlines | 3 | 2026-06-02 |
| AIZ991 | Arkia Israel Airlines | 3 | 2026-05-30 |
| SEY1008 | - | 2 | 2026-06-14 |
| SEY1007 | Air Seychelles | 2 | 2026-06-12 |
| ETD441 | Etihad Airways | 2 | 2026-06-18 |
| ETD440 | - | 2 | 2026-06-17 |
| AIZ335 | Arkia Israel Airlines | 2 | 2026-05-24 |
| AIZ292 | Arkia Israel Airlines | 2 | 2026-05-14 |
| AIZ291 | Arkia Israel Airlines | 2 | 2026-05-14 |
| AIZ105 | Arkia Israel Airlines | 2 | 2026-05-14 |
| HFY511P | - | 1 | 2026-06-02 |
| HFY511 | Hi Fly | 1 | 2026-06-02 |
| HFY271P | Hi Fly | 1 | 2026-06-07 |
| ETD2069 | - | 1 | 2026-06-14 |
| ETD160 | - | 1 | 2026-06-19 |
| ETD159 | - | 1 | 2026-06-18 |
| AIZ996 | Arkia Israel Airlines | 1 | 2026-05-21 |
| AIZ995 | Arkia Israel Airlines | 1 | 2026-05-19 |
| AIZ744 | Arkia Israel Airlines | 1 | 2026-05-24 |
| AIZ743 | Arkia Israel Airlines | 1 | 2026-05-24 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-19 | ETD160 | - | Jun 19, 10:19 UTC | Jun 19, 15:14 UTC | 4h 55m |
| 2026-06-18 | ETD159 | - | Jun 18, 23:25 UTC | Jun 19, 04:44 UTC | 5h 19m |
| 2026-06-18 | ETD441 | MNL → AUH | Jun 18, 11:35 UTC | Jun 18, 18:10 UTC | 6h 35m |
| 2026-06-17 | ETD440 | - | Jun 17, 20:35 UTC | Jun 18, 03:50 UTC | 7h 15m |
| 2026-06-16 | ETD441 | MNL → AUH | Jun 16, 11:35 UTC | Jun 16, 18:09 UTC | 6h 35m |
| 2026-06-15 | ETD440 | - | Jun 15, 20:59 UTC | Jun 16, 03:35 UTC | 6h 35m |
| 2026-06-14 | ETD2069 | - | Jun 14, 16:40 UTC | Jun 14, 23:15 UTC | 6h 34m |
| 2026-06-14 | SEY1008 | - | Jun 14, 09:35 UTC | Jun 14, 14:10 UTC | 4h 35m |
| 2026-06-12 | SEY1007 | CDG → SEZ | Jun 12, 20:40 UTC | Jun 13, 00:25 UTC | 3h 45m |
| 2026-06-12 | SEY1008 | SEZ → CDG | Jun 12, 10:20 UTC | Jun 12, 15:00 UTC | 4h 40m |
| 2026-06-07 | SEY1007 | CDG → SEZ | Jun 7, 18:00 UTC | Jun 7, 21:45 UTC | 3h 45m |
| 2026-06-07 | HFY271P | BYJ → ISL | Jun 7, 08:10 UTC | Jun 7, 11:55 UTC | 3h 45m |
| 2026-06-02 | HFY511P | RHO → AYT | Jun 2, 17:40 UTC | Jun 2, 18:20 UTC | 40m |
| 2026-06-02 | HFY511 | PRG → YYZ | Jun 2, 14:45 UTC | Jun 2, 16:00 UTC | 1h 15m |
| 2026-06-02 | AIZ992 | JFK → TLV | Jun 2, 00:35 UTC | Jun 2, 10:20 UTC | 9h 45m |
| 2026-05-30 | AIZ991 | TLV → JFK | May 30, 22:05 UTC | May 31, 09:35 UTC | 11h 30m |
| 2026-05-28 | AIZ992 | JFK → TLV | May 28, 21:25 UTC | May 29, 07:35 UTC | 10h 10m |
| 2026-05-27 | AIZ991 | TLV → JFK | May 27, 21:30 UTC | May 28, 08:30 UTC | 11h 0m |
| 2026-05-26 | AIZ992 | JFK → TLV | May 26, 23:39 UTC | May 27, 10:05 UTC | 10h 25m |
| 2026-05-25 | AIZ991 | TLV → JFK | May 25, 21:49 UTC | May 26, 09:15 UTC | 11h 25m |
| 2026-05-24 | AIZ744 | CDG → TLV | May 24, 21:05 UTC | May 24, 23:46 UTC | 2h 41m |
| 2026-05-24 | AIZ743 | TLV → CDG | May 24, 14:40 UTC | May 24, 18:55 UTC | 4h 15m |
| 2026-05-24 | AIZ336 | FCO → TLV | May 24, 09:30 UTC | May 24, 12:25 UTC | 2h 55m |
| 2026-05-24 | AIZ335 | TLV → FCO | May 24, 03:25 UTC | May 24, 06:30 UTC | 3h 5m |
| 2026-05-23 | AIZ1336 | FCO → TLV | May 23, 20:20 UTC | May 23, 23:10 UTC | 2h 50m |
| 2026-05-23 | AIZ335 | TLV → FCO | May 23, 15:20 UTC | May 23, 18:25 UTC | 3h 6m |
| 2026-05-22 | AIZ514 | AMS → TLV | May 22, 17:35 UTC | May 22, 21:35 UTC | 4h 0m |
| 2026-05-22 | AIZ513 | TLV → AMS | May 22, 10:55 UTC | May 22, 15:15 UTC | 4h 20m |
| 2026-05-21 | AIZ996 | JFK → TLV | May 21, 01:55 UTC | May 21, 12:00 UTC | 10h 5m |
| 2026-05-19 | AIZ995 | SOF → JFK | May 19, 21:25 UTC | May 20, 08:40 UTC | 11h 16m |
| 2026-05-19 | AIZ302 | LCA → TLV | May 19, 18:30 UTC | May 19, 19:20 UTC | 50m |
| 2026-05-14 | AIZ105 | TLV → RHO | May 14, 21:30 UTC | May 14, 22:15 UTC | 45m |
| 2026-05-14 | AIZ292 | BUD → TLV | May 14, 12:50 UTC | May 14, 15:35 UTC | 2h 45m |
| 2026-05-14 | AIZ291 | TLV → BUD | May 14, 06:30 UTC | May 14, 09:35 UTC | 3h 5m |
| 2026-05-14 | AIZ112 | CRA → TLV | May 14, 03:25 UTC | May 14, 04:05 UTC | 40m |
| 2026-05-10 | AIZ161 | TLV → LCA | May 10, 18:35 UTC | May 10, 19:19 UTC | 45m |
| 2026-05-10 | AIZ292 | BUD → TLV | May 10, 14:04 UTC | May 10, 16:55 UTC | 2h 50m |
| 2026-05-10 | AIZ291 | TLV → BUD | May 10, 06:35 UTC | May 10, 09:35 UTC | 3h 0m |
| 2026-05-10 | AIZ204 | - | May 10, 04:04 UTC | May 10, 04:45 UTC | 40m |
| 2026-05-07 | AIZ105 | TLV → RHO | May 7, 04:55 UTC | May 7, 05:20 UTC | 25m |
| 2026-05-07 | AIZ596 | HAN → TLV | May 7, 00:25 UTC | May 7, 02:35 UTC | 2h 10m |
| 2026-05-05 | AIZ595 | LCA → HAN | May 5, 15:20 UTC | May 5, 17:40 UTC | 2h 20m |
| 2026-05-05 | AIZ102 | MAD → MAD | May 5, 10:05 UTC | May 5, 11:55 UTC | 1h 50m |
| 2026-04-22 | AIZ101 | - | Apr 22, 17:15 UTC | Apr 22, 19:10 UTC | 1h 55m |
| 2026-04-22 | AIZ592 | BOM → BKK | Apr 22, 03:15 UTC | Apr 22, 15:15 UTC | 12h 0m |
| 2026-04-21 | AIZ591 | BOM → BKK | Apr 21, 14:01 UTC | Apr 22, 00:50 UTC | 10h 50m |
| 2026-04-21 | AIZ1160 | - | Apr 21, 11:05 UTC | Apr 21, 12:10 UTC | 1h 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-TCE page for operator, model, and routing details .