sensors Mode-S transponder
0CA3FC
ICAO 24-bit transponder address
- Hex
- 0CA3FC
- Octal
- 03121774
- Decimal
- 828,412
- Flights observed
- 34
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 1d ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| V2TMB | - | 34 | 2026-07-17 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | V2TMB | - | Jul 17, 13:05 UTC | Jul 17, 13:15 UTC | 10m |
| 2026-07-15 | V2TMB | - | Jul 15, 15:15 UTC | Jul 15, 15:25 UTC | 10m |
| 2026-07-15 | V2TMB | - | Jul 15, 13:35 UTC | Jul 15, 13:45 UTC | 10m |
| 2026-07-13 | V2TMB | - | Jul 13, 13:25 UTC | Jul 13, 13:45 UTC | 20m |
| 2026-07-12 | V2TMB | - | Jul 12, 21:45 UTC | Jul 12, 21:55 UTC | 10m |
| 2026-07-12 | V2TMB | - | Jul 12, 13:55 UTC | Jul 12, 14:15 UTC | 20m |
| 2026-07-11 | V2TMB | - | Jul 11, 23:20 UTC | Jul 11, 23:30 UTC | 10m |
| 2026-07-11 | V2TMB | - | Jul 11, 14:40 UTC | Jul 11, 14:50 UTC | 10m |
| 2026-07-11 | V2TMB | - | Jul 11, 13:35 UTC | Jul 11, 13:50 UTC | 15m |
| 2026-07-10 | V2TMB | - | Jul 10, 13:20 UTC | Jul 10, 13:35 UTC | 15m |
| 2026-07-09 | V2TMB | - | Jul 9, 22:00 UTC | Jul 9, 22:10 UTC | 10m |
| 2026-07-06 | V2TMB | - | Jul 6, 12:40 UTC | Jul 6, 12:55 UTC | 15m |
| 2026-07-05 | V2TMB | - | Jul 5, 12:50 UTC | Jul 5, 13:10 UTC | 20m |
| 2026-07-04 | V2TMB | - | Jul 4, 22:20 UTC | Jul 4, 22:30 UTC | 10m |
| 2026-07-03 | V2TMB | - | Jul 3, 23:05 UTC | Jul 3, 23:35 UTC | 30m |
| 2026-07-03 | V2TMB | - | Jul 3, 22:10 UTC | Jul 3, 22:25 UTC | 15m |
| 2026-07-03 | V2TMB | - | Jul 3, 13:50 UTC | Jul 3, 14:10 UTC | 20m |
| 2026-06-29 | V2TMB | - | Jun 29, 11:29 UTC | Jun 29, 11:55 UTC | 25m |
| 2026-06-28 | V2TMB | - | Jun 28, 21:20 UTC | Jun 28, 21:30 UTC | 10m |
| 2026-06-28 | V2TMB | - | Jun 28, 11:50 UTC | Jun 28, 12:05 UTC | 15m |
| 2026-05-04 | V2TMB | - | May 4, 11:30 UTC | May 4, 11:50 UTC | 20m |
| 2026-05-03 | V2TMB | - | May 3, 11:50 UTC | May 3, 12:00 UTC | 10m |
| 2026-05-01 | V2TMB | - | May 1, 11:45 UTC | May 1, 12:00 UTC | 15m |
| 2026-04-30 | V2TMB | - | Apr 30, 12:15 UTC | Apr 30, 12:25 UTC | 10m |
| 2026-04-27 | V2TMB | - | Apr 27, 11:40 UTC | Apr 27, 11:55 UTC | 15m |
| 2026-04-26 | V2TMB | - | Apr 26, 22:35 UTC | Apr 26, 22:50 UTC | 15m |
| 2026-04-26 | V2TMB | - | Apr 26, 12:15 UTC | Apr 26, 12:25 UTC | 10m |
| 2026-04-23 | V2TMB | - | Apr 23, 12:40 UTC | Apr 23, 12:55 UTC | 15m |
| 2026-04-20 | V2TMB | - | Apr 20, 11:45 UTC | Apr 20, 12:05 UTC | 20m |
| 2026-04-19 | V2TMB | - | Apr 19, 12:45 UTC | Apr 19, 13:00 UTC | 15m |
| 2026-04-17 | V2TMB | - | Apr 17, 11:25 UTC | Apr 17, 11:40 UTC | 15m |
| 2026-04-16 | V2TMB | - | Apr 16, 22:54 UTC | Apr 16, 23:05 UTC | 10m |
| 2026-04-16 | V2TMB | - | Apr 16, 12:39 UTC | Apr 16, 12:55 UTC | 15m |
| 2026-04-13 | V2TMB | - | Apr 13, 11:35 UTC | Apr 13, 12:00 UTC | 25m |
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.