sensors Mode-S transponder
0C219D
ICAO 24-bit transponder address · allocated to Suriname
Currently assigned to HP-1938UCG · BOEING 737-300
- Hex
- 0C219D
- Octal
- 03020635
- Decimal
- 795,037
- Country
- SR
- Tail
- HP-1938UCG
- Type
- B733
- Flights observed
- 43
- Distinct callsigns
- 20
- Country
- SR
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 0C219D 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| UCG280 | - | 4 | 2026-05-18 |
| UCG253 | - | 4 | 2026-05-09 |
| UCG247 | - | 4 | 2026-05-25 |
| UCG471 | - | 3 | 2026-05-27 |
| UCG301 | - | 3 | 2026-05-26 |
| UCG972 | - | 2 | 2026-05-29 |
| UCG970 | Uniworld Air Cargo | 2 | 2026-05-28 |
| UCG954 | - | 2 | 2026-05-29 |
| UCG953 | Uniworld Air Cargo | 2 | 2026-05-28 |
| UCG774 | - | 2 | 2026-05-25 |
| UCG470 | Uniworld Air Cargo | 2 | 2026-05-29 |
| UCG337 | - | 2 | 2026-05-04 |
| UCG332 | - | 2 | 2026-05-20 |
| UCG330 | - | 2 | 2026-04-23 |
| UCG246 | Uniworld Air Cargo | 2 | 2026-05-25 |
| UCG847 | - | 1 | 2026-04-17 |
| UCG795 | - | 1 | 2026-06-01 |
| UCG211 | - | 1 | 2026-04-26 |
| UCG142 | - | 1 | 2026-04-24 |
| UCG | - | 1 | 2026-05-17 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-01 | UCG795 | - | Jun 1, 02:15 UTC | Jun 1, 02:30 UTC | 15m |
| 2026-05-29 | UCG470 | PTY → PTY | May 29, 21:05 UTC | May 30, 01:20 UTC | 4h 15m |
| 2026-05-29 | UCG972 | - | May 29, 01:50 UTC | May 30, 01:15 UTC | 23h 25m |
| 2026-05-29 | UCG954 | - | May 29, 00:15 UTC | May 29, 00:25 UTC | 10m |
| 2026-05-28 | UCG953 | CUR → AUA | May 28, 12:00 UTC | May 28, 12:20 UTC | 20m |
| 2026-05-28 | UCG970 | PTY → CUR | May 28, 10:40 UTC | May 28, 10:50 UTC | 10m |
| 2026-05-27 | UCG471 | - | May 27, 16:55 UTC | May 27, 21:10 UTC | 4h 15m |
| 2026-05-26 | UCG301 | - | May 26, 17:20 UTC | May 27, 17:15 UTC | 23h 56m |
| 2026-05-26 | UCG301 | - | May 26, 17:04 UTC | May 26, 17:59 UTC | 55m |
| 2026-05-25 | UCG774 | - | May 25, 21:35 UTC | May 26, 03:40 UTC | 6h 5m |
| 2026-05-25 | UCG247 | - | May 25, 09:25 UTC | May 25, 09:45 UTC | 20m |
| 2026-05-25 | UCG246 | BOG → CCS | May 25, 05:20 UTC | May 25, 05:35 UTC | 15m |
| 2026-05-20 | UCG332 | - | May 20, 04:40 UTC | May 20, 07:20 UTC | 2h 40m |
| 2026-05-18 | UCG280 | - | May 18, 05:30 UTC | May 18, 07:40 UTC | 2h 10m |
| 2026-05-17 | UCG246 | BOG → CCS | May 17, 21:30 UTC | May 18, 02:55 UTC | 5h 25m |
| 2026-05-17 | UCG332 | - | May 17, 17:30 UTC | May 17, 17:50 UTC | 20m |
| 2026-05-17 | UCG | - | May 17, 15:10 UTC | May 17, 16:05 UTC | 55m |
| 2026-05-15 | UCG280 | - | May 15, 03:35 UTC | May 15, 05:50 UTC | 2h 15m |
| 2026-05-15 | UCG247 | - | May 15, 00:30 UTC | May 15, 00:50 UTC | 20m |
| 2026-05-10 | UCG301 | - | May 10, 19:15 UTC | May 10, 20:00 UTC | 45m |
| 2026-05-10 | UCG280 | - | May 10, 15:55 UTC | May 10, 16:40 UTC | 45m |
| 2026-05-09 | UCG253 | - | May 9, 11:15 UTC | May 9, 11:40 UTC | 25m |
| 2026-05-06 | UCG253 | - | May 6, 10:45 UTC | May 6, 11:05 UTC | 20m |
| 2026-05-04 | UCG337 | - | May 4, 21:45 UTC | May 4, 23:15 UTC | 1h 30m |
| 2026-05-04 | UCG774 | - | May 4, 07:45 UTC | May 4, 08:25 UTC | 40m |
| 2026-05-02 | UCG253 | - | May 2, 12:35 UTC | May 2, 12:55 UTC | 20m |
| 2026-04-26 | UCG211 | - | Apr 26, 12:45 UTC | Apr 26, 13:00 UTC | 15m |
| 2026-04-26 | UCG247 | - | Apr 26, 10:35 UTC | Apr 26, 10:50 UTC | 15m |
| 2026-04-25 | UCG337 | - | Apr 25, 13:35 UTC | Apr 25, 14:45 UTC | 1h 10m |
| 2026-04-24 | UCG142 | - | Apr 24, 14:25 UTC | Apr 24, 15:00 UTC | 35m |
| 2026-04-23 | UCG330 | - | Apr 23, 16:20 UTC | Apr 23, 17:00 UTC | 40m |
| 2026-04-23 | UCG330 | - | Apr 23, 15:15 UTC | Apr 23, 15:25 UTC | 10m |
| 2026-04-19 | UCG280 | - | Apr 19, 17:00 UTC | Apr 19, 19:25 UTC | 2h 25m |
| 2026-04-19 | UCG247 | - | Apr 19, 12:45 UTC | Apr 19, 13:05 UTC | 20m |
| 2026-04-18 | UCG253 | - | Apr 18, 12:40 UTC | Apr 18, 13:05 UTC | 25m |
| 2026-04-17 | UCG847 | - | Apr 17, 18:25 UTC | Apr 17, 18:35 UTC | 10m |
| 2026-04-17 | UCG972 | - | Apr 17, 01:20 UTC | Apr 17, 01:35 UTC | 15m |
| 2026-04-17 | UCG954 | - | Apr 17, 00:10 UTC | Apr 17, 00:20 UTC | 10m |
| 2026-04-16 | UCG953 | - | Apr 16, 12:00 UTC | Apr 16, 12:19 UTC | 20m |
| 2026-04-16 | UCG970 | - | Apr 16, 10:45 UTC | Apr 16, 10:54 UTC | 10m |
| 2026-04-14 | UCG471 | - | Apr 14, 16:50 UTC | Apr 14, 17:00 UTC | 10m |
| 2026-04-14 | UCG471 | - | Apr 14, 16:35 UTC | Apr 14, 16:45 UTC | 10m |
| 2026-04-14 | UCG470 | - | Apr 14, 12:50 UTC | Apr 14, 13:00 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.
Prefer a tail-number view? See the HP-1938UCG page for operator, model, and routing details .