sensors Mode-S transponder
AB79E3
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N839BA · BOEING 737-700 · operated by BOEING CO
- Hex
- AB79E3
- Octal
- 52674743
- Decimal
- 11,237,859
- Country
- US
- Tail
- N839BA
- Type
- B737
- Flights observed
- 39
- Distinct callsigns
- 17
- Country
- US
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address AB79E3 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| RDN779 | - | 4 | 2026-05-31 |
| RDN509 | - | 4 | 2026-05-15 |
| RDN848 | - | 3 | 2026-05-17 |
| RDN760 | - | 3 | 2026-06-09 |
| RDN152 | - | 3 | 2026-06-24 |
| RDN138 | - | 3 | 2026-06-18 |
| RDN022 | - | 3 | 2026-06-11 |
| RDN995 | - | 2 | 2026-06-17 |
| RDN935 | - | 2 | 2026-06-03 |
| RDN913 | - | 2 | 2026-05-25 |
| RDN694 | - | 2 | 2026-04-13 |
| RDN035 | - | 2 | 2026-06-23 |
| RDN008 | - | 2 | 2026-06-22 |
| RDN857 | - | 1 | 2026-05-06 |
| RDN833 | - | 1 | 2026-05-11 |
| RDN102 | - | 1 | 2026-06-18 |
| RDN084 | - | 1 | 2026-06-21 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-24 | RDN152 | - | Jun 24, 19:59 UTC | Jun 24, 21:34 UTC | 1h 35m |
| 2026-06-24 | RDN152 | - | Jun 24, 17:55 UTC | Jun 24, 19:24 UTC | 1h 30m |
| 2026-06-24 | RDN152 | - | Jun 24, 16:29 UTC | Jun 24, 16:54 UTC | 25m |
| 2026-06-23 | RDN035 | - | Jun 23, 23:29 UTC | Jun 24, 00:49 UTC | 1h 20m |
| 2026-06-23 | RDN035 | CEA → IAD | Jun 23, 20:34 UTC | Jun 23, 22:40 UTC | 2h 5m |
| 2026-06-22 | RDN008 | - | Jun 22, 13:29 UTC | Jun 22, 15:20 UTC | 1h 50m |
| 2026-06-22 | RDN008 | IAD → LUK | Jun 22, 11:39 UTC | Jun 22, 12:54 UTC | 1h 15m |
| 2026-06-21 | RDN084 | - | Jun 21, 18:20 UTC | Jun 21, 19:29 UTC | 1h 10m |
| 2026-06-18 | RDN138 | - | Jun 18, 20:30 UTC | Jun 18, 22:00 UTC | 1h 30m |
| 2026-06-18 | RDN138 | - | Jun 18, 18:10 UTC | Jun 18, 19:40 UTC | 1h 30m |
| 2026-06-18 | RDN138 | - | Jun 18, 15:25 UTC | Jun 18, 17:21 UTC | 1h 56m |
| 2026-06-18 | RDN102 | - | Jun 18, 12:10 UTC | Jun 18, 14:10 UTC | 2h 0m |
| 2026-06-17 | RDN995 | - | Jun 17, 17:10 UTC | Jun 17, 19:30 UTC | 2h 20m |
| 2026-06-17 | RDN995 | - | Jun 17, 15:00 UTC | Jun 17, 16:25 UTC | 1h 25m |
| 2026-06-11 | RDN022 | - | Jun 11, 18:05 UTC | Jun 11, 18:55 UTC | 50m |
| 2026-06-10 | RDN022 | - | Jun 10, 20:40 UTC | Jun 10, 22:25 UTC | 1h 45m |
| 2026-06-10 | RDN022 | IAD → ADS | Jun 10, 16:10 UTC | Jun 10, 18:45 UTC | 2h 35m |
| 2026-06-09 | RDN760 | - | Jun 9, 13:35 UTC | Jun 9, 15:50 UTC | 2h 15m |
| 2026-06-09 | RDN760 | - | Jun 9, 01:10 UTC | Jun 9, 12:30 UTC | 11h 20m |
| 2026-06-06 | RDN760 | - | Jun 6, 02:50 UTC | Jun 6, 12:40 UTC | 9h 50m |
| 2026-06-03 | RDN935 | - | Jun 3, 23:10 UTC | Jun 4, 01:00 UTC | 1h 50m |
| 2026-06-03 | RDN935 | - | Jun 3, 21:05 UTC | Jun 3, 21:30 UTC | 25m |
| 2026-05-31 | RDN779 | DEN → GYY | May 31, 22:35 UTC | Jun 1, 00:30 UTC | 1h 55m |
| 2026-05-31 | RDN779 | - | May 31, 10:25 UTC | May 31, 20:30 UTC | 10h 5m |
| 2026-05-27 | RDN779 | - | May 27, 20:55 UTC | May 28, 04:25 UTC | 7h 30m |
| 2026-05-26 | RDN779 | - | May 26, 19:20 UTC | May 26, 20:24 UTC | 1h 5m |
| 2026-05-25 | RDN913 | - | May 25, 16:55 UTC | May 25, 18:10 UTC | 1h 15m |
| 2026-05-25 | RDN913 | - | May 25, 15:20 UTC | May 25, 15:40 UTC | 20m |
| 2026-05-17 | RDN848 | - | May 17, 20:45 UTC | May 17, 21:30 UTC | 45m |
| 2026-05-17 | RDN848 | ADS → SUS | May 17, 18:55 UTC | May 17, 20:10 UTC | 1h 15m |
| 2026-05-17 | RDN848 | - | May 17, 17:10 UTC | May 17, 18:25 UTC | 1h 15m |
| 2026-05-15 | RDN509 | - | May 15, 19:00 UTC | May 16, 00:35 UTC | 5h 35m |
| 2026-05-15 | RDN509 | - | May 15, 08:50 UTC | May 15, 17:35 UTC | 8h 44m |
| 2026-05-12 | RDN509 | - | May 12, 21:55 UTC | May 13, 06:55 UTC | 9h 0m |
| 2026-05-12 | RDN509 | IAD → ANC | May 12, 12:40 UTC | May 12, 20:05 UTC | 7h 25m |
| 2026-05-11 | RDN833 | - | May 11, 18:10 UTC | May 11, 19:25 UTC | 1h 15m |
| 2026-05-06 | RDN857 | - | May 6, 21:40 UTC | May 6, 23:40 UTC | 2h 0m |
| 2026-04-13 | RDN694 | - | Apr 13, 12:20 UTC | Apr 13, 14:25 UTC | 2h 5m |
| 2026-04-13 | RDN694 | - | Apr 13, 12:00 UTC | Apr 13, 12:15 UTC | 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 N839BA page for operator, model, and routing details .