sensors Mode-S transponder
A6082F
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N488VC · operated by OAKLR LLC
- Hex
- A6082F
- Octal
- 51404057
- Decimal
- 10,881,071
- Country
- US
- Tail
- N488VC
- Type
- CL35
- Flights observed
- 47
- Distinct callsigns
- 1
- Country
- US
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address A6082F 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 |
|---|---|---|---|
| TFF988 | - | 47 | 2026-06-26 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-26 | TFF988 | - | Jun 26, 17:54 UTC | Jun 26, 22:25 UTC | 4h 30m |
| 2026-06-26 | TFF988 | - | Jun 26, 16:09 UTC | Jun 26, 16:24 UTC | 15m |
| 2026-06-24 | TFF988 | - | Jun 24, 14:20 UTC | Jun 24, 18:05 UTC | 3h 45m |
| 2026-06-23 | TFF988 | - | Jun 23, 22:49 UTC | Jun 23, 23:00 UTC | 10m |
| 2026-06-23 | TFF988 | - | Jun 23, 18:50 UTC | Jun 23, 22:15 UTC | 3h 25m |
| 2026-06-21 | TFF988 | - | Jun 21, 16:14 UTC | Jun 21, 20:29 UTC | 4h 15m |
| 2026-06-21 | TFF988 | FRG → BGR | Jun 21, 11:59 UTC | Jun 21, 12:55 UTC | 55m |
| 2026-06-21 | TFF988 | - | Jun 21, 10:09 UTC | Jun 21, 10:19 UTC | 10m |
| 2026-06-20 | TFF988 | - | Jun 20, 02:49 UTC | Jun 20, 02:59 UTC | 10m |
| 2026-06-19 | TFF988 | - | Jun 19, 22:49 UTC | Jun 20, 01:55 UTC | 3h 5m |
| 2026-06-19 | TFF988 | - | Jun 19, 20:40 UTC | Jun 19, 21:44 UTC | 1h 5m |
| 2026-06-18 | TFF988 | - | Jun 18, 21:50 UTC | Jun 19, 21:44 UTC | 23h 54m |
| 2026-06-18 | TFF988 | - | Jun 18, 18:05 UTC | Jun 18, 22:25 UTC | 4h 20m |
| 2026-06-18 | TFF988 | - | Jun 18, 16:10 UTC | Jun 18, 17:10 UTC | 1h 0m |
| 2026-06-15 | TFF988 | - | Jun 15, 16:59 UTC | Jun 15, 18:04 UTC | 1h 5m |
| 2026-06-15 | TFF988 | - | Jun 15, 10:15 UTC | Jun 15, 16:19 UTC | 6h 5m |
| 2026-06-11 | TFF988 | - | Jun 11, 12:45 UTC | Jun 11, 13:20 UTC | 35m |
| 2026-06-09 | TFF988 | - | Jun 9, 02:30 UTC | Jun 9, 08:05 UTC | 5h 35m |
| 2026-06-08 | TFF988 | - | Jun 8, 16:10 UTC | Jun 8, 16:45 UTC | 35m |
| 2026-06-03 | TFF988 | - | Jun 3, 22:10 UTC | Jun 3, 23:45 UTC | 1h 35m |
| 2026-06-03 | TFF988 | - | Jun 3, 14:30 UTC | Jun 3, 16:15 UTC | 1h 45m |
| 2026-05-31 | TFF988 | TEB → HPN | May 31, 16:10 UTC | May 31, 16:35 UTC | 25m |
| 2026-05-31 | TFF988 | - | May 31, 12:30 UTC | May 31, 15:20 UTC | 2h 50m |
| 2026-05-30 | TFF988 | - | May 30, 12:40 UTC | May 30, 15:20 UTC | 2h 40m |
| 2026-05-29 | TFF988 | - | May 29, 17:05 UTC | May 29, 17:55 UTC | 50m |
| 2026-05-29 | TFF988 | - | May 29, 15:10 UTC | May 29, 15:30 UTC | 20m |
| 2026-05-22 | TFF988 | - | May 22, 17:40 UTC | May 22, 20:30 UTC | 2h 50m |
| 2026-05-20 | TFF988 | - | May 20, 18:55 UTC | May 20, 21:15 UTC | 2h 20m |
| 2026-05-20 | TFF988 | - | May 20, 18:00 UTC | May 20, 18:20 UTC | 20m |
| 2026-05-15 | TFF988 | SMX → HPN | May 15, 17:25 UTC | May 15, 22:20 UTC | 4h 55m |
| 2026-05-13 | TFF988 | - | May 13, 14:05 UTC | May 13, 20:15 UTC | 6h 10m |
| 2026-05-09 | TFF988 | - | May 9, 20:44 UTC | May 9, 21:34 UTC | 50m |
| 2026-05-08 | TFF988 | - | May 8, 14:25 UTC | May 8, 14:55 UTC | 30m |
| 2026-05-07 | TFF988 | - | May 7, 16:55 UTC | May 7, 18:40 UTC | 1h 45m |
| 2026-05-05 | TFF988 | - | May 5, 21:25 UTC | May 5, 22:15 UTC | 50m |
| 2026-05-04 | TFF988 | - | May 4, 20:05 UTC | May 4, 22:35 UTC | 2h 30m |
| 2026-05-03 | TFF988 | BJC → HPN | May 3, 15:50 UTC | May 3, 19:05 UTC | 3h 15m |
| 2026-04-30 | TFF988 | - | Apr 30, 14:20 UTC | Apr 30, 18:05 UTC | 3h 45m |
| 2026-04-28 | TFF988 | - | Apr 28, 22:30 UTC | Apr 29, 02:35 UTC | 4h 5m |
| 2026-04-26 | TFF988 | - | Apr 26, 13:30 UTC | Apr 26, 18:15 UTC | 4h 45m |
| 2026-04-26 | TFF988 | - | Apr 26, 12:55 UTC | Apr 26, 13:25 UTC | 30m |
| 2026-04-24 | TFF988 | - | Apr 24, 18:20 UTC | Apr 25, 00:20 UTC | 6h 0m |
| 2026-04-19 | TFF988 | - | Apr 19, 13:15 UTC | Apr 19, 18:25 UTC | 5h 10m |
| 2026-04-15 | TFF988 | - | Apr 15, 17:05 UTC | Apr 15, 18:25 UTC | 1h 20m |
| 2026-04-15 | TFF988 | - | Apr 15, 15:05 UTC | Apr 15, 17:00 UTC | 1h 55m |
| 2026-04-13 | TFF988 | - | Apr 13, 12:20 UTC | Apr 13, 14:20 UTC | 2h 0m |
| 2026-04-13 | TFF988 | - | Apr 13, 09:50 UTC | Apr 13, 10:25 UTC | 35m |
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 N488VC page for operator, model, and routing details .