sensors Mode-S transponder
4BB1AB
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-LMK · DASSAULT Falcon 6X
- Hex
- 4BB1AB
- Octal
- 22730653
- Decimal
- 4,960,683
- Country
- TR
- Tail
- TC-LMK
- Type
- FA6X
- Flights observed
- 66
- Distinct callsigns
- 1
- Country
- TR
- Last broadcast
- 16h ago
Last known position
Country allocation
The ICAO 24-bit address 4BB1AB 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 |
|---|---|---|---|
| TCLMK | - | 66 | 2026-07-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | TCLMK | - | Jul 17, 13:55 UTC | Jul 17, 14:35 UTC | 40m |
| 2026-07-17 | TCLMK | - | Jul 17, 11:50 UTC | Jul 17, 12:45 UTC | 55m |
| 2026-07-16 | TCLMK | - | Jul 16, 15:05 UTC | Jul 16, 17:30 UTC | 2h 25m |
| 2026-07-16 | TCLMK | - | Jul 16, 05:50 UTC | Jul 16, 06:10 UTC | 20m |
| 2026-07-16 | TCLMK | - | Jul 16, 04:20 UTC | Jul 16, 04:50 UTC | 30m |
| 2026-07-14 | TCLMK | - | Jul 14, 09:15 UTC | Jul 14, 18:15 UTC | 9h 0m |
| 2026-07-13 | TCLMK | - | Jul 13, 16:30 UTC | Jul 13, 17:00 UTC | 30m |
| 2026-07-03 | TCLMK | - | Jul 3, 15:15 UTC | Jul 3, 15:45 UTC | 30m |
| 2026-07-03 | TCLMK | - | Jul 3, 13:00 UTC | Jul 3, 14:30 UTC | 1h 30m |
| 2026-07-02 | TCLMK | - | Jul 2, 12:10 UTC | Jul 2, 13:50 UTC | 1h 40m |
| 2026-07-01 | TCLMK | - | Jul 1, 13:35 UTC | Jul 1, 16:20 UTC | 2h 45m |
| 2026-06-30 | TCLMK | - | Jun 30, 16:40 UTC | Jun 30, 19:35 UTC | 2h 55m |
| 2026-06-30 | TCLMK | - | Jun 30, 14:55 UTC | Jun 30, 15:25 UTC | 30m |
| 2026-06-27 | TCLMK | - | Jun 27, 12:25 UTC | Jun 27, 13:04 UTC | 40m |
| 2026-06-26 | TCLMK | - | Jun 26, 20:34 UTC | Jun 26, 21:15 UTC | 40m |
| 2026-06-25 | TCLMK | - | Jun 25, 15:24 UTC | Jun 25, 15:44 UTC | 20m |
| 2026-06-25 | TCLMK | - | Jun 25, 10:25 UTC | Jun 25, 14:24 UTC | 4h 0m |
| 2026-06-22 | TCLMK | - | Jun 22, 23:29 UTC | Jun 23, 14:19 UTC | 14h 50m |
| 2026-06-21 | TCLMK | - | Jun 21, 17:15 UTC | Jun 21, 17:35 UTC | 20m |
| 2026-06-21 | TCLMK | - | Jun 21, 14:15 UTC | Jun 21, 15:05 UTC | 50m |
| 2026-06-21 | TCLMK | - | Jun 21, 11:55 UTC | Jun 21, 12:40 UTC | 45m |
| 2026-06-20 | TCLMK | - | Jun 20, 08:55 UTC | Jun 20, 09:39 UTC | 45m |
| 2026-06-19 | TCLMK | LBG → ISL | Jun 19, 17:39 UTC | Jun 19, 20:34 UTC | 2h 55m |
| 2026-06-17 | TCLMK | LBG → LBG | Jun 17, 10:30 UTC | Jun 17, 10:50 UTC | 20m |
| 2026-06-10 | TCLMK | - | Jun 10, 19:30 UTC | Jun 10, 21:45 UTC | 2h 15m |
| 2026-06-07 | TCLMK | - | Jun 7, 14:40 UTC | Jun 7, 15:00 UTC | 20m |
| 2026-06-07 | TCLMK | - | Jun 7, 11:00 UTC | Jun 7, 11:25 UTC | 25m |
| 2026-06-06 | TCLMK | - | Jun 6, 05:40 UTC | Jun 6, 06:00 UTC | 20m |
| 2026-06-04 | TCLMK | - | Jun 4, 10:10 UTC | Jun 4, 10:35 UTC | 25m |
| 2026-06-03 | TCLMK | - | Jun 3, 07:30 UTC | Jun 3, 07:50 UTC | 20m |
| 2026-06-02 | TCLMK | - | Jun 2, 07:20 UTC | Jun 2, 07:50 UTC | 30m |
| 2026-05-31 | TCLMK | - | May 31, 13:00 UTC | May 31, 13:25 UTC | 25m |
| 2026-05-31 | TCLMK | - | May 31, 10:50 UTC | May 31, 12:25 UTC | 1h 35m |
| 2026-05-31 | TCLMK | - | May 31, 08:50 UTC | May 31, 09:35 UTC | 45m |
| 2026-05-23 | TCLMK | - | May 23, 14:00 UTC | May 23, 14:40 UTC | 40m |
| 2026-05-23 | TCLMK | - | May 23, 13:05 UTC | May 23, 13:25 UTC | 20m |
| 2026-05-23 | TCLMK | - | May 23, 10:00 UTC | May 23, 12:00 UTC | 2h 0m |
| 2026-05-21 | TCLMK | - | May 21, 10:55 UTC | May 21, 11:05 UTC | 10m |
| 2026-05-20 | TCLMK | - | May 20, 14:10 UTC | May 20, 14:30 UTC | 20m |
| 2026-05-18 | TCLMK | - | May 18, 16:50 UTC | May 19, 12:20 UTC | 19h 29m |
| 2026-05-18 | TCLMK | - | May 18, 16:25 UTC | May 19, 12:20 UTC | 19h 54m |
| 2026-05-11 | TCLMK | - | May 11, 08:40 UTC | May 11, 10:55 UTC | 2h 15m |
| 2026-05-09 | TCLMK | - | May 9, 13:40 UTC | May 9, 17:05 UTC | 3h 25m |
| 2026-05-05 | TCLMK | - | May 5, 16:20 UTC | May 5, 16:30 UTC | 10m |
| 2026-05-03 | TCLMK | - | May 3, 13:10 UTC | May 3, 13:25 UTC | 15m |
| 2026-04-30 | TCLMK | - | Apr 30, 14:15 UTC | Apr 30, 14:30 UTC | 15m |
| 2026-04-30 | TCLMK | - | Apr 30, 13:20 UTC | Apr 30, 14:00 UTC | 40m |
| 2026-04-29 | TCLMK | - | Apr 29, 22:10 UTC | Apr 29, 22:20 UTC | 10m |
| 2026-04-29 | TCLMK | - | Apr 29, 16:30 UTC | Apr 29, 19:20 UTC | 2h 50m |
| 2026-04-29 | TCLMK | - | Apr 29, 03:24 UTC | Apr 29, 07:45 UTC | 4h 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-LMK page for operator, model, and routing details .