sensors Mode-S transponder

A3E95D

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N351JS · operated by RAINIER FLIGHT SERVICE LLC

Hex
A3E95D
Octal
50764535
Decimal
10,742,109
Country
US
Tail
N351JS
Type
C172
No current signal · last broadcast 9h ago
Flights observed
192
Distinct callsigns
1
Country
US
Last broadcast
9h ago

Last known position

Most recent position reported by Mode-S A3E95D.

Country allocation

The ICAO 24-bit address A3E95D 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
RFS710 - 192 2026-07-18

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-18 RFS710 - Jul 18, 01:34 UTCJul 18, 03:00 UTC1h 26m
2026-07-17 RFS710 - Jul 17, 19:05 UTCJul 17, 20:35 UTC1h 30m
2026-07-16 RFS710 - Jul 16, 00:35 UTCJul 16, 02:00 UTC1h 25m
2026-07-15 RFS710 - Jul 15, 21:55 UTCJul 15, 23:20 UTC1h 25m
2026-07-15 RFS710 - Jul 15, 19:25 UTCJul 15, 20:45 UTC1h 20m
2026-07-15 RFS710 - Jul 15, 17:20 UTCJul 15, 18:05 UTC45m
2026-07-15 RFS710 CLM → PAE Jul 15, 04:40 UTCJul 15, 05:15 UTC35m
2026-07-15 RFS710 - Jul 15, 03:40 UTCJul 15, 04:15 UTC35m
2026-07-15 RFS710 - Jul 15, 00:40 UTCJul 15, 01:45 UTC1h 5m
2026-07-14 RFS710 - Jul 14, 21:50 UTCJul 14, 23:30 UTC1h 39m
2026-07-14 RFS710 PAE → PAE Jul 14, 19:25 UTCJul 14, 20:10 UTC45m
2026-07-14 RFS710 - Jul 14, 15:40 UTCJul 14, 16:40 UTC1h 0m
2026-07-13 RFS710 - Jul 13, 23:20 UTCJul 13, 23:45 UTC25m
2026-07-08 RFS710 - Jul 8, 21:00 UTCJul 8, 21:30 UTC30m
2026-07-07 RFS710 - Jul 7, 21:55 UTCJul 7, 23:20 UTC1h 25m
2026-07-07 RFS710 - Jul 7, 18:35 UTCJul 7, 19:30 UTC55m
2026-07-07 RFS710 PAE → PAE Jul 7, 15:50 UTCJul 7, 16:40 UTC50m
2026-07-07 RFS710 - Jul 7, 00:45 UTCJul 7, 02:50 UTC2h 5m
2026-07-06 RFS710 PAE → PAE Jul 6, 20:40 UTCJul 6, 21:35 UTC55m
2026-07-06 RFS710 PAE → PAE Jul 6, 16:40 UTCJul 6, 17:30 UTC50m
2026-07-06 RFS710 PAE → PAE Jul 6, 00:15 UTCJul 6, 01:25 UTC1h 10m
2026-07-05 RFS710 - Jul 5, 20:20 UTCJul 5, 22:40 UTC2h 20m
2026-07-05 RFS710 - Jul 5, 04:40 UTCJul 5, 06:00 UTC1h 20m
2026-07-04 RFS710 PAE → PAE Jul 4, 22:25 UTCJul 4, 23:35 UTC1h 10m
2026-07-04 RFS710 - Jul 4, 20:05 UTCJul 4, 21:00 UTC55m
2026-07-04 RFS710 PAE → PAE Jul 4, 16:15 UTCJul 4, 17:55 UTC1h 40m
2026-07-04 RFS710 PAE → PAE Jul 4, 05:30 UTCJul 4, 05:45 UTC15m
2026-07-03 RFS710 - Jul 3, 23:00 UTCJul 4, 00:20 UTC1h 20m
2026-07-03 RFS710 - Jul 3, 20:40 UTCJul 3, 21:35 UTC55m
2026-07-02 RFS710 - Jul 2, 20:55 UTCJul 2, 21:50 UTC55m
2026-07-02 RFS710 - Jul 2, 01:10 UTCJul 2, 02:40 UTC1h 30m
2026-06-30 RFS710 - Jun 30, 23:10 UTCJul 1, 00:15 UTC1h 5m
2026-06-30 RFS710 PAE → PAE Jun 30, 20:35 UTCJun 30, 21:20 UTC45m
2026-06-27 RFS710 - Jun 27, 22:40 UTCJun 28, 01:04 UTC2h 25m
2026-06-27 RFS710 - Jun 27, 19:05 UTCJun 27, 19:55 UTC50m
2026-06-26 RFS710 PAE → PAE Jun 26, 00:55 UTCJun 26, 02:24 UTC1h 30m
2026-06-25 RFS710 PAE → PAE Jun 25, 21:50 UTCJun 25, 23:05 UTC1h 15m
2026-06-25 RFS710 - Jun 25, 04:35 UTCJun 25, 06:09 UTC1h 35m
2026-06-24 RFS710 - Jun 24, 20:49 UTCJun 24, 21:44 UTC55m
2026-06-24 RFS710 - Jun 24, 18:34 UTCJun 24, 19:34 UTC1h 0m
2026-06-24 RFS710 - Jun 24, 16:24 UTCJun 24, 17:25 UTC1h 0m
2026-06-24 RFS710 - Jun 24, 00:15 UTCJun 24, 01:39 UTC1h 25m
2026-06-23 RFS710 - Jun 23, 16:05 UTCJun 23, 17:34 UTC1h 30m
2026-06-23 RFS710 PAE → PAE Jun 23, 01:15 UTCJun 23, 03:25 UTC2h 10m
2026-06-22 RFS710 PAE → PAE Jun 22, 23:24 UTCJun 23, 00:00 UTC35m
2026-06-22 RFS710 - Jun 22, 20:44 UTCJun 22, 21:45 UTC1h 0m
2026-06-22 RFS710 - Jun 22, 18:40 UTCJun 22, 19:44 UTC1h 5m
2026-06-22 RFS710 - Jun 22, 14:49 UTCJun 22, 16:20 UTC1h 30m
2026-06-21 RFS710 - Jun 21, 23:24 UTCJun 22, 01:15 UTC1h 50m
2026-06-21 RFS710 - Jun 21, 20:40 UTCJun 21, 22:04 UTC1h 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 N351JS page for operator, model, and routing details .

Mode-S A3E95D frequently asked

What is Mode-S code A3E95D?
A3E95D is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N351JS.
Where is Mode-S A3E95D registered?
Mode-S code A3E95D is allocated to United States (US). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is A3E95D broadcasting right now?
No active broadcast right now. Last signal was 9h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A3E95D, octal 50764535, decimal 10,742,109.
What flights does A3E95D operate?
Mode-S A3E95D has broadcast 1 distinct callsign, including RFS710.