sensors Mode-S transponder
5004F4
ICAO 24-bit transponder address
Currently assigned to T7-Y8998 · GULFSTREAM G700
- Hex
- 5004F4
- Octal
- 24002364
- Decimal
- 5,244,148
- Tail
- T7-Y8998
- Type
- GA7C
- Flights observed
- 31
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 4d ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| T7Y8998 | - | 31 | 2026-07-26 |
Recent flights last 31
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | T7Y8998 | BED → TEB | Jul 26, 17:20 UTC | Jul 26, 18:20 UTC | 1h 0m |
| 2026-07-25 | T7Y8998 | - | Jul 25, 16:30 UTC | Jul 25, 19:15 UTC | 2h 45m |
| 2026-07-23 | T7Y8998 | HND → MIA | Jul 23, 13:35 UTC | Jul 24, 02:35 UTC | 13h 0m |
| 2026-07-22 | T7Y8998 | - | Jul 22, 10:20 UTC | Jul 22, 13:30 UTC | 3h 10m |
| 2026-07-19 | T7Y8998 | CCU → HKG | Jul 19, 09:20 UTC | Jul 19, 13:15 UTC | 3h 55m |
| 2026-07-19 | T7Y8998 | - | Jul 19, 07:50 UTC | Jul 19, 08:25 UTC | 35m |
| 2026-07-18 | T7Y8998 | - | Jul 18, 03:00 UTC | Jul 18, 06:40 UTC | 3h 40m |
| 2026-07-14 | T7Y8998 | - | Jul 14, 19:30 UTC | Jul 15, 03:35 UTC | 8h 4m |
| 2026-07-14 | T7Y8998 | - | Jul 14, 17:35 UTC | Jul 14, 18:00 UTC | 25m |
| 2026-07-14 | T7Y8998 | - | Jul 14, 11:10 UTC | Jul 14, 11:55 UTC | 45m |
| 2026-07-10 | T7Y8998 | - | Jul 10, 02:15 UTC | Jul 10, 02:30 UTC | 15m |
| 2026-07-10 | T7Y8998 | - | Jul 10, 00:50 UTC | Jul 10, 01:05 UTC | 15m |
| 2026-07-09 | T7Y8998 | - | Jul 9, 05:30 UTC | Jul 9, 05:40 UTC | 10m |
| 2026-07-07 | T7Y8998 | - | Jul 7, 09:40 UTC | Jul 7, 09:55 UTC | 15m |
| 2026-07-07 | T7Y8998 | - | Jul 7, 08:00 UTC | Jul 7, 09:05 UTC | 1h 5m |
| 2026-07-07 | T7Y8998 | - | Jul 7, 06:05 UTC | Jul 7, 06:50 UTC | 45m |
| 2026-07-05 | T7Y8998 | - | Jul 5, 11:30 UTC | Jul 5, 12:20 UTC | 50m |
| 2026-07-05 | T7Y8998 | - | Jul 5, 07:40 UTC | Jul 5, 10:35 UTC | 2h 55m |
| 2026-07-01 | T7Y8998 | - | Jul 1, 00:30 UTC | Jul 1, 00:50 UTC | 20m |
| 2026-06-30 | T7Y8998 | - | Jun 30, 15:30 UTC | Jun 30, 17:45 UTC | 2h 15m |
| 2026-06-29 | T7Y8998 | - | Jun 29, 15:04 UTC | Jun 29, 16:55 UTC | 1h 50m |
| 2026-06-28 | T7Y8998 | - | Jun 28, 11:25 UTC | Jun 28, 13:19 UTC | 1h 55m |
| 2026-06-25 | T7Y8998 | - | Jun 25, 11:50 UTC | Jun 25, 12:35 UTC | 45m |
| 2026-06-22 | T7Y8998 | - | Jun 22, 19:09 UTC | Jun 23, 08:09 UTC | 13h 0m |
| 2026-06-16 | T7Y8998 | - | Jun 16, 16:20 UTC | Jun 16, 16:50 UTC | 30m |
| 2026-06-16 | T7Y8998 | - | Jun 16, 13:19 UTC | Jun 16, 15:40 UTC | 2h 20m |
| 2026-06-16 | T7Y8998 | - | Jun 16, 11:40 UTC | Jun 16, 11:49 UTC | 10m |
| 2026-06-16 | T7Y8998 | - | Jun 16, 09:10 UTC | Jun 16, 09:25 UTC | 15m |
| 2026-06-16 | T7Y8998 | - | Jun 16, 07:34 UTC | Jun 16, 08:39 UTC | 1h 5m |
| 2026-06-12 | T7Y8998 | - | Jun 12, 08:45 UTC | Jun 12, 21:00 UTC | 12h 15m |
| 2026-06-12 | T7Y8998 | - | Jun 12, 05:55 UTC | Jun 12, 07:40 UTC | 1h 45m |
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 T7-Y8998 page for operator, model, and routing details .