sensors Mode-S transponder
0C8018
ICAO 24-bit transponder address · allocated to Colombia
Currently assigned to PZ-TFC · FOKKER 70
- Hex
- 0C8018
- Octal
- 03100030
- Decimal
- 819,224
- Country
- CO
- Tail
- PZ-TFC
- Type
- F70
- Flights observed
- 80
- Distinct callsigns
- 4
- Country
- CO
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 0C8018 falls within the block assigned to Colombia (CO) by ICAO Annex 10, Volume III. Every aircraft registered in Colombia 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | EDR629 | - | Jul 13, 14:00 UTC | Jul 13, 16:00 UTC | 2h 0m |
| 2026-07-11 | EDR726 | - | Jul 11, 18:40 UTC | Jul 11, 19:30 UTC | 50m |
| 2026-07-11 | EDR726 | - | Jul 11, 15:50 UTC | Jul 11, 16:05 UTC | 15m |
| 2026-07-10 | EDR725 | - | Jul 10, 16:05 UTC | Jul 11, 16:00 UTC | 23h 56m |
| 2026-07-10 | EDR725 | - | Jul 10, 15:30 UTC | Jul 10, 17:30 UTC | 2h 0m |
| 2026-07-07 | EDR630 | - | Jul 7, 19:45 UTC | Jul 7, 20:30 UTC | 45m |
| 2026-07-07 | EDR630 | - | Jul 7, 16:40 UTC | Jul 7, 16:50 UTC | 10m |
| 2026-07-06 | EDR629 | - | Jul 6, 13:55 UTC | Jul 6, 15:50 UTC | 1h 55m |
| 2026-07-04 | EDR726 | - | Jul 4, 18:35 UTC | Jul 4, 19:25 UTC | 50m |
| 2026-07-04 | EDR726 | - | Jul 4, 15:45 UTC | Jul 4, 16:00 UTC | 15m |
| 2026-07-03 | EDR725 | - | Jul 3, 16:05 UTC | Jul 4, 16:00 UTC | 23h 55m |
| 2026-07-01 | EDR630 | - | Jul 1, 19:45 UTC | Jul 1, 20:15 UTC | 30m |
| 2026-07-01 | EDR630 | - | Jul 1, 16:55 UTC | Jul 1, 17:05 UTC | 10m |
| 2026-06-30 | EDR629 | - | Jun 30, 18:05 UTC | Jul 1, 17:05 UTC | 23h 0m |
| 2026-06-30 | EDR629 | - | Jun 30, 16:25 UTC | Jun 30, 18:20 UTC | 1h 55m |
| 2026-06-29 | EDR629 | - | Jun 29, 22:30 UTC | Jun 30, 18:20 UTC | 19h 51m |
| 2026-06-29 | EDR726 | - | Jun 29, 19:44 UTC | Jun 29, 20:00 UTC | 15m |
| 2026-06-26 | EDR725 | - | Jun 26, 16:35 UTC | Jun 26, 18:29 UTC | 1h 55m |
| 2026-06-23 | EDR630 | SDQ → PBM | Jun 23, 19:50 UTC | Jun 23, 20:15 UTC | 25m |
| 2026-06-23 | EDR630 | SDQ → PBM | Jun 23, 15:59 UTC | Jun 23, 16:09 UTC | 10m |
| 2026-06-22 | EDR629 | - | Jun 22, 13:54 UTC | Jun 22, 15:50 UTC | 1h 55m |
| 2026-06-20 | EDR726 | GEO → PBM | Jun 20, 20:09 UTC | Jun 20, 20:49 UTC | 40m |
| 2026-06-20 | EDR726 | GEO → PBM | Jun 20, 16:09 UTC | Jun 20, 16:19 UTC | 10m |
| 2026-06-19 | EDR725 | - | Jun 19, 15:44 UTC | Jun 19, 17:34 UTC | 1h 50m |
| 2026-06-16 | EDR630 | SDQ → PBM | Jun 16, 23:45 UTC | Jun 16, 23:55 UTC | 10m |
| 2026-06-16 | EDR630 | SDQ → PBM | Jun 16, 18:09 UTC | Jun 16, 18:20 UTC | 10m |
| 2026-06-15 | EDR629 | PBM → SCU | Jun 15, 14:00 UTC | Jun 15, 15:50 UTC | 1h 50m |
| 2026-06-13 | EDR726 | GEO → PBM | Jun 13, 18:35 UTC | Jun 13, 19:00 UTC | 25m |
| 2026-06-12 | EDR725 | - | Jun 12, 15:35 UTC | Jun 12, 17:25 UTC | 1h 50m |
| 2026-06-08 | EDR629 | PBM → SCU | Jun 8, 14:00 UTC | Jun 8, 14:30 UTC | 30m |
| 2026-06-06 | EDR726 | GEO → PBM | Jun 6, 18:39 UTC | Jun 6, 19:14 UTC | 35m |
| 2026-06-06 | EDR726 | GEO → PBM | Jun 6, 15:59 UTC | Jun 6, 16:10 UTC | 10m |
| 2026-06-05 | EDR725 | - | Jun 5, 16:05 UTC | Jun 6, 15:59 UTC | 23h 55m |
| 2026-06-05 | EDR725 | - | Jun 5, 15:45 UTC | Jun 5, 17:40 UTC | 1h 55m |
| 2026-06-02 | EDR630 | SDQ → PBM | Jun 2, 19:05 UTC | Jun 2, 19:40 UTC | 35m |
| 2026-06-01 | EDR629 | PBM → SCU | Jun 1, 14:25 UTC | Jun 1, 16:20 UTC | 1h 55m |
| 2026-05-30 | EDR726 | GEO → PBM | May 30, 18:45 UTC | May 30, 19:00 UTC | 15m |
| 2026-05-30 | EDR726 | GEO → PBM | May 30, 16:00 UTC | May 30, 16:10 UTC | 10m |
| 2026-05-29 | EDR725 | - | May 29, 16:05 UTC | May 30, 16:00 UTC | 23h 55m |
| 2026-05-29 | EDR725 | - | May 29, 15:35 UTC | May 29, 17:30 UTC | 1h 55m |
| 2026-05-26 | EDR630 | SDQ → PBM | May 26, 18:45 UTC | May 26, 19:15 UTC | 30m |
| 2026-05-25 | EDR629 | PBM → SCU | May 25, 13:50 UTC | May 25, 15:45 UTC | 1h 55m |
| 2026-05-23 | EDR726 | GEO → PBM | May 23, 18:45 UTC | May 23, 19:15 UTC | 30m |
| 2026-05-23 | EDR726 | GEO → PBM | May 23, 16:05 UTC | May 23, 16:20 UTC | 15m |
| 2026-05-22 | EDR725 | - | May 22, 15:35 UTC | May 22, 17:25 UTC | 1h 50m |
| 2026-05-19 | EDR630 | SDQ → PBM | May 19, 19:05 UTC | May 19, 19:35 UTC | 30m |
| 2026-05-18 | EDR629 | PBM → SCU | May 18, 13:40 UTC | May 18, 15:40 UTC | 2h 0m |
| 2026-05-16 | EDR726 | GEO → PBM | May 16, 18:20 UTC | May 16, 18:55 UTC | 35m |
| 2026-05-16 | EDR726 | GEO → PBM | May 16, 15:45 UTC | May 16, 16:00 UTC | 15m |
| 2026-05-15 | EDR725 | - | May 15, 16:05 UTC | May 16, 16:00 UTC | 23h 56m |
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 PZ-TFC page for operator, model, and routing details .