Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AB8B8C

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N843FS · BEECHCRAFT Super King Air 350 · operated by WILMINGTON TRUST CO TRUSTEE

Hex
AB8B8C
Octal
52705614
Decimal
11,242,380
Country
US
Tail
N843FS
Type
B350
No current signal · last broadcast 12d ago
Flights observed
168
Distinct callsigns
10
Country
US
Last broadcast
12d ago

Last known position

Most recent position reported by Mode-S AB8B8C.

Country allocation

The ICAO 24-bit address AB8B8C 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 10 distinct

Callsign Airline Flights Last seen
NFX101 - 24 2026-07-21
NFX102 - 23 2026-07-23
NFX104 - 22 2026-07-24
NFX103 - 21 2026-07-23
NFX601 - 19 2026-07-16
NFX602 - 18 2026-07-16
NFX600 - 16 2026-07-20
NFX603 - 12 2026-07-17
N843FS - 12 2026-07-22
NFX1O1 - 1 2026-07-23

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-24 NFX104 SJC → BUR Jul 24, 01:05 UTCJul 24, 02:15 UTC1h 10m
2026-07-23 NFX103 BUR → SJC Jul 23, 23:15 UTCJul 24, 00:20 UTC1h 5m
2026-07-23 NFX102 - Jul 23, 15:45 UTCJul 23, 16:50 UTC1h 5m
2026-07-23 NFX1O1 BUR → SJC Jul 23, 13:55 UTCJul 23, 15:00 UTC1h 5m
2026-07-22 N843FS - Jul 22, 17:45 UTCJul 22, 18:15 UTC30m
2026-07-22 NFX104 SJC → BUR Jul 22, 01:05 UTCJul 22, 02:15 UTC1h 10m
2026-07-21 NFX103 BUR → SJC Jul 21, 22:55 UTCJul 22, 00:00 UTC1h 5m
2026-07-21 NFX102 - Jul 21, 15:20 UTCJul 21, 16:25 UTC1h 5m
2026-07-21 NFX101 BUR → SJC Jul 21, 13:55 UTCJul 21, 14:55 UTC1h 0m
2026-07-20 NFX600 - Jul 20, 14:05 UTCJul 20, 15:15 UTC1h 10m
2026-07-17 NFX603 BUR → SJC Jul 17, 00:50 UTCJul 17, 01:55 UTC1h 5m
2026-07-16 NFX602 SJC → BUR Jul 16, 23:10 UTCJul 17, 00:14 UTC1h 5m
2026-07-16 NFX601 BUR → SJC Jul 16, 16:15 UTCJul 16, 17:20 UTC1h 5m
2026-07-16 NFX600 SJC → BUR Jul 16, 14:05 UTCJul 16, 15:14 UTC1h 10m
2026-07-16 NFX603 BUR → SJC Jul 16, 00:55 UTCJul 16, 02:00 UTC1h 5m
2026-07-15 NFX602 - Jul 15, 22:50 UTCJul 16, 00:00 UTC1h 10m
2026-07-15 NFX601 BUR → SJC Jul 15, 15:55 UTCJul 15, 17:00 UTC1h 5m
2026-07-15 NFX600 SJC → BUR Jul 15, 14:05 UTCJul 15, 15:10 UTC1h 5m
2026-07-15 NFX603 BUR → SJC Jul 15, 01:00 UTCJul 15, 02:05 UTC1h 5m
2026-07-14 NFX602 SJC → BUR Jul 14, 23:10 UTCJul 15, 00:20 UTC1h 10m
2026-07-14 NFX601 - Jul 14, 16:00 UTCJul 14, 17:00 UTC1h 0m
2026-07-14 NFX600 SJC → BUR Jul 14, 14:00 UTCJul 14, 15:05 UTC1h 5m
2026-07-14 NFX603 - Jul 14, 01:00 UTCJul 14, 02:00 UTC1h 0m
2026-07-13 NFX602 SJC → BUR Jul 13, 23:05 UTCJul 14, 00:20 UTC1h 15m
2026-07-13 NFX601 BUR → SJC Jul 13, 15:55 UTCJul 13, 16:55 UTC1h 0m
2026-07-13 NFX600 - Jul 13, 14:05 UTCJul 13, 15:15 UTC1h 10m
2026-07-13 NFX602 - Jul 13, 01:55 UTCJul 13, 03:01 UTC1h 5m
2026-07-12 NFX601 SFO → BUR Jul 12, 23:55 UTCJul 13, 01:20 UTC1h 25m
2026-07-12 NFX600 SJC → SFO Jul 12, 22:20 UTCJul 12, 22:40 UTC20m
2026-07-10 NFX603 - Jul 10, 00:45 UTCJul 10, 01:55 UTC1h 10m
2026-07-09 NFX602 SJC → BUR Jul 9, 23:00 UTCJul 10, 00:00 UTC1h 0m
2026-07-09 NFX601 - Jul 9, 16:20 UTCJul 9, 17:30 UTC1h 10m
2026-07-09 NFX600 SJC → BUR Jul 9, 14:10 UTCJul 9, 15:10 UTC1h 0m
2026-07-09 NFX603 BUR → SJC Jul 9, 00:50 UTCJul 9, 02:00 UTC1h 10m
2026-07-08 NFX602 SJC → BUR Jul 8, 23:00 UTCJul 9, 00:00 UTC1h 0m
2026-07-08 NFX601 BUR → SJC Jul 8, 15:55 UTCJul 8, 17:00 UTC1h 5m
2026-07-08 NFX600 SJC → BUR Jul 8, 14:05 UTCJul 8, 15:10 UTC1h 5m
2026-07-08 NFX603 BUR → SJC Jul 8, 00:40 UTCJul 8, 01:45 UTC1h 5m
2026-07-07 NFX602 SJC → BUR Jul 7, 22:50 UTCJul 7, 23:55 UTC1h 5m
2026-07-07 NFX601 - Jul 7, 15:55 UTCJul 7, 16:55 UTC1h 0m
2026-07-07 NFX600 SJC → BUR Jul 7, 14:05 UTCJul 7, 15:10 UTC1h 5m
2026-07-07 NFX602 - Jul 7, 00:50 UTCJul 7, 01:55 UTC1h 5m
2026-07-06 NFX602 SJC → BUR Jul 6, 22:50 UTCJul 6, 23:55 UTC1h 5m
2026-07-02 NFX601 BUR → SJC Jul 2, 16:05 UTCJul 2, 17:10 UTC1h 5m
2026-07-02 NFX104 SJC → BUR Jul 2, 00:50 UTCJul 2, 01:50 UTC1h 0m
2026-07-01 NFX103 BUR → SJC Jul 1, 22:50 UTCJul 1, 23:55 UTC1h 5m
2026-06-25 NFX602 SJC → BUR Jun 25, 23:19 UTCJun 26, 00:24 UTC1h 5m
2026-06-25 NFX601 BUR → SJC Jun 25, 15:59 UTCJun 25, 17:05 UTC1h 5m
2026-06-25 NFX600 SJC → BUR Jun 25, 13:59 UTCJun 25, 15:10 UTC1h 10m
2026-06-25 NFX603 BUR → SJC Jun 25, 00:55 UTCJun 25, 01:59 UTC1h 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 N843FS page for operator, model, and routing details .

Mode-S AB8B8C frequently asked

What is Mode-S code AB8B8C?
AB8B8C is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N843FS.
Where is Mode-S AB8B8C registered?
Mode-S code AB8B8C 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 AB8B8C broadcasting right now?
No active broadcast right now. Last signal was 12d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AB8B8C, octal 52705614, decimal 11,242,380.
What flights does AB8B8C operate?
Mode-S AB8B8C has broadcast 10 distinct callsigns, including NFX101, NFX102, NFX104, NFX103, NFX601.