sensors Mode-S transponder
4BC9B3
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-RMS · BOMBARDIER BD-700 Global 5000/5500
- Hex
- 4BC9B3
- Octal
- 22744663
- Decimal
- 4,966,835
- Country
- TR
- Tail
- TC-RMS
- Type
- GL5T
- Flights observed
- 48
- Distinct callsigns
- 1
- Country
- TR
- Last broadcast
- 8h ago
Last known position
Country allocation
The ICAO 24-bit address 4BC9B3 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 |
|---|---|---|---|
| TCRMS | - | 48 | 2026-06-14 |
Recent flights last 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-14 | TCRMS | - | Jun 14, 09:55 UTC | Jun 14, 10:50 UTC | 55m |
| 2026-06-14 | TCRMS | - | Jun 14, 08:25 UTC | Jun 14, 09:05 UTC | 40m |
| 2026-06-10 | TCRMS | - | Jun 10, 10:10 UTC | Jun 10, 11:00 UTC | 50m |
| 2026-06-10 | TCRMS | - | Jun 10, 07:45 UTC | Jun 10, 08:20 UTC | 35m |
| 2026-06-08 | TCRMS | - | Jun 8, 09:45 UTC | Jun 8, 10:20 UTC | 35m |
| 2026-06-08 | TCRMS | - | Jun 8, 08:25 UTC | Jun 8, 08:55 UTC | 30m |
| 2026-06-08 | TCRMS | - | Jun 8, 05:40 UTC | Jun 8, 06:15 UTC | 35m |
| 2026-06-06 | TCRMS | - | Jun 6, 07:50 UTC | Jun 6, 09:15 UTC | 1h 25m |
| 2026-06-06 | TCRMS | - | Jun 6, 05:30 UTC | Jun 6, 06:15 UTC | 45m |
| 2026-06-05 | TCRMS | - | Jun 5, 08:10 UTC | Jun 5, 08:50 UTC | 40m |
| 2026-06-02 | TCRMS | - | Jun 2, 15:10 UTC | Jun 2, 19:10 UTC | 4h 0m |
| 2026-06-02 | TCRMS | - | Jun 2, 13:45 UTC | Jun 2, 14:00 UTC | 15m |
| 2026-06-02 | TCRMS | - | Jun 2, 11:40 UTC | Jun 2, 11:50 UTC | 10m |
| 2026-06-01 | TCRMS | - | Jun 1, 11:30 UTC | Jun 1, 14:05 UTC | 2h 35m |
| 2026-05-31 | TCRMS | - | May 31, 17:50 UTC | May 31, 18:10 UTC | 20m |
| 2026-05-31 | TCRMS | - | May 31, 13:40 UTC | May 31, 16:35 UTC | 2h 55m |
| 2026-05-31 | TCRMS | - | May 31, 10:55 UTC | May 31, 12:45 UTC | 1h 50m |
| 2026-05-31 | TCRMS | - | May 31, 08:25 UTC | May 31, 09:45 UTC | 1h 20m |
| 2026-05-31 | TCRMS | BTS → BUD | May 31, 00:05 UTC | May 31, 00:35 UTC | 30m |
| 2026-05-30 | TCRMS | - | May 30, 12:00 UTC | May 30, 12:25 UTC | 25m |
| 2026-05-30 | TCRMS | ISL → BUD | May 30, 09:30 UTC | May 30, 11:05 UTC | 1h 35m |
| 2026-05-30 | TCRMS | - | May 30, 07:25 UTC | May 30, 08:15 UTC | 50m |
| 2026-05-28 | TCRMS | - | May 28, 15:40 UTC | May 28, 17:15 UTC | 1h 35m |
| 2026-05-28 | TCRMS | - | May 28, 09:40 UTC | May 28, 14:25 UTC | 4h 45m |
| 2026-05-28 | TCRMS | - | May 28, 07:40 UTC | May 28, 07:55 UTC | 15m |
| 2026-05-28 | TCRMS | - | May 28, 04:40 UTC | May 28, 06:20 UTC | 1h 40m |
| 2026-05-28 | TCRMS | - | May 28, 01:05 UTC | May 28, 02:10 UTC | 1h 5m |
| 2026-05-26 | TCRMS | - | May 26, 20:09 UTC | May 26, 21:14 UTC | 1h 5m |
| 2026-05-26 | TCRMS | - | May 26, 18:34 UTC | May 26, 19:05 UTC | 30m |
| 2026-05-26 | TCRMS | - | May 26, 15:35 UTC | May 26, 15:54 UTC | 20m |
| 2026-05-24 | TCRMS | - | May 24, 09:30 UTC | May 24, 10:20 UTC | 50m |
| 2026-05-24 | TCRMS | - | May 24, 07:50 UTC | May 24, 08:20 UTC | 30m |
| 2026-05-24 | TCRMS | - | May 24, 07:00 UTC | May 24, 07:10 UTC | 10m |
| 2026-05-23 | TCRMS | - | May 23, 13:35 UTC | May 23, 14:25 UTC | 50m |
| 2026-05-23 | TCRMS | - | May 23, 10:10 UTC | May 23, 12:30 UTC | 2h 20m |
| 2026-05-23 | TCRMS | - | May 23, 06:50 UTC | May 23, 07:00 UTC | 10m |
| 2026-05-22 | TCRMS | - | May 22, 11:45 UTC | May 22, 13:15 UTC | 1h 30m |
| 2026-05-20 | TCRMS | - | May 20, 02:05 UTC | May 20, 02:30 UTC | 25m |
| 2026-05-19 | TCRMS | - | May 19, 19:55 UTC | May 19, 22:45 UTC | 2h 50m |
| 2026-05-19 | TCRMS | - | May 19, 15:40 UTC | May 19, 18:50 UTC | 3h 10m |
| 2026-05-09 | TCRMS | - | May 9, 15:10 UTC | May 9, 17:55 UTC | 2h 45m |
| 2026-05-07 | TCRMS | - | May 7, 07:20 UTC | May 7, 10:50 UTC | 3h 30m |
| 2026-05-01 | TCRMS | - | May 1, 08:00 UTC | May 1, 09:25 UTC | 1h 25m |
| 2026-04-30 | TCRMS | - | Apr 30, 14:10 UTC | Apr 30, 15:55 UTC | 1h 45m |
| 2026-04-30 | TCRMS | - | Apr 30, 07:45 UTC | Apr 30, 08:20 UTC | 35m |
| 2026-04-28 | TCRMS | - | Apr 28, 20:10 UTC | Apr 28, 21:15 UTC | 1h 5m |
| 2026-04-27 | TCRMS | - | Apr 27, 13:05 UTC | Apr 27, 15:50 UTC | 2h 45m |
| 2026-04-24 | TCRMS | - | Apr 24, 17:40 UTC | Apr 24, 21:00 UTC | 3h 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-RMS page for operator, model, and routing details .