sensors Mode-S transponder
4B8210
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to 16-0055 · AIRBUS A-400M
- Hex
- 4B8210
- Octal
- 22701020
- Decimal
- 4,948,496
- Country
- TR
- Tail
- 16-0055
- Type
- A400
- Flights observed
- 47
- Distinct callsigns
- 18
- Country
- TR
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 4B8210 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TUAF902 | - | 8 | 2026-07-15 |
| TUAF759 | - | 4 | 2026-07-08 |
| TUAF730 | - | 4 | 2026-04-15 |
| TUAF758 | - | 3 | 2026-07-02 |
| TUAF732 | - | 3 | 2026-04-23 |
| TUAF303 | - | 3 | 2026-04-20 |
| ESEN16 | - | 3 | 2026-07-17 |
| ESEN11 | - | 3 | 2026-07-06 |
| TUAF822 | - | 2 | 2026-04-29 |
| TUAF820 | - | 2 | 2026-04-28 |
| TUAF819 | - | 2 | 2026-04-27 |
| TUAF734 | - | 2 | 2026-05-02 |
| TUAF509 | - | 2 | 2026-05-03 |
| ESEN03 | - | 2 | 2026-04-19 |
| TUAF209 | - | 1 | 2026-04-25 |
| ESEN22 | - | 1 | 2026-07-05 |
| ESEN05 | - | 1 | 2026-04-16 |
| ESEN04 | - | 1 | 2026-05-03 |
Recent flights last 47
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | ESEN16 | - | Jul 17, 13:20 UTC | Jul 17, 13:55 UTC | 35m |
| 2026-07-17 | ESEN16 | - | Jul 17, 10:20 UTC | Jul 17, 11:25 UTC | 1h 5m |
| 2026-07-17 | ESEN16 | - | Jul 17, 06:54 UTC | Jul 17, 07:25 UTC | 30m |
| 2026-07-15 | TUAF902 | - | Jul 15, 00:00 UTC | Jul 15, 00:30 UTC | 30m |
| 2026-07-14 | TUAF902 | OPO → ISL | Jul 14, 18:10 UTC | Jul 14, 22:40 UTC | 4h 30m |
| 2026-07-14 | TUAF902 | - | Jul 14, 14:00 UTC | Jul 14, 16:05 UTC | 2h 5m |
| 2026-07-12 | TUAF902 | - | Jul 12, 21:40 UTC | Jul 13, 04:45 UTC | 7h 5m |
| 2026-07-11 | TUAF902 | - | Jul 11, 19:45 UTC | Jul 11, 20:00 UTC | 15m |
| 2026-07-10 | TUAF902 | - | Jul 10, 08:25 UTC | Jul 10, 11:00 UTC | 2h 35m |
| 2026-07-10 | TUAF902 | - | Jul 10, 01:40 UTC | Jul 10, 06:50 UTC | 5h 10m |
| 2026-07-09 | TUAF902 | - | Jul 9, 10:15 UTC | Jul 10, 06:50 UTC | 20h 35m |
| 2026-07-08 | TUAF759 | - | Jul 8, 15:10 UTC | Jul 9, 08:35 UTC | 17h 25m |
| 2026-07-08 | TUAF759 | - | Jul 8, 10:05 UTC | Jul 9, 08:35 UTC | 22h 30m |
| 2026-07-08 | TUAF759 | - | Jul 8, 08:30 UTC | Jul 8, 16:30 UTC | 8h 0m |
| 2026-07-08 | TUAF759 | - | Jul 8, 05:45 UTC | Jul 8, 06:35 UTC | 50m |
| 2026-07-06 | ESEN11 | - | Jul 6, 12:30 UTC | Jul 6, 12:45 UTC | 15m |
| 2026-07-06 | ESEN11 | - | Jul 6, 11:05 UTC | Jul 6, 11:30 UTC | 25m |
| 2026-07-06 | ESEN11 | - | Jul 6, 09:20 UTC | Jul 6, 09:45 UTC | 25m |
| 2026-07-05 | ESEN22 | - | Jul 5, 09:30 UTC | Jul 5, 09:40 UTC | 10m |
| 2026-07-02 | TUAF758 | - | Jul 2, 21:50 UTC | Jul 3, 02:40 UTC | 4h 50m |
| 2026-07-01 | TUAF758 | - | Jul 1, 13:30 UTC | Jul 1, 17:55 UTC | 4h 25m |
| 2026-07-01 | TUAF758 | - | Jul 1, 11:25 UTC | Jul 1, 12:00 UTC | 35m |
| 2026-05-03 | TUAF509 | - | May 3, 16:20 UTC | May 3, 17:45 UTC | 1h 25m |
| 2026-05-03 | TUAF509 | - | May 3, 13:55 UTC | May 3, 15:05 UTC | 1h 10m |
| 2026-05-03 | ESEN04 | - | May 3, 09:45 UTC | May 3, 09:55 UTC | 10m |
| 2026-05-02 | TUAF734 | - | May 2, 10:10 UTC | May 2, 12:55 UTC | 2h 45m |
| 2026-05-01 | TUAF734 | - | May 1, 00:00 UTC | May 1, 02:45 UTC | 2h 45m |
| 2026-04-29 | TUAF822 | - | Apr 29, 16:50 UTC | Apr 29, 19:15 UTC | 2h 25m |
| 2026-04-28 | TUAF822 | - | Apr 28, 18:10 UTC | Apr 29, 11:45 UTC | 17h 36m |
| 2026-04-28 | TUAF820 | - | Apr 28, 08:05 UTC | Apr 28, 17:15 UTC | 9h 10m |
| 2026-04-27 | TUAF820 | - | Apr 27, 18:20 UTC | Apr 28, 17:15 UTC | 22h 55m |
| 2026-04-27 | TUAF819 | - | Apr 27, 14:30 UTC | Apr 27, 17:00 UTC | 2h 30m |
| 2026-04-27 | TUAF819 | - | Apr 27, 07:15 UTC | Apr 27, 09:50 UTC | 2h 35m |
| 2026-04-25 | TUAF209 | - | Apr 25, 21:30 UTC | Apr 25, 22:05 UTC | 35m |
| 2026-04-23 | TUAF732 | - | Apr 23, 17:20 UTC | Apr 23, 17:45 UTC | 24m |
| 2026-04-23 | TUAF732 | - | Apr 23, 14:25 UTC | Apr 23, 16:25 UTC | 2h 0m |
| 2026-04-21 | TUAF732 | - | Apr 21, 21:10 UTC | Apr 21, 22:40 UTC | 1h 30m |
| 2026-04-20 | TUAF303 | - | Apr 20, 18:55 UTC | Apr 20, 19:10 UTC | 15m |
| 2026-04-20 | TUAF303 | - | Apr 20, 16:35 UTC | Apr 20, 17:25 UTC | 50m |
| 2026-04-20 | TUAF303 | - | Apr 20, 12:50 UTC | Apr 20, 13:50 UTC | 1h 0m |
| 2026-04-19 | ESEN03 | - | Apr 19, 12:20 UTC | Apr 19, 12:45 UTC | 25m |
| 2026-04-19 | ESEN03 | - | Apr 19, 11:20 UTC | Apr 19, 11:35 UTC | 15m |
| 2026-04-16 | ESEN05 | - | Apr 16, 11:44 UTC | Apr 16, 11:54 UTC | 10m |
| 2026-04-15 | TUAF730 | - | Apr 15, 19:25 UTC | Apr 15, 19:50 UTC | 25m |
| 2026-04-15 | TUAF730 | - | Apr 15, 17:05 UTC | Apr 15, 17:45 UTC | 40m |
| 2026-04-13 | TUAF730 | - | Apr 13, 20:35 UTC | Apr 13, 22:20 UTC | 1h 45m |
| 2026-04-13 | TUAF730 | - | Apr 13, 18:45 UTC | Apr 13, 19:10 UTC | 25m |
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 16-0055 page for operator, model, and routing details .