sensors Mode-S transponder
A7D35E
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N603L · BOMBARDIER CL-600 Challenger · operated by EGN LLC
- Hex
- A7D35E
- Octal
- 51751536
- Decimal
- 10,998,622
- Country
- US
- Tail
- N603L
- Type
- CL60
- Flights observed
- 44
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address A7D35E falls within the block assigned to United States (US) by ICAO Annex 10, Volume III. Every aircraft registered in United States 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 |
|---|---|---|---|
| TWY63 | - | 44 | 2026-07-19 |
Recent flights last 44
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-19 | TWY63 | - | Jul 19, 19:25 UTC | Jul 19, 22:05 UTC | 2h 40m |
| 2026-07-16 | TWY63 | - | Jul 16, 09:40 UTC | Jul 16, 10:10 UTC | 30m |
| 2026-07-16 | TWY63 | - | Jul 16, 07:35 UTC | Jul 16, 09:05 UTC | 1h 30m |
| 2026-07-16 | TWY63 | - | Jul 16, 03:00 UTC | Jul 16, 06:55 UTC | 3h 55m |
| 2026-07-15 | TWY63 | BED → LAS | Jul 15, 01:50 UTC | Jul 15, 06:40 UTC | 4h 50m |
| 2026-07-12 | TWY63 | - | Jul 12, 03:35 UTC | Jul 12, 04:05 UTC | 30m |
| 2026-07-11 | TWY63 | - | Jul 11, 23:55 UTC | Jul 12, 02:55 UTC | 3h 0m |
| 2026-07-08 | TWY63 | - | Jul 8, 16:35 UTC | Jul 8, 18:45 UTC | 2h 10m |
| 2026-07-06 | TWY63 | - | Jul 6, 23:30 UTC | Jul 7, 03:20 UTC | 3h 50m |
| 2026-07-06 | TWY63 | - | Jul 6, 15:10 UTC | Jul 6, 15:35 UTC | 25m |
| 2026-07-01 | TWY63 | - | Jul 1, 02:15 UTC | Jul 1, 04:35 UTC | 2h 20m |
| 2026-06-30 | TWY63 | BED → FCM | Jun 30, 13:10 UTC | Jun 30, 15:50 UTC | 2h 40m |
| 2026-06-28 | TWY63 | - | Jun 28, 09:10 UTC | Jun 28, 17:30 UTC | 8h 20m |
| 2026-06-24 | TWY63 | - | Jun 24, 11:45 UTC | Jun 24, 12:25 UTC | 40m |
| 2026-06-24 | TWY63 | - | Jun 24, 04:10 UTC | Jun 24, 10:04 UTC | 5h 55m |
| 2026-06-23 | TWY63 | OPO → BED | Jun 23, 14:04 UTC | Jun 23, 21:24 UTC | 7h 20m |
| 2026-06-21 | TWY63 | - | Jun 21, 12:40 UTC | Jun 21, 19:20 UTC | 6h 40m |
| 2026-06-19 | TWY63 | - | Jun 19, 18:25 UTC | Jun 19, 19:39 UTC | 1h 15m |
| 2026-05-17 | TWY63 | - | May 17, 23:45 UTC | May 18, 00:15 UTC | 30m |
| 2026-05-17 | TWY63 | - | May 17, 18:50 UTC | May 17, 23:00 UTC | 4h 10m |
| 2026-05-15 | TWY63 | - | May 15, 02:55 UTC | May 15, 03:20 UTC | 25m |
| 2026-05-15 | TWY63 | - | May 15, 01:10 UTC | May 15, 01:40 UTC | 30m |
| 2026-05-14 | TWY63 | - | May 14, 13:40 UTC | May 14, 17:20 UTC | 3h 40m |
| 2026-05-13 | TWY63 | - | May 13, 16:55 UTC | May 13, 19:55 UTC | 3h 0m |
| 2026-05-13 | TWY63 | - | May 13, 14:45 UTC | May 13, 15:15 UTC | 30m |
| 2026-05-13 | TWY63 | - | May 13, 02:25 UTC | May 13, 03:05 UTC | 40m |
| 2026-05-12 | TWY63 | - | May 12, 21:35 UTC | May 12, 22:05 UTC | 30m |
| 2026-05-12 | TWY63 | - | May 12, 19:40 UTC | May 12, 20:20 UTC | 40m |
| 2026-05-10 | TWY63 | - | May 10, 20:50 UTC | May 11, 00:54 UTC | 4h 5m |
| 2026-05-08 | TWY63 | - | May 8, 18:25 UTC | May 8, 19:20 UTC | 55m |
| 2026-05-08 | TWY63 | - | May 8, 16:55 UTC | May 8, 17:25 UTC | 30m |
| 2026-05-08 | TWY63 | - | May 8, 15:30 UTC | May 8, 16:15 UTC | 45m |
| 2026-04-21 | TWY63 | - | Apr 21, 18:30 UTC | Apr 21, 21:10 UTC | 2h 40m |
| 2026-04-19 | TWY63 | BED → PBI | Apr 19, 20:40 UTC | Apr 19, 23:35 UTC | 2h 55m |
| 2026-04-19 | TWY63 | - | Apr 19, 12:10 UTC | Apr 19, 13:20 UTC | 1h 10m |
| 2026-04-17 | TWY63 | - | Apr 17, 17:25 UTC | Apr 17, 18:55 UTC | 1h 30m |
| 2026-04-17 | TWY63 | - | Apr 17, 16:40 UTC | Apr 17, 17:15 UTC | 35m |
| 2026-04-17 | TWY63 | - | Apr 17, 15:20 UTC | Apr 17, 15:40 UTC | 20m |
| 2026-04-17 | TWY63 | - | Apr 17, 13:20 UTC | Apr 17, 14:25 UTC | 1h 5m |
| 2026-04-17 | TWY63 | - | Apr 17, 11:45 UTC | Apr 17, 13:15 UTC | 1h 30m |
| 2026-04-17 | TWY63 | NTU → BED | Apr 17, 03:20 UTC | Apr 17, 04:20 UTC | 1h 0m |
| 2026-04-17 | TWY63 | - | Apr 17, 01:55 UTC | Apr 17, 03:15 UTC | 1h 20m |
| 2026-04-16 | TWY63 | - | Apr 16, 21:14 UTC | Apr 16, 22:10 UTC | 55m |
| 2026-04-16 | TWY63 | - | Apr 16, 19:20 UTC | Apr 16, 21:10 UTC | 1h 50m |
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 N603L page for operator, model, and routing details .