sensors Mode-S transponder
504E87
ICAO 24-bit transponder address · allocated to Moldova
Currently assigned to ER-00003 · AIRBUS A-321
- Hex
- 504E87
- Octal
- 24047207
- Decimal
- 5,262,983
- Country
- MD
- Tail
- ER-00003
- Type
- A321
- Flights observed
- 151
- Distinct callsigns
- 20
- Country
- MD
- Last broadcast
- 43m ago
Current position
Country allocation
The ICAO 24-bit address 504E87 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 |
|---|---|---|---|
| FIA6344 | Four Island Air | 14 | 2026-05-03 |
| FIA6343 | Four Island Air | 10 | 2026-05-03 |
| FIA5711 | Four Island Air | 10 | 2026-05-03 |
| FIA5712 | Four Island Air | 9 | 2026-05-03 |
| FIE533 | - | 8 | 2026-05-24 |
| FIA5581 | Four Island Air | 8 | 2026-05-17 |
| FIA5902 | Four Island Air | 7 | 2026-04-29 |
| FIA5901 | Four Island Air | 7 | 2026-04-29 |
| FIA5686 | Four Island Air | 6 | 2026-04-29 |
| FIA5685 | Four Island Air | 6 | 2026-04-29 |
| FIE534 | - | 5 | 2026-05-23 |
| FIA5812 | Four Island Air | 5 | 2026-05-02 |
| FIA5811 | Four Island Air | 4 | 2026-05-02 |
| FIA5738 | Four Island Air | 4 | 2026-05-23 |
| FIA5737 | Four Island Air | 4 | 2026-05-30 |
| FIA5617 | Four Island Air | 4 | 2026-05-22 |
| FIA5582 | Four Island Air | 4 | 2026-05-17 |
| FIA5232 | Four Island Air | 4 | 2026-05-24 |
| FIA5231 | Four Island Air | 4 | 2026-05-24 |
| FIA5618 | Four Island Air | 3 | 2026-05-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | FIA5737 | RMO → AMS | May 30, 09:40 UTC | May 30, 11:45 UTC | 2h 5m |
| 2026-05-30 | FIA6312 | AYT → RMO | May 30, 00:05 UTC | May 30, 01:40 UTC | 1h 35m |
| 2026-05-29 | FIA6311 | RMO → AYT | May 29, 21:55 UTC | May 29, 22:45 UTC | 50m |
| 2026-05-29 | FIA5714 | PRG → RMO | May 29, 12:10 UTC | May 29, 13:35 UTC | 1h 25m |
| 2026-05-29 | FIA5713 | RMO → PRG | May 29, 09:10 UTC | May 29, 10:45 UTC | 1h 35m |
| 2026-05-29 | FIA5326 | IST → RMO | May 29, 06:50 UTC | May 29, 07:35 UTC | 45m |
| 2026-05-29 | FIA5325 | RMO → IST | May 29, 04:40 UTC | May 29, 05:00 UTC | 20m |
| 2026-05-29 | FIA6312 | AYT → RMO | May 29, 00:10 UTC | May 29, 01:40 UTC | 1h 30m |
| 2026-05-24 | FIA5232 | BLQ → RMO | May 24, 12:35 UTC | May 24, 14:20 UTC | 1h 45m |
| 2026-05-24 | FIA5231 | RMO → BLQ | May 24, 09:15 UTC | May 24, 11:05 UTC | 1h 50m |
| 2026-05-24 | FIE533 | - | May 24, 04:40 UTC | May 24, 05:30 UTC | 50m |
| 2026-05-23 | FIE534 | - | May 23, 23:15 UTC | May 23, 23:30 UTC | 15m |
| 2026-05-23 | FIA5738 | AMS → RMO | May 23, 14:00 UTC | May 23, 16:10 UTC | 2h 10m |
| 2026-05-23 | FIA5737 | RMO → AMS | May 23, 09:50 UTC | May 23, 12:10 UTC | 2h 20m |
| 2026-05-22 | FIA5618 | LTN → RMO | May 22, 21:40 UTC | May 23, 00:15 UTC | 2h 35m |
| 2026-05-22 | FIA5617 | RMO → LTN | May 22, 17:25 UTC | May 22, 20:20 UTC | 2h 55m |
| 2026-05-22 | FIA5714 | PRG → RMO | May 22, 07:20 UTC | May 22, 08:45 UTC | 1h 25m |
| 2026-05-22 | FIA5713 | RMO → PRG | May 22, 04:20 UTC | May 22, 05:50 UTC | 1h 30m |
| 2026-05-20 | FIE534 | - | May 20, 21:50 UTC | May 20, 23:45 UTC | 1h 55m |
| 2026-05-19 | FIA6516 | - | May 19, 21:00 UTC | May 19, 23:10 UTC | 2h 10m |
| 2026-05-19 | FIA6515 | - | May 19, 17:05 UTC | May 19, 19:00 UTC | 1h 55m |
| 2026-05-17 | FIA5582 | TBS → RMO | May 17, 22:20 UTC | May 17, 23:25 UTC | 1h 5m |
| 2026-05-17 | FIA5581 | RMO → TBS | May 17, 20:35 UTC | May 17, 20:55 UTC | 20m |
| 2026-05-16 | FIE533 | - | May 16, 21:50 UTC | May 17, 05:20 UTC | 7h 30m |
| 2026-05-16 | FIA5738 | AMS → RMO | May 16, 14:05 UTC | May 16, 16:15 UTC | 2h 10m |
| 2026-05-16 | FIA5737 | RMO → AMS | May 16, 09:40 UTC | May 16, 12:05 UTC | 2h 25m |
| 2026-05-16 | FIE533 | - | May 16, 05:35 UTC | May 16, 07:41 UTC | 2h 6m |
| 2026-05-15 | FIE533 | - | May 15, 06:35 UTC | May 15, 22:30 UTC | 15h 54m |
| 2026-05-13 | FIE533 | - | May 13, 04:30 UTC | May 13, 05:20 UTC | 50m |
| 2026-05-12 | FIE534 | - | May 12, 23:40 UTC | May 12, 23:50 UTC | 10m |
| 2026-05-10 | FIA5582 | TBS → RMO | May 10, 22:15 UTC | May 10, 23:25 UTC | 1h 10m |
| 2026-05-10 | FIA5581 | RMO → TBS | May 10, 04:55 UTC | May 10, 20:45 UTC | 15h 50m |
| 2026-05-09 | FIE534 | - | May 9, 23:20 UTC | May 9, 23:40 UTC | 20m |
| 2026-05-09 | FIA5738 | AMS → RMO | May 9, 15:30 UTC | May 9, 17:35 UTC | 2h 5m |
| 2026-05-09 | FIA5737 | RMO → AMS | May 9, 07:45 UTC | May 9, 13:50 UTC | 6h 5m |
| 2026-05-08 | FIE533 | - | May 8, 04:44 UTC | May 8, 05:35 UTC | 50m |
| 2026-05-07 | FIE533 | - | May 7, 04:40 UTC | May 7, 05:35 UTC | 55m |
| 2026-05-05 | FIE533 | - | May 5, 06:25 UTC | May 5, 07:15 UTC | 50m |
| 2026-05-04 | FIE534 | - | May 4, 22:25 UTC | May 4, 23:00 UTC | 35m |
| 2026-05-04 | FIA5738 | AMS → RMO | May 4, 15:20 UTC | May 4, 16:25 UTC | 1h 5m |
| 2026-05-03 | FIA5712 | DUB → RMO | May 3, 22:34 UTC | May 4, 01:40 UTC | 3h 5m |
| 2026-05-03 | FIA5711 | RMO → DUB | May 3, 17:54 UTC | May 3, 21:10 UTC | 3h 15m |
| 2026-05-03 | FIA6344 | SSH → RMO | May 3, 11:05 UTC | May 3, 13:30 UTC | 2h 25m |
| 2026-05-03 | FIA6343 | RMO → SSH | May 3, 06:55 UTC | May 3, 08:55 UTC | 2h 0m |
| 2026-05-02 | FIA5812 | LIS → RMO | May 2, 22:15 UTC | May 3, 02:05 UTC | 3h 50m |
| 2026-05-02 | FIA5811 | RMO → LIS | May 2, 16:30 UTC | May 2, 20:50 UTC | 4h 20m |
| 2026-05-02 | FIA6343 | RMO → SSH | May 2, 06:20 UTC | May 2, 13:20 UTC | 7h 0m |
| 2026-05-01 | FIA5712 | DUB → RMO | May 1, 22:25 UTC | May 2, 01:40 UTC | 3h 15m |
| 2026-05-01 | FIA5711 | RMO → DUB | May 1, 17:35 UTC | May 1, 20:55 UTC | 3h 20m |
| 2026-05-01 | FIA6343 | RMO → SSH | May 1, 06:10 UTC | May 1, 13:05 UTC | 6h 55m |
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-00003 page for operator, model, and routing details .