sensors Mode-S transponder
5002E7
ICAO 24-bit transponder address · allocated to San Marino
Currently assigned to T7-AAA7 · BOMBARDIER BD-700 Global 7000/7500
- Hex
- 5002E7
- Octal
- 24001347
- Decimal
- 5,243,623
- Country
- SM
- Tail
- T7-AAA7
- Type
- GL7T
- Flights observed
- 49
- Distinct callsigns
- 1
- Country
- SM
- Last broadcast
- Jul 26, 09:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 5002E7 falls within the block assigned to San Marino (SM) by ICAO Annex 10, Volume III. Every aircraft registered in San Marino 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| T7AAA7 | - | 49 | 2026-07-26 |
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | T7AAA7 | - | Jul 26, 05:55 UTC | Jul 26, 09:45 UTC | 3h 51m |
| 2026-07-25 | T7AAA7 | - | Jul 25, 23:55 UTC | Jul 26, 04:05 UTC | 4h 10m |
| 2026-07-21 | T7AAA7 | - | Jul 21, 22:20 UTC | Jul 22, 05:25 UTC | 7h 5m |
| 2026-07-21 | T7AAA7 | - | Jul 21, 18:25 UTC | Jul 21, 18:35 UTC | 10m |
| 2026-07-19 | T7AAA7 | LAS → TEB | Jul 19, 06:25 UTC | Jul 19, 11:00 UTC | 4h 35m |
| 2026-07-17 | T7AAA7 | - | Jul 17, 10:20 UTC | Jul 17, 20:44 UTC | 10h 25m |
| 2026-07-17 | T7AAA7 | - | Jul 17, 04:29 UTC | Jul 17, 08:54 UTC | 4h 25m |
| 2026-07-12 | T7AAA7 | - | Jul 12, 18:05 UTC | Jul 12, 22:15 UTC | 4h 10m |
| 2026-07-10 | T7AAA7 | - | Jul 10, 05:40 UTC | Jul 10, 10:30 UTC | 4h 50m |
| 2026-06-30 | T7AAA7 | - | Jun 30, 04:55 UTC | Jun 30, 15:00 UTC | 10h 5m |
| 2026-06-28 | T7AAA7 | - | Jun 28, 14:45 UTC | Jun 28, 16:25 UTC | 1h 40m |
| 2026-06-27 | T7AAA7 | BUR → ATL | Jun 27, 05:25 UTC | Jun 27, 09:00 UTC | 3h 35m |
| 2026-06-27 | T7AAA7 | ATL → BUR | Jun 27, 00:00 UTC | Jun 27, 04:05 UTC | 4h 5m |
| 2026-06-26 | T7AAA7 | - | Jun 26, 20:40 UTC | Jun 26, 21:59 UTC | 1h 20m |
| 2026-06-25 | T7AAA7 | - | Jun 25, 13:50 UTC | Jun 25, 15:40 UTC | 1h 50m |
| 2026-06-20 | T7AAA7 | - | Jun 20, 13:24 UTC | Jun 20, 13:44 UTC | 20m |
| 2026-06-19 | T7AAA7 | ATL → LAS | Jun 19, 17:09 UTC | Jun 19, 20:55 UTC | 3h 45m |
| 2026-06-18 | T7AAA7 | - | Jun 18, 07:10 UTC | Jun 18, 09:45 UTC | 2h 35m |
| 2026-06-17 | T7AAA7 | - | Jun 17, 19:05 UTC | Jun 17, 23:30 UTC | 4h 25m |
| 2026-06-16 | T7AAA7 | - | Jun 16, 04:25 UTC | Jun 16, 16:10 UTC | 11h 45m |
| 2026-06-13 | T7AAA7 | - | Jun 13, 21:55 UTC | Jun 14, 02:10 UTC | 4h 15m |
| 2026-06-12 | T7AAA7 | - | Jun 12, 13:15 UTC | Jun 12, 14:40 UTC | 1h 25m |
| 2026-06-12 | T7AAA7 | - | Jun 12, 10:10 UTC | Jun 12, 11:25 UTC | 1h 15m |
| 2026-06-12 | T7AAA7 | - | Jun 12, 03:35 UTC | Jun 12, 09:00 UTC | 5h 25m |
| 2026-05-31 | T7AAA7 | - | May 31, 23:55 UTC | Jun 1, 01:45 UTC | 1h 50m |
| 2026-05-29 | T7AAA7 | - | May 29, 15:55 UTC | May 30, 09:55 UTC | 18h 0m |
| 2026-05-29 | T7AAA7 | - | May 29, 12:45 UTC | May 30, 09:55 UTC | 21h 10m |
| 2026-05-29 | T7AAA7 | - | May 29, 07:25 UTC | May 29, 11:30 UTC | 4h 5m |
| 2026-05-22 | T7AAA7 | - | May 22, 19:25 UTC | May 22, 23:05 UTC | 3h 40m |
| 2026-05-22 | T7AAA7 | - | May 22, 14:00 UTC | May 22, 17:55 UTC | 3h 55m |
| 2026-05-21 | T7AAA7 | - | May 21, 13:20 UTC | May 21, 14:25 UTC | 1h 5m |
| 2026-05-21 | T7AAA7 | - | May 21, 05:10 UTC | May 21, 06:20 UTC | 1h 10m |
| 2026-05-17 | T7AAA7 | - | May 17, 20:40 UTC | May 18, 01:40 UTC | 5h 0m |
| 2026-05-17 | T7AAA7 | - | May 17, 15:25 UTC | May 17, 17:45 UTC | 2h 20m |
| 2026-05-16 | T7AAA7 | - | May 16, 04:50 UTC | May 16, 06:50 UTC | 2h 1m |
| 2026-05-15 | T7AAA7 | - | May 15, 05:50 UTC | May 16, 05:46 UTC | 23h 55m |
| 2026-05-15 | T7AAA7 | - | May 15, 01:10 UTC | May 15, 07:00 UTC | 5h 50m |
| 2026-05-10 | T7AAA7 | - | May 10, 16:55 UTC | May 10, 18:55 UTC | 2h 0m |
| 2026-05-09 | T7AAA7 | - | May 9, 10:10 UTC | May 9, 10:30 UTC | 20m |
| 2026-05-09 | T7AAA7 | - | May 9, 08:25 UTC | May 9, 09:20 UTC | 55m |
| 2026-05-06 | T7AAA7 | - | May 6, 08:40 UTC | May 6, 13:10 UTC | 4h 30m |
| 2026-05-01 | T7AAA7 | - | May 1, 11:15 UTC | May 1, 13:05 UTC | 1h 50m |
| 2026-04-28 | T7AAA7 | - | Apr 28, 22:49 UTC | Apr 28, 23:20 UTC | 30m |
| 2026-04-23 | T7AAA7 | - | Apr 23, 16:30 UTC | Apr 23, 17:35 UTC | 1h 5m |
| 2026-04-20 | T7AAA7 | - | Apr 20, 16:10 UTC | Apr 20, 17:25 UTC | 1h 15m |
| 2026-04-19 | T7AAA7 | - | Apr 19, 14:00 UTC | Apr 19, 18:15 UTC | 4h 15m |
| 2026-04-17 | T7AAA7 | - | Apr 17, 09:20 UTC | Apr 17, 10:05 UTC | 45m |
| 2026-04-17 | T7AAA7 | - | Apr 17, 07:35 UTC | Apr 17, 09:15 UTC | 1h 40m |
| 2026-04-17 | T7AAA7 | - | Apr 17, 05:40 UTC | Apr 17, 06:45 UTC | 1h 5m |
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-AAA7 page for operator, model, and routing details .