sensors Mode-S transponder
A35DBE
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N316GN · GULFSTREAM 5 · operated by GENERAL INDUSTRIES LLC
- Hex
- A35DBE
- Octal
- 50656676
- Decimal
- 10,706,366
- Country
- US
- Tail
- N316GN
- Type
- GLF5
- Flights observed
- 47
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 16h ago
Current position
Country allocation
The ICAO 24-bit address A35DBE 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 |
|---|---|---|---|
| EJM316 | - | 47 | 2026-07-18 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | EJM316 | - | Jul 18, 18:05 UTC | Jul 18, 21:10 UTC | 3h 5m |
| 2026-07-17 | EJM316 | - | Jul 17, 21:20 UTC | Jul 18, 00:10 UTC | 2h 50m |
| 2026-07-17 | EJM316 | PHL → PBI | Jul 17, 17:40 UTC | Jul 17, 19:35 UTC | 1h 55m |
| 2026-07-06 | EJM316 | - | Jul 6, 22:35 UTC | Jul 6, 23:30 UTC | 55m |
| 2026-07-06 | EJM316 | - | Jul 6, 21:20 UTC | Jul 6, 22:00 UTC | 40m |
| 2026-07-06 | EJM316 | - | Jul 6, 17:20 UTC | Jul 6, 18:20 UTC | 1h 0m |
| 2026-07-06 | EJM316 | - | Jul 6, 15:55 UTC | Jul 6, 16:35 UTC | 40m |
| 2026-07-02 | EJM316 | - | Jul 2, 00:45 UTC | Jul 2, 01:35 UTC | 50m |
| 2026-07-01 | EJM316 | - | Jul 1, 23:40 UTC | Jul 2, 00:10 UTC | 30m |
| 2026-07-01 | EJM316 | - | Jul 1, 14:25 UTC | Jul 1, 15:00 UTC | 35m |
| 2026-06-26 | EJM316 | - | Jun 26, 19:50 UTC | Jun 27, 00:05 UTC | 4h 15m |
| 2026-06-26 | EJM316 | - | Jun 26, 01:05 UTC | Jun 26, 03:00 UTC | 1h 55m |
| 2026-06-17 | EJM316 | - | Jun 17, 23:00 UTC | Jun 18, 00:55 UTC | 1h 55m |
| 2026-06-17 | EJM316 | PSQ → MSP | Jun 17, 13:35 UTC | Jun 17, 15:55 UTC | 2h 20m |
| 2026-06-05 | EJM316 | - | Jun 5, 18:40 UTC | Jun 5, 19:35 UTC | 55m |
| 2026-05-24 | EJM316 | - | May 24, 20:35 UTC | May 24, 21:15 UTC | 40m |
| 2026-05-24 | EJM316 | - | May 24, 17:45 UTC | May 24, 19:45 UTC | 2h 0m |
| 2026-05-18 | EJM316 | - | May 18, 23:25 UTC | May 19, 01:20 UTC | 1h 55m |
| 2026-05-17 | EJM316 | - | May 17, 23:55 UTC | May 18, 01:55 UTC | 2h 0m |
| 2026-05-17 | EJM316 | - | May 17, 14:25 UTC | May 17, 16:55 UTC | 2h 30m |
| 2026-05-16 | EJM316 | TEB → BOS | May 16, 21:25 UTC | May 16, 22:15 UTC | 50m |
| 2026-05-16 | EJM316 | - | May 16, 15:40 UTC | May 16, 20:15 UTC | 4h 35m |
| 2026-05-15 | EJM316 | - | May 15, 23:30 UTC | May 15, 23:40 UTC | 10m |
| 2026-05-15 | EJM316 | TEB → VNY | May 15, 17:05 UTC | May 15, 22:10 UTC | 5h 5m |
| 2026-05-15 | EJM316 | ORH → TEB | May 15, 14:05 UTC | May 15, 14:55 UTC | 49m |
| 2026-05-14 | EJM316 | - | May 14, 19:05 UTC | May 14, 21:30 UTC | 2h 25m |
| 2026-05-14 | EJM316 | - | May 14, 13:01 UTC | May 14, 15:05 UTC | 2h 5m |
| 2026-05-08 | EJM316 | - | May 8, 22:00 UTC | May 8, 22:50 UTC | 50m |
| 2026-05-08 | EJM316 | - | May 8, 18:00 UTC | May 8, 18:40 UTC | 40m |
| 2026-05-08 | EJM316 | - | May 8, 15:45 UTC | May 8, 16:50 UTC | 1h 5m |
| 2026-05-08 | EJM316 | - | May 8, 11:25 UTC | May 8, 12:25 UTC | 1h 0m |
| 2026-05-03 | EJM316 | - | May 3, 09:15 UTC | May 3, 18:05 UTC | 8h 50m |
| 2026-04-28 | EJM316 | - | Apr 28, 11:30 UTC | Apr 28, 19:45 UTC | 8h 15m |
| 2026-04-27 | EJM316 | - | Apr 27, 22:40 UTC | Apr 28, 00:00 UTC | 1h 20m |
| 2026-04-27 | EJM316 | - | Apr 27, 12:20 UTC | Apr 27, 13:35 UTC | 1h 15m |
| 2026-04-25 | EJM316 | - | Apr 25, 20:00 UTC | Apr 25, 22:05 UTC | 2h 5m |
| 2026-04-23 | EJM316 | - | Apr 23, 23:50 UTC | Apr 24, 02:30 UTC | 2h 40m |
| 2026-04-23 | EJM316 | - | Apr 23, 15:55 UTC | Apr 23, 17:05 UTC | 1h 10m |
| 2026-04-21 | EJM316 | - | Apr 21, 18:00 UTC | Apr 21, 19:00 UTC | 1h 0m |
| 2026-04-20 | EJM316 | - | Apr 20, 22:15 UTC | Apr 21, 00:25 UTC | 2h 10m |
| 2026-04-20 | EJM316 | - | Apr 20, 15:50 UTC | Apr 20, 18:25 UTC | 2h 35m |
| 2026-04-19 | EJM316 | - | Apr 19, 20:35 UTC | Apr 19, 21:05 UTC | 30m |
| 2026-04-19 | EJM316 | - | Apr 19, 17:45 UTC | Apr 19, 20:00 UTC | 2h 15m |
| 2026-04-15 | EJM316 | - | Apr 15, 02:55 UTC | Apr 15, 04:20 UTC | 1h 25m |
| 2026-04-15 | EJM316 | - | Apr 15, 02:10 UTC | Apr 15, 02:50 UTC | 40m |
| 2026-04-14 | EJM316 | - | Apr 14, 20:05 UTC | Apr 14, 20:40 UTC | 35m |
| 2026-04-14 | EJM316 | - | Apr 14, 18:55 UTC | Apr 14, 19:05 UTC | 10m |
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 N316GN page for operator, model, and routing details .