Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

A28F48

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N264QS · BOMBARDIER CL-600 Challenger · operated by NETJETS SALES INC, AMJ HOLDINGS 2 LLC, FREEDOM MORTGAGE CORP, TAYLOR JOSEPH, KAMJ NX PLANE LLC, KIRBY RISK CORP

Hex
A28F48
Octal
50507510
Decimal
10,653,512
Country
US
Tail
N264QS
Type
CL60
No current signal · last broadcast 12h ago
Flights observed
54
Distinct callsigns
2
Country
US
Last broadcast
12h ago

Last known position

Most recent position reported by Mode-S A28F48.

Country allocation

The ICAO 24-bit address A28F48 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 2 distinct

Callsign Airline Flights Last seen
EJA264 NetJets 50 2026-06-03
N264QS - 4 2026-06-03

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-06-03 N264QS - Jun 3, 22:05 UTCJun 3, 23:00 UTC55m
2026-06-03 EJA264 FTY → STT Jun 3, 15:15 UTCJun 3, 20:10 UTC4h 55m
2026-06-02 EJA264 FTY → STT Jun 2, 18:00 UTCJun 2, 18:30 UTC30m
2026-06-01 EJA264 FTY → STT Jun 1, 21:50 UTCJun 2, 01:10 UTC3h 20m
2026-06-01 EJA264 FTY → STT Jun 1, 14:20 UTCJun 1, 15:30 UTC1h 10m
2026-06-01 EJA264 FTY → STT Jun 1, 12:20 UTCJun 1, 13:10 UTC50m
2026-05-31 EJA264 FTY → STT May 31, 21:25 UTCMay 31, 22:10 UTC45m
2026-05-31 EJA264 FTY → STT May 31, 18:15 UTCMay 31, 20:05 UTC1h 50m
2026-05-31 EJA264 FTY → STT May 31, 15:45 UTCMay 31, 16:55 UTC1h 10m
2026-05-30 N264QS - May 30, 16:00 UTCMay 30, 23:50 UTC7h 50m
2026-05-30 EJA264 FTY → STT May 30, 13:55 UTCMay 30, 15:00 UTC1h 5m
2026-05-29 EJA264 FTY → STT May 29, 16:20 UTCMay 29, 21:10 UTC4h 50m
2026-05-27 EJA264 FTY → STT May 27, 22:50 UTCMay 28, 01:10 UTC2h 20m
2026-05-24 EJA264 FTY → STT May 24, 19:40 UTCMay 24, 20:35 UTC55m
2026-05-23 EJA264 FTY → STT May 23, 19:00 UTCMay 23, 20:25 UTC1h 25m
2026-05-23 EJA264 FTY → STT May 23, 16:25 UTCMay 23, 17:00 UTC35m
2026-05-22 EJA264 FTY → STT May 22, 20:20 UTCMay 22, 22:55 UTC2h 35m
2026-05-22 EJA264 FTY → STT May 22, 16:30 UTCMay 22, 17:50 UTC1h 20m
2026-05-22 EJA264 FTY → STT May 22, 13:35 UTCMay 22, 15:35 UTC2h 0m
2026-05-03 EJA264 FTY → STT May 3, 14:30 UTCMay 3, 21:29 UTC7h 0m
2026-05-03 EJA264 FTY → STT May 3, 12:25 UTCMay 3, 13:05 UTC40m
2026-05-02 EJA264 FTY → STT May 2, 17:55 UTCMay 2, 19:20 UTC1h 25m
2026-05-01 EJA264 FTY → STT May 1, 19:45 UTCMay 1, 20:25 UTC40m
2026-05-01 EJA264 FTY → STT May 1, 16:45 UTCMay 1, 17:00 UTC15m
2026-05-01 EJA264 FTY → STT May 1, 14:00 UTCMay 1, 14:15 UTC15m
2026-05-01 EJA264 FTY → STT May 1, 12:10 UTCMay 1, 12:55 UTC45m
2026-04-30 EJA264 FTY → STT Apr 30, 21:10 UTCApr 30, 22:25 UTC1h 15m
2026-04-30 EJA264 FTY → STT Apr 30, 16:20 UTCApr 30, 18:55 UTC2h 35m
2026-04-29 EJA264 FTY → STT Apr 29, 20:05 UTCApr 30, 18:55 UTC22h 50m
2026-04-29 EJA264 FTY → STT Apr 29, 19:55 UTCApr 30, 18:00 UTC22h 5m
2026-04-29 EJA264 FTY → STT Apr 29, 18:15 UTCApr 29, 18:35 UTC20m
2026-04-29 EJA264 FTY → STT Apr 29, 15:35 UTCApr 29, 17:05 UTC1h 30m
2026-04-28 EJA264 FTY → STT Apr 28, 20:05 UTCApr 28, 20:30 UTC25m
2026-04-28 EJA264 FTY → STT Apr 28, 12:30 UTCApr 28, 18:20 UTC5h 50m
2026-04-27 EJA264 FTY → STT Apr 27, 17:25 UTCApr 27, 18:10 UTC45m
2026-04-27 EJA264 FTY → STT Apr 27, 14:15 UTCApr 27, 16:40 UTC2h 25m
2026-04-26 EJA264 FTY → STT Apr 26, 16:45 UTCApr 26, 17:50 UTC1h 5m
2026-04-26 EJA264 FTY → STT Apr 26, 14:00 UTCApr 26, 16:10 UTC2h 10m
2026-04-25 EJA264 FTY → STT Apr 25, 23:10 UTCApr 26, 00:10 UTC1h 0m
2026-04-25 EJA264 FTY → STT Apr 25, 21:05 UTCApr 25, 21:50 UTC45m
2026-04-25 EJA264 FTY → STT Apr 25, 15:30 UTCApr 25, 16:10 UTC40m
2026-04-24 EJA264 FTY → STT Apr 24, 15:10 UTCApr 24, 17:20 UTC2h 10m
2026-04-23 EJA264 FTY → STT Apr 23, 20:45 UTCApr 23, 21:15 UTC30m
2026-04-23 EJA264 FTY → STT Apr 23, 19:25 UTCApr 23, 20:00 UTC35m
2026-04-23 EJA264 FTY → STT Apr 23, 15:55 UTCApr 23, 16:25 UTC30m
2026-04-23 EJA264 FTY → STT Apr 23, 00:55 UTCApr 23, 02:10 UTC1h 15m
2026-04-22 EJA264 FTY → STT Apr 22, 17:10 UTCApr 22, 18:35 UTC1h 25m
2026-04-21 EJA264 FTY → STT Apr 21, 23:20 UTCApr 22, 00:25 UTC1h 5m
2026-04-21 EJA264 FTY → STT Apr 21, 17:45 UTCApr 21, 22:35 UTC4h 50m
2026-04-20 EJA264 FTY → STT Apr 20, 12:05 UTCApr 20, 17:20 UTC5h 15m

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 N264QS page for operator, model, and routing details .

Mode-S A28F48 frequently asked

What is Mode-S code A28F48?
A28F48 is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N264QS.
Where is Mode-S A28F48 registered?
Mode-S code A28F48 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 A28F48 broadcasting right now?
No active broadcast right now. Last signal was 12h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex A28F48, octal 50507510, decimal 10,653,512.
What flights does A28F48 operate?
Mode-S A28F48 has broadcast 2 distinct callsigns, including EJA264, N264QS.