sensors Mode-S transponder
505A87
ICAO 24-bit transponder address
- Hex
- 505A87
- Octal
- 24055207
- Decimal
- 5,266,055
- Flights observed
- 30
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 23h ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OMTVG | - | 30 | 2026-07-25 |
Recent flights last 30
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | OMTVG | - | Jul 25, 08:45 UTC | Jul 25, 10:15 UTC | 1h 30m |
| 2026-07-25 | OMTVG | - | Jul 25, 06:15 UTC | Jul 25, 07:50 UTC | 1h 35m |
| 2026-07-24 | OMTVG | - | Jul 24, 06:30 UTC | Jul 24, 07:05 UTC | 35m |
| 2026-07-23 | OMTVG | - | Jul 23, 10:15 UTC | Jul 23, 11:55 UTC | 1h 40m |
| 2026-07-23 | OMTVG | - | Jul 23, 07:10 UTC | Jul 23, 09:00 UTC | 1h 50m |
| 2026-07-15 | OMTVG | BRU → BTS | Jul 15, 17:05 UTC | Jul 15, 19:00 UTC | 1h 55m |
| 2026-07-15 | OMTVG | BTS → BRU | Jul 15, 04:40 UTC | Jul 15, 07:15 UTC | 2h 35m |
| 2026-07-09 | OMTVG | - | Jul 9, 11:15 UTC | Jul 9, 11:50 UTC | 35m |
| 2026-07-09 | OMTVG | - | Jul 9, 09:15 UTC | Jul 9, 09:50 UTC | 35m |
| 2026-07-08 | OMTVG | - | Jul 8, 11:45 UTC | Jul 8, 12:30 UTC | 45m |
| 2026-07-08 | OMTVG | - | Jul 8, 07:30 UTC | Jul 8, 08:05 UTC | 35m |
| 2026-07-07 | OMTVG | - | Jul 7, 15:10 UTC | Jul 7, 15:50 UTC | 40m |
| 2026-07-03 | OMTVG | - | Jul 3, 14:30 UTC | Jul 3, 15:15 UTC | 45m |
| 2026-06-29 | OMTVG | - | Jun 29, 05:54 UTC | Jun 29, 06:40 UTC | 45m |
| 2026-06-25 | OMTVG | - | Jun 25, 13:35 UTC | Jun 25, 14:39 UTC | 1h 5m |
| 2026-06-25 | OMTVG | - | Jun 25, 06:25 UTC | Jun 25, 07:25 UTC | 1h 0m |
| 2026-06-23 | OMTVG | - | Jun 23, 09:54 UTC | Jun 23, 10:39 UTC | 45m |
| 2026-06-23 | OMTVG | - | Jun 23, 06:19 UTC | Jun 23, 07:09 UTC | 50m |
| 2026-06-18 | OMTVG | - | Jun 18, 14:25 UTC | Jun 18, 15:05 UTC | 40m |
| 2026-06-18 | OMTVG | - | Jun 18, 09:10 UTC | Jun 18, 09:50 UTC | 40m |
| 2026-06-18 | OMTVG | - | Jun 18, 07:30 UTC | Jun 18, 08:05 UTC | 35m |
| 2026-06-17 | OMTVG | - | Jun 17, 12:25 UTC | Jun 17, 16:05 UTC | 3h 40m |
| 2026-06-16 | OMTVG | - | Jun 16, 05:30 UTC | Jun 16, 08:44 UTC | 3h 15m |
| 2026-06-15 | OMTVG | - | Jun 15, 15:15 UTC | Jun 15, 15:45 UTC | 30m |
| 2026-06-11 | OMTVG | - | Jun 11, 11:10 UTC | Jun 11, 11:50 UTC | 40m |
| 2026-06-11 | OMTVG | - | Jun 11, 05:40 UTC | Jun 11, 06:10 UTC | 30m |
| 2026-06-10 | OMTVG | - | Jun 10, 14:05 UTC | Jun 10, 14:50 UTC | 45m |
| 2026-06-09 | OMTVG | - | Jun 9, 13:40 UTC | Jun 9, 14:15 UTC | 35m |
| 2026-06-09 | OMTVG | - | Jun 9, 12:45 UTC | Jun 9, 13:15 UTC | 30m |
| 2026-06-09 | OMTVG | - | Jun 9, 08:35 UTC | Jun 9, 09:05 UTC | 30m |
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.