sensors Mode-S transponder
4BD26D
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-TSM · BOMBARDIER BD-100 Challenger 350
- Hex
- 4BD26D
- Octal
- 22751155
- Decimal
- 4,969,069
- Country
- TR
- Tail
- TC-TSM
- Type
- CL35
- Flights observed
- 67
- Distinct callsigns
- 1
- Country
- TR
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 4BD26D 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 |
|---|---|---|---|
| TCTSM | - | 67 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | TCTSM | - | Jul 17, 08:00 UTC | Jul 17, 09:10 UTC | 1h 10m |
| 2026-07-14 | TCTSM | - | Jul 14, 05:45 UTC | Jul 14, 06:35 UTC | 50m |
| 2026-07-11 | TCTSM | - | Jul 11, 10:55 UTC | Jul 11, 11:45 UTC | 50m |
| 2026-07-11 | TCTSM | - | Jul 11, 08:25 UTC | Jul 11, 10:00 UTC | 1h 35m |
| 2026-07-08 | TCTSM | - | Jul 8, 18:45 UTC | Jul 8, 20:40 UTC | 1h 55m |
| 2026-07-07 | TCTSM | - | Jul 7, 10:50 UTC | Jul 7, 11:25 UTC | 35m |
| 2026-07-07 | TCTSM | - | Jul 7, 09:10 UTC | Jul 7, 10:10 UTC | 1h 0m |
| 2026-07-06 | TCTSM | - | Jul 6, 07:55 UTC | Jul 6, 08:40 UTC | 45m |
| 2026-07-03 | TCTSM | - | Jul 3, 14:00 UTC | Jul 3, 22:00 UTC | 8h 0m |
| 2026-07-03 | TCTSM | - | Jul 3, 08:20 UTC | Jul 3, 09:30 UTC | 1h 10m |
| 2026-07-01 | TCTSM | - | Jul 1, 19:15 UTC | Jul 1, 19:50 UTC | 35m |
| 2026-07-01 | TCTSM | - | Jul 1, 12:35 UTC | Jul 1, 13:40 UTC | 1h 5m |
| 2026-07-01 | TCTSM | - | Jul 1, 10:10 UTC | Jul 1, 11:10 UTC | 1h 0m |
| 2026-07-01 | TCTSM | - | Jul 1, 08:30 UTC | Jul 1, 09:15 UTC | 45m |
| 2026-06-30 | TCTSM | - | Jun 30, 08:05 UTC | Jun 30, 09:05 UTC | 1h 0m |
| 2026-06-28 | TCTSM | - | Jun 28, 08:14 UTC | Jun 28, 09:10 UTC | 55m |
| 2026-06-27 | TCTSM | - | Jun 27, 11:44 UTC | Jun 28, 09:10 UTC | 21h 25m |
| 2026-06-23 | TCTSM | - | Jun 23, 08:54 UTC | Jun 23, 10:10 UTC | 1h 15m |
| 2026-06-20 | TCTSM | - | Jun 20, 10:09 UTC | Jun 20, 10:59 UTC | 50m |
| 2026-06-20 | TCTSM | - | Jun 20, 08:29 UTC | Jun 20, 09:39 UTC | 1h 10m |
| 2026-06-17 | TCTSM | - | Jun 17, 16:35 UTC | Jun 17, 17:40 UTC | 1h 5m |
| 2026-06-16 | TCTSM | - | Jun 16, 15:55 UTC | Jun 16, 16:39 UTC | 45m |
| 2026-06-13 | TCTSM | - | Jun 13, 08:50 UTC | Jun 13, 09:30 UTC | 40m |
| 2026-06-10 | TCTSM | - | Jun 10, 21:00 UTC | Jun 10, 21:35 UTC | 35m |
| 2026-06-09 | TCTSM | - | Jun 9, 14:00 UTC | Jun 9, 14:55 UTC | 55m |
| 2026-06-06 | TCTSM | - | Jun 6, 10:45 UTC | Jun 6, 11:35 UTC | 50m |
| 2026-06-06 | TCTSM | - | Jun 6, 08:50 UTC | Jun 6, 10:00 UTC | 1h 10m |
| 2026-06-06 | TCTSM | - | Jun 6, 07:10 UTC | Jun 6, 07:20 UTC | 10m |
| 2026-06-03 | TCTSM | - | Jun 3, 16:10 UTC | Jun 3, 17:15 UTC | 1h 5m |
| 2026-06-02 | TCTSM | - | Jun 2, 15:35 UTC | Jun 2, 16:00 UTC | 25m |
| 2026-06-02 | TCTSM | AMM → ISL | Jun 2, 08:35 UTC | Jun 2, 09:35 UTC | 1h 0m |
| 2026-05-31 | TCTSM | - | May 31, 16:55 UTC | May 31, 17:20 UTC | 25m |
| 2026-05-28 | TCTSM | - | May 28, 09:40 UTC | May 28, 10:15 UTC | 35m |
| 2026-05-26 | TCTSM | - | May 26, 13:04 UTC | May 26, 14:45 UTC | 1h 40m |
| 2026-05-26 | TCTSM | - | May 26, 10:50 UTC | May 26, 12:05 UTC | 1h 15m |
| 2026-05-25 | TCTSM | - | May 25, 07:30 UTC | May 25, 08:00 UTC | 30m |
| 2026-05-23 | TCTSM | - | May 23, 10:50 UTC | May 23, 12:10 UTC | 1h 20m |
| 2026-05-23 | TCTSM | - | May 23, 08:55 UTC | May 23, 09:55 UTC | 1h 0m |
| 2026-05-23 | TCTSM | - | May 23, 05:50 UTC | May 23, 06:15 UTC | 25m |
| 2026-05-23 | TCTSM | - | May 23, 04:40 UTC | May 23, 05:15 UTC | 35m |
| 2026-05-22 | TCTSM | - | May 22, 04:10 UTC | May 22, 04:40 UTC | 30m |
| 2026-05-18 | TCTSM | - | May 18, 17:45 UTC | May 18, 18:15 UTC | 30m |
| 2026-05-16 | TCTSM | - | May 16, 20:40 UTC | May 16, 21:20 UTC | 40m |
| 2026-05-16 | TCTSM | - | May 16, 10:40 UTC | May 16, 11:51 UTC | 1h 10m |
| 2026-05-13 | TCTSM | - | May 13, 17:00 UTC | May 13, 17:25 UTC | 25m |
| 2026-05-09 | TCTSM | - | May 9, 09:05 UTC | May 9, 09:30 UTC | 25m |
| 2026-05-06 | TCTSM | - | May 6, 18:00 UTC | May 6, 18:30 UTC | 30m |
| 2026-05-04 | TCTSM | - | May 4, 11:30 UTC | May 4, 13:45 UTC | 2h 15m |
| 2026-05-04 | TCTSM | - | May 4, 07:20 UTC | May 4, 09:30 UTC | 2h 10m |
| 2026-05-02 | TCTSM | - | May 2, 14:55 UTC | May 2, 15:15 UTC | 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-TSM page for operator, model, and routing details .