sensors Mode-S transponder
4B934D
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-DZM · BEECH 400 Beechjet
- Hex
- 4B934D
- Octal
- 22711515
- Decimal
- 4,952,909
- Country
- TR
- Tail
- TC-DZM
- Type
- BE40
- Flights observed
- 65
- Distinct callsigns
- 2
- Country
- TR
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 4B934D 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 2 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | QRJ02 | AYT → MLA | Jul 14, 16:55 UTC | Jul 14, 19:15 UTC | 2h 20m |
| 2026-07-10 | QRJ02 | - | Jul 10, 14:00 UTC | Jul 10, 17:40 UTC | 3h 40m |
| 2026-07-10 | QRJ02 | LNZ → LBG | Jul 10, 09:15 UTC | Jul 10, 10:50 UTC | 1h 35m |
| 2026-07-10 | QRJ002 | IBZ → LNZ | Jul 10, 05:10 UTC | Jul 10, 07:15 UTC | 2h 5m |
| 2026-07-10 | QRJ002 | - | Jul 10, 00:25 UTC | Jul 10, 03:45 UTC | 3h 20m |
| 2026-07-06 | QRJ02 | - | Jul 6, 15:15 UTC | Jul 6, 16:10 UTC | 55m |
| 2026-07-04 | QRJ02 | - | Jul 4, 06:50 UTC | Jul 4, 08:10 UTC | 1h 20m |
| 2026-07-01 | QRJ02 | - | Jul 1, 17:45 UTC | Jul 1, 18:35 UTC | 50m |
| 2026-07-01 | QRJ02 | - | Jul 1, 11:25 UTC | Jul 1, 13:15 UTC | 1h 50m |
| 2026-07-01 | QRJ02 | - | Jul 1, 10:20 UTC | Jul 1, 10:55 UTC | 35m |
| 2026-07-01 | QRJ02 | - | Jul 1, 07:10 UTC | Jul 1, 09:25 UTC | 2h 15m |
| 2026-06-30 | QRJ02 | - | Jun 30, 09:55 UTC | Jun 30, 10:00 UTC | 5m |
| 2026-06-30 | QRJ02 | - | Jun 30, 08:00 UTC | Jun 30, 08:55 UTC | 55m |
| 2026-06-30 | QRJ02 | - | Jun 30, 05:25 UTC | Jun 30, 07:00 UTC | 1h 35m |
| 2026-06-27 | QRJ002 | - | Jun 27, 16:49 UTC | Jun 27, 19:09 UTC | 2h 20m |
| 2026-06-27 | QRJ02 | - | Jun 27, 14:09 UTC | Jun 27, 15:00 UTC | 50m |
| 2026-06-27 | QRJ02 | - | Jun 27, 11:44 UTC | Jun 27, 12:29 UTC | 45m |
| 2026-06-27 | QRJ02 | - | Jun 27, 08:29 UTC | Jun 27, 10:00 UTC | 1h 30m |
| 2026-06-26 | QRJ02 | - | Jun 26, 19:45 UTC | Jun 26, 22:29 UTC | 2h 45m |
| 2026-06-26 | QRJ02 | - | Jun 26, 16:44 UTC | Jun 26, 17:50 UTC | 1h 5m |
| 2026-06-17 | QRJ02 | - | Jun 17, 07:35 UTC | Jun 17, 10:35 UTC | 3h 0m |
| 2026-06-15 | QRJ02 | - | Jun 15, 12:15 UTC | Jun 15, 14:30 UTC | 2h 15m |
| 2026-06-15 | QRJ02 | - | Jun 15, 03:30 UTC | Jun 15, 06:35 UTC | 3h 5m |
| 2026-06-13 | QRJ02 | - | Jun 13, 13:40 UTC | Jun 13, 13:55 UTC | 15m |
| 2026-06-13 | QRJ02 | - | Jun 13, 11:05 UTC | Jun 13, 11:55 UTC | 50m |
| 2026-06-12 | QRJ02 | - | Jun 12, 12:45 UTC | Jun 12, 13:40 UTC | 55m |
| 2026-06-11 | QRJ02 | - | Jun 11, 15:50 UTC | Jun 12, 11:15 UTC | 19h 26m |
| 2026-06-11 | QRJ02 | - | Jun 11, 13:25 UTC | Jun 11, 13:50 UTC | 25m |
| 2026-06-10 | QRJ02 | LIN → OTP | Jun 10, 15:35 UTC | Jun 10, 17:35 UTC | 2h 0m |
| 2026-06-10 | QRJ02 | - | Jun 10, 11:20 UTC | Jun 10, 13:20 UTC | 2h 0m |
| 2026-06-10 | QRJ02 | - | Jun 10, 08:40 UTC | Jun 10, 10:20 UTC | 1h 40m |
| 2026-06-09 | QRJ02 | - | Jun 9, 14:55 UTC | Jun 9, 21:15 UTC | 6h 20m |
| 2026-06-06 | QRJ02 | - | Jun 6, 14:09 UTC | Jun 6, 16:10 UTC | 2h 0m |
| 2026-06-05 | QRJ02 | - | Jun 5, 04:25 UTC | Jun 5, 06:25 UTC | 2h 0m |
| 2026-06-05 | QRJ02 | - | Jun 5, 02:20 UTC | Jun 5, 02:35 UTC | 15m |
| 2026-06-01 | QRJ02 | - | Jun 1, 16:50 UTC | Jun 1, 19:10 UTC | 2h 20m |
| 2026-06-01 | QRJ02 | - | Jun 1, 08:15 UTC | Jun 1, 14:15 UTC | 6h 0m |
| 2026-05-26 | QRJ02 | - | May 26, 13:04 UTC | May 26, 18:50 UTC | 5h 45m |
| 2026-05-24 | QRJ02 | - | May 24, 07:35 UTC | May 24, 08:35 UTC | 1h 0m |
| 2026-05-24 | QRJ02 | - | May 24, 05:10 UTC | May 24, 06:15 UTC | 1h 5m |
| 2026-05-24 | QRJ02 | - | May 24, 00:05 UTC | May 24, 03:45 UTC | 3h 40m |
| 2026-05-23 | QRJ02 | - | May 23, 13:20 UTC | May 23, 15:20 UTC | 2h 0m |
| 2026-05-22 | QRJ02 | - | May 22, 06:20 UTC | May 22, 09:45 UTC | 3h 25m |
| 2026-05-14 | QRJ02 | - | May 14, 15:40 UTC | May 14, 16:15 UTC | 35m |
| 2026-05-11 | QRJ02 | - | May 11, 16:10 UTC | May 11, 17:05 UTC | 56m |
| 2026-05-11 | QRJ02 | - | May 11, 09:05 UTC | May 11, 09:45 UTC | 40m |
| 2026-05-10 | QRJ02 | - | May 10, 16:10 UTC | May 10, 16:55 UTC | 45m |
| 2026-05-10 | QRJ02 | - | May 10, 14:04 UTC | May 10, 14:54 UTC | 50m |
| 2026-05-10 | QRJ02 | - | May 10, 11:05 UTC | May 10, 11:50 UTC | 45m |
| 2026-05-06 | QRJ02 | - | May 6, 17:45 UTC | May 6, 18:25 UTC | 40m |
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-DZM page for operator, model, and routing details .