sensors Mode-S transponder
504E70
ICAO 24-bit transponder address · allocated to Moldova
Currently assigned to ER-BYK · BOEING 747-400
- Hex
- 504E70
- Octal
- 24047160
- Decimal
- 5,262,960
- Country
- MD
- Tail
- ER-BYK
- Type
- B744
- Flights observed
- 138
- Distinct callsigns
- 16
- Country
- MD
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 504E70 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TVR4704 | Tavrey Airlines | 27 | 2026-05-22 |
| TVR4702 | Tavrey Airlines | 21 | 2026-05-17 |
| TVR4703 | Tavrey Airlines | 14 | 2026-05-21 |
| TVR4701 | Tavrey Airlines | 13 | 2026-05-17 |
| TVR4717 | Tavrey Airlines | 9 | 2026-05-23 |
| TVR4721 | - | 8 | 2026-05-17 |
| TVR4718 | Tavrey Airlines | 7 | 2026-05-25 |
| TVR4719 | Tavrey Airlines | 6 | 2026-05-27 |
| TVR4712 | Tavrey Airlines | 6 | 2026-04-18 |
| TVR4722 | - | 5 | 2026-05-19 |
| TVR4716 | Tavrey Airlines | 5 | 2026-04-28 |
| TVR4714 | - | 5 | 2026-04-21 |
| TVR4715 | Tavrey Airlines | 4 | 2026-04-21 |
| TVR4705 | Tavrey Airlines | 4 | 2026-04-20 |
| TVR4713 | Tavrey Airlines | 2 | 2026-04-18 |
| TVR4707 | Tavrey Airlines | 2 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-27 | TVR4719 | TLV → HKG | May 27, 06:29 UTC | May 27, 13:45 UTC | 7h 15m |
| 2026-05-25 | TVR4718 | DWC → TLV | May 25, 19:35 UTC | May 26, 13:04 UTC | 17h 30m |
| 2026-05-25 | TVR4718 | DWC → TLV | May 25, 17:05 UTC | May 26, 13:04 UTC | 19h 59m |
| 2026-05-24 | TVR4718 | DWC → TLV | May 24, 18:25 UTC | May 24, 21:45 UTC | 3h 20m |
| 2026-05-23 | TVR4717 | SYD → HKG | May 23, 13:10 UTC | May 23, 16:55 UTC | 3h 45m |
| 2026-05-22 | TVR4704 | HKG → DWC | May 22, 05:45 UTC | May 22, 09:40 UTC | 3h 55m |
| 2026-05-22 | TVR4704 | HKG → DWC | May 22, 03:45 UTC | May 22, 04:00 UTC | 15m |
| 2026-05-21 | TVR4703 | DWC → HKG | May 21, 18:20 UTC | May 22, 00:10 UTC | 5h 50m |
| 2026-05-21 | TVR4703 | DWC → HKG | May 21, 17:05 UTC | May 21, 17:20 UTC | 15m |
| 2026-05-21 | TVR4704 | HKG → DWC | May 21, 05:40 UTC | May 21, 09:35 UTC | 3h 55m |
| 2026-05-21 | TVR4704 | HKG → DWC | May 21, 03:35 UTC | May 21, 03:50 UTC | 15m |
| 2026-05-20 | TVR4703 | DWC → HKG | May 20, 08:40 UTC | May 21, 00:50 UTC | 16h 10m |
| 2026-05-20 | TVR4704 | HKG → DWC | May 20, 06:40 UTC | May 20, 06:55 UTC | 15m |
| 2026-05-19 | TVR4703 | DWC → HKG | May 19, 22:40 UTC | May 20, 04:35 UTC | 5h 55m |
| 2026-05-19 | TVR4722 | - | May 19, 06:50 UTC | May 19, 14:05 UTC | 7h 15m |
| 2026-05-17 | TVR4721 | - | May 17, 18:05 UTC | May 18, 12:20 UTC | 18h 15m |
| 2026-05-17 | TVR4721 | - | May 17, 17:30 UTC | May 18, 12:20 UTC | 18h 50m |
| 2026-05-17 | TVR4721 | - | May 17, 14:25 UTC | May 18, 12:20 UTC | 21h 55m |
| 2026-05-17 | TVR4702 | HKG → HKG | May 17, 12:20 UTC | May 17, 12:35 UTC | 15m |
| 2026-05-17 | TVR4701 | DMM → DWC | May 17, 03:40 UTC | May 17, 09:30 UTC | 5h 50m |
| 2026-05-14 | TVR4722 | - | May 14, 05:15 UTC | May 14, 21:25 UTC | 16h 10m |
| 2026-05-13 | TVR4722 | - | May 13, 19:55 UTC | May 14, 05:15 UTC | 9h 20m |
| 2026-05-13 | TVR4721 | - | May 13, 05:35 UTC | May 13, 20:00 UTC | 14h 25m |
| 2026-05-12 | TVR4721 | - | May 12, 19:55 UTC | May 13, 05:40 UTC | 9h 45m |
| 2026-05-11 | TVR4721 | - | May 11, 03:50 UTC | May 11, 19:45 UTC | 15h 55m |
| 2026-05-10 | TVR4722 | - | May 10, 08:50 UTC | May 10, 22:20 UTC | 13h 30m |
| 2026-05-09 | TVR4722 | - | May 9, 14:40 UTC | May 10, 08:50 UTC | 18h 10m |
| 2026-05-09 | TVR4721 | - | May 9, 05:40 UTC | May 9, 10:45 UTC | 5h 5m |
| 2026-05-09 | TVR4721 | SHJ → SHJ | May 9, 03:35 UTC | May 9, 04:00 UTC | 25m |
| 2026-05-08 | TVR4702 | HKG → HKG | May 8, 03:24 UTC | May 8, 05:20 UTC | 1h 55m |
| 2026-05-08 | TVR4702 | HKG → HKG | May 8, 01:24 UTC | May 8, 01:35 UTC | 10m |
| 2026-05-07 | TVR4701 | DMM → DWC | May 7, 18:30 UTC | May 7, 22:25 UTC | 3h 55m |
| 2026-05-06 | TVR4702 | HKG → HKG | May 6, 03:20 UTC | May 6, 05:20 UTC | 2h 0m |
| 2026-05-06 | TVR4702 | HKG → HKG | May 6, 01:20 UTC | May 6, 01:35 UTC | 15m |
| 2026-05-05 | TVR4701 | DMM → DWC | May 5, 04:35 UTC | May 5, 22:10 UTC | 17h 35m |
| 2026-05-05 | TVR4702 | HKG → HKG | May 5, 02:30 UTC | May 5, 02:40 UTC | 10m |
| 2026-05-04 | TVR4701 | DMM → DWC | May 4, 17:35 UTC | May 5, 00:10 UTC | 6h 36m |
| 2026-05-04 | TVR4702 | HKG → HKG | May 4, 09:00 UTC | May 4, 09:20 UTC | 20m |
| 2026-05-04 | TVR4702 | HKG → HKG | May 4, 03:35 UTC | May 4, 07:10 UTC | 3h 35m |
| 2026-05-04 | TVR4702 | HKG → HKG | May 4, 01:35 UTC | May 4, 01:44 UTC | 10m |
| 2026-05-03 | TVR4701 | DMM → DWC | May 3, 15:25 UTC | May 3, 22:15 UTC | 6h 50m |
| 2026-05-03 | TVR4702 | HKG → HKG | May 3, 03:50 UTC | May 3, 09:40 UTC | 5h 50m |
| 2026-05-03 | TVR4702 | HKG → HKG | May 3, 01:50 UTC | May 3, 02:05 UTC | 15m |
| 2026-05-02 | TVR4701 | DMM → DWC | May 2, 15:10 UTC | May 2, 22:15 UTC | 7h 5m |
| 2026-05-02 | TVR4702 | HKG → HKG | May 2, 11:20 UTC | May 2, 11:40 UTC | 20m |
| 2026-05-02 | TVR4702 | HKG → HKG | May 2, 06:00 UTC | May 2, 09:40 UTC | 3h 40m |
| 2026-05-02 | TVR4702 | HKG → HKG | May 2, 03:55 UTC | May 2, 04:05 UTC | 10m |
| 2026-05-02 | TVR4701 | DMM → DWC | May 2, 01:25 UTC | May 2, 01:30 UTC | 5m |
| 2026-05-01 | TVR4701 | DMM → DWC | May 1, 18:00 UTC | May 1, 23:10 UTC | 5h 10m |
| 2026-05-01 | TVR4702 | HKG → HKG | May 1, 09:40 UTC | May 1, 15:25 UTC | 5h 45m |
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-BYK page for operator, model, and routing details .