sensors Mode-S transponder
504E88
ICAO 24-bit transponder address · allocated to Moldova
Currently assigned to ER-SMA · BOEING 737-700
- Hex
- 504E88
- Octal
- 24047210
- Decimal
- 5,262,984
- Country
- MD
- Tail
- ER-SMA
- Type
- B737
- Flights observed
- 142
- Distinct callsigns
- 20
- Country
- MD
- Last broadcast
- 27m ago
Last known position
Country allocation
The ICAO 24-bit address 504E88 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 |
|---|---|---|---|
| SQY6101 | - | 13 | 2026-05-26 |
| SQY7504 | - | 12 | 2026-05-15 |
| SEU405 | XL Airways France | 11 | 2026-05-20 |
| SQY6102 | - | 10 | 2026-05-28 |
| SEU406 | XL Airways France | 10 | 2026-05-20 |
| SQY7508 | - | 8 | 2026-05-24 |
| SEU414 | XL Airways France | 8 | 2026-04-27 |
| SEU413 | XL Airways France | 8 | 2026-04-27 |
| SQY7503 | - | 7 | 2026-05-15 |
| SQY7502 | - | 5 | 2026-05-14 |
| SEU534 | XL Airways France | 5 | 2026-05-22 |
| SQY7512 | - | 4 | 2026-05-09 |
| SQY7507 | - | 4 | 2026-05-23 |
| SQY7511 | - | 3 | 2026-05-16 |
| SQY7505 | - | 3 | 2026-04-19 |
| SQY7506 | - | 2 | 2026-04-26 |
| SQY7501 | - | 2 | 2026-05-04 |
| SQY4507 | - | 2 | 2026-05-29 |
| SQY4002 | - | 2 | 2026-05-23 |
| SQY4001 | - | 2 | 2026-05-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SQY4508 | - | May 29, 23:45 UTC | May 30, 06:00 UTC | 6h 15m |
| 2026-05-29 | SQY4507 | - | May 29, 22:05 UTC | May 29, 22:45 UTC | 40m |
| 2026-05-29 | SEU352 | ATH → RMO | May 29, 10:00 UTC | May 29, 11:35 UTC | 1h 35m |
| 2026-05-29 | SQY4708 | - | May 29, 00:15 UTC | May 29, 07:45 UTC | 7h 30m |
| 2026-05-28 | SQY6102 | - | May 28, 06:25 UTC | May 28, 23:10 UTC | 16h 45m |
| 2026-05-27 | SQY5024 | - | May 27, 16:50 UTC | May 28, 03:40 UTC | 10h 50m |
| 2026-05-27 | SEU491 | RMO → NCE | May 27, 13:20 UTC | May 27, 15:20 UTC | 2h 0m |
| 2026-05-27 | SQY7614 | - | May 27, 08:50 UTC | May 27, 11:10 UTC | 2h 20m |
| 2026-05-27 | SQY7613 | - | May 27, 04:49 UTC | May 27, 06:44 UTC | 1h 55m |
| 2026-05-26 | SQY4507 | - | May 26, 22:25 UTC | May 26, 23:10 UTC | 45m |
| 2026-05-26 | SQY515 | - | May 26, 13:54 UTC | May 26, 16:30 UTC | 2h 35m |
| 2026-05-26 | SQY6101 | - | May 26, 01:05 UTC | May 26, 06:54 UTC | 5h 50m |
| 2026-05-25 | SEU426 | PMI → RMO | May 25, 16:40 UTC | May 25, 19:54 UTC | 3h 15m |
| 2026-05-25 | SEU425 | RMO → PMI | May 25, 13:00 UTC | May 25, 15:05 UTC | 2h 5m |
| 2026-05-25 | SEU352 | ATH → RMO | May 25, 09:25 UTC | May 25, 11:00 UTC | 1h 35m |
| 2026-05-25 | SEU351 | RMO → ATH | May 25, 05:45 UTC | May 25, 07:15 UTC | 1h 30m |
| 2026-05-24 | SQY9204 | - | May 24, 08:05 UTC | May 25, 03:25 UTC | 19h 20m |
| 2026-05-24 | SQY6101 | - | May 24, 06:30 UTC | May 25, 03:25 UTC | 20h 55m |
| 2026-05-24 | SQY6101 | - | May 24, 04:05 UTC | May 25, 03:25 UTC | 23h 20m |
| 2026-05-24 | SQY6101 | - | May 24, 02:05 UTC | May 25, 02:00 UTC | 23h 55m |
| 2026-05-24 | SQY7508 | - | May 24, 01:35 UTC | May 24, 21:45 UTC | 20h 10m |
| 2026-05-23 | SQY7507 | - | May 23, 22:30 UTC | May 23, 23:50 UTC | 1h 20m |
| 2026-05-23 | SEU322 | SKG → RMO | May 23, 08:40 UTC | May 23, 09:50 UTC | 1h 10m |
| 2026-05-23 | SQY4002 | - | May 23, 00:05 UTC | May 23, 07:10 UTC | 7h 4m |
| 2026-05-22 | SEU534 | LCA → RMO | May 22, 14:55 UTC | May 22, 15:40 UTC | 45m |
| 2026-05-22 | SEU534 | LCA → RMO | May 22, 13:50 UTC | May 22, 14:20 UTC | 30m |
| 2026-05-22 | SEU302 | HER → RMO | May 22, 00:20 UTC | May 22, 02:00 UTC | 1h 40m |
| 2026-05-21 | SQY7507 | - | May 21, 11:25 UTC | May 21, 22:50 UTC | 11h 25m |
| 2026-05-21 | SQY6101 | - | May 21, 03:10 UTC | May 21, 09:45 UTC | 6h 35m |
| 2026-05-20 | SEU406 | BCN → RMO | May 20, 17:20 UTC | May 20, 20:10 UTC | 2h 50m |
| 2026-05-20 | SEU405 | RMO → BCN | May 20, 13:10 UTC | May 20, 15:15 UTC | 2h 5m |
| 2026-05-20 | SEU302 | HER → RMO | May 20, 00:50 UTC | May 20, 02:30 UTC | 1h 40m |
| 2026-05-19 | SQY6101 | - | May 19, 06:15 UTC | May 19, 23:25 UTC | 17h 10m |
| 2026-05-19 | SEU304 | HER → RMO | May 19, 00:30 UTC | May 19, 02:05 UTC | 1h 35m |
| 2026-05-18 | SEU303 | RMO → HER | May 18, 10:45 UTC | May 18, 23:05 UTC | 12h 19m |
| 2026-05-18 | SQY4003 | - | May 18, 03:55 UTC | May 18, 09:00 UTC | 5h 5m |
| 2026-05-17 | SEU406 | BCN → RMO | May 17, 20:10 UTC | May 18, 02:10 UTC | 6h 0m |
| 2026-05-17 | SEU405 | RMO → BCN | May 17, 11:20 UTC | May 17, 18:30 UTC | 7h 10m |
| 2026-05-16 | SQY6101 | - | May 16, 22:30 UTC | May 17, 08:45 UTC | 10h 15m |
| 2026-05-16 | SQY6101 | - | May 16, 10:25 UTC | May 17, 08:45 UTC | 22h 20m |
| 2026-05-16 | SQY7511 | - | May 16, 00:25 UTC | May 16, 08:26 UTC | 8h 1m |
| 2026-05-15 | SEU534 | LCA → RMO | May 15, 16:05 UTC | May 15, 22:45 UTC | 6h 40m |
| 2026-05-15 | SEU533 | RMO → LCA | May 15, 14:05 UTC | May 15, 14:55 UTC | 49m |
| 2026-05-15 | SQY7504 | - | May 15, 08:30 UTC | May 15, 11:15 UTC | 2h 45m |
| 2026-05-15 | SQY7503 | - | May 15, 00:20 UTC | May 15, 06:40 UTC | 6h 20m |
| 2026-05-14 | SQY7502 | - | May 14, 04:50 UTC | May 14, 22:45 UTC | 17h 55m |
| 2026-05-13 | SEU406 | BCN → RMO | May 13, 17:20 UTC | May 14, 02:50 UTC | 9h 30m |
| 2026-05-13 | SQY7504 | - | May 13, 01:30 UTC | May 13, 15:25 UTC | 13h 55m |
| 2026-05-12 | SQY6102 | - | May 12, 04:30 UTC | May 12, 23:40 UTC | 19h 10m |
| 2026-05-11 | SQY7503 | - | May 11, 06:15 UTC | May 11, 13:20 UTC | 7h 5m |
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-SMA page for operator, model, and routing details .