sensors Mode-S transponder
AE1258
ICAO 24-bit transponder address
Currently assigned to 166376 · Gulfstream Aerospace C-37B
- Hex
- AE1258
- Octal
- 53411130
- Decimal
- 11,407,960
- Tail
- 166376
- Type
- GLF5
- Flights observed
- 56
- Distinct callsigns
- 14
- Country
- -
- Last broadcast
- 1d ago
Last known position
Callsign history 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VV376 | - | 9 | 2026-05-10 |
| VV922 | - | 7 | 2026-06-03 |
| VM616 | - | 6 | 2026-04-16 |
| VM903 | - | 5 | 2026-05-15 |
| VV904 | - | 4 | 2026-06-08 |
| VV822 | - | 4 | 2026-05-16 |
| VV800 | - | 4 | 2026-05-11 |
| VM802 | - | 4 | 2026-06-06 |
| VM678 | - | 3 | 2026-06-07 |
| VM510 | - | 3 | 2026-05-21 |
| VV588 | - | 2 | 2026-04-30 |
| VM900 | - | 2 | 2026-05-13 |
| VM376 | - | 2 | 2026-04-14 |
| EXEC1F | - | 1 | 2026-06-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-08 | VV904 | - | Jun 8, 19:45 UTC | Jun 8, 20:45 UTC | 1h 0m |
| 2026-06-08 | VV904 | - | Jun 8, 10:45 UTC | Jun 8, 11:45 UTC | 1h 0m |
| 2026-06-07 | EXEC1F | - | Jun 7, 17:00 UTC | Jun 7, 17:40 UTC | 40m |
| 2026-06-07 | VM678 | - | Jun 7, 14:05 UTC | Jun 7, 14:50 UTC | 45m |
| 2026-06-06 | VM802 | - | Jun 6, 11:14 UTC | Jun 6, 17:54 UTC | 6h 40m |
| 2026-06-06 | VM802 | - | Jun 6, 07:55 UTC | Jun 6, 08:50 UTC | 55m |
| 2026-06-04 | VM802 | STR → NHT | Jun 4, 14:30 UTC | Jun 4, 15:40 UTC | 1h 10m |
| 2026-06-03 | VM802 | - | Jun 3, 12:05 UTC | Jun 3, 19:30 UTC | 7h 25m |
| 2026-06-03 | VV922 | NZY → ADW | Jun 3, 00:35 UTC | Jun 3, 05:05 UTC | 4h 30m |
| 2026-06-02 | VV922 | - | Jun 2, 23:00 UTC | Jun 2, 23:40 UTC | 40m |
| 2026-06-01 | VV922 | - | Jun 1, 21:25 UTC | Jun 2, 02:35 UTC | 5h 10m |
| 2026-05-29 | VV922 | SYD → HNL | May 29, 22:10 UTC | May 30, 07:25 UTC | 9h 15m |
| 2026-05-27 | VV922 | PER → SYD | May 27, 04:09 UTC | May 27, 07:50 UTC | 3h 41m |
| 2026-05-24 | VV922 | - | May 24, 23:00 UTC | May 25, 03:20 UTC | 4h 20m |
| 2026-05-23 | VV922 | HNL → SYD | May 23, 18:25 UTC | May 24, 04:55 UTC | 10h 30m |
| 2026-05-21 | VM510 | - | May 21, 23:15 UTC | May 21, 23:35 UTC | 20m |
| 2026-05-21 | VM510 | - | May 21, 12:55 UTC | May 21, 19:05 UTC | 6h 10m |
| 2026-05-20 | VM510 | - | May 20, 21:10 UTC | May 20, 22:05 UTC | 55m |
| 2026-05-16 | VV822 | - | May 16, 14:51 UTC | May 16, 15:20 UTC | 30m |
| 2026-05-16 | VV822 | - | May 16, 10:50 UTC | May 16, 11:16 UTC | 25m |
| 2026-05-15 | VM903 | - | May 15, 21:10 UTC | May 15, 22:05 UTC | 55m |
| 2026-05-15 | VM903 | - | May 15, 19:10 UTC | May 15, 20:30 UTC | 1h 20m |
| 2026-05-15 | VM903 | - | May 15, 15:40 UTC | May 15, 16:30 UTC | 50m |
| 2026-05-14 | VV822 | TPA → ADW | May 14, 20:05 UTC | May 14, 21:55 UTC | 1h 50m |
| 2026-05-14 | VV822 | - | May 14, 17:20 UTC | May 14, 19:20 UTC | 2h 0m |
| 2026-05-13 | VM900 | STR → ADW | May 13, 12:25 UTC | May 13, 21:10 UTC | 8h 45m |
| 2026-05-12 | VM900 | - | May 12, 11:40 UTC | May 12, 19:15 UTC | 7h 35m |
| 2026-05-11 | VV800 | - | May 11, 15:40 UTC | May 11, 16:50 UTC | 1h 10m |
| 2026-05-10 | VV800 | - | May 10, 15:05 UTC | May 11, 00:10 UTC | 9h 5m |
| 2026-05-10 | VV376 | - | May 10, 01:55 UTC | May 10, 02:24 UTC | 30m |
| 2026-05-10 | VV376 | - | May 10, 00:55 UTC | May 10, 01:14 UTC | 20m |
| 2026-05-09 | VV800 | - | May 9, 22:15 UTC | May 9, 22:30 UTC | 15m |
| 2026-05-09 | VV800 | - | May 9, 11:55 UTC | May 9, 17:35 UTC | 5h 40m |
| 2026-05-08 | VM903 | - | May 8, 18:30 UTC | May 8, 21:55 UTC | 3h 25m |
| 2026-05-08 | VM903 | ADW → HIF | May 8, 12:55 UTC | May 8, 17:00 UTC | 4h 5m |
| 2026-05-04 | VV376 | - | May 4, 19:35 UTC | May 4, 23:30 UTC | 3h 55m |
| 2026-05-04 | VV376 | - | May 4, 12:55 UTC | May 4, 17:25 UTC | 4h 30m |
| 2026-05-02 | VV904 | - | May 2, 00:10 UTC | May 2, 01:50 UTC | 1h 40m |
| 2026-05-01 | VV904 | - | May 1, 21:35 UTC | May 1, 23:30 UTC | 1h 55m |
| 2026-04-30 | VV588 | - | Apr 30, 14:05 UTC | Apr 30, 15:35 UTC | 1h 30m |
| 2026-04-30 | VV588 | - | Apr 30, 11:50 UTC | Apr 30, 13:05 UTC | 1h 15m |
| 2026-04-24 | VM678 | - | Apr 24, 18:55 UTC | Apr 24, 21:00 UTC | 2h 5m |
| 2026-04-24 | VM678 | - | Apr 24, 15:10 UTC | Apr 24, 17:15 UTC | 2h 5m |
| 2026-04-22 | VV376 | - | Apr 22, 14:30 UTC | Apr 22, 15:50 UTC | 1h 20m |
| 2026-04-17 | VV376 | - | Apr 17, 19:25 UTC | Apr 17, 19:50 UTC | 25m |
| 2026-04-17 | VV376 | - | Apr 17, 17:25 UTC | Apr 17, 19:20 UTC | 1h 55m |
| 2026-04-17 | VV376 | - | Apr 17, 15:20 UTC | Apr 17, 17:15 UTC | 1h 55m |
| 2026-04-17 | VV376 | - | Apr 17, 14:35 UTC | Apr 17, 15:15 UTC | 39m |
| 2026-04-16 | VM616 | - | Apr 16, 23:20 UTC | Apr 17, 00:40 UTC | 1h 20m |
| 2026-04-16 | VM616 | - | Apr 16, 22:30 UTC | Apr 16, 23:10 UTC | 40m |
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 166376 page for operator, model, and routing details .