sensors Mode-S transponder
0B4413
ICAO 24-bit transponder address · allocated to Nicaragua
- Hex
- 0B4413
- Octal
- 02642023
- Decimal
- 738,323
- Country
- NI
- Flights observed
- 27
- Distinct callsigns
- 1
- Country
- NI
- Last broadcast
- Jul 25, 16:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 0B4413 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 |
|---|---|---|---|
| TGJDN | - | 27 | 2026-07-25 |
Recent flights last 27
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | TGJDN | - | Jul 25, 15:50 UTC | Jul 25, 16:00 UTC | 10m |
| 2026-07-21 | TGJDN | - | Jul 21, 14:00 UTC | Jul 21, 14:20 UTC | 20m |
| 2026-07-17 | TGJDN | - | Jul 17, 17:25 UTC | Jul 17, 17:44 UTC | 20m |
| 2026-07-08 | TGJDN | - | Jul 8, 14:35 UTC | Jul 8, 14:45 UTC | 10m |
| 2026-06-28 | TGJDN | - | Jun 28, 21:20 UTC | Jun 28, 21:34 UTC | 15m |
| 2026-06-24 | TGJDN | - | Jun 24, 12:50 UTC | Jun 24, 13:10 UTC | 20m |
| 2026-06-20 | TGJDN | - | Jun 20, 18:45 UTC | Jun 20, 19:04 UTC | 20m |
| 2026-06-19 | TGJDN | - | Jun 19, 18:44 UTC | Jun 19, 19:04 UTC | 20m |
| 2026-06-16 | TGJDN | - | Jun 16, 19:50 UTC | Jun 16, 20:05 UTC | 15m |
| 2026-06-16 | TGJDN | - | Jun 16, 13:15 UTC | Jun 16, 13:30 UTC | 15m |
| 2026-06-05 | TGJDN | - | Jun 5, 18:25 UTC | Jun 5, 18:35 UTC | 10m |
| 2026-05-29 | TGJDN | - | May 29, 20:15 UTC | May 29, 20:30 UTC | 15m |
| 2026-05-29 | TGJDN | - | May 29, 16:20 UTC | May 29, 16:35 UTC | 15m |
| 2026-05-28 | TGJDN | - | May 28, 18:05 UTC | May 28, 18:30 UTC | 25m |
| 2026-05-22 | TGJDN | - | May 22, 19:00 UTC | May 22, 19:20 UTC | 20m |
| 2026-05-19 | TGJDN | - | May 19, 20:35 UTC | May 19, 20:50 UTC | 15m |
| 2026-05-19 | TGJDN | - | May 19, 14:05 UTC | May 19, 14:20 UTC | 15m |
| 2026-05-15 | TGJDN | - | May 15, 21:00 UTC | May 15, 21:10 UTC | 10m |
| 2026-05-14 | TGJDN | - | May 14, 21:20 UTC | May 14, 21:35 UTC | 15m |
| 2026-05-08 | TGJDN | - | May 8, 19:55 UTC | May 8, 20:05 UTC | 10m |
| 2026-05-08 | TGJDN | - | May 8, 13:45 UTC | May 8, 14:05 UTC | 20m |
| 2026-04-30 | TGJDN | - | Apr 30, 15:45 UTC | Apr 30, 15:55 UTC | 10m |
| 2026-04-24 | TGJDN | - | Apr 24, 21:30 UTC | Apr 24, 21:45 UTC | 15m |
| 2026-04-24 | TGJDN | - | Apr 24, 14:45 UTC | Apr 24, 15:00 UTC | 15m |
| 2026-04-23 | TGJDN | - | Apr 23, 18:10 UTC | Apr 23, 18:20 UTC | 10m |
| 2026-04-21 | TGJDN | - | Apr 21, 14:40 UTC | Apr 21, 14:50 UTC | 10m |
| 2026-04-18 | TGJDN | - | Apr 18, 17:40 UTC | Apr 18, 17:50 UTC | 10m |
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.