Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

AB2B4F

ICAO 24-bit transponder address · allocated to United States

Currently assigned to N819FG · BEECH 400 Beechjet · operated by FRIESEN GROUP INC

Hex
AB2B4F
Octal
52625517
Decimal
11,217,743
Country
US
Tail
N819FG
Type
BE40
No current signal · last broadcast 16h ago
Flights observed
74
Distinct callsigns
1
Country
US
Last broadcast
16h ago

Last known position

Most recent position reported by Mode-S AB2B4F.

Country allocation

The ICAO 24-bit address AB2B4F 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
N819FG - 74 2026-07-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 N819FG - Jul 14, 00:00 UTCJul 14, 01:25 UTC1h 25m
2026-07-13 N819FG - Jul 13, 15:20 UTCJul 13, 15:45 UTC25m
2026-07-13 N819FG RDD → VNY Jul 13, 13:10 UTCJul 13, 14:30 UTC1h 20m
2026-07-11 N819FG - Jul 11, 01:35 UTCJul 11, 02:55 UTC1h 20m
2026-07-10 N819FG RDD → CLD Jul 10, 23:05 UTCJul 11, 00:35 UTC1h 30m
2026-07-09 N819FG - Jul 9, 20:00 UTCJul 9, 21:30 UTC1h 30m
2026-07-09 N819FG RDD → CLD Jul 9, 15:25 UTCJul 9, 17:00 UTC1h 35m
2026-07-06 N819FG CLD → RDD Jul 6, 19:15 UTCJul 6, 20:40 UTC1h 25m
2026-07-06 N819FG - Jul 6, 16:25 UTCJul 6, 17:50 UTC1h 25m
2026-07-06 N819FG - Jul 6, 15:10 UTCJul 6, 15:20 UTC10m
2026-07-02 N819FG - Jul 2, 21:10 UTCJul 2, 21:20 UTC10m
2026-07-02 N819FG - Jul 2, 19:20 UTCJul 2, 20:35 UTC1h 15m
2026-07-02 N819FG RDD → CLD Jul 2, 15:00 UTCJul 2, 16:30 UTC1h 30m
2026-06-27 N819FG CLD → RDD Jun 27, 20:04 UTCJun 27, 21:34 UTC1h 30m
2026-06-27 N819FG - Jun 27, 17:55 UTCJun 27, 19:09 UTC1h 15m
2026-06-26 N819FG CLD → OAK Jun 26, 20:24 UTCJun 26, 21:35 UTC1h 10m
2026-06-26 N819FG - Jun 26, 17:04 UTCJun 26, 18:34 UTC1h 30m
2026-06-25 N819FG - Jun 25, 00:24 UTCJun 25, 00:59 UTC35m
2026-06-24 N819FG - Jun 24, 21:19 UTCJun 24, 22:04 UTC45m
2026-06-24 N819FG CLD → RDD Jun 24, 01:34 UTCJun 24, 03:00 UTC1h 25m
2026-06-23 N819FG RDD → CLD Jun 23, 23:24 UTCJun 24, 00:55 UTC1h 30m
2026-06-23 N819FG CLD → RDD Jun 23, 16:50 UTCJun 23, 18:14 UTC1h 25m
2026-06-23 N819FG RDD → CLD Jun 23, 13:19 UTCJun 23, 14:55 UTC1h 35m
2026-06-20 N819FG CLD → RDD Jun 20, 17:04 UTCJun 20, 18:29 UTC1h 25m
2026-06-20 N819FG APC → CLD Jun 20, 04:49 UTCJun 20, 06:10 UTC1h 20m
2026-06-19 N819FG CLD → APC Jun 19, 16:34 UTCJun 19, 18:05 UTC1h 30m
2026-06-19 N819FG - Jun 19, 14:04 UTCJun 19, 15:39 UTC1h 35m
2026-06-17 N819FG - Jun 17, 02:15 UTCJun 17, 03:40 UTC1h 25m
2026-06-16 N819FG RDD → CLD Jun 16, 23:45 UTCJun 17, 01:20 UTC1h 35m
2026-06-16 N819FG CLD → RDD Jun 16, 16:25 UTCJun 16, 17:49 UTC1h 25m
2026-06-16 N819FG RDD → CLD Jun 16, 13:44 UTCJun 16, 15:20 UTC1h 35m
2026-06-14 N819FG - Jun 14, 01:15 UTCJun 14, 02:40 UTC1h 25m
2026-06-13 N819FG MHR → CLD Jun 13, 23:05 UTCJun 14, 00:15 UTC1h 10m
2026-06-13 N819FG RDD → MHR Jun 13, 21:15 UTCJun 13, 21:45 UTC30m
2026-06-13 N819FG MHR → RDD Jun 13, 00:50 UTCJun 13, 01:15 UTC25m
2026-06-12 N819FG CLD → MHR Jun 12, 22:35 UTCJun 12, 23:40 UTC1h 5m
2026-06-12 N819FG RDD → CLD Jun 12, 19:35 UTCJun 12, 21:05 UTC1h 30m
2026-06-10 N819FG - Jun 10, 01:25 UTCJun 10, 03:00 UTC1h 35m
2026-06-09 N819FG RDD → CLD Jun 9, 23:10 UTCJun 10, 00:35 UTC1h 25m
2026-06-09 N819FG - Jun 9, 17:30 UTCJun 9, 19:15 UTC1h 45m
2026-06-07 N819FG - Jun 7, 23:00 UTCJun 8, 02:05 UTC3h 5m
2026-06-05 N819FG - Jun 5, 20:25 UTCJun 5, 23:25 UTC3h 0m
2026-06-05 N819FG RDD → CLD Jun 5, 16:30 UTCJun 5, 18:00 UTC1h 30m
2026-06-04 N819FG - Jun 4, 03:20 UTCJun 4, 04:55 UTC1h 35m
2026-06-04 N819FG RDD → CLD Jun 4, 01:10 UTCJun 4, 02:40 UTC1h 30m
2026-06-03 N819FG CLD → RDD Jun 3, 17:00 UTCJun 3, 18:30 UTC1h 30m
2026-06-02 N819FG SFO → CLD Jun 2, 23:05 UTCJun 3, 00:15 UTC1h 10m
2026-06-02 N819FG RDD → SFO Jun 2, 20:40 UTCJun 2, 21:40 UTC1h 0m
2026-06-01 N819FG - Jun 1, 03:05 UTCJun 1, 04:35 UTC1h 30m
2026-06-01 N819FG PDX → CLD Jun 1, 00:10 UTCJun 1, 02:25 UTC2h 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 N819FG page for operator, model, and routing details .

Mode-S AB2B4F frequently asked

What is Mode-S code AB2B4F?
AB2B4F is an ICAO 24-bit transponder address. Allocated to United States. Assigned to N819FG.
Where is Mode-S AB2B4F registered?
Mode-S code AB2B4F 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 AB2B4F broadcasting right now?
No active broadcast right now. Last signal was 16h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex AB2B4F, octal 52625517, decimal 11,217,743.
What flights does AB2B4F operate?
Mode-S AB2B4F has broadcast 1 distinct callsign, including N819FG.