sensors Mode-S transponder
AE152C
ICAO 24-bit transponder address
Currently assigned to 166378 · Gulfstream Aerospace C-37B
- Hex
- AE152C
- Octal
- 53412454
- Decimal
- 11,408,684
- Tail
- 166378
- Type
- GLF5
- Flights observed
- 86
- Distinct callsigns
- 19
- Country
- -
- Last broadcast
- 1d ago
Last known position
Callsign history 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| VV501 | - | 14 | 2026-06-26 |
| VV378 | - | 11 | 2026-07-16 |
| VV922 | - | 8 | 2026-04-17 |
| VV587 | - | 6 | 2026-07-17 |
| VM903 | - | 6 | 2026-07-15 |
| VM678 | - | 6 | 2026-07-03 |
| VM616 | - | 6 | 2026-07-24 |
| VV600 | - | 4 | 2026-06-05 |
| VV589 | - | 4 | 2026-07-09 |
| VV602 | - | 3 | 2026-06-16 |
| VV588 | - | 3 | 2026-05-05 |
| VM500 | - | 3 | 2026-05-27 |
| VV904 | - | 2 | 2026-07-01 |
| VV800 | - | 2 | 2026-07-11 |
| VM844 | - | 2 | 2026-05-16 |
| VM512 | - | 2 | 2026-06-12 |
| VM510 | - | 2 | 2026-04-25 |
| VV376 | - | 1 | 2026-05-08 |
| VM378 | - | 1 | 2026-05-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | VM616 | - | Jul 24, 17:00 UTC | Jul 24, 18:05 UTC | 1h 5m |
| 2026-07-24 | VM616 | - | Jul 24, 13:45 UTC | Jul 24, 14:40 UTC | 55m |
| 2026-07-20 | VM616 | NCO → ADW | Jul 20, 22:20 UTC | Jul 20, 23:20 UTC | 1h 0m |
| 2026-07-20 | VM616 | - | Jul 20, 20:30 UTC | Jul 20, 21:25 UTC | 55m |
| 2026-07-17 | VV587 | - | Jul 17, 17:30 UTC | Jul 17, 21:05 UTC | 3h 35m |
| 2026-07-17 | VV587 | - | Jul 17, 10:55 UTC | Jul 17, 14:44 UTC | 3h 50m |
| 2026-07-16 | VV378 | - | Jul 16, 18:05 UTC | Jul 16, 20:00 UTC | 1h 55m |
| 2026-07-15 | VM903 | - | Jul 15, 22:40 UTC | Jul 15, 23:10 UTC | 30m |
| 2026-07-15 | VM903 | - | Jul 15, 14:00 UTC | Jul 15, 14:25 UTC | 25m |
| 2026-07-14 | VV378 | - | Jul 14, 19:45 UTC | Jul 14, 22:50 UTC | 3h 4m |
| 2026-07-14 | VV378 | - | Jul 14, 16:00 UTC | Jul 14, 18:15 UTC | 2h 15m |
| 2026-07-13 | VV378 | - | Jul 13, 21:20 UTC | Jul 13, 22:30 UTC | 1h 10m |
| 2026-07-13 | VV378 | ADW → FFO | Jul 13, 19:15 UTC | Jul 13, 20:55 UTC | 1h 40m |
| 2026-07-11 | VV800 | - | Jul 11, 14:30 UTC | Jul 11, 16:20 UTC | 1h 50m |
| 2026-07-09 | VV800 | - | Jul 9, 15:30 UTC | Jul 9, 17:20 UTC | 1h 50m |
| 2026-07-09 | VV589 | MCF → ADW | Jul 9, 01:40 UTC | Jul 9, 03:40 UTC | 2h 0m |
| 2026-07-08 | VV589 | - | Jul 8, 22:55 UTC | Jul 9, 00:50 UTC | 1h 55m |
| 2026-07-04 | VV587 | JFK → ADW | Jul 4, 17:45 UTC | Jul 4, 18:35 UTC | 50m |
| 2026-07-04 | VV587 | - | Jul 4, 14:00 UTC | Jul 4, 15:10 UTC | 1h 10m |
| 2026-07-03 | VM678 | LGA → ADW | Jul 3, 15:20 UTC | Jul 3, 16:00 UTC | 40m |
| 2026-07-03 | VM678 | ADW → LGA | Jul 3, 13:45 UTC | Jul 3, 14:25 UTC | 40m |
| 2026-07-01 | VV904 | - | Jul 1, 22:25 UTC | Jul 2, 01:15 UTC | 2h 50m |
| 2026-06-30 | VV904 | - | Jun 30, 22:45 UTC | Jul 1, 01:30 UTC | 2h 45m |
| 2026-06-26 | VV501 | - | Jun 26, 08:45 UTC | Jun 26, 17:29 UTC | 8h 45m |
| 2026-06-26 | VV501 | - | Jun 26, 06:09 UTC | Jun 26, 06:35 UTC | 25m |
| 2026-06-25 | VV501 | - | Jun 25, 02:35 UTC | Jun 25, 03:40 UTC | 1h 5m |
| 2026-06-24 | VV501 | - | Jun 24, 01:14 UTC | Jun 24, 01:39 UTC | 25m |
| 2026-06-23 | VV501 | - | Jun 23, 05:00 UTC | Jun 23, 05:20 UTC | 20m |
| 2026-06-22 | VV501 | - | Jun 22, 08:00 UTC | Jun 22, 08:19 UTC | 20m |
| 2026-06-21 | VV501 | - | Jun 21, 00:04 UTC | Jun 21, 14:34 UTC | 14h 30m |
| 2026-06-20 | VV501 | - | Jun 20, 08:14 UTC | Jun 20, 08:25 UTC | 10m |
| 2026-06-19 | VV501 | - | Jun 19, 21:54 UTC | Jun 20, 03:54 UTC | 6h 0m |
| 2026-06-19 | VV501 | - | Jun 19, 13:59 UTC | Jun 19, 14:15 UTC | 15m |
| 2026-06-19 | VV501 | - | Jun 19, 12:34 UTC | Jun 19, 13:24 UTC | 50m |
| 2026-06-18 | VV501 | - | Jun 18, 15:55 UTC | Jun 18, 17:21 UTC | 1h 26m |
| 2026-06-17 | VV501 | - | Jun 17, 19:55 UTC | Jun 17, 22:25 UTC | 2h 30m |
| 2026-06-17 | VV501 | - | Jun 17, 12:30 UTC | Jun 17, 14:25 UTC | 1h 55m |
| 2026-06-16 | VV602 | BOS → ADW | Jun 16, 19:50 UTC | Jun 16, 21:00 UTC | 1h 10m |
| 2026-06-16 | VV602 | - | Jun 16, 17:15 UTC | Jun 16, 18:20 UTC | 1h 5m |
| 2026-06-16 | VV602 | - | Jun 16, 11:15 UTC | Jun 16, 12:05 UTC | 50m |
| 2026-06-12 | VM512 | - | Jun 12, 17:40 UTC | Jun 12, 18:45 UTC | 1h 5m |
| 2026-06-11 | VM512 | - | Jun 11, 11:40 UTC | Jun 11, 12:35 UTC | 55m |
| 2026-06-08 | VV587 | - | Jun 8, 08:30 UTC | Jun 8, 16:10 UTC | 7h 40m |
| 2026-06-06 | VV587 | - | Jun 6, 10:30 UTC | Jun 6, 16:55 UTC | 6h 25m |
| 2026-06-05 | VV600 | - | Jun 5, 16:50 UTC | Jun 5, 21:10 UTC | 4h 20m |
| 2026-06-04 | VV600 | PWT → NZY | Jun 4, 01:55 UTC | Jun 4, 04:05 UTC | 2h 10m |
| 2026-06-02 | VV600 | - | Jun 2, 23:40 UTC | Jun 2, 23:55 UTC | 15m |
| 2026-06-01 | VV600 | - | Jun 1, 17:30 UTC | Jun 1, 22:15 UTC | 4h 45m |
| 2026-05-31 | VM678 | - | May 31, 09:50 UTC | May 31, 17:50 UTC | 8h 0m |
| 2026-05-30 | VM678 | - | May 30, 00:25 UTC | May 30, 07:25 UTC | 7h 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 166378 page for operator, model, and routing details .