sensors Mode-S transponder
504E7E
ICAO 24-bit transponder address · allocated to Moldova
Currently assigned to ER-00010 · AIRBUS A-320
- Hex
- 504E7E
- Octal
- 24047176
- Decimal
- 5,262,974
- Country
- MD
- Tail
- ER-00010
- Type
- A320
- Flights observed
- 81
- Distinct callsigns
- 20
- Country
- MD
- Last broadcast
- 10h ago
Current position
Country allocation
The ICAO 24-bit address 504E7E falls within the block assigned to Moldova (MD) by ICAO Annex 10, Volume III. Every aircraft registered in Moldova 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 |
|---|---|---|---|
| FIE533 | - | 9 | 2026-05-23 |
| FIA6742 | - | 5 | 2026-04-14 |
| FIA6741 | Four Island Air | 5 | 2026-04-18 |
| FIA5712 | Four Island Air | 5 | 2026-04-18 |
| FIA5904 | Four Island Air | 4 | 2026-05-02 |
| FIA5903 | Four Island Air | 4 | 2026-05-02 |
| FIA5711 | Four Island Air | 4 | 2026-04-17 |
| FIA6343 | Four Island Air | 3 | 2026-04-19 |
| FIA5582 | Four Island Air | 3 | 2026-05-03 |
| FIA5548 | Four Island Air | 3 | 2026-04-25 |
| FIA5547 | Four Island Air | 3 | 2026-04-25 |
| FIE534 | - | 2 | 2026-05-22 |
| FIA5713 | - | 2 | 2026-04-13 |
| FIA5686 | Four Island Air | 2 | 2026-04-15 |
| FIA5512 | Four Island Air | 2 | 2026-04-29 |
| FIA5511 | Four Island Air | 2 | 2026-04-28 |
| FIA5509 | Four Island Air | 2 | 2026-05-14 |
| FIA5326 | Four Island Air | 2 | 2026-04-24 |
| FIA5325 | Four Island Air | 2 | 2026-04-24 |
| FIE868 | - | 1 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | FIE868 | - | May 29, 19:10 UTC | May 29, 19:25 UTC | 15m |
| 2026-05-24 | FIA5610 | - | May 24, 20:30 UTC | May 24, 21:30 UTC | 1h 0m |
| 2026-05-24 | FIA5609 | - | May 24, 17:25 UTC | May 24, 19:00 UTC | 1h 35m |
| 2026-05-23 | FIE533 | - | May 23, 04:25 UTC | May 23, 05:20 UTC | 55m |
| 2026-05-22 | FIE534 | - | May 22, 21:45 UTC | May 22, 22:25 UTC | 40m |
| 2026-05-14 | FIA5510 | TLV → RMO | May 14, 17:10 UTC | May 14, 19:25 UTC | 2h 15m |
| 2026-05-14 | FIA5509 | RMO → TLV | May 14, 13:20 UTC | May 14, 15:30 UTC | 2h 10m |
| 2026-05-13 | FIA5509 | RMO → TLV | May 13, 15:35 UTC | May 14, 15:30 UTC | 23h 55m |
| 2026-05-13 | FIA5738 | AMS → RMO | May 13, 14:10 UTC | May 14, 13:30 UTC | 23h 20m |
| 2026-05-13 | FIA5737 | RMO → AMS | May 13, 10:35 UTC | May 13, 12:20 UTC | 1h 45m |
| 2026-05-03 | FIA5582 | TBS → RMO | May 3, 22:54 UTC | May 3, 23:55 UTC | 1h 0m |
| 2026-05-03 | FIA5581 | RMO → TBS | May 3, 19:00 UTC | May 3, 21:35 UTC | 2h 35m |
| 2026-05-03 | FIA5836 | BRU → RMO | May 3, 14:10 UTC | May 3, 16:25 UTC | 2h 15m |
| 2026-05-03 | FIA5835 | RMO → BRU | May 3, 05:05 UTC | May 3, 12:30 UTC | 7h 25m |
| 2026-05-02 | FIA5904 | NCE → RMO | May 2, 16:30 UTC | May 2, 18:45 UTC | 2h 15m |
| 2026-05-02 | FIA5903 | RMO → NCE | May 2, 12:45 UTC | May 2, 15:00 UTC | 2h 15m |
| 2026-05-02 | FIA5814 | ALC → RMO | May 2, 08:15 UTC | May 2, 11:30 UTC | 3h 15m |
| 2026-05-02 | FIA5813 | RMO → ALC | May 2, 03:20 UTC | May 2, 06:35 UTC | 3h 15m |
| 2026-04-30 | FIE533 | - | Apr 30, 21:55 UTC | May 1, 05:25 UTC | 7h 30m |
| 2026-04-30 | FIE533 | - | Apr 30, 06:10 UTC | Apr 30, 07:10 UTC | 1h 0m |
| 2026-04-29 | FIA5512 | BCN → RMO | Apr 29, 15:10 UTC | Apr 29, 17:40 UTC | 2h 30m |
| 2026-04-28 | FIA5511 | RMO → BCN | Apr 28, 23:20 UTC | Apr 29, 13:20 UTC | 14h 1m |
| 2026-04-28 | FIA5234 | VRN → RMO | Apr 28, 13:15 UTC | Apr 28, 14:55 UTC | 1h 40m |
| 2026-04-28 | FIA5233 | RMO → VRN | Apr 28, 10:00 UTC | Apr 28, 11:55 UTC | 1h 55m |
| 2026-04-27 | FIE533 | - | Apr 27, 05:05 UTC | Apr 27, 05:55 UTC | 50m |
| 2026-04-26 | FIE533 | - | Apr 26, 06:20 UTC | Apr 26, 23:20 UTC | 17h 0m |
| 2026-04-25 | FIE534 | - | Apr 25, 23:15 UTC | Apr 25, 23:35 UTC | 20m |
| 2026-04-25 | FIA5548 | STN → RMO | Apr 25, 17:10 UTC | Apr 25, 19:35 UTC | 2h 25m |
| 2026-04-25 | FIA5547 | RMO → STN | Apr 25, 12:35 UTC | Apr 25, 15:35 UTC | 3h 0m |
| 2026-04-25 | FIE533 | - | Apr 25, 04:25 UTC | Apr 25, 05:25 UTC | 1h 0m |
| 2026-04-24 | FIA5326 | IST → RMO | Apr 24, 06:55 UTC | Apr 24, 23:20 UTC | 16h 25m |
| 2026-04-24 | FIA5325 | RMO → IST | Apr 24, 04:15 UTC | Apr 24, 04:50 UTC | 35m |
| 2026-04-23 | FIA5325 | RMO → IST | Apr 23, 07:35 UTC | Apr 24, 04:50 UTC | 21h 14m |
| 2026-04-23 | FIA5326 | IST → RMO | Apr 23, 06:55 UTC | Apr 24, 04:50 UTC | 21h 54m |
| 2026-04-22 | FIA5512 | BCN → RMO | Apr 22, 15:10 UTC | Apr 22, 17:50 UTC | 2h 40m |
| 2026-04-22 | FIA5511 | RMO → BCN | Apr 22, 10:30 UTC | Apr 22, 13:35 UTC | 3h 5m |
| 2026-04-22 | FIE533 | - | Apr 22, 05:50 UTC | Apr 22, 06:50 UTC | 1h 0m |
| 2026-04-20 | FIE533 | - | Apr 20, 04:30 UTC | Apr 20, 05:25 UTC | 55m |
| 2026-04-19 | FIA6343 | RMO → SSH | Apr 19, 04:30 UTC | Apr 19, 22:15 UTC | 17h 45m |
| 2026-04-18 | FIA5904 | NCE → RMO | Apr 18, 17:55 UTC | Apr 18, 20:00 UTC | 2h 5m |
| 2026-04-18 | FIA5903 | - | Apr 18, 14:15 UTC | Apr 18, 16:35 UTC | 2h 20m |
| 2026-04-18 | FIA6741 | RMO → SSH | Apr 18, 07:25 UTC | Apr 18, 08:35 UTC | 1h 10m |
| 2026-04-18 | FIA6741 | RMO → SSH | Apr 18, 06:05 UTC | Apr 18, 12:55 UTC | 6h 50m |
| 2026-04-18 | FIA5712 | DUB → RMO | Apr 18, 01:25 UTC | Apr 18, 01:35 UTC | 10m |
| 2026-04-17 | FIA5712 | DUB → RMO | Apr 17, 23:25 UTC | Apr 18, 01:20 UTC | 1h 55m |
| 2026-04-17 | FIA5712 | DUB → RMO | Apr 17, 22:35 UTC | Apr 17, 23:20 UTC | 45m |
| 2026-04-17 | FIA5711 | RMO → DUB | Apr 17, 19:25 UTC | Apr 17, 21:10 UTC | 1h 45m |
| 2026-04-17 | FIA5711 | RMO → DUB | Apr 17, 17:35 UTC | Apr 17, 19:20 UTC | 1h 45m |
| 2026-04-17 | FIA6344 | SSH → RMO | Apr 17, 11:30 UTC | Apr 17, 12:55 UTC | 1h 25m |
| 2026-04-17 | FIA6343 | RMO → SSH | Apr 17, 07:20 UTC | Apr 17, 08:45 UTC | 1h 25m |
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 ER-00010 page for operator, model, and routing details .