sensors Mode-S transponder
4A1921
ICAO 24-bit transponder address · allocated to Romania
Currently assigned to YR-FIA · AIRBUS A-320
- Hex
- 4A1921
- Octal
- 22414441
- Decimal
- 4,856,097
- Country
- RO
- Tail
- YR-FIA
- Type
- A320
- Flights observed
- 154
- Distinct callsigns
- 20
- Country
- RO
- Last broadcast
- Jul 26, 22:15 UTC
Last known position
Country allocation
The ICAO 24-bit address 4A1921 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| FOE7501 | - | 28 | 2026-06-19 |
| FOE7502 | - | 27 | 2026-06-19 |
| FOE7096 | - | 9 | 2026-06-14 |
| FOE7095 | - | 8 | 2026-06-14 |
| FOE8442 | - | 7 | 2026-06-13 |
| NIA173 | Nile Air | 5 | 2026-07-23 |
| FOE8441 | - | 5 | 2026-06-11 |
| FOE8429 | - | 5 | 2026-06-13 |
| NIA192 | Nile Air | 4 | 2026-07-24 |
| NIA191 | Nile Air | 4 | 2026-07-24 |
| NIA8604 | Nile Air | 2 | 2026-07-25 |
| NIA8603 | Nile Air | 2 | 2026-07-25 |
| NIA8601 | Nile Air | 2 | 2026-07-25 |
| FOE8430 | - | 2 | 2026-05-16 |
| NIA9102 | - | 1 | 2026-07-08 |
| NIA851 | - | 1 | 2026-07-10 |
| NIA7704 | Nile Air | 1 | 2026-07-26 |
| NIA7703 | Nile Air | 1 | 2026-07-26 |
| NIA7701 | Nile Air | 1 | 2026-07-19 |
| NIA7499 | Nile Air | 1 | 2026-07-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | NIA7704 | VIE → HRG | Jul 26, 20:35 UTC | Jul 26, 22:15 UTC | 1h 40m |
| 2026-07-26 | NIA7703 | HRG → VIE | Jul 26, 10:15 UTC | Jul 26, 19:20 UTC | 9h 5m |
| 2026-07-25 | NIA8604 | ERF → HRG | Jul 25, 22:40 UTC | Jul 26, 08:45 UTC | 10h 6m |
| 2026-07-25 | NIA8603 | HRG → ERF | Jul 25, 11:30 UTC | Jul 25, 21:30 UTC | 10h 0m |
| 2026-07-25 | NIA8601 | HRG → DUS | Jul 25, 03:05 UTC | Jul 25, 09:55 UTC | 6h 50m |
| 2026-07-24 | NIA192 | SAW → CAI | Jul 24, 13:45 UTC | Jul 24, 15:10 UTC | 1h 25m |
| 2026-07-24 | NIA191 | CAI → SAW | Jul 24, 10:30 UTC | Jul 24, 12:10 UTC | 1h 40m |
| 2026-07-23 | NIA224 | BGY → CAI | Jul 23, 22:30 UTC | Jul 24, 01:25 UTC | 2h 55m |
| 2026-07-23 | NIA223 | CAI → BGY | Jul 23, 15:10 UTC | Jul 23, 18:50 UTC | 3h 40m |
| 2026-07-23 | NIA173 | CAI → SHJ | Jul 23, 02:55 UTC | Jul 23, 09:25 UTC | 6h 30m |
| 2026-07-23 | NIA173 | CAI → SHJ | Jul 23, 00:50 UTC | Jul 23, 01:05 UTC | 15m |
| 2026-07-22 | NIA192 | SAW → CAI | Jul 22, 14:45 UTC | Jul 22, 16:20 UTC | 1h 35m |
| 2026-07-22 | NIA191 | - | Jul 22, 11:30 UTC | Jul 22, 13:05 UTC | 1h 35m |
| 2026-07-22 | NIA173 | CAI → SHJ | Jul 22, 02:50 UTC | Jul 22, 04:25 UTC | 1h 35m |
| 2026-07-22 | NIA173 | CAI → SHJ | Jul 22, 00:55 UTC | Jul 22, 01:05 UTC | 10m |
| 2026-07-20 | NIA6102 | - | Jul 20, 11:35 UTC | Jul 20, 13:00 UTC | 1h 25m |
| 2026-07-19 | NIA7499 | HAM → HRG | Jul 19, 20:50 UTC | Jul 20, 09:25 UTC | 12h 35m |
| 2026-07-19 | NIA7498 | - | Jul 19, 09:35 UTC | Jul 19, 19:20 UTC | 9h 45m |
| 2026-07-19 | NIA7701 | HRG → BUD | Jul 19, 02:30 UTC | Jul 19, 08:35 UTC | 6h 5m |
| 2026-07-13 | NIA192 | SAW → CAI | Jul 13, 15:30 UTC | Jul 13, 17:20 UTC | 1h 50m |
| 2026-07-13 | NIA191 | - | Jul 13, 10:30 UTC | Jul 13, 12:00 UTC | 1h 30m |
| 2026-07-12 | NIA192 | SAW → CAI | Jul 12, 13:30 UTC | Jul 12, 15:10 UTC | 1h 40m |
| 2026-07-12 | NIA191 | - | Jul 12, 10:25 UTC | Jul 12, 11:55 UTC | 1h 30m |
| 2026-07-11 | NIA8604 | - | Jul 11, 22:35 UTC | Jul 12, 05:50 UTC | 7h 15m |
| 2026-07-11 | NIA8603 | BER → ERF | Jul 11, 10:55 UTC | Jul 11, 21:20 UTC | 10h 25m |
| 2026-07-10 | NIA8601 | - | Jul 10, 20:45 UTC | Jul 11, 09:35 UTC | 12h 50m |
| 2026-07-10 | NIA851 | - | Jul 10, 12:50 UTC | Jul 10, 19:20 UTC | 6h 30m |
| 2026-07-10 | NIA174 | - | Jul 10, 07:10 UTC | Jul 10, 10:20 UTC | 3h 10m |
| 2026-07-10 | NIA173 | - | Jul 10, 02:05 UTC | Jul 10, 05:40 UTC | 3h 35m |
| 2026-07-08 | NIA9102 | - | Jul 8, 10:50 UTC | Jul 8, 13:00 UTC | 2h 10m |
| 2026-06-28 | AWG611 | - | Jun 28, 12:29 UTC | Jun 28, 15:14 UTC | 2h 45m |
| 2026-06-28 | AWG610 | - | Jun 28, 07:54 UTC | Jun 28, 10:30 UTC | 2h 35m |
| 2026-06-27 | AWG6003 | - | Jun 27, 15:05 UTC | Jun 27, 15:39 UTC | 35m |
| 2026-06-27 | AWG4209 | - | Jun 27, 06:05 UTC | Jun 27, 13:44 UTC | 7h 40m |
| 2026-06-19 | FOE7502 | BRU → OTP | Jun 19, 18:54 UTC | Jun 19, 21:19 UTC | 2h 25m |
| 2026-06-19 | FOE7501 | - | Jun 19, 15:14 UTC | Jun 19, 17:44 UTC | 2h 30m |
| 2026-06-18 | HYS021P | - | Jun 18, 19:05 UTC | Jun 18, 19:40 UTC | 35m |
| 2026-06-18 | HYS5472 | - | Jun 18, 16:00 UTC | Jun 18, 18:05 UTC | 2h 5m |
| 2026-06-18 | HYS5471 | - | Jun 18, 12:25 UTC | Jun 18, 14:35 UTC | 2h 10m |
| 2026-06-18 | HYS278 | - | Jun 18, 10:50 UTC | Jun 18, 11:15 UTC | 25m |
| 2026-06-18 | HYS7442 | - | Jun 18, 08:00 UTC | Jun 18, 09:25 UTC | 1h 25m |
| 2026-06-18 | HYS7441 | - | Jun 18, 05:05 UTC | Jun 18, 06:25 UTC | 1h 20m |
| 2026-06-17 | HYS8311 | - | Jun 17, 07:50 UTC | Jun 17, 16:35 UTC | 8h 45m |
| 2026-06-16 | AWG4127 | RHO → OTP | Jun 16, 18:55 UTC | Jun 16, 20:30 UTC | 1h 36m |
| 2026-06-16 | AWG4126 | OTP → RHO | Jun 16, 16:10 UTC | Jun 16, 17:49 UTC | 1h 40m |
| 2026-06-16 | AWG4133 | HER → OTP | Jun 16, 13:34 UTC | Jun 16, 14:55 UTC | 1h 20m |
| 2026-06-16 | AWG4134 | IAS → HER | Jun 16, 09:40 UTC | Jun 16, 11:30 UTC | 1h 50m |
| 2026-06-16 | AWG4135 | HER → IAS | Jun 16, 06:54 UTC | Jun 16, 08:25 UTC | 1h 30m |
| 2026-06-16 | AWG4132 | OTP → HER | Jun 16, 03:55 UTC | Jun 16, 05:20 UTC | 1h 25m |
| 2026-06-15 | FOE7502 | - | Jun 15, 09:40 UTC | Jun 15, 11:54 UTC | 2h 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-FIA page for operator, model, and routing details .