sensors Mode-S transponder
0B433A
ICAO 24-bit transponder address · allocated to Nicaragua
- Hex
- 0B433A
- Octal
- 02641472
- Decimal
- 738,106
- Country
- NI
- Flights observed
- 37
- Distinct callsigns
- 1
- Country
- NI
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 0B433A falls within the block assigned to Nicaragua (NI) by ICAO Annex 10, Volume III. Every aircraft registered in Nicaragua 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 |
|---|---|---|---|
| TGCHE | - | 37 | 2026-07-24 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | TGCHE | - | Jul 24, 18:55 UTC | Jul 24, 19:10 UTC | 15m |
| 2026-07-20 | TGCHE | - | Jul 20, 11:30 UTC | Jul 20, 11:40 UTC | 10m |
| 2026-07-18 | TGCHE | GUA → GUA | Jul 18, 16:05 UTC | Jul 18, 16:20 UTC | 15m |
| 2026-07-04 | TGCHE | - | Jul 4, 14:00 UTC | Jul 4, 14:55 UTC | 55m |
| 2026-07-03 | TGCHE | GUA → GUA | Jul 3, 17:00 UTC | Jul 3, 17:15 UTC | 15m |
| 2026-07-03 | TGCHE | GUA → GUA | Jul 3, 14:50 UTC | Jul 3, 16:00 UTC | 1h 10m |
| 2026-07-03 | TGCHE | GUA → GUA | Jul 3, 13:55 UTC | Jul 3, 14:05 UTC | 10m |
| 2026-06-27 | TGCHE | - | Jun 27, 21:50 UTC | Jun 27, 22:20 UTC | 30m |
| 2026-06-27 | TGCHE | - | Jun 27, 13:00 UTC | Jun 27, 13:44 UTC | 45m |
| 2026-06-24 | TGCHE | - | Jun 24, 21:04 UTC | Jun 24, 21:14 UTC | 10m |
| 2026-06-21 | TGCHE | GUA → GUA | Jun 21, 20:34 UTC | Jun 21, 20:45 UTC | 10m |
| 2026-06-21 | TGCHE | - | Jun 21, 13:24 UTC | Jun 21, 14:05 UTC | 40m |
| 2026-06-19 | TGCHE | - | Jun 19, 21:44 UTC | Jun 19, 21:54 UTC | 10m |
| 2026-06-15 | TGCHE | - | Jun 15, 21:09 UTC | Jun 15, 21:20 UTC | 10m |
| 2026-06-15 | TGCHE | - | Jun 15, 13:00 UTC | Jun 15, 13:45 UTC | 45m |
| 2026-06-09 | TGCHE | - | Jun 9, 22:25 UTC | Jun 9, 22:40 UTC | 15m |
| 2026-06-09 | TGCHE | - | Jun 9, 14:10 UTC | Jun 9, 14:25 UTC | 15m |
| 2026-06-09 | TGCHE | GUA → GUA | Jun 9, 12:55 UTC | Jun 9, 13:25 UTC | 30m |
| 2026-06-05 | TGCHE | - | Jun 5, 19:05 UTC | Jun 5, 19:40 UTC | 35m |
| 2026-06-05 | TGCHE | - | Jun 5, 17:20 UTC | Jun 5, 17:35 UTC | 15m |
| 2026-06-05 | TGCHE | GUA → GUA | Jun 5, 15:20 UTC | Jun 5, 15:45 UTC | 25m |
| 2026-06-04 | TGCHE | GUA → GUA | Jun 4, 20:15 UTC | Jun 4, 20:40 UTC | 25m |
| 2026-05-24 | TGCHE | - | May 24, 15:50 UTC | May 24, 16:00 UTC | 10m |
| 2026-05-23 | TGCHE | - | May 23, 15:00 UTC | May 23, 15:15 UTC | 15m |
| 2026-05-15 | TGCHE | - | May 15, 20:35 UTC | May 15, 20:45 UTC | 10m |
| 2026-05-15 | TGCHE | - | May 15, 19:30 UTC | May 15, 19:45 UTC | 15m |
| 2026-05-14 | TGCHE | - | May 14, 18:55 UTC | May 14, 19:05 UTC | 10m |
| 2026-05-14 | TGCHE | - | May 14, 16:35 UTC | May 14, 16:45 UTC | 10m |
| 2026-05-14 | TGCHE | - | May 14, 15:30 UTC | May 14, 15:45 UTC | 15m |
| 2026-05-03 | TGCHE | - | May 3, 22:54 UTC | May 3, 23:04 UTC | 10m |
| 2026-05-02 | TGCHE | - | May 2, 14:40 UTC | May 2, 15:00 UTC | 20m |
| 2026-05-02 | TGCHE | GUA → GUA | May 2, 13:40 UTC | May 2, 13:55 UTC | 15m |
| 2026-04-25 | TGCHE | - | Apr 25, 20:40 UTC | Apr 25, 21:00 UTC | 20m |
| 2026-04-25 | TGCHE | - | Apr 25, 14:30 UTC | Apr 25, 14:50 UTC | 20m |
| 2026-04-20 | TGCHE | GUA → GUA | Apr 20, 18:15 UTC | Apr 20, 18:35 UTC | 20m |
| 2026-04-17 | TGCHE | GUA → GUA | Apr 17, 19:50 UTC | Apr 17, 20:20 UTC | 30m |
| 2026-04-16 | TGCHE | - | Apr 16, 16:25 UTC | Apr 16, 16:50 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.