sensors Mode-S transponder
0D129C
ICAO 24-bit transponder address · allocated to Mexico
Currently assigned to XA-PBT · GULFSTREAM G280
- Hex
- 0D129C
- Octal
- 03211234
- Decimal
- 856,732
- Country
- MX
- Tail
- XA-PBT
- Type
- G280
- Flights observed
- 60
- Distinct callsigns
- 1
- Country
- MX
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 0D129C falls within the block assigned to Mexico (MX) by ICAO Annex 10, Volume III. Every aircraft registered in Mexico 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 |
|---|---|---|---|
| XAPBT | - | 60 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | XAPBT | - | Jul 17, 20:29 UTC | Jul 17, 22:35 UTC | 2h 5m |
| 2026-07-17 | XAPBT | - | Jul 17, 17:05 UTC | Jul 17, 19:45 UTC | 2h 40m |
| 2026-07-16 | XAPBT | NTR → RST | Jul 16, 17:54 UTC | Jul 16, 20:39 UTC | 2h 45m |
| 2026-07-15 | XAPBT | - | Jul 15, 17:45 UTC | Jul 15, 19:45 UTC | 2h 0m |
| 2026-07-15 | XAPBT | - | Jul 15, 15:05 UTC | Jul 15, 15:20 UTC | 15m |
| 2026-07-15 | XAPBT | - | Jul 15, 01:30 UTC | Jul 15, 03:55 UTC | 2h 25m |
| 2026-07-14 | XAPBT | - | Jul 14, 23:45 UTC | Jul 15, 00:55 UTC | 1h 10m |
| 2026-07-13 | XAPBT | NTR → DAL | Jul 13, 22:10 UTC | Jul 13, 23:40 UTC | 1h 30m |
| 2026-07-12 | XAPBT | - | Jul 12, 19:05 UTC | Jul 12, 19:35 UTC | 30m |
| 2026-07-08 | XAPBT | - | Jul 8, 23:25 UTC | Jul 8, 23:45 UTC | 20m |
| 2026-07-06 | XAPBT | - | Jul 6, 22:10 UTC | Jul 7, 00:05 UTC | 1h 55m |
| 2026-07-06 | XAPBT | - | Jul 6, 20:05 UTC | Jul 6, 20:20 UTC | 15m |
| 2026-07-06 | XAPBT | NTR → APA | Jul 6, 17:15 UTC | Jul 6, 19:30 UTC | 2h 15m |
| 2026-07-06 | XAPBT | - | Jul 6, 05:45 UTC | Jul 6, 06:55 UTC | 1h 10m |
| 2026-07-05 | XAPBT | - | Jul 5, 16:15 UTC | Jul 5, 16:40 UTC | 25m |
| 2026-06-20 | XAPBT | - | Jun 20, 22:10 UTC | Jun 21, 00:40 UTC | 2h 30m |
| 2026-06-20 | XAPBT | LRD → SLC | Jun 20, 17:24 UTC | Jun 20, 19:55 UTC | 2h 30m |
| 2026-06-20 | XAPBT | NTR → LRD | Jun 20, 16:05 UTC | Jun 20, 16:34 UTC | 30m |
| 2026-06-19 | XAPBT | - | Jun 19, 16:14 UTC | Jun 19, 16:49 UTC | 35m |
| 2026-06-19 | XAPBT | - | Jun 19, 14:09 UTC | Jun 19, 15:44 UTC | 1h 35m |
| 2026-06-14 | XAPBT | - | Jun 14, 20:00 UTC | Jun 14, 20:15 UTC | 15m |
| 2026-06-14 | XAPBT | NTR → APA | Jun 14, 17:10 UTC | Jun 14, 19:20 UTC | 2h 10m |
| 2026-06-12 | XAPBT | - | Jun 12, 00:55 UTC | Jun 12, 02:05 UTC | 1h 10m |
| 2026-06-10 | XAPBT | - | Jun 10, 22:15 UTC | Jun 10, 22:40 UTC | 25m |
| 2026-06-08 | XAPBT | - | Jun 8, 20:25 UTC | Jun 8, 23:10 UTC | 2h 45m |
| 2026-06-08 | XAPBT | NTR → RST | Jun 8, 17:00 UTC | Jun 8, 19:35 UTC | 2h 35m |
| 2026-06-07 | XAPBT | - | Jun 7, 19:05 UTC | Jun 7, 19:35 UTC | 30m |
| 2026-06-03 | XAPBT | - | Jun 3, 22:05 UTC | Jun 3, 22:25 UTC | 20m |
| 2026-06-02 | XAPBT | - | Jun 2, 16:25 UTC | Jun 3, 00:15 UTC | 7h 50m |
| 2026-06-01 | XAPBT | - | Jun 1, 22:10 UTC | Jun 1, 22:25 UTC | 15m |
| 2026-05-31 | XAPBT | - | May 31, 21:10 UTC | May 31, 21:35 UTC | 25m |
| 2026-05-31 | XAPBT | - | May 31, 17:25 UTC | May 31, 17:50 UTC | 25m |
| 2026-05-29 | XAPBT | - | May 29, 19:10 UTC | May 29, 19:40 UTC | 30m |
| 2026-05-29 | XAPBT | - | May 29, 15:50 UTC | May 29, 16:10 UTC | 20m |
| 2026-05-26 | XAPBT | - | May 26, 17:44 UTC | May 26, 22:59 UTC | 5h 15m |
| 2026-05-24 | XAPBT | - | May 24, 21:05 UTC | May 24, 23:46 UTC | 2h 41m |
| 2026-05-24 | XAPBT | NTR → RST | May 24, 17:45 UTC | May 24, 20:20 UTC | 2h 35m |
| 2026-05-23 | XAPBT | - | May 23, 19:30 UTC | May 23, 21:25 UTC | 1h 55m |
| 2026-05-23 | XAPBT | - | May 23, 16:15 UTC | May 23, 17:45 UTC | 1h 30m |
| 2026-05-19 | XAPBT | - | May 19, 18:35 UTC | May 19, 19:05 UTC | 30m |
| 2026-05-18 | XAPBT | - | May 18, 23:20 UTC | May 19, 19:05 UTC | 19h 45m |
| 2026-05-18 | XAPBT | - | May 18, 21:15 UTC | May 18, 22:15 UTC | 1h 0m |
| 2026-05-17 | XAPBT | RST → NTR | May 17, 15:15 UTC | May 17, 18:10 UTC | 2h 55m |
| 2026-05-12 | XAPBT | RST → RST | May 12, 21:20 UTC | May 12, 21:25 UTC | 5m |
| 2026-05-12 | XAPBT | - | May 12, 17:55 UTC | May 12, 20:35 UTC | 2h 40m |
| 2026-05-12 | XAPBT | - | May 12, 15:40 UTC | May 12, 16:50 UTC | 1h 10m |
| 2026-05-11 | XAPBT | - | May 11, 15:50 UTC | May 11, 16:10 UTC | 20m |
| 2026-05-10 | XAPBT | - | May 10, 14:54 UTC | May 10, 18:29 UTC | 3h 35m |
| 2026-05-07 | XAPBT | NTR → RDU | May 7, 15:55 UTC | May 7, 18:30 UTC | 2h 35m |
| 2026-05-05 | XAPBT | - | May 5, 22:40 UTC | May 5, 23: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 XA-PBT page for operator, model, and routing details .