sensors Mode-S transponder
491673
ICAO 24-bit transponder address · allocated to Portugal
Currently assigned to CS-ESS · BOMBARDIER BD-700 Global 7000/7500
- Hex
- 491673
- Octal
- 22213163
- Decimal
- 4,789,875
- Country
- PT
- Tail
- CS-ESS
- Type
- GL7T
- Flights observed
- 56
- Distinct callsigns
- 1
- Country
- PT
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 491673 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| JME750A | - | 56 | 2026-07-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | JME750A | OPO → CAT | Jul 12, 14:45 UTC | Jul 12, 15:25 UTC | 40m |
| 2026-07-10 | JME750A | - | Jul 10, 09:05 UTC | Jul 10, 09:45 UTC | 40m |
| 2026-07-09 | JME750A | - | Jul 9, 23:20 UTC | Jul 10, 08:05 UTC | 8h 45m |
| 2026-07-06 | JME750A | - | Jul 6, 14:10 UTC | Jul 6, 22:40 UTC | 8h 30m |
| 2026-07-06 | JME750A | CAT → LIS | Jul 6, 11:40 UTC | Jul 6, 11:55 UTC | 15m |
| 2026-07-04 | JME750A | OPO → CAT | Jul 4, 13:10 UTC | Jul 4, 13:55 UTC | 45m |
| 2026-07-04 | JME750A | FAO → OPO | Jul 4, 11:10 UTC | Jul 4, 12:05 UTC | 55m |
| 2026-06-27 | JME750A | FNC → FAO | Jun 27, 18:29 UTC | Jun 27, 19:49 UTC | 1h 20m |
| 2026-06-27 | JME750A | - | Jun 27, 17:09 UTC | Jun 27, 17:25 UTC | 15m |
| 2026-06-27 | JME750A | - | Jun 27, 16:10 UTC | Jun 27, 16:39 UTC | 30m |
| 2026-06-25 | JME750A | - | Jun 25, 19:09 UTC | Jun 25, 19:39 UTC | 30m |
| 2026-06-24 | JME750A | FAO → CAT | Jun 24, 17:20 UTC | Jun 24, 17:45 UTC | 25m |
| 2026-06-24 | JME750A | - | Jun 24, 15:05 UTC | Jun 24, 15:39 UTC | 35m |
| 2026-06-16 | JME750A | - | Jun 16, 14:50 UTC | Jun 16, 19:05 UTC | 4h 15m |
| 2026-06-16 | JME750A | - | Jun 16, 13:25 UTC | Jun 16, 13:44 UTC | 20m |
| 2026-06-15 | JME750A | - | Jun 15, 13:54 UTC | Jun 15, 14:10 UTC | 15m |
| 2026-06-15 | JME750A | - | Jun 15, 09:05 UTC | Jun 15, 13:15 UTC | 4h 10m |
| 2026-06-14 | JME750A | OPO → CAT | Jun 14, 15:00 UTC | Jun 14, 15:40 UTC | 40m |
| 2026-06-12 | JME750A | - | Jun 12, 08:30 UTC | Jun 12, 09:15 UTC | 45m |
| 2026-06-10 | JME750A | - | Jun 10, 22:10 UTC | Jun 11, 06:35 UTC | 8h 25m |
| 2026-06-07 | JME750A | - | Jun 7, 11:00 UTC | Jun 7, 18:35 UTC | 7h 35m |
| 2026-06-04 | JME750A | - | Jun 4, 09:30 UTC | Jun 4, 10:05 UTC | 35m |
| 2026-06-02 | JME750A | - | Jun 2, 15:45 UTC | Jun 2, 17:05 UTC | 1h 20m |
| 2026-06-01 | JME750A | - | Jun 1, 12:55 UTC | Jun 1, 14:10 UTC | 1h 15m |
| 2026-05-31 | JME750A | BUD → CAT | May 31, 11:20 UTC | May 31, 14:25 UTC | 3h 5m |
| 2026-05-31 | JME750A | - | May 31, 08:25 UTC | May 31, 08:50 UTC | 25m |
| 2026-05-29 | JME750A | BUD → BTS | May 29, 14:40 UTC | May 29, 15:00 UTC | 20m |
| 2026-05-29 | JME750A | - | May 29, 10:35 UTC | May 29, 13:45 UTC | 3h 10m |
| 2026-05-24 | JME750A | OPO → CAT | May 24, 15:05 UTC | May 24, 15:40 UTC | 35m |
| 2026-05-22 | JME750A | CAT → OPO | May 22, 09:40 UTC | May 22, 10:15 UTC | 35m |
| 2026-05-21 | JME750A | - | May 21, 23:10 UTC | May 22, 08:50 UTC | 9h 40m |
| 2026-05-18 | JME750A | - | May 18, 23:05 UTC | May 18, 23:20 UTC | 15m |
| 2026-05-18 | JME750A | - | May 18, 16:20 UTC | May 18, 16:25 UTC | 5m |
| 2026-05-14 | JME750A | LIS → GUA | May 14, 11:50 UTC | May 14, 21:55 UTC | 10h 5m |
| 2026-05-14 | JME750A | - | May 14, 09:00 UTC | May 14, 09:15 UTC | 15m |
| 2026-05-11 | JME750A | VLC → CAT | May 11, 15:20 UTC | May 11, 16:45 UTC | 1h 25m |
| 2026-05-11 | JME750A | - | May 11, 07:05 UTC | May 11, 08:10 UTC | 1h 5m |
| 2026-05-10 | JME750A | OPO → CAT | May 10, 18:29 UTC | May 10, 19:15 UTC | 45m |
| 2026-05-08 | JME750A | - | May 8, 08:59 UTC | May 8, 09:49 UTC | 50m |
| 2026-05-07 | JME750A | - | May 7, 15:45 UTC | May 7, 16:15 UTC | 30m |
| 2026-05-07 | JME750A | - | May 7, 15:05 UTC | May 7, 15:15 UTC | 10m |
| 2026-05-07 | JME750A | - | May 7, 09:20 UTC | May 7, 09:30 UTC | 10m |
| 2026-05-07 | JME750A | - | May 7, 07:55 UTC | May 7, 08:20 UTC | 25m |
| 2026-05-03 | JME750A | OPO → CAT | May 3, 15:20 UTC | May 3, 16:00 UTC | 40m |
| 2026-05-03 | JME750A | - | May 3, 12:00 UTC | May 3, 13:50 UTC | 1h 50m |
| 2026-04-30 | JME750A | OPO → FAB | Apr 30, 15:55 UTC | Apr 30, 17:30 UTC | 1h 35m |
| 2026-04-30 | JME750A | - | Apr 30, 14:05 UTC | Apr 30, 14:45 UTC | 40m |
| 2026-04-27 | JME750A | SVQ → CAT | Apr 27, 09:20 UTC | Apr 27, 10:10 UTC | 50m |
| 2026-04-27 | JME750A | FAO → SVQ | Apr 27, 07:35 UTC | Apr 27, 08:00 UTC | 25m |
| 2026-04-25 | JME750A | - | Apr 25, 13:05 UTC | Apr 25, 13:30 UTC | 25m |
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-ESS page for operator, model, and routing details .