sensors Mode-S transponder
A6548A
ICAO 24-bit transponder address · allocated to United States
Currently assigned to N507GC · operated by CLOUDBOUND LOGISTICS LLC
- Hex
- A6548A
- Octal
- 51452212
- Decimal
- 10,900,618
- Country
- US
- Tail
- N507GC
- Type
- C680
- Flights observed
- 57
- Distinct callsigns
- 5
- Country
- US
- Last broadcast
- Jul 25, 00:40 UTC
Current position
Country allocation
The ICAO 24-bit address A6548A 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 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | OFT4 | ORL → SRQ | Jul 25, 00:10 UTC | Jul 25, 00:40 UTC | 30m |
| 2026-07-24 | OFT4 | - | Jul 24, 14:00 UTC | Jul 24, 15:15 UTC | 1h 15m |
| 2026-07-22 | OFT9 | - | Jul 22, 16:15 UTC | Jul 22, 17:45 UTC | 1h 30m |
| 2026-07-20 | N507GC | TEB → IAD | Jul 20, 13:00 UTC | Jul 20, 13:45 UTC | 45m |
| 2026-07-19 | N507GC | IAD → TEB | Jul 19, 13:05 UTC | Jul 19, 14:45 UTC | 1h 40m |
| 2026-07-16 | OFT9 | - | Jul 16, 19:14 UTC | Jul 16, 21:40 UTC | 2h 25m |
| 2026-07-15 | OFT9 | - | Jul 15, 22:00 UTC | Jul 15, 22:30 UTC | 30m |
| 2026-07-15 | OFT9 | - | Jul 15, 15:15 UTC | Jul 15, 17:15 UTC | 2h 0m |
| 2026-07-02 | OFT9 | - | Jul 2, 22:10 UTC | Jul 3, 00:30 UTC | 2h 20m |
| 2026-07-02 | OFT9 | - | Jul 2, 20:00 UTC | Jul 2, 20:25 UTC | 25m |
| 2026-07-02 | OFT9 | - | Jul 2, 16:50 UTC | Jul 2, 17:10 UTC | 20m |
| 2026-07-02 | OFT9 | - | Jul 2, 12:45 UTC | Jul 2, 13:30 UTC | 45m |
| 2026-07-02 | OFT9 | - | Jul 2, 11:45 UTC | Jul 2, 12:00 UTC | 15m |
| 2026-07-01 | OFT9 | - | Jul 1, 23:55 UTC | Jul 2, 01:55 UTC | 2h 0m |
| 2026-07-01 | N507GC | - | Jul 1, 13:50 UTC | Jul 1, 15:25 UTC | 1h 35m |
| 2026-06-29 | N507GC | - | Jun 29, 12:34 UTC | Jun 29, 13:44 UTC | 1h 10m |
| 2026-06-29 | N507GC | - | Jun 29, 09:00 UTC | Jun 29, 10:24 UTC | 1h 25m |
| 2026-06-19 | N507GC | - | Jun 19, 23:59 UTC | Jun 20, 00:44 UTC | 45m |
| 2026-06-19 | N507GC | - | Jun 19, 19:09 UTC | Jun 19, 22:45 UTC | 3h 35m |
| 2026-06-18 | N507GC | - | Jun 18, 12:40 UTC | Jun 18, 15:40 UTC | 3h 0m |
| 2026-06-18 | 507GC | - | Jun 18, 10:05 UTC | Jun 18, 10:50 UTC | 45m |
| 2026-06-17 | OFT9 | - | Jun 17, 02:25 UTC | Jun 17, 02:35 UTC | 10m |
| 2026-06-17 | OFT9 | - | Jun 17, 00:15 UTC | Jun 17, 01:15 UTC | 1h 0m |
| 2026-06-16 | OFT9 | - | Jun 16, 23:45 UTC | Jun 17, 00:10 UTC | 25m |
| 2026-06-16 | OFT9 | - | Jun 16, 22:25 UTC | Jun 16, 23:10 UTC | 45m |
| 2026-06-16 | OFT9 | - | Jun 16, 16:35 UTC | Jun 16, 17:45 UTC | 1h 10m |
| 2026-06-16 | OFT9 | - | Jun 16, 15:35 UTC | Jun 16, 15:45 UTC | 10m |
| 2026-06-16 | OFT9 | - | Jun 16, 13:25 UTC | Jun 16, 14:20 UTC | 55m |
| 2026-06-06 | N507GC | - | Jun 6, 19:30 UTC | Jun 6, 22:44 UTC | 3h 15m |
| 2026-06-03 | N507GC | - | Jun 3, 17:50 UTC | Jun 3, 20:50 UTC | 3h 0m |
| 2026-06-01 | N507GC | - | Jun 1, 21:55 UTC | Jun 1, 23:40 UTC | 1h 45m |
| 2026-05-21 | OFT9 | HSV → ROG | May 21, 23:25 UTC | May 22, 00:25 UTC | 1h 0m |
| 2026-05-21 | OFT9 | - | May 21, 22:05 UTC | May 21, 22:20 UTC | 15m |
| 2026-05-21 | OFT9 | - | May 21, 21:15 UTC | May 21, 21:35 UTC | 20m |
| 2026-05-21 | OFT9 | - | May 21, 16:10 UTC | May 21, 16:20 UTC | 10m |
| 2026-05-21 | OFT9 | - | May 21, 15:00 UTC | May 21, 15:15 UTC | 15m |
| 2026-05-21 | OFT9 | - | May 21, 13:01 UTC | May 21, 13:45 UTC | 45m |
| 2026-05-20 | OFT9 | - | May 20, 11:45 UTC | May 20, 12:05 UTC | 20m |
| 2026-05-14 | N507GC | - | May 14, 21:20 UTC | May 14, 22:30 UTC | 1h 10m |
| 2026-05-14 | N507GC | - | May 14, 18:45 UTC | May 14, 20:30 UTC | 1h 45m |
| 2026-05-13 | N507GC | - | May 13, 18:15 UTC | May 13, 18:45 UTC | 30m |
| 2026-05-13 | N507GC | - | May 13, 16:40 UTC | May 13, 17:30 UTC | 50m |
| 2026-05-13 | N507GC | - | May 13, 11:00 UTC | May 13, 11:35 UTC | 35m |
| 2026-05-12 | N507GC | - | May 12, 12:10 UTC | May 12, 13:40 UTC | 1h 30m |
| 2026-05-12 | N507GC | - | May 12, 09:30 UTC | May 12, 10:35 UTC | 1h 5m |
| 2026-05-09 | N507GC | - | May 9, 17:05 UTC | May 9, 20:30 UTC | 3h 25m |
| 2026-05-09 | N507GC | - | May 9, 14:50 UTC | May 9, 16:05 UTC | 1h 15m |
| 2026-05-08 | N507GC | - | May 8, 20:45 UTC | May 8, 22:30 UTC | 1h 45m |
| 2026-05-06 | OFT4 | - | May 6, 02:40 UTC | May 6, 04:45 UTC | 2h 5m |
| 2026-05-06 | OFT4 | - | May 6, 01:01 UTC | May 6, 02:01 UTC | 1h 0m |
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 N507GC page for operator, model, and routing details .