sensors Mode-S transponder
4BD273
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-TSS · BOMBARDIER BD-700 Global 5000/5500
- Hex
- 4BD273
- Octal
- 22751163
- Decimal
- 4,969,075
- Country
- TR
- Tail
- TC-TSS
- Type
- GL5T
- Flights observed
- 59
- Distinct callsigns
- 1
- Country
- TR
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 4BD273 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 |
|---|---|---|---|
| TCTSS | - | 59 | 2026-07-23 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | TCTSS | - | Jul 23, 06:30 UTC | Jul 23, 07:10 UTC | 40m |
| 2026-07-23 | TCTSS | - | Jul 23, 04:55 UTC | Jul 23, 05:35 UTC | 40m |
| 2026-07-07 | TCTSS | - | Jul 7, 16:05 UTC | Jul 7, 16:35 UTC | 30m |
| 2026-07-07 | TCTSS | - | Jul 7, 12:30 UTC | Jul 7, 14:55 UTC | 2h 25m |
| 2026-07-07 | TCTSS | - | Jul 7, 09:30 UTC | Jul 7, 11:30 UTC | 2h 0m |
| 2026-07-06 | TCTSS | - | Jul 6, 22:40 UTC | Jul 7, 08:00 UTC | 9h 20m |
| 2026-07-02 | TCTSS | PIE → FLL | Jul 2, 16:40 UTC | Jul 2, 17:45 UTC | 1h 5m |
| 2026-07-01 | TCTSS | - | Jul 1, 14:05 UTC | Jul 1, 17:20 UTC | 3h 15m |
| 2026-07-01 | TCTSS | - | Jul 1, 08:50 UTC | Jul 1, 14:00 UTC | 5h 10m |
| 2026-07-01 | TCTSS | NCE → GLA | Jul 1, 05:10 UTC | Jul 1, 07:25 UTC | 2h 15m |
| 2026-06-30 | TCTSS | - | Jun 30, 12:50 UTC | Jun 30, 15:15 UTC | 2h 25m |
| 2026-06-30 | TCTSS | - | Jun 30, 10:30 UTC | Jun 30, 10:45 UTC | 15m |
| 2026-06-26 | TCTSS | - | Jun 26, 17:09 UTC | Jun 26, 20:24 UTC | 3h 15m |
| 2026-06-26 | TCTSS | LAX → FAB | Jun 26, 06:19 UTC | Jun 26, 16:20 UTC | 10h 0m |
| 2026-06-21 | TCTSS | SFO → LAX | Jun 21, 20:00 UTC | Jun 21, 20:54 UTC | 55m |
| 2026-06-17 | TCTSS | - | Jun 17, 03:35 UTC | Jun 17, 05:15 UTC | 1h 40m |
| 2026-06-17 | TCTSS | - | Jun 17, 00:10 UTC | Jun 17, 00:35 UTC | 25m |
| 2026-06-12 | TCTSS | - | Jun 12, 20:05 UTC | Jun 13, 04:55 UTC | 8h 49m |
| 2026-06-12 | TCTSS | - | Jun 12, 15:30 UTC | Jun 12, 19:10 UTC | 3h 40m |
| 2026-06-09 | TCTSS | - | Jun 9, 19:50 UTC | Jun 9, 21:20 UTC | 1h 30m |
| 2026-06-09 | TCTSS | LIN → NCE | Jun 9, 17:00 UTC | Jun 9, 17:50 UTC | 50m |
| 2026-06-05 | TCTSS | - | Jun 5, 11:35 UTC | Jun 5, 12:10 UTC | 35m |
| 2026-06-05 | TCTSS | - | Jun 5, 08:10 UTC | Jun 5, 10:50 UTC | 2h 40m |
| 2026-06-03 | TCTSS | - | Jun 3, 12:45 UTC | Jun 3, 13:25 UTC | 40m |
| 2026-06-03 | TCTSS | - | Jun 3, 08:35 UTC | Jun 3, 08:55 UTC | 20m |
| 2026-06-03 | TCTSS | - | Jun 3, 05:45 UTC | Jun 3, 06:10 UTC | 25m |
| 2026-05-31 | TCTSS | - | May 31, 14:05 UTC | May 31, 14:55 UTC | 50m |
| 2026-05-31 | TCTSS | - | May 31, 00:05 UTC | May 31, 00:20 UTC | 15m |
| 2026-05-30 | TCTSS | - | May 30, 22:30 UTC | May 30, 23:25 UTC | 55m |
| 2026-05-30 | TCTSS | - | May 30, 11:30 UTC | May 30, 12:25 UTC | 55m |
| 2026-05-30 | TCTSS | - | May 30, 08:20 UTC | May 30, 08:55 UTC | 35m |
| 2026-05-26 | TCTSS | - | May 26, 20:05 UTC | May 26, 20:20 UTC | 15m |
| 2026-05-25 | TCTSS | - | May 25, 11:40 UTC | May 25, 12:20 UTC | 40m |
| 2026-05-25 | TCTSS | - | May 25, 10:00 UTC | May 25, 10:40 UTC | 40m |
| 2026-05-25 | TCTSS | NSI → ATH | May 25, 03:10 UTC | May 25, 08:00 UTC | 4h 50m |
| 2026-05-23 | TCTSS | - | May 23, 14:50 UTC | May 23, 15:50 UTC | 1h 0m |
| 2026-05-23 | TCTSS | - | May 23, 10:45 UTC | May 23, 11:35 UTC | 50m |
| 2026-05-22 | TCTSS | - | May 22, 22:10 UTC | May 22, 22:45 UTC | 35m |
| 2026-05-22 | TCTSS | - | May 22, 09:00 UTC | May 22, 09:45 UTC | 45m |
| 2026-05-21 | TCTSS | - | May 21, 11:55 UTC | May 21, 12:40 UTC | 45m |
| 2026-05-21 | TCTSS | - | May 21, 10:35 UTC | May 21, 11:20 UTC | 45m |
| 2026-05-19 | TCTSS | - | May 19, 16:40 UTC | May 19, 17:00 UTC | 20m |
| 2026-05-19 | TCTSS | - | May 19, 13:45 UTC | May 19, 14:10 UTC | 25m |
| 2026-05-14 | TCTSS | - | May 14, 14:50 UTC | May 14, 15:15 UTC | 25m |
| 2026-05-14 | TCTSS | - | May 14, 13:30 UTC | May 14, 14:10 UTC | 40m |
| 2026-05-12 | TCTSS | - | May 12, 18:00 UTC | May 12, 19:15 UTC | 1h 15m |
| 2026-05-10 | TCTSS | - | May 10, 21:10 UTC | May 10, 22:25 UTC | 1h 15m |
| 2026-05-08 | TCTSS | - | May 8, 11:30 UTC | May 8, 15:15 UTC | 3h 45m |
| 2026-05-02 | TCTSS | - | May 2, 20:05 UTC | May 2, 20:35 UTC | 30m |
| 2026-05-02 | TCTSS | - | May 2, 06:40 UTC | May 2, 07:05 UTC | 25m |
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-TSS page for operator, model, and routing details .