sensors Mode-S transponder
4BCCEF
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-SGO · DASSAULT Falcon 2000
- Hex
- 4BCCEF
- Octal
- 22746357
- Decimal
- 4,967,663
- Country
- TR
- Tail
- TC-SGO
- Type
- F2TH
- Flights observed
- 55
- Distinct callsigns
- 1
- Country
- TR
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 4BCCEF falls within the block assigned to Turkey (TR) by ICAO Annex 10, Volume III. Every aircraft registered in Turkey 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 |
|---|---|---|---|
| TCSGO | - | 55 | 2026-06-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-18 | TCSGO | - | Jun 18, 19:20 UTC | Jun 18, 20:05 UTC | 45m |
| 2026-06-18 | TCSGO | - | Jun 18, 17:21 UTC | Jun 18, 18:20 UTC | 59m |
| 2026-06-18 | TCSGO | - | Jun 18, 14:35 UTC | Jun 18, 14:45 UTC | 10m |
| 2026-06-17 | TCSGO | - | Jun 17, 14:15 UTC | Jun 17, 15:00 UTC | 45m |
| 2026-06-17 | TCSGO | - | Jun 17, 05:00 UTC | Jun 17, 05:40 UTC | 40m |
| 2026-06-15 | TCSGO | - | Jun 15, 17:30 UTC | Jun 15, 19:30 UTC | 2h 0m |
| 2026-06-15 | TCSGO | - | Jun 15, 14:34 UTC | Jun 15, 16:45 UTC | 2h 10m |
| 2026-06-13 | TCSGO | - | Jun 13, 12:20 UTC | Jun 13, 13:05 UTC | 45m |
| 2026-06-13 | TCSGO | - | Jun 13, 09:15 UTC | Jun 13, 09:55 UTC | 40m |
| 2026-06-13 | TCSGO | - | Jun 13, 07:20 UTC | Jun 13, 08:10 UTC | 50m |
| 2026-06-13 | TCSGO | - | Jun 13, 05:20 UTC | Jun 13, 06:05 UTC | 45m |
| 2026-06-10 | TCSGO | - | Jun 10, 11:20 UTC | Jun 10, 11:40 UTC | 20m |
| 2026-06-10 | TCSGO | - | Jun 10, 08:50 UTC | Jun 10, 10:45 UTC | 1h 55m |
| 2026-06-09 | TCSGO | - | Jun 9, 13:50 UTC | Jun 10, 10:45 UTC | 20h 55m |
| 2026-06-09 | TCSGO | - | Jun 9, 11:50 UTC | Jun 10, 10:45 UTC | 22h 55m |
| 2026-06-09 | TCSGO | - | Jun 9, 11:10 UTC | Jun 10, 09:45 UTC | 22h 35m |
| 2026-06-09 | TCSGO | - | Jun 9, 07:45 UTC | Jun 9, 09:20 UTC | 1h 35m |
| 2026-06-08 | TCSGO | - | Jun 8, 14:00 UTC | Jun 8, 14:55 UTC | 55m |
| 2026-06-08 | TCSGO | - | Jun 8, 11:35 UTC | Jun 8, 12:25 UTC | 50m |
| 2026-06-05 | TCSGO | - | Jun 5, 22:30 UTC | Jun 6, 00:45 UTC | 2h 15m |
| 2026-06-05 | TCSGO | - | Jun 5, 15:10 UTC | Jun 5, 21:45 UTC | 6h 35m |
| 2026-06-04 | TCSGO | - | Jun 4, 15:50 UTC | Jun 5, 15:45 UTC | 23h 55m |
| 2026-06-04 | TCSGO | - | Jun 4, 12:10 UTC | Jun 4, 16:25 UTC | 4h 15m |
| 2026-06-04 | TCSGO | - | Jun 4, 09:20 UTC | Jun 4, 10:20 UTC | 1h 0m |
| 2026-06-02 | TCSGO | - | Jun 2, 10:30 UTC | Jun 2, 12:50 UTC | 2h 20m |
| 2026-05-31 | TCSGO | - | May 31, 10:10 UTC | May 31, 12:40 UTC | 2h 30m |
| 2026-05-30 | TCSGO | - | May 30, 14:25 UTC | May 30, 16:10 UTC | 1h 45m |
| 2026-05-30 | TCSGO | - | May 30, 09:00 UTC | May 30, 13:15 UTC | 4h 15m |
| 2026-05-29 | TCSGO | - | May 29, 11:50 UTC | May 30, 11:45 UTC | 23h 55m |
| 2026-05-29 | TCSGO | - | May 29, 10:10 UTC | May 30, 09:45 UTC | 23h 35m |
| 2026-05-24 | TCSGO | - | May 24, 10:10 UTC | May 24, 10:20 UTC | 10m |
| 2026-05-22 | TCSGO | - | May 22, 16:20 UTC | May 22, 19:35 UTC | 3h 15m |
| 2026-05-22 | TCSGO | - | May 22, 10:05 UTC | May 22, 14:40 UTC | 4h 35m |
| 2026-05-21 | TCSGO | - | May 21, 15:50 UTC | May 22, 14:40 UTC | 22h 50m |
| 2026-05-21 | TCSGO | - | May 21, 13:50 UTC | May 22, 13:45 UTC | 23h 55m |
| 2026-05-21 | TCSGO | - | May 21, 13:05 UTC | May 22, 11:45 UTC | 22h 40m |
| 2026-05-20 | TCSGO | - | May 20, 18:55 UTC | May 21, 16:20 UTC | 21h 25m |
| 2026-05-20 | TCSGO | - | May 20, 15:50 UTC | May 21, 15:45 UTC | 23h 55m |
| 2026-05-20 | TCSGO | - | May 20, 14:55 UTC | May 20, 19:00 UTC | 4h 5m |
| 2026-05-20 | TCSGO | - | May 20, 10:15 UTC | May 20, 12:10 UTC | 1h 55m |
| 2026-05-19 | TCSGO | - | May 19, 13:50 UTC | May 20, 12:10 UTC | 22h 21m |
| 2026-05-19 | TCSGO | - | May 19, 13:20 UTC | May 20, 11:45 UTC | 22h 26m |
| 2026-05-19 | TCSGO | - | May 19, 10:20 UTC | May 19, 11:55 UTC | 1h 35m |
| 2026-05-15 | TCSGO | - | May 15, 09:35 UTC | May 15, 09:50 UTC | 15m |
| 2026-05-15 | TCSGO | - | May 15, 06:35 UTC | May 15, 07:35 UTC | 1h 0m |
| 2026-05-10 | TCSGO | - | May 10, 12:49 UTC | May 10, 13:30 UTC | 40m |
| 2026-05-09 | TCSGO | - | May 9, 08:30 UTC | May 9, 08:45 UTC | 15m |
| 2026-05-08 | TCSGO | - | May 8, 17:55 UTC | May 9, 07:40 UTC | 13h 45m |
| 2026-05-08 | TCSGO | - | May 8, 07:39 UTC | May 8, 08:05 UTC | 25m |
| 2026-05-06 | TCSGO | - | May 6, 19:05 UTC | May 6, 20:25 UTC | 1h 20m |
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 TC-SGO page for operator, model, and routing details .