sensors Mode-S transponder
155BBC
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-89020 · SUKHOI Superjet 100-95
- Hex
- 155BBC
- Octal
- 05255674
- Decimal
- 1,399,740
- Country
- RU
- Tail
- RA-89020
- Type
- SU95
- Flights observed
- 41
- Distinct callsigns
- 18
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 155BBC falls within the block assigned to Russia (RU) by ICAO Annex 10, Volume III. Every aircraft registered in Russia 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 |
|---|---|---|---|
| GZP262 | - | 7 | 2026-07-16 |
| GZP260 | - | 6 | 2026-06-02 |
| GZP252 | - | 4 | 2026-07-13 |
| GZP914 | Gazpromavia | 3 | 2026-06-25 |
| GZP292 | - | 3 | 2026-06-06 |
| GZP706 | - | 2 | 2026-06-20 |
| GZP485 | - | 2 | 2026-07-20 |
| GZP472 | - | 2 | 2026-06-18 |
| GZP468 | - | 2 | 2026-05-23 |
| GZP259 | - | 2 | 2026-05-01 |
| GZP9676 | - | 1 | 2026-07-02 |
| GZP910 | - | 1 | 2026-05-10 |
| GZP486 | - | 1 | 2026-05-20 |
| GZP414 | - | 1 | 2026-04-13 |
| GZP407 | - | 1 | 2026-04-14 |
| GZP261 | - | 1 | 2026-04-26 |
| GZP204 | - | 1 | 2026-04-22 |
| 9642 | - | 1 | 2026-05-21 |
Recent flights last 41
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-20 | GZP485 | - | Jul 20, 01:40 UTC | Jul 20, 07:15 UTC | 5h 35m |
| 2026-07-16 | GZP262 | - | Jul 16, 09:15 UTC | Jul 16, 09:45 UTC | 30m |
| 2026-07-13 | GZP252 | - | Jul 13, 09:30 UTC | Jul 13, 10:55 UTC | 1h 25m |
| 2026-07-09 | GZP262 | - | Jul 9, 09:05 UTC | Jul 9, 10:35 UTC | 1h 30m |
| 2026-07-05 | GZP252 | - | Jul 5, 09:05 UTC | Jul 5, 10:40 UTC | 1h 35m |
| 2026-07-02 | GZP9676 | - | Jul 2, 08:55 UTC | Jul 2, 09:20 UTC | 25m |
| 2026-06-26 | GZP262 | - | Jun 26, 05:10 UTC | Jun 26, 15:34 UTC | 10h 25m |
| 2026-06-25 | GZP914 | NYM → VKO | Jun 25, 13:50 UTC | Jun 26, 05:35 UTC | 15h 45m |
| 2026-06-20 | GZP706 | - | Jun 20, 08:14 UTC | Jun 20, 08:39 UTC | 25m |
| 2026-06-18 | GZP472 | - | Jun 18, 12:30 UTC | Jun 18, 13:00 UTC | 30m |
| 2026-06-13 | GZP252 | - | Jun 13, 09:30 UTC | Jun 13, 10:55 UTC | 1h 25m |
| 2026-06-11 | GZP914 | NYM → VKO | Jun 11, 13:40 UTC | Jun 11, 14:55 UTC | 1h 15m |
| 2026-06-09 | GZP262 | - | Jun 9, 09:05 UTC | Jun 9, 10:25 UTC | 1h 20m |
| 2026-06-06 | GZP292 | - | Jun 6, 08:30 UTC | Jun 6, 08:40 UTC | 10m |
| 2026-06-04 | GZP262 | - | Jun 4, 09:05 UTC | Jun 4, 09:35 UTC | 30m |
| 2026-06-03 | GZP262 | - | Jun 3, 13:35 UTC | Jun 4, 09:35 UTC | 20h 0m |
| 2026-06-02 | GZP260 | - | Jun 2, 14:10 UTC | Jun 2, 14:35 UTC | 25m |
| 2026-05-26 | GZP292 | - | May 26, 08:24 UTC | May 26, 08:34 UTC | 10m |
| 2026-05-23 | GZP468 | - | May 23, 11:15 UTC | May 23, 11:45 UTC | 30m |
| 2026-05-22 | GZP468 | - | May 22, 13:25 UTC | May 23, 11:45 UTC | 22h 20m |
| 2026-05-21 | 9642 | - | May 21, 13:55 UTC | May 21, 14:20 UTC | 25m |
| 2026-05-20 | GZP486 | - | May 20, 09:35 UTC | May 20, 09:45 UTC | 10m |
| 2026-05-20 | GZP485 | - | May 20, 01:50 UTC | May 20, 07:25 UTC | 5h 36m |
| 2026-05-15 | GZP260 | - | May 15, 05:25 UTC | May 15, 05:50 UTC | 25m |
| 2026-05-13 | GZP252 | - | May 13, 12:30 UTC | May 13, 12:55 UTC | 25m |
| 2026-05-12 | GZP262 | - | May 12, 05:25 UTC | May 12, 05:50 UTC | 25m |
| 2026-05-10 | GZP910 | - | May 10, 13:14 UTC | May 10, 13:40 UTC | 25m |
| 2026-05-08 | GZP914 | NYM → VKO | May 8, 13:50 UTC | May 8, 15:20 UTC | 1h 30m |
| 2026-05-02 | GZP260 | - | May 2, 09:10 UTC | May 2, 10:25 UTC | 1h 15m |
| 2026-05-01 | GZP259 | - | May 1, 07:30 UTC | May 1, 08:30 UTC | 1h 0m |
| 2026-04-30 | GZP259 | - | Apr 30, 09:05 UTC | May 1, 08:30 UTC | 23h 25m |
| 2026-04-30 | GZP292 | - | Apr 30, 08:50 UTC | Apr 30, 09:05 UTC | 15m |
| 2026-04-26 | GZP261 | - | Apr 26, 09:40 UTC | Apr 26, 10:00 UTC | 20m |
| 2026-04-26 | GZP260 | - | Apr 26, 05:20 UTC | Apr 26, 05:40 UTC | 20m |
| 2026-04-24 | GZP260 | - | Apr 24, 09:10 UTC | Apr 24, 09:35 UTC | 25m |
| 2026-04-23 | GZP260 | - | Apr 23, 14:20 UTC | Apr 24, 09:35 UTC | 19h 15m |
| 2026-04-22 | GZP204 | - | Apr 22, 13:45 UTC | Apr 22, 14:45 UTC | 1h 0m |
| 2026-04-20 | GZP706 | - | Apr 20, 12:00 UTC | Apr 20, 12:25 UTC | 25m |
| 2026-04-18 | GZP472 | - | Apr 18, 11:45 UTC | Apr 18, 12:15 UTC | 30m |
| 2026-04-14 | GZP407 | - | Apr 14, 06:20 UTC | Apr 14, 06:30 UTC | 10m |
| 2026-04-13 | GZP414 | - | Apr 13, 14:10 UTC | Apr 13, 14:25 UTC | 15m |
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 RA-89020 page for operator, model, and routing details .