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
- 86
- Distinct callsigns
- 10
- Country
- RO
- Last broadcast
- 1d ago
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 10 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-07 | RCR3312 | - | Jun 7, 10:05 UTC | Jun 7, 10:45 UTC | 40m |
| 2026-06-06 | RCR3301 | - | Jun 6, 10:04 UTC | Jun 7, 02:50 UTC | 16h 45m |
| 2026-06-05 | RCR3301 | - | Jun 5, 10:10 UTC | Jun 6, 02:50 UTC | 16h 40m |
| 2026-06-04 | RCR3301 | - | Jun 4, 12:45 UTC | Jun 5, 04:00 UTC | 15h 15m |
| 2026-06-04 | RCR3302 | - | Jun 4, 09:35 UTC | Jun 4, 09:45 UTC | 10m |
| 2026-06-04 | RCR3302 | - | Jun 4, 07:10 UTC | Jun 4, 08:30 UTC | 1h 20m |
| 2026-06-03 | RCR3302 | - | Jun 3, 09:10 UTC | Jun 4, 08:30 UTC | 23h 20m |
| 2026-06-03 | RCR3301 | - | Jun 3, 07:35 UTC | Jun 3, 09:45 UTC | 2h 10m |
| 2026-06-02 | RCR3302 | - | Jun 2, 08:45 UTC | Jun 3, 03:15 UTC | 18h 30m |
| 2026-06-02 | RCR3301 | - | Jun 2, 07:30 UTC | Jun 3, 03:15 UTC | 19h 45m |
| 2026-06-02 | RCR3302 | - | Jun 2, 03:55 UTC | Jun 2, 04:15 UTC | 20m |
| 2026-06-01 | RCR3302 | - | Jun 1, 08:40 UTC | Jun 2, 03:00 UTC | 18h 20m |
| 2026-06-01 | RCR3301 | - | Jun 1, 07:35 UTC | Jun 2, 03:00 UTC | 19h 25m |
| 2026-06-01 | RCR3302 | - | Jun 1, 03:55 UTC | Jun 1, 04:15 UTC | 20m |
| 2026-06-01 | RCR3302 | - | Jun 1, 01:45 UTC | Jun 1, 03:00 UTC | 1h 15m |
| 2026-05-30 | RCR3301 | - | May 30, 08:50 UTC | May 30, 10:55 UTC | 2h 5m |
| 2026-05-30 | RCR3302 | - | May 30, 04:50 UTC | May 30, 05:10 UTC | 20m |
| 2026-05-29 | RCR3328 | - | May 29, 08:35 UTC | May 30, 03:55 UTC | 19h 20m |
| 2026-05-29 | RCR3328 | - | May 29, 08:10 UTC | May 30, 03:55 UTC | 19h 45m |
| 2026-05-28 | RCR5509 | - | May 28, 15:25 UTC | May 28, 20:55 UTC | 5h 30m |
| 2026-05-28 | RCR5509 | - | May 28, 03:55 UTC | May 28, 04:15 UTC | 20m |
| 2026-05-27 | RCR5530 | - | May 27, 11:10 UTC | May 27, 11:40 UTC | 30m |
| 2026-05-27 | RCR5530 | - | May 27, 01:19 UTC | May 27, 03:34 UTC | 2h 15m |
| 2026-05-26 | RCR3302 | - | May 26, 19:45 UTC | May 26, 20:00 UTC | 15m |
| 2026-05-26 | RCR3302 | - | May 26, 17:44 UTC | May 26, 18:55 UTC | 1h 10m |
| 2026-05-25 | RCR3302 | - | May 25, 20:45 UTC | May 26, 18:55 UTC | 22h 10m |
| 2026-05-25 | RCR3301 | - | May 25, 19:20 UTC | May 26, 18:30 UTC | 23h 10m |
| 2026-05-25 | RCR3302 | - | May 25, 13:50 UTC | May 25, 14:00 UTC | 10m |
| 2026-05-25 | RCR3302 | - | May 25, 11:35 UTC | May 25, 12:50 UTC | 1h 15m |
| 2026-05-24 | RCR3302 | - | May 24, 17:25 UTC | May 25, 12:50 UTC | 19h 25m |
| 2026-05-24 | RCR7635 | - | May 24, 09:05 UTC | May 24, 18:10 UTC | 9h 5m |
| 2026-05-24 | RCR3303 | - | May 24, 04:00 UTC | May 24, 06:25 UTC | 2h 25m |
| 2026-05-23 | RCR3302 | - | May 23, 10:35 UTC | May 23, 11:05 UTC | 30m |
| 2026-05-22 | RCR3301 | - | May 22, 17:55 UTC | May 23, 09:45 UTC | 15h 49m |
| 2026-05-22 | RCR3302 | - | May 22, 14:10 UTC | May 22, 14:35 UTC | 25m |
| 2026-05-21 | RCR3302 | - | May 21, 19:40 UTC | May 22, 13:15 UTC | 17h 35m |
| 2026-05-21 | RCR3302 | - | May 21, 17:50 UTC | May 22, 13:15 UTC | 19h 25m |
| 2026-05-21 | RCR3302 | - | May 21, 14:15 UTC | May 21, 14:35 UTC | 20m |
| 2026-05-21 | RCR3302 | - | May 21, 12:20 UTC | May 21, 13:25 UTC | 1h 5m |
| 2026-05-19 | RCR3301 | - | May 19, 16:50 UTC | May 19, 17:25 UTC | 35m |
| 2026-05-18 | RCR3302 | - | May 18, 19:20 UTC | May 19, 13:40 UTC | 18h 20m |
| 2026-05-18 | RCR3302 | - | May 18, 04:25 UTC | May 18, 16:20 UTC | 11h 55m |
| 2026-05-17 | RCR3302 | - | May 17, 19:10 UTC | May 18, 16:20 UTC | 21h 10m |
| 2026-05-17 | RCR3303 | - | May 17, 14:35 UTC | May 18, 14:30 UTC | 23h 55m |
| 2026-05-17 | RCR3303 | - | May 17, 13:01 UTC | May 18, 04:25 UTC | 15h 25m |
| 2026-05-16 | RCR3301 | - | May 16, 20:50 UTC | May 16, 23:35 UTC | 2h 45m |
| 2026-05-16 | RCR3302 | - | May 16, 17:01 UTC | May 16, 17:20 UTC | 20m |
| 2026-05-16 | RCR3302 | - | May 16, 14:46 UTC | May 16, 16:00 UTC | 1h 15m |
| 2026-05-15 | RCR3302 | - | May 15, 17:50 UTC | May 16, 16:00 UTC | 22h 11m |
| 2026-05-14 | RCR3302 | - | May 14, 18:35 UTC | May 15, 12:50 UTC | 18h 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 YR-FSB page for operator, model, and routing details .