sensors Mode-S transponder
4BBB30
ICAO 24-bit transponder address · allocated to Turkey
Currently assigned to TC-NYP · AIRBUS A-330-200
- Hex
- 4BBB30
- Octal
- 22735460
- Decimal
- 4,963,120
- Country
- TR
- Tail
- TC-NYP
- Type
- A332
- Flights observed
- 35
- Distinct callsigns
- 20
- Country
- TR
- Last broadcast
- 12h ago
Last known position
Country allocation
The ICAO 24-bit address 4BBB30 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 |
|---|---|---|---|
| FAD7389 | - | 3 | 2026-06-06 |
| FAD7320 | - | 2 | 2026-06-08 |
| FAD6134 | - | 2 | 2026-05-11 |
| FAD8380 | - | 1 | 2026-04-18 |
| FAD7518 | Rog-Air | 1 | 2026-06-07 |
| FAD7402 | Rog-Air | 1 | 2026-06-01 |
| FAD7388 | Rog-Air | 1 | 2026-06-05 |
| FAD7387 | - | 1 | 2026-06-05 |
| FAD7386 | Rog-Air | 1 | 2026-06-04 |
| FAD7384 | Rog-Air | 1 | 2026-06-04 |
| FAD7381 | - | 1 | 2026-06-02 |
| FAD7380 | Rog-Air | 1 | 2026-06-01 |
| FAD7321 | - | 1 | 2026-06-09 |
| FAD7311 | - | 1 | 2026-06-06 |
| FAD7310 | Rog-Air | 1 | 2026-06-06 |
| FAD6771 | - | 1 | 2026-05-15 |
| FAD6770 | - | 1 | 2026-05-14 |
| FAD6741 | - | 1 | 2026-05-20 |
| FAD6740 | - | 1 | 2026-05-20 |
| FAD6718 | - | 1 | 2026-05-22 |
Recent flights last 35
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-09 | FAD7321 | - | Jun 9, 04:35 UTC | Jun 9, 09:25 UTC | 4h 50m |
| 2026-06-08 | FAD7320 | - | Jun 8, 20:25 UTC | Jun 9, 01:20 UTC | 4h 55m |
| 2026-06-08 | FAD7320 | - | Jun 8, 01:40 UTC | Jun 8, 20:50 UTC | 19h 10m |
| 2026-06-07 | FAD7518 | JED → CAI | Jun 7, 23:10 UTC | Jun 7, 23:30 UTC | 20m |
| 2026-06-06 | FAD7311 | - | Jun 6, 13:20 UTC | Jun 7, 07:35 UTC | 18h 15m |
| 2026-06-06 | FAD7310 | JED → CCU | Jun 6, 09:30 UTC | Jun 7, 07:35 UTC | 22h 5m |
| 2026-06-06 | FAD7389 | - | Jun 6, 00:05 UTC | Jun 6, 19:04 UTC | 19h 0m |
| 2026-06-05 | FAD7389 | - | Jun 5, 22:10 UTC | Jun 6, 19:04 UTC | 20h 55m |
| 2026-06-05 | FAD7389 | - | Jun 5, 21:20 UTC | Jun 6, 19:04 UTC | 21h 45m |
| 2026-06-05 | FAD7388 | JED → GAU | Jun 5, 18:10 UTC | Jun 5, 18:20 UTC | 10m |
| 2026-06-05 | FAD7387 | - | Jun 5, 02:55 UTC | Jun 5, 17:20 UTC | 14h 25m |
| 2026-06-04 | FAD7386 | JED → GAU | Jun 4, 06:40 UTC | Jun 4, 23:40 UTC | 17h 0m |
| 2026-06-04 | FAD7384 | JED → GAU | Jun 4, 00:10 UTC | Jun 4, 03:05 UTC | 2h 55m |
| 2026-06-02 | FAD7381 | - | Jun 2, 12:35 UTC | Jun 2, 17:45 UTC | 5h 10m |
| 2026-06-01 | FAD7380 | JED → GAU | Jun 1, 20:40 UTC | Jun 2, 09:30 UTC | 12h 50m |
| 2026-06-01 | FAD7402 | JED → YEI | Jun 1, 17:10 UTC | Jun 1, 18:50 UTC | 1h 40m |
| 2026-05-22 | FAD6718 | - | May 22, 09:50 UTC | May 22, 10:10 UTC | 20m |
| 2026-05-20 | FAD6741 | - | May 20, 07:10 UTC | May 20, 16:30 UTC | 9h 20m |
| 2026-05-20 | FAD6740 | - | May 20, 04:05 UTC | May 20, 04:30 UTC | 25m |
| 2026-05-18 | FAD6145 | - | May 18, 02:25 UTC | May 18, 15:45 UTC | 13h 20m |
| 2026-05-16 | FAD6517 | - | May 16, 16:35 UTC | May 16, 16:45 UTC | 10m |
| 2026-05-15 | FAD6771 | - | May 15, 16:40 UTC | May 16, 07:41 UTC | 15h 1m |
| 2026-05-14 | FAD6770 | - | May 14, 20:05 UTC | May 15, 14:15 UTC | 18h 10m |
| 2026-05-11 | FAD6134 | - | May 11, 04:00 UTC | May 11, 15:05 UTC | 11h 5m |
| 2026-05-10 | FAD6134 | - | May 10, 08:10 UTC | May 11, 06:35 UTC | 22h 25m |
| 2026-05-08 | FAD6156 | - | May 8, 14:25 UTC | May 9, 02:30 UTC | 12h 5m |
| 2026-05-06 | FAD6150 | - | May 6, 20:10 UTC | May 7, 09:15 UTC | 13h 5m |
| 2026-05-03 | FAD6341 | CCU → MED | May 3, 10:30 UTC | May 3, 15:40 UTC | 5h 10m |
| 2026-05-03 | FAD6340 | - | May 3, 01:50 UTC | May 3, 06:15 UTC | 4h 24m |
| 2026-04-25 | FAD6427 | ADB → MED | Apr 25, 17:15 UTC | Apr 25, 18:45 UTC | 1h 30m |
| 2026-04-25 | FAD6426 | - | Apr 25, 12:45 UTC | Apr 25, 14:05 UTC | 1h 20m |
| 2026-04-20 | FAD6387 | - | Apr 20, 15:00 UTC | Apr 20, 20:45 UTC | 5h 45m |
| 2026-04-19 | FAD6385 | - | Apr 19, 18:15 UTC | Apr 20, 09:30 UTC | 15h 15m |
| 2026-04-18 | FAD6384 | - | Apr 18, 20:30 UTC | Apr 19, 11:55 UTC | 15h 25m |
| 2026-04-18 | FAD8380 | - | Apr 18, 17:30 UTC | Apr 18, 18:25 UTC | 55m |
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-NYP page for operator, model, and routing details .