sensors Mode-S transponder
AE630B
ICAO 24-bit transponder address
Currently assigned to 167082
- Hex
- AE630B
- Octal
- 53461413
- Decimal
- 11,428,619
- Tail
- 167082
- Type
- HAWK
- Flights observed
- 89
- Distinct callsigns
- 5
- Country
- -
- Last broadcast
- 1d ago
Last known position
Callsign history 5 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-27 | CD210 | - | Jun 27, 12:50 UTC | Jun 27, 13:04 UTC | 15m |
| 2026-06-27 | CD210 | - | Jun 27, 11:14 UTC | Jun 27, 11:30 UTC | 15m |
| 2026-06-26 | CD210 | - | Jun 26, 14:05 UTC | Jun 26, 14:25 UTC | 20m |
| 2026-06-25 | CD210 | - | Jun 25, 14:50 UTC | Jun 25, 15:15 UTC | 25m |
| 2026-06-24 | HAWK210 | - | Jun 24, 20:24 UTC | Jun 24, 21:44 UTC | 1h 20m |
| 2026-06-24 | HAWK210 | - | Jun 24, 16:59 UTC | Jun 24, 18:34 UTC | 1h 35m |
| 2026-06-24 | BLZR210 | NQI → NQI | Jun 24, 03:35 UTC | Jun 24, 04:30 UTC | 55m |
| 2026-06-23 | LTHL210 | - | Jun 23, 19:15 UTC | Jun 23, 20:15 UTC | 1h 0m |
| 2026-06-23 | BLZR210 | NQI → NQI | Jun 23, 16:09 UTC | Jun 23, 16:54 UTC | 45m |
| 2026-06-22 | HAWK210 | NQI → NQI | Jun 22, 21:59 UTC | Jun 22, 22:59 UTC | 1h 0m |
| 2026-06-22 | BLZR210 | - | Jun 22, 15:54 UTC | Jun 22, 16:54 UTC | 1h 0m |
| 2026-06-19 | HAWK210 | - | Jun 19, 00:40 UTC | Jun 19, 01:19 UTC | 40m |
| 2026-06-18 | HAWK210 | - | Jun 18, 22:25 UTC | Jun 18, 22:40 UTC | 15m |
| 2026-06-18 | HAWK210 | - | Jun 18, 19:55 UTC | Jun 18, 20:40 UTC | 45m |
| 2026-06-18 | HAWK210 | - | Jun 18, 18:55 UTC | Jun 18, 19:00 UTC | 5m |
| 2026-06-18 | HAWK210 | - | Jun 18, 15:50 UTC | Jun 18, 16:00 UTC | 10m |
| 2026-06-18 | HAWK210 | NQI → NQI | Jun 18, 01:25 UTC | Jun 18, 02:30 UTC | 1h 5m |
| 2026-06-17 | HAWK210 | - | Jun 17, 20:25 UTC | Jun 17, 21:15 UTC | 50m |
| 2026-06-17 | HAWK210 | NQI → NQI | Jun 17, 18:55 UTC | Jun 17, 19:45 UTC | 50m |
| 2026-06-17 | LTHL210 | - | Jun 17, 16:30 UTC | Jun 17, 17:10 UTC | 40m |
| 2026-06-10 | BLZR210 | - | Jun 10, 18:40 UTC | Jun 10, 19:25 UTC | 45m |
| 2026-06-10 | BLZR210 | NQI → NQI | Jun 10, 13:05 UTC | Jun 10, 14:10 UTC | 1h 5m |
| 2026-06-09 | BLZR210 | NQI → NQI | Jun 9, 22:35 UTC | Jun 9, 23:50 UTC | 1h 15m |
| 2026-06-09 | HAWK210 | - | Jun 9, 16:45 UTC | Jun 9, 18:10 UTC | 1h 25m |
| 2026-06-09 | HAWK210 | - | Jun 9, 15:05 UTC | Jun 9, 15:50 UTC | 45m |
| 2026-06-08 | BLZR210 | - | Jun 8, 21:05 UTC | Jun 8, 21:15 UTC | 10m |
| 2026-06-08 | BLZR210 | NQI → NQI | Jun 8, 14:50 UTC | Jun 8, 15:55 UTC | 1h 5m |
| 2026-06-05 | BLZR210 | - | Jun 5, 20:10 UTC | Jun 5, 20:40 UTC | 30m |
| 2026-06-05 | BLZR210 | NQI → NQI | Jun 5, 15:50 UTC | Jun 5, 17:05 UTC | 1h 15m |
| 2026-06-04 | HAWK210 | - | Jun 4, 19:35 UTC | Jun 4, 19:45 UTC | 10m |
| 2026-06-04 | HAWK210 | NQI → NQI | Jun 4, 16:00 UTC | Jun 4, 16:50 UTC | 50m |
| 2026-06-02 | HAWK210 | - | Jun 2, 20:15 UTC | Jun 2, 21:05 UTC | 50m |
| 2026-06-02 | HAWK210 | NQI → NQI | Jun 2, 16:45 UTC | Jun 2, 17:10 UTC | 25m |
| 2026-06-02 | HAWK210 | NQI → NQI | Jun 2, 15:30 UTC | Jun 2, 16:15 UTC | 45m |
| 2026-06-01 | BLZR210 | NQI → NQI | Jun 1, 21:45 UTC | Jun 1, 22:50 UTC | 1h 5m |
| 2026-06-01 | BLZR210 | NQI → NQI | Jun 1, 19:20 UTC | Jun 1, 20:05 UTC | 45m |
| 2026-06-01 | HAWK210 | NQI → NQI | Jun 1, 16:20 UTC | Jun 1, 17:10 UTC | 50m |
| 2026-05-31 | HAWK210 | NQI → NQI | May 31, 18:05 UTC | May 31, 19:15 UTC | 1h 10m |
| 2026-05-29 | HAWK210 | - | May 29, 14:25 UTC | May 29, 15:10 UTC | 45m |
| 2026-05-29 | HAWK210 | - | May 29, 01:40 UTC | May 29, 02:40 UTC | 1h 0m |
| 2026-05-28 | HAWK210 | NQI → NQI | May 28, 21:00 UTC | May 28, 21:30 UTC | 30m |
| 2026-05-28 | HAWK210 | NQI → NQI | May 28, 16:35 UTC | May 28, 17:25 UTC | 50m |
| 2026-05-27 | HAWK210 | NQI → NQI | May 27, 20:55 UTC | May 27, 21:45 UTC | 50m |
| 2026-05-26 | HAWK210 | NQI → NQI | May 26, 21:14 UTC | May 26, 22:39 UTC | 1h 25m |
| 2026-05-26 | HAWK210 | NQI → NQI | May 26, 18:14 UTC | May 26, 19:10 UTC | 55m |
| 2026-05-26 | HAWK210 | - | May 26, 16:55 UTC | May 26, 17:50 UTC | 55m |
| 2026-05-26 | HAWK210 | - | May 26, 14:40 UTC | May 26, 15:20 UTC | 40m |
| 2026-05-26 | HAWK210 | NQI → NQI | May 26, 13:19 UTC | May 26, 14:09 UTC | 50m |
| 2026-05-21 | HAWK210 | - | May 21, 20:50 UTC | May 21, 21:50 UTC | 1h 0m |
| 2026-05-21 | HAWK210 | NQI → NQI | May 21, 18:15 UTC | May 21, 18:35 UTC | 20m |
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 167082 page for operator, model, and routing details .