sensors Mode-S transponder
A2FB16
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N291VK · GULFSTREAM 4
- Hex
- A2FB16
- Octal
- 50575426
- Decimal
- 10,681,110
- Country
- US
- Tail
- N291VK
- Type
- GLF4
- Flights observed
- 47
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address A2FB16 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 |
|---|---|---|---|
| N291VK | - | 47 | 2026-07-15 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-15 | N291VK | - | Jul 15, 02:55 UTC | Jul 15, 03:30 UTC | 35m |
| 2026-07-14 | N291VK | KEF → BGR | Jul 14, 21:45 UTC | Jul 15, 02:15 UTC | 4h 29m |
| 2026-07-14 | N291VK | - | Jul 14, 12:55 UTC | Jul 14, 19:35 UTC | 6h 40m |
| 2026-07-14 | N291VK | - | Jul 14, 08:45 UTC | Jul 14, 11:30 UTC | 2h 45m |
| 2026-07-13 | N291VK | DUB → DWC | Jul 13, 08:55 UTC | Jul 13, 16:55 UTC | 8h 0m |
| 2026-07-12 | N291VK | - | Jul 12, 15:40 UTC | Jul 12, 18:40 UTC | 3h 0m |
| 2026-07-12 | N291VK | - | Jul 12, 07:40 UTC | Jul 12, 12:35 UTC | 4h 55m |
| 2026-07-12 | N291VK | - | Jul 12, 03:45 UTC | Jul 12, 04:15 UTC | 30m |
| 2026-07-08 | N291VK | - | Jul 8, 19:05 UTC | Jul 8, 19:55 UTC | 50m |
| 2026-07-07 | N291VK | - | Jul 7, 23:35 UTC | Jul 8, 19:55 UTC | 20h 20m |
| 2026-07-07 | N291VK | - | Jul 7, 21:35 UTC | Jul 8, 19:55 UTC | 22h 20m |
| 2026-07-07 | N291VK | - | Jul 7, 20:45 UTC | Jul 8, 01:10 UTC | 4h 25m |
| 2026-07-06 | N291VK | - | Jul 6, 02:45 UTC | Jul 6, 08:55 UTC | 6h 10m |
| 2026-07-05 | N291VK | OAK → FOK | Jul 5, 20:30 UTC | Jul 6, 01:35 UTC | 5h 5m |
| 2026-07-02 | N291VK | - | Jul 2, 21:55 UTC | Jul 2, 22:20 UTC | 25m |
| 2026-07-02 | N291VK | - | Jul 2, 17:10 UTC | Jul 2, 17:40 UTC | 30m |
| 2026-07-02 | N291VK | - | Jul 2, 03:00 UTC | Jul 2, 03:25 UTC | 25m |
| 2026-07-01 | N291VK | BGR → VNY | Jul 1, 20:30 UTC | Jul 2, 02:25 UTC | 5h 55m |
| 2026-07-01 | N291VK | - | Jul 1, 12:30 UTC | Jul 1, 19:25 UTC | 6h 55m |
| 2026-06-30 | N291VK | MAD → BQH | Jun 30, 18:25 UTC | Jun 30, 20:10 UTC | 1h 45m |
| 2026-06-30 | N291VK | - | Jun 30, 05:20 UTC | Jun 30, 17:20 UTC | 12h 0m |
| 2026-06-30 | N291VK | - | Jun 30, 01:04 UTC | Jun 30, 02:20 UTC | 1h 16m |
| 2026-06-29 | N291VK | - | Jun 29, 22:39 UTC | Jun 29, 22:49 UTC | 10m |
| 2026-06-28 | N291VK | - | Jun 28, 00:50 UTC | Jun 28, 02:14 UTC | 1h 25m |
| 2026-06-27 | N291VK | - | Jun 27, 22:09 UTC | Jun 27, 23:34 UTC | 1h 25m |
| 2026-06-27 | N291VK | - | Jun 27, 18:45 UTC | Jun 27, 21:04 UTC | 2h 20m |
| 2026-06-17 | N291VK | - | Jun 17, 22:40 UTC | Jun 17, 23:05 UTC | 25m |
| 2026-06-04 | N291VK | - | Jun 4, 15:10 UTC | Jun 4, 15:30 UTC | 20m |
| 2026-06-02 | N291VK | - | Jun 2, 18:00 UTC | Jun 2, 19:10 UTC | 1h 10m |
| 2026-05-27 | N291VK | FLL → FXE | May 27, 05:09 UTC | May 27, 05:19 UTC | 10m |
| 2026-05-27 | N291VK | - | May 27, 01:54 UTC | May 27, 04:30 UTC | 2h 35m |
| 2026-05-26 | N291VK | - | May 26, 22:15 UTC | May 27, 00:30 UTC | 2h 15m |
| 2026-05-14 | N291VK | - | May 14, 09:45 UTC | May 14, 12:15 UTC | 2h 30m |
| 2026-05-14 | N291VK | - | May 14, 05:40 UTC | May 14, 07:30 UTC | 1h 50m |
| 2026-05-13 | N291VK | YYZ → YWG | May 13, 20:05 UTC | May 13, 22:10 UTC | 2h 5m |
| 2026-05-07 | N291VK | YYC → YYZ | May 7, 21:05 UTC | May 8, 00:29 UTC | 3h 25m |
| 2026-05-06 | N291VK | - | May 6, 07:30 UTC | May 6, 07:55 UTC | 25m |
| 2026-05-04 | N291VK | - | May 4, 23:40 UTC | May 5, 00:50 UTC | 1h 10m |
| 2026-05-03 | N291VK | MAD → YVR | May 3, 11:15 UTC | May 3, 23:15 UTC | 12h 0m |
| 2026-05-02 | N291VK | - | May 2, 18:15 UTC | May 3, 07:35 UTC | 13h 19m |
| 2026-05-02 | N291VK | - | May 2, 14:30 UTC | May 2, 16:55 UTC | 2h 25m |
| 2026-04-29 | N291VK | - | Apr 29, 23:25 UTC | Apr 30, 01:15 UTC | 1h 50m |
| 2026-04-29 | N291VK | - | Apr 29, 18:25 UTC | Apr 29, 18:50 UTC | 25m |
| 2026-04-23 | N291VK | - | Apr 23, 18:00 UTC | Apr 23, 18:30 UTC | 30m |
| 2026-04-20 | N291VK | VNY → OAK | Apr 20, 18:30 UTC | Apr 20, 19:30 UTC | 1h 0m |
| 2026-04-18 | N291VK | OAK → VNY | Apr 18, 17:20 UTC | Apr 18, 18:10 UTC | 50m |
| 2026-04-13 | N291VK | - | Apr 13, 21:00 UTC | Apr 13, 22:05 UTC | 1h 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 N291VK page for operator, model, and routing details .