sensors Mode-S transponder
4A1A62
ICAO 24-bit transponder address · allocated to Romania
Currently assigned to YR-FSB · BOEING 747-400
- Hex
- 4A1A62
- Octal
- 22415142
- Decimal
- 4,856,418
- Country
- RO
- Tail
- YR-FSB
- Type
- B744
- Flights observed
- 146
- Distinct callsigns
- 13
- Country
- RO
- Last broadcast
- Jul 6, 17:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 4A1A62 falls within the block assigned to Romania (RO) by ICAO Annex 10, Volume III. Every aircraft registered in Romania 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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| RCR3302 | - | 92 | 2026-07-06 |
| RCR3301 | - | 29 | 2026-07-05 |
| RCR3303 | - | 6 | 2026-05-24 |
| RCR5530 | - | 4 | 2026-06-22 |
| RCR5509 | - | 2 | 2026-05-28 |
| RCR3623 | - | 2 | 2026-04-23 |
| RCR3422 | - | 2 | 2026-06-22 |
| RCR3328 | - | 2 | 2026-05-29 |
| RCR3320 | - | 2 | 2026-06-30 |
| RCR3312 | - | 2 | 2026-06-22 |
| RCR7635 | - | 1 | 2026-05-24 |
| RCR3622 | - | 1 | 2026-04-22 |
| RCR3360 | - | 1 | 2026-07-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-06 | RCR3360 | - | Jul 6, 15:55 UTC | Jul 6, 17:00 UTC | 1h 5m |
| 2026-07-06 | RCR3302 | - | Jul 6, 09:50 UTC | Jul 6, 10:10 UTC | 20m |
| 2026-07-05 | RCR3302 | - | Jul 5, 14:35 UTC | Jul 6, 08:55 UTC | 18h 20m |
| 2026-07-05 | RCR3301 | - | Jul 5, 14:00 UTC | Jul 6, 08:55 UTC | 18h 55m |
| 2026-07-05 | RCR3302 | - | Jul 5, 07:35 UTC | Jul 5, 10:05 UTC | 2h 30m |
| 2026-07-04 | RCR3302 | - | Jul 4, 13:25 UTC | Jul 5, 10:05 UTC | 20h 40m |
| 2026-07-03 | RCR3301 | - | Jul 3, 14:50 UTC | Jul 4, 08:30 UTC | 17h 40m |
| 2026-07-02 | RCR3302 | - | Jul 2, 14:35 UTC | Jul 3, 09:45 UTC | 19h 10m |
| 2026-07-02 | RCR3301 | - | Jul 2, 13:50 UTC | Jul 3, 09:45 UTC | 19h 55m |
| 2026-07-02 | RCR3302 | - | Jul 2, 08:15 UTC | Jul 2, 10:50 UTC | 2h 35m |
| 2026-07-01 | RCR3302 | - | Jul 1, 15:05 UTC | Jul 2, 10:50 UTC | 19h 45m |
| 2026-07-01 | RCR3302 | - | Jul 1, 13:05 UTC | Jul 2, 10:50 UTC | 21h 45m |
| 2026-07-01 | RCR3302 | - | Jul 1, 08:55 UTC | Jul 1, 09:15 UTC | 20m |
| 2026-06-30 | RCR3302 | - | Jun 30, 10:40 UTC | Jul 1, 08:05 UTC | 21h 25m |
| 2026-06-30 | RCR3320 | - | Jun 30, 09:05 UTC | Jun 30, 11:10 UTC | 2h 5m |
| 2026-06-29 | RCR3320 | - | Jun 29, 21:19 UTC | Jun 29, 22:39 UTC | 1h 20m |
| 2026-06-29 | RCR3302 | - | Jun 29, 12:20 UTC | Jun 29, 14:54 UTC | 2h 35m |
| 2026-06-28 | RCR3302 | - | Jun 28, 14:59 UTC | Jun 29, 14:29 UTC | 23h 30m |
| 2026-06-28 | RCR3302 | - | Jun 28, 08:25 UTC | Jun 28, 10:44 UTC | 2h 20m |
| 2026-06-27 | RCR3302 | - | Jun 27, 10:45 UTC | Jun 28, 10:30 UTC | 23h 45m |
| 2026-06-27 | RCR3301 | - | Jun 27, 09:09 UTC | Jun 28, 08:29 UTC | 23h 20m |
| 2026-06-27 | RCR3302 | - | Jun 27, 02:45 UTC | Jun 27, 04:00 UTC | 1h 15m |
| 2026-06-26 | RCR3301 | - | Jun 26, 01:39 UTC | Jun 26, 02:24 UTC | 45m |
| 2026-06-25 | RCR3302 | - | Jun 25, 14:14 UTC | Jun 25, 14:34 UTC | 20m |
| 2026-06-24 | RCR3302 | - | Jun 24, 22:45 UTC | Jun 25, 13:20 UTC | 14h 35m |
| 2026-06-24 | RCR3302 | - | Jun 24, 17:05 UTC | Jun 24, 18:20 UTC | 1h 15m |
| 2026-06-23 | RCR3301 | - | Jun 23, 15:24 UTC | Jun 23, 17:44 UTC | 2h 20m |
| 2026-06-22 | RCR3312 | BUD → OTP | Jun 22, 20:44 UTC | Jun 23, 13:00 UTC | 16h 15m |
| 2026-06-22 | RCR3422 | - | Jun 22, 14:14 UTC | Jun 22, 17:25 UTC | 3h 10m |
| 2026-06-22 | RCR3422 | - | Jun 22, 02:59 UTC | Jun 22, 03:14 UTC | 15m |
| 2026-06-22 | RCR5530 | - | Jun 22, 00:04 UTC | Jun 22, 00:40 UTC | 35m |
| 2026-06-21 | RCR5530 | - | Jun 21, 14:54 UTC | Jun 21, 16:54 UTC | 2h 0m |
| 2026-06-21 | RCR3302 | - | Jun 21, 09:59 UTC | Jun 21, 10:19 UTC | 20m |
| 2026-06-20 | RCR3302 | - | Jun 20, 13:29 UTC | Jun 21, 09:15 UTC | 19h 45m |
| 2026-06-20 | RCR3302 | - | Jun 20, 09:29 UTC | Jun 20, 09:39 UTC | 10m |
| 2026-06-19 | RCR3302 | - | Jun 19, 14:34 UTC | Jun 20, 08:34 UTC | 18h 0m |
| 2026-06-19 | RCR3301 | - | Jun 19, 13:50 UTC | Jun 20, 08:34 UTC | 18h 45m |
| 2026-06-18 | RCR3302 | - | Jun 18, 14:35 UTC | Jun 19, 09:40 UTC | 19h 4m |
| 2026-06-18 | RCR3302 | - | Jun 18, 14:01 UTC | Jun 19, 09:40 UTC | 19h 39m |
| 2026-06-17 | RCR3302 | - | Jun 17, 14:35 UTC | Jun 18, 09:55 UTC | 19h 20m |
| 2026-06-17 | RCR3301 | - | Jun 17, 13:55 UTC | Jun 18, 09:55 UTC | 20h 0m |
| 2026-06-17 | RCR3302 | - | Jun 17, 09:25 UTC | Jun 17, 09:45 UTC | 20m |
| 2026-06-16 | RCR3301 | - | Jun 16, 14:35 UTC | Jun 17, 08:35 UTC | 18h 1m |
| 2026-06-16 | RCR3301 | - | Jun 16, 14:20 UTC | Jun 17, 08:35 UTC | 18h 16m |
| 2026-06-16 | RCR3302 | - | Jun 16, 08:55 UTC | Jun 16, 11:35 UTC | 2h 40m |
| 2026-06-15 | RCR3302 | - | Jun 15, 14:45 UTC | Jun 16, 11:35 UTC | 20h 50m |
| 2026-06-15 | RCR3302 | - | Jun 15, 10:40 UTC | Jun 15, 11:00 UTC | 20m |
| 2026-06-15 | RCR3302 | - | Jun 15, 08:35 UTC | Jun 15, 09:49 UTC | 1h 15m |
| 2026-06-13 | RCR3301 | - | Jun 13, 13:45 UTC | Jun 13, 15:55 UTC | 2h 10m |
| 2026-06-13 | RCR3302 | - | Jun 13, 09:55 UTC | Jun 13, 10:15 UTC | 20m |
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 YR-FSB page for operator, model, and routing details .