sensors Mode-S transponder
4B8587
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-ALG · GULFSTREAM 5
- Hex
- 4B8587
- Octal
- 22702607
- Decimal
- 4,949,383
- Country
- TR
- Tail
- TC-ALG
- Type
- GLF5
- Flights observed
- 39
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 4B8587 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| HMZ7948 | - | 2 | 2026-06-01 |
| HMZ6366 | - | 2 | 2026-04-25 |
| HMZ294 | - | 2 | 2026-05-20 |
| HMZ289 | - | 2 | 2026-05-24 |
| HMZ250 | - | 2 | 2026-05-03 |
| HMZ235 | - | 2 | 2026-04-17 |
| HMZ232 | - | 2 | 2026-04-17 |
| HMZ231 | - | 2 | 2026-04-16 |
| HMZ214 | - | 2 | 2026-04-13 |
| HMZ9151 | - | 1 | 2026-04-17 |
| HMZ7950 | - | 1 | 2026-06-02 |
| HMZ7949 | - | 1 | 2026-06-02 |
| HMZ7932 | - | 1 | 2026-05-21 |
| HMZ6362 | - | 1 | 2026-04-24 |
| HMZ6361 | - | 1 | 2026-04-23 |
| HMZ296 | - | 1 | 2026-05-24 |
| HMZ290 | - | 1 | 2026-05-16 |
| HMZ287 | - | 1 | 2026-05-23 |
| HMZ284 | - | 1 | 2026-05-19 |
| HMZ283 | - | 1 | 2026-05-18 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | HMZ7950 | - | Jun 2, 17:50 UTC | Jun 2, 18:55 UTC | 1h 5m |
| 2026-06-02 | HMZ7949 | TLV → AMM | Jun 2, 16:00 UTC | Jun 2, 16:45 UTC | 45m |
| 2026-06-01 | HMZ7948 | - | Jun 1, 22:55 UTC | Jun 2, 15:20 UTC | 16h 25m |
| 2026-06-01 | HMZ7948 | - | Jun 1, 16:00 UTC | Jun 2, 15:20 UTC | 23h 20m |
| 2026-06-01 | HMZ2005 | - | Jun 1, 14:15 UTC | Jun 2, 13:45 UTC | 23h 30m |
| 2026-05-29 | HMZ2003 | - | May 29, 17:40 UTC | May 29, 18:35 UTC | 55m |
| 2026-05-28 | HMZ2002 | - | May 28, 16:25 UTC | May 28, 17:35 UTC | 1h 10m |
| 2026-05-24 | HMZ296 | - | May 24, 01:50 UTC | May 24, 21:45 UTC | 19h 55m |
| 2026-05-24 | HMZ289 | - | May 24, 00:10 UTC | May 24, 21:45 UTC | 21h 35m |
| 2026-05-23 | HMZ289 | - | May 23, 14:15 UTC | May 24, 02:00 UTC | 11h 46m |
| 2026-05-23 | HMZ287 | - | May 23, 09:30 UTC | May 23, 09:40 UTC | 10m |
| 2026-05-21 | HMZ7932 | - | May 21, 16:35 UTC | May 21, 16:50 UTC | 15m |
| 2026-05-20 | HMZ294 | - | May 20, 13:00 UTC | May 20, 14:30 UTC | 1h 30m |
| 2026-05-19 | HMZ294 | - | May 19, 15:50 UTC | May 20, 14:30 UTC | 22h 41m |
| 2026-05-19 | HMZ284 | - | May 19, 14:05 UTC | May 20, 13:45 UTC | 23h 41m |
| 2026-05-18 | HMZ283 | - | May 18, 22:00 UTC | May 19, 11:05 UTC | 13h 5m |
| 2026-05-16 | HMZ290 | - | May 16, 10:31 UTC | May 16, 10:55 UTC | 25m |
| 2026-05-07 | HMZ274 | - | May 7, 15:35 UTC | May 7, 16:40 UTC | 1h 5m |
| 2026-05-04 | HMZ272 | - | May 4, 17:00 UTC | May 4, 18:45 UTC | 1h 46m |
| 2026-05-03 | HMZ250 | - | May 3, 08:25 UTC | May 3, 09:30 UTC | 1h 5m |
| 2026-05-02 | HMZ250 | - | May 2, 10:10 UTC | May 3, 09:30 UTC | 23h 19m |
| 2026-05-02 | HMZ249 | - | May 2, 08:55 UTC | May 2, 11:10 UTC | 2h 15m |
| 2026-04-30 | HMZ248 | - | Apr 30, 19:00 UTC | Apr 30, 20:00 UTC | 1h 0m |
| 2026-04-25 | HMZ6366 | - | Apr 25, 16:55 UTC | Apr 25, 18:45 UTC | 1h 50m |
| 2026-04-24 | HMZ6366 | - | Apr 24, 20:00 UTC | Apr 25, 18:45 UTC | 22h 45m |
| 2026-04-24 | HMZ6362 | - | Apr 24, 15:35 UTC | Apr 24, 17:10 UTC | 1h 35m |
| 2026-04-23 | HMZ6361 | - | Apr 23, 08:30 UTC | Apr 23, 15:25 UTC | 6h 55m |
| 2026-04-17 | HMZ9151 | - | Apr 17, 18:15 UTC | Apr 18, 12:05 UTC | 17h 51m |
| 2026-04-17 | HMZ235 | - | Apr 17, 13:20 UTC | Apr 17, 13:45 UTC | 25m |
| 2026-04-17 | HMZ235 | - | Apr 17, 12:35 UTC | Apr 17, 13:15 UTC | 40m |
| 2026-04-17 | HMZ232 | - | Apr 17, 01:20 UTC | Apr 17, 02:45 UTC | 1h 25m |
| 2026-04-17 | HMZ232 | - | Apr 17, 00:55 UTC | Apr 17, 01:15 UTC | 20m |
| 2026-04-16 | HMZ231 | - | Apr 16, 23:20 UTC | Apr 16, 23:35 UTC | 15m |
| 2026-04-16 | HMZ231 | - | Apr 16, 21:24 UTC | Apr 16, 22:00 UTC | 35m |
| 2026-04-16 | HMZ230 | - | Apr 16, 17:15 UTC | Apr 16, 18:25 UTC | 1h 10m |
| 2026-04-16 | HMZ222 | - | Apr 16, 12:45 UTC | Apr 16, 13:05 UTC | 20m |
| 2026-04-16 | HMZ221 | - | Apr 16, 10:05 UTC | Apr 16, 10:49 UTC | 45m |
| 2026-04-13 | HMZ214 | - | Apr 13, 16:15 UTC | Apr 13, 17:00 UTC | 45m |
| 2026-04-13 | HMZ214 | - | Apr 13, 15:45 UTC | Apr 13, 16:15 UTC | 30m |
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-ALG page for operator, model, and routing details .