sensors Mode-S transponder
A18D7F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N2BW · BOMBARDIER BD-700 Global 7000/7500 · operated by BANK OF UTAH TRUSTEE
- Hex
- A18D7F
- Octal
- 50306577
- Decimal
- 10,587,519
- Country
- US
- Tail
- N2BW
- Type
- GL7T
- Flights observed
- 62
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address A18D7F 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 |
|---|---|---|---|
| N2BW | - | 62 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | N2BW | - | Jul 17, 07:40 UTC | Jul 17, 08:10 UTC | 30m |
| 2026-07-17 | N2BW | TEB → SJC | Jul 17, 02:05 UTC | Jul 17, 07:00 UTC | 4h 55m |
| 2026-07-16 | N2BW | - | Jul 16, 21:45 UTC | Jul 16, 23:59 UTC | 2h 15m |
| 2026-07-15 | N2BW | - | Jul 15, 16:40 UTC | Jul 15, 19:25 UTC | 2h 45m |
| 2026-07-12 | N2BW | - | Jul 12, 19:35 UTC | Jul 12, 20:20 UTC | 45m |
| 2026-07-12 | N2BW | - | Jul 12, 18:10 UTC | Jul 12, 18:25 UTC | 15m |
| 2026-07-12 | N2BW | - | Jul 12, 16:01 UTC | Jul 12, 17:25 UTC | 1h 25m |
| 2026-07-07 | N2BW | - | Jul 7, 14:15 UTC | Jul 7, 15:15 UTC | 1h 0m |
| 2026-07-06 | N2BW | - | Jul 6, 22:25 UTC | Jul 6, 22:55 UTC | 30m |
| 2026-06-26 | N2BW | - | Jun 26, 20:10 UTC | Jun 26, 20:40 UTC | 30m |
| 2026-06-26 | N2BW | - | Jun 26, 18:20 UTC | Jun 26, 19:14 UTC | 55m |
| 2026-06-26 | N2BW | - | Jun 26, 16:24 UTC | Jun 26, 17:15 UTC | 50m |
| 2026-06-24 | N2BW | AEP → SJC | Jun 24, 14:34 UTC | Jun 25, 02:19 UTC | 11h 45m |
| 2026-06-23 | N2BW | SJC → AEP | Jun 23, 01:59 UTC | Jun 23, 13:29 UTC | 11h 30m |
| 2026-06-21 | N2BW | - | Jun 21, 22:29 UTC | Jun 21, 23:24 UTC | 55m |
| 2026-06-21 | N2BW | - | Jun 21, 20:50 UTC | Jun 21, 21:39 UTC | 50m |
| 2026-06-21 | N2BW | - | Jun 21, 18:29 UTC | Jun 21, 19:00 UTC | 30m |
| 2026-06-18 | N2BW | RHV → SBP | Jun 18, 19:00 UTC | Jun 18, 19:35 UTC | 35m |
| 2026-06-18 | N2BW | VNY → SJC | Jun 18, 17:00 UTC | Jun 18, 17:50 UTC | 50m |
| 2026-06-17 | N2BW | SJC → VNY | Jun 17, 22:00 UTC | Jun 17, 22:50 UTC | 50m |
| 2026-06-15 | N2BW | BED → SJC | Jun 15, 19:55 UTC | Jun 16, 01:04 UTC | 5h 10m |
| 2026-06-15 | N2BW | - | Jun 15, 10:55 UTC | Jun 15, 18:35 UTC | 7h 40m |
| 2026-06-15 | N2BW | - | Jun 15, 09:10 UTC | Jun 15, 09:40 UTC | 30m |
| 2026-06-11 | N2BW | - | Jun 11, 09:25 UTC | Jun 11, 10:00 UTC | 35m |
| 2026-06-11 | N2BW | - | Jun 11, 01:05 UTC | Jun 11, 08:00 UTC | 6h 55m |
| 2026-06-10 | N2BW | SJC → BOS | Jun 10, 19:15 UTC | Jun 11, 00:00 UTC | 4h 45m |
| 2026-06-09 | N2BW | - | Jun 9, 21:15 UTC | Jun 9, 21:45 UTC | 30m |
| 2026-06-03 | N2BW | - | Jun 3, 22:15 UTC | Jun 3, 22:45 UTC | 30m |
| 2026-06-03 | N2BW | - | Jun 3, 16:00 UTC | Jun 3, 21:05 UTC | 5h 5m |
| 2026-06-03 | N2BW | RTM → BED | Jun 3, 08:20 UTC | Jun 3, 14:40 UTC | 6h 20m |
| 2026-06-02 | N2BW | - | Jun 2, 08:35 UTC | Jun 2, 10:50 UTC | 2h 15m |
| 2026-06-02 | N2BW | - | Jun 2, 05:00 UTC | Jun 2, 07:00 UTC | 2h 0m |
| 2026-06-01 | N2BW | - | Jun 1, 09:25 UTC | Jun 1, 09:35 UTC | 10m |
| 2026-06-01 | N2BW | JFK → AMS | Jun 1, 01:45 UTC | Jun 1, 08:10 UTC | 6h 25m |
| 2026-05-30 | N2BW | - | May 30, 22:10 UTC | May 31, 01:11 UTC | 3h 1m |
| 2026-05-30 | N2BW | - | May 30, 20:20 UTC | May 30, 21:00 UTC | 40m |
| 2026-05-26 | N2BW | - | May 26, 21:09 UTC | May 26, 21:59 UTC | 50m |
| 2026-05-26 | N2BW | BCN → ANC | May 26, 10:39 UTC | May 26, 19:55 UTC | 9h 15m |
| 2026-05-24 | N2BW | - | May 24, 10:00 UTC | May 24, 11:15 UTC | 1h 15m |
| 2026-05-24 | N2BW | - | May 24, 07:00 UTC | May 24, 09:15 UTC | 2h 15m |
| 2026-05-24 | N2BW | - | May 24, 04:50 UTC | May 24, 05:20 UTC | 30m |
| 2026-05-17 | N2BW | - | May 17, 14:15 UTC | May 17, 14:55 UTC | 40m |
| 2026-05-17 | N2BW | - | May 17, 11:15 UTC | May 17, 12:55 UTC | 1h 40m |
| 2026-05-17 | N2BW | - | May 17, 08:25 UTC | May 17, 10:15 UTC | 1h 50m |
| 2026-05-17 | N2BW | - | May 17, 06:10 UTC | May 17, 07:05 UTC | 55m |
| 2026-05-14 | N2BW | - | May 14, 00:30 UTC | May 14, 09:30 UTC | 9h 0m |
| 2026-05-13 | N2BW | - | May 13, 21:15 UTC | May 13, 23:10 UTC | 1h 55m |
| 2026-05-13 | N2BW | - | May 13, 19:30 UTC | May 13, 20:15 UTC | 45m |
| 2026-05-12 | N2BW | - | May 12, 17:40 UTC | May 12, 18:00 UTC | 20m |
| 2026-04-29 | N2BW | - | Apr 29, 18:25 UTC | Apr 29, 23:45 UTC | 5h 19m |
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 N2BW page for operator, model, and routing details .