sensors Mode-S transponder
50010B
ICAO 24-bit transponder address · allocated to San Marino
Currently assigned to T7-LKT · GULFSTREAM G650
- Hex
- 50010B
- Octal
- 24000413
- Decimal
- 5,243,147
- Country
- SM
- Tail
- T7-LKT
- Type
- GLF6
- Flights observed
- 69
- Distinct callsigns
- 1
- Country
- SM
- Last broadcast
- 23h ago
Last known position
Country allocation
The ICAO 24-bit address 50010B 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 |
|---|---|---|---|
| TAG02 | - | 69 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | TAG02 | - | Jul 17, 01:35 UTC | Jul 17, 03:10 UTC | 1h 35m |
| 2026-07-16 | TAG02 | - | Jul 16, 22:55 UTC | Jul 17, 00:35 UTC | 1h 40m |
| 2026-07-16 | TAG02 | - | Jul 16, 08:45 UTC | Jul 16, 09:10 UTC | 25m |
| 2026-07-16 | TAG02 | - | Jul 16, 07:05 UTC | Jul 16, 07:20 UTC | 15m |
| 2026-07-13 | TAG02 | - | Jul 13, 05:15 UTC | Jul 13, 06:01 UTC | 45m |
| 2026-07-13 | TAG02 | - | Jul 13, 03:20 UTC | Jul 13, 04:00 UTC | 40m |
| 2026-07-11 | TAG02 | - | Jul 11, 05:01 UTC | Jul 11, 05:35 UTC | 35m |
| 2026-07-11 | TAG02 | - | Jul 11, 03:05 UTC | Jul 11, 03:30 UTC | 25m |
| 2026-07-09 | TAG02 | - | Jul 9, 12:15 UTC | Jul 10, 00:10 UTC | 11h 55m |
| 2026-07-05 | TAG02 | - | Jul 5, 10:00 UTC | Jul 5, 12:20 UTC | 2h 20m |
| 2026-07-05 | TAG02 | - | Jul 5, 06:45 UTC | Jul 5, 07:30 UTC | 45m |
| 2026-06-29 | TAG02 | - | Jun 29, 14:19 UTC | Jun 29, 14:39 UTC | 20m |
| 2026-06-29 | TAG02 | - | Jun 29, 12:05 UTC | Jun 29, 13:19 UTC | 1h 15m |
| 2026-06-29 | TAG02 | - | Jun 29, 07:25 UTC | Jun 29, 08:35 UTC | 1h 10m |
| 2026-06-26 | TAG02 | - | Jun 26, 11:49 UTC | Jun 26, 13:04 UTC | 1h 15m |
| 2026-06-20 | TAG02 | - | Jun 20, 12:54 UTC | Jun 20, 15:54 UTC | 3h 0m |
| 2026-06-19 | TAG02 | - | Jun 19, 10:54 UTC | Jun 19, 14:04 UTC | 3h 10m |
| 2026-06-19 | TAG02 | - | Jun 19, 03:24 UTC | Jun 19, 09:04 UTC | 5h 40m |
| 2026-06-19 | TAG02 | - | Jun 19, 01:04 UTC | Jun 19, 01:50 UTC | 45m |
| 2026-06-16 | TAG02 | LAS → HPN | Jun 16, 05:59 UTC | Jun 16, 10:09 UTC | 4h 10m |
| 2026-06-14 | TAG02 | HND → LAS | Jun 14, 07:05 UTC | Jun 14, 16:05 UTC | 9h 0m |
| 2026-06-13 | TAG02 | - | Jun 13, 02:55 UTC | Jun 13, 06:20 UTC | 3h 24m |
| 2026-06-12 | TAG02 | - | Jun 12, 23:50 UTC | Jun 13, 00:05 UTC | 15m |
| 2026-06-05 | TAG02 | - | Jun 5, 10:15 UTC | Jun 5, 11:55 UTC | 1h 40m |
| 2026-06-05 | TAG02 | - | Jun 5, 09:15 UTC | Jun 5, 09:30 UTC | 15m |
| 2026-06-05 | TAG02 | - | Jun 5, 07:40 UTC | Jun 5, 08:40 UTC | 1h 0m |
| 2026-06-02 | TAG02 | - | Jun 2, 04:05 UTC | Jun 2, 05:45 UTC | 1h 40m |
| 2026-06-02 | TAG02 | - | Jun 2, 00:20 UTC | Jun 2, 01:10 UTC | 50m |
| 2026-05-21 | TAG02 | BKI → SZB | May 21, 06:20 UTC | May 21, 08:25 UTC | 2h 5m |
| 2026-05-20 | TAG02 | SZB → BKI | May 20, 23:20 UTC | May 21, 04:15 UTC | 4h 55m |
| 2026-05-17 | TAG02 | - | May 17, 09:00 UTC | May 17, 10:40 UTC | 1h 40m |
| 2026-05-17 | TAG02 | - | May 17, 06:25 UTC | May 17, 07:25 UTC | 1h 0m |
| 2026-05-14 | TAG02 | - | May 14, 10:05 UTC | May 14, 10:35 UTC | 30m |
| 2026-05-14 | TAG02 | - | May 14, 08:00 UTC | May 14, 08:35 UTC | 35m |
| 2026-05-14 | TAG02 | - | May 14, 03:25 UTC | May 14, 05:05 UTC | 1h 40m |
| 2026-05-14 | TAG02 | - | May 14, 00:25 UTC | May 14, 01:20 UTC | 55m |
| 2026-05-07 | TAG02 | - | May 7, 13:45 UTC | May 7, 13:55 UTC | 10m |
| 2026-05-07 | TAG02 | - | May 7, 10:50 UTC | May 7, 11:05 UTC | 15m |
| 2026-05-07 | TAG02 | - | May 7, 09:20 UTC | May 7, 09:55 UTC | 35m |
| 2026-05-07 | TAG02 | - | May 7, 06:30 UTC | May 7, 06:45 UTC | 15m |
| 2026-05-05 | TAG02 | - | May 5, 07:05 UTC | May 5, 07:45 UTC | 40m |
| 2026-05-05 | TAG02 | - | May 5, 04:05 UTC | May 5, 04:20 UTC | 15m |
| 2026-05-04 | TAG02 | - | May 4, 12:45 UTC | May 4, 13:15 UTC | 30m |
| 2026-05-04 | TAG02 | - | May 4, 05:25 UTC | May 4, 05:40 UTC | 15m |
| 2026-05-03 | TAG02 | - | May 3, 15:25 UTC | May 3, 15:45 UTC | 20m |
| 2026-05-03 | TAG02 | - | May 3, 12:30 UTC | May 3, 12:50 UTC | 20m |
| 2026-05-03 | TAG02 | - | May 3, 10:20 UTC | May 3, 11:15 UTC | 55m |
| 2026-05-01 | TAG02 | - | May 1, 07:30 UTC | May 1, 07:50 UTC | 20m |
| 2026-05-01 | TAG02 | - | May 1, 04:40 UTC | May 1, 04:55 UTC | 15m |
| 2026-05-01 | TAG02 | - | May 1, 02:55 UTC | May 1, 03:10 UTC | 15m |
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-LKT page for operator, model, and routing details .