sensors Mode-S transponder
0C21F7
ICAO 24-bit transponder address · allocated to Suriname
Currently assigned to HP-2011UCG · BOEING 737-300
- Hex
- 0C21F7
- Octal
- 03020767
- Decimal
- 795,127
- Country
- SR
- Tail
- HP-2011UCG
- Type
- B733
- Flights observed
- 37
- Distinct callsigns
- 17
- Country
- SR
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 0C21F7 falls within the block assigned to Suriname (SR) by ICAO Annex 10, Volume III. Every aircraft registered in Suriname 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UCG253 | - | 6 | 2026-05-23 |
| UCG470 | Uniworld Air Cargo | 5 | 2026-05-10 |
| UCG843 | Uniworld Air Cargo | 3 | 2026-04-22 |
| UCG795 | - | 3 | 2026-05-30 |
| UCG247 | - | 3 | 2026-05-23 |
| UCG210 | Uniworld Air Cargo | 3 | 2026-05-30 |
| UCG953 | Uniworld Air Cargo | 2 | 2026-05-07 |
| UCG472 | - | 2 | 2026-04-24 |
| UCG249 | Uniworld Air Cargo | 2 | 2026-05-25 |
| UCG974 | - | 1 | 2026-04-27 |
| UCG970 | Uniworld Air Cargo | 1 | 2026-05-07 |
| UCG954 | - | 1 | 2026-05-08 |
| UCG794 | - | 1 | 2026-05-16 |
| UCG471 | - | 1 | 2026-05-08 |
| UCG291 | - | 1 | 2026-04-14 |
| UCG193 | - | 1 | 2026-05-16 |
| UCG192 | - | 1 | 2026-05-30 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | UCG192 | - | May 30, 13:35 UTC | May 30, 13:55 UTC | 20m |
| 2026-05-30 | UCG795 | - | May 30, 11:10 UTC | May 30, 11:15 UTC | 5m |
| 2026-05-30 | UCG210 | PTY → BOG | May 30, 08:15 UTC | May 30, 08:35 UTC | 20m |
| 2026-05-27 | UCG795 | - | May 27, 12:15 UTC | May 27, 15:40 UTC | 3h 25m |
| 2026-05-25 | UCG249 | CCS → BOG | May 25, 11:50 UTC | May 25, 12:10 UTC | 20m |
| 2026-05-23 | UCG253 | - | May 23, 10:10 UTC | May 23, 11:40 UTC | 1h 30m |
| 2026-05-23 | UCG247 | - | May 23, 01:15 UTC | May 23, 01:35 UTC | 20m |
| 2026-05-20 | UCG253 | - | May 20, 09:45 UTC | May 20, 11:15 UTC | 1h 30m |
| 2026-05-20 | UCG247 | - | May 20, 07:25 UTC | May 20, 07:50 UTC | 25m |
| 2026-05-16 | UCG253 | - | May 16, 08:41 UTC | May 16, 10:11 UTC | 1h 30m |
| 2026-05-16 | UCG794 | - | May 16, 05:46 UTC | May 16, 06:06 UTC | 20m |
| 2026-05-16 | UCG193 | - | May 16, 03:25 UTC | May 16, 03:55 UTC | 30m |
| 2026-05-13 | UCG253 | - | May 13, 11:25 UTC | May 13, 11:55 UTC | 30m |
| 2026-05-10 | UCG470 | PTY → PTY | May 10, 14:25 UTC | May 10, 18:39 UTC | 4h 15m |
| 2026-05-08 | UCG471 | - | May 8, 01:45 UTC | May 8, 18:50 UTC | 17h 5m |
| 2026-05-08 | UCG954 | - | May 8, 00:14 UTC | May 8, 00:25 UTC | 10m |
| 2026-05-07 | UCG953 | CUR → AUA | May 7, 12:10 UTC | May 7, 12:25 UTC | 15m |
| 2026-05-07 | UCG970 | PTY → CUR | May 7, 10:35 UTC | May 7, 10:50 UTC | 15m |
| 2026-05-02 | UCG470 | PTY → PTY | May 2, 13:25 UTC | May 2, 17:45 UTC | 4h 20m |
| 2026-04-28 | UCG470 | PTY → PTY | Apr 28, 13:45 UTC | Apr 28, 18:05 UTC | 4h 20m |
| 2026-04-27 | UCG470 | PTY → PTY | Apr 27, 16:00 UTC | Apr 28, 14:10 UTC | 22h 10m |
| 2026-04-27 | UCG974 | - | Apr 27, 13:55 UTC | Apr 27, 14:20 UTC | 25m |
| 2026-04-27 | UCG795 | - | Apr 27, 10:15 UTC | Apr 27, 10:30 UTC | 15m |
| 2026-04-26 | UCG249 | CCS → BOG | Apr 26, 16:15 UTC | Apr 26, 16:35 UTC | 20m |
| 2026-04-25 | UCG253 | - | Apr 25, 12:35 UTC | Apr 25, 14:00 UTC | 1h 25m |
| 2026-04-25 | UCG210 | PTY → BOG | Apr 25, 07:45 UTC | Apr 25, 08:00 UTC | 15m |
| 2026-04-24 | UCG472 | - | Apr 24, 10:50 UTC | Apr 24, 23:00 UTC | 12h 10m |
| 2026-04-24 | UCG472 | - | Apr 24, 02:10 UTC | Apr 24, 23:00 UTC | 20h 50m |
| 2026-04-23 | UCG953 | CUR → AUA | Apr 23, 11:50 UTC | Apr 23, 12:10 UTC | 20m |
| 2026-04-22 | UCG843 | HAV → SJO | Apr 22, 20:40 UTC | Apr 23, 10:50 UTC | 14h 11m |
| 2026-04-22 | UCG843 | HAV → SJO | Apr 22, 14:25 UTC | Apr 23, 10:50 UTC | 20h 25m |
| 2026-04-22 | UCG843 | HAV → SJO | Apr 22, 10:15 UTC | Apr 23, 01:15 UTC | 15h 0m |
| 2026-04-22 | UCG210 | PTY → BOG | Apr 22, 07:00 UTC | Apr 22, 07:15 UTC | 15m |
| 2026-04-18 | UCG470 | - | Apr 18, 11:45 UTC | Apr 18, 23:45 UTC | 12h 0m |
| 2026-04-16 | UCG247 | - | Apr 16, 10:09 UTC | Apr 16, 10:29 UTC | 20m |
| 2026-04-15 | UCG253 | - | Apr 15, 13:01 UTC | Apr 15, 14:20 UTC | 1h 20m |
| 2026-04-14 | UCG291 | - | Apr 14, 15:25 UTC | Apr 14, 15:40 UTC | 15m |
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 HP-2011UCG page for operator, model, and routing details .