sensors Mode-S transponder
4BA0E5
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-HGE · AIRBUS HELICOPTERS EC-135/635
- Hex
- 4BA0E5
- Octal
- 22720345
- Decimal
- 4,956,389
- Country
- TR
- Tail
- TC-HGE
- Type
- EC35
- Flights observed
- 60
- Distinct callsigns
- 1
- Country
- TR
- Last broadcast
- 16d ago
Last known position
Country allocation
The ICAO 24-bit address 4BA0E5 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 |
|---|---|---|---|
| TCHGE | - | 60 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-01 | TCHGE | - | Jul 1, 12:00 UTC | Jul 1, 12:15 UTC | 15m |
| 2026-07-01 | TCHGE | - | Jul 1, 11:10 UTC | Jul 1, 11:25 UTC | 15m |
| 2026-06-24 | TCHGE | - | Jun 24, 07:59 UTC | Jun 24, 08:09 UTC | 10m |
| 2026-06-24 | TCHGE | ANK → ANK | Jun 24, 07:05 UTC | Jun 24, 07:20 UTC | 15m |
| 2026-06-23 | TCHGE | - | Jun 23, 07:40 UTC | Jun 23, 07:55 UTC | 15m |
| 2026-06-23 | TCHGE | ANK → ANK | Jun 23, 05:54 UTC | Jun 23, 06:04 UTC | 10m |
| 2026-06-22 | TCHGE | - | Jun 22, 11:19 UTC | Jun 22, 11:35 UTC | 15m |
| 2026-06-22 | TCHGE | - | Jun 22, 09:45 UTC | Jun 22, 09:54 UTC | 10m |
| 2026-06-22 | TCHGE | - | Jun 22, 08:00 UTC | Jun 22, 08:15 UTC | 15m |
| 2026-06-22 | TCHGE | - | Jun 22, 06:19 UTC | Jun 22, 06:35 UTC | 15m |
| 2026-06-10 | TCHGE | - | Jun 10, 07:35 UTC | Jun 10, 08:55 UTC | 1h 20m |
| 2026-06-09 | TCHGE | - | Jun 9, 12:50 UTC | Jun 9, 13:05 UTC | 15m |
| 2026-06-08 | TCHGE | - | Jun 8, 04:05 UTC | Jun 8, 04:25 UTC | 20m |
| 2026-06-05 | TCHGE | - | Jun 5, 14:25 UTC | Jun 5, 14:50 UTC | 25m |
| 2026-06-05 | TCHGE | - | Jun 5, 10:10 UTC | Jun 5, 10:20 UTC | 10m |
| 2026-06-05 | TCHGE | - | Jun 5, 07:35 UTC | Jun 5, 08:25 UTC | 50m |
| 2026-06-05 | TCHGE | - | Jun 5, 04:45 UTC | Jun 5, 06:05 UTC | 1h 20m |
| 2026-06-04 | TCHGE | - | Jun 4, 04:25 UTC | Jun 4, 05:10 UTC | 45m |
| 2026-06-04 | TCHGE | - | Jun 4, 03:20 UTC | Jun 4, 03:35 UTC | 15m |
| 2026-06-03 | TCHGE | - | Jun 3, 12:40 UTC | Jun 3, 13:25 UTC | 45m |
| 2026-06-03 | TCHGE | - | Jun 3, 11:35 UTC | Jun 3, 11:50 UTC | 15m |
| 2026-06-02 | TCHGE | - | Jun 2, 10:45 UTC | Jun 2, 11:30 UTC | 45m |
| 2026-06-01 | TCHGE | - | Jun 1, 13:30 UTC | Jun 1, 14:15 UTC | 45m |
| 2026-05-31 | TCHGE | - | May 31, 11:00 UTC | May 31, 11:20 UTC | 20m |
| 2026-05-31 | TCHGE | - | May 31, 08:55 UTC | May 31, 09:10 UTC | 15m |
| 2026-05-28 | TCHGE | - | May 28, 15:05 UTC | May 28, 15:45 UTC | 40m |
| 2026-05-28 | TCHGE | - | May 28, 14:05 UTC | May 28, 14:15 UTC | 10m |
| 2026-05-28 | TCHGE | - | May 28, 07:35 UTC | May 28, 08:05 UTC | 30m |
| 2026-05-28 | TCHGE | - | May 28, 05:55 UTC | May 28, 06:40 UTC | 45m |
| 2026-05-27 | TCHGE | - | May 27, 05:29 UTC | May 27, 06:20 UTC | 50m |
| 2026-05-26 | TCHGE | - | May 26, 15:05 UTC | May 26, 15:35 UTC | 30m |
| 2026-05-20 | TCHGE | - | May 20, 12:30 UTC | May 20, 14:00 UTC | 1h 30m |
| 2026-05-20 | TCHGE | - | May 20, 10:20 UTC | May 20, 10:55 UTC | 35m |
| 2026-05-16 | TCHGE | - | May 16, 13:46 UTC | May 16, 14:11 UTC | 25m |
| 2026-05-14 | TCHGE | - | May 14, 10:15 UTC | May 14, 11:01 UTC | 45m |
| 2026-05-14 | TCHGE | - | May 14, 09:10 UTC | May 14, 09:25 UTC | 15m |
| 2026-05-11 | TCHGE | - | May 11, 12:55 UTC | May 11, 13:05 UTC | 10m |
| 2026-05-11 | TCHGE | - | May 11, 11:05 UTC | May 11, 11:30 UTC | 25m |
| 2026-05-11 | TCHGE | - | May 11, 08:30 UTC | May 11, 09:00 UTC | 30m |
| 2026-05-11 | TCHGE | - | May 11, 06:45 UTC | May 11, 07:05 UTC | 20m |
| 2026-05-10 | TCHGE | - | May 10, 09:45 UTC | May 10, 10:05 UTC | 20m |
| 2026-05-04 | TCHGE | - | May 4, 15:35 UTC | May 4, 16:20 UTC | 45m |
| 2026-05-01 | TCHGE | - | May 1, 07:40 UTC | May 1, 08:20 UTC | 40m |
| 2026-04-27 | TCHGE | - | Apr 27, 07:30 UTC | Apr 27, 07:45 UTC | 15m |
| 2026-04-27 | TCHGE | - | Apr 27, 05:40 UTC | Apr 27, 05:50 UTC | 10m |
| 2026-04-26 | TCHGE | - | Apr 26, 07:35 UTC | Apr 26, 09:20 UTC | 1h 45m |
| 2026-04-25 | TCHGE | - | Apr 25, 12:55 UTC | Apr 25, 13:40 UTC | 45m |
| 2026-04-25 | TCHGE | - | Apr 25, 11:20 UTC | Apr 25, 11:55 UTC | 35m |
| 2026-04-25 | TCHGE | - | Apr 25, 09:40 UTC | Apr 25, 10:10 UTC | 30m |
| 2026-04-25 | TCHGE | - | Apr 25, 08:20 UTC | Apr 25, 09:00 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-HGE page for operator, model, and routing details .