Not currently tracked · last seen 5h ago
- Flights observed
- 349 showing last 50
- Avg flight time
- 6h 55m
- Typical route
- CGH → CGH
- Last seen
- 5h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-13 | - | Jul 13, 21:45 UTC | Jul 14, 02:05 UTC | 4h 20m |
| 2026-07-13 | - | Jul 13, 17:20 UTC | Jul 13, 19:55 UTC | 2h 35m |
| 2026-07-13 | - | Jul 13, 09:55 UTC | Jul 13, 15:20 UTC | 5h 25m |
| 2026-07-13 | - | Jul 13, 05:50 UTC | Jul 13, 08:40 UTC | 2h 50m |
| 2026-07-13 | - | Jul 13, 00:25 UTC | Jul 13, 04:35 UTC | 4h 10m |
| 2026-07-12 | - | Jul 12, 20:20 UTC | Jul 12, 23:20 UTC | 3h 0m |
| 2026-07-12 | CGH → CGH | Jul 12, 16:05 UTC | Jul 12, 18:50 UTC | 2h 45m |
| 2026-07-12 | - | Jul 12, 09:05 UTC | Jul 12, 13:25 UTC | 4h 20m |
| 2026-07-11 | - | Jul 11, 12:40 UTC | Jul 12, 01:05 UTC | 12h 25m |
| 2026-07-11 | - | Jul 11, 01:30 UTC | Jul 11, 10:40 UTC | 9h 10m |
| 2026-07-10 | FOR → CGH | Jul 10, 19:45 UTC | Jul 10, 23:00 UTC | 3h 15m |
| 2026-07-10 | - | Jul 10, 15:45 UTC | Jul 10, 18:45 UTC | 3h 0m |
| 2026-07-10 | CGH → CGH | Jul 10, 10:05 UTC | Jul 10, 13:45 UTC | 3h 40m |
| 2026-07-10 | - | Jul 10, 00:25 UTC | Jul 10, 01:10 UTC | 45m |
| 2026-07-09 | - | Jul 9, 22:00 UTC | Jul 9, 23:10 UTC | 1h 10m |
| 2026-07-09 | - | Jul 9, 16:35 UTC | Jul 9, 17:15 UTC | 40m |
| 2026-07-09 | - | Jul 9, 08:45 UTC | Jul 9, 13:35 UTC | 4h 50m |
| 2026-07-09 | - | Jul 9, 02:45 UTC | Jul 9, 05:15 UTC | 2h 30m |
| 2026-07-08 | - | Jul 8, 23:30 UTC | Jul 9, 00:25 UTC | 55m |
| 2026-07-08 | - | Jul 8, 09:15 UTC | Jul 8, 21:55 UTC | 12h 40m |
| 2026-07-07 | - | Jul 7, 20:10 UTC | Jul 8, 02:10 UTC | 6h 0m |
| 2026-07-07 | - | Jul 7, 12:25 UTC | Jul 7, 16:30 UTC | 4h 5m |
| 2026-07-07 | - | Jul 7, 02:05 UTC | Jul 7, 10:45 UTC | 8h 40m |
| 2026-07-06 | - | Jul 6, 22:15 UTC | Jul 7, 01:05 UTC | 2h 50m |
| 2026-07-06 | - | Jul 6, 16:00 UTC | Jul 6, 21:10 UTC | 5h 10m |
| 2026-07-06 | - | Jul 6, 13:15 UTC | Jul 6, 14:30 UTC | 1h 15m |
| 2026-07-06 | - | Jul 6, 00:20 UTC | Jul 6, 00:55 UTC | 35m |
| 2026-07-05 | - | Jul 5, 07:45 UTC | Jul 5, 22:55 UTC | 15h 10m |
| 2026-07-04 | - | Jul 4, 23:20 UTC | Jul 5, 22:55 UTC | 23h 35m |
| 2026-07-04 | - | Jul 4, 21:35 UTC | Jul 5, 13:30 UTC | 15h 55m |
| 2026-07-04 | - | Jul 4, 17:10 UTC | Jul 4, 19:50 UTC | 2h 40m |
| 2026-07-04 | - | Jul 4, 15:15 UTC | Jul 4, 16:00 UTC | 45m |
| 2026-07-04 | - | Jul 4, 13:20 UTC | Jul 4, 14:10 UTC | 50m |
| 2026-07-04 | - | Jul 4, 01:50 UTC | Jul 4, 10:05 UTC | 8h 15m |
| 2026-07-03 | GIG → IGU | Jul 3, 22:25 UTC | Jul 3, 23:15 UTC | 50m |
| 2026-07-03 | - | Jul 3, 20:10 UTC | Jul 3, 21:20 UTC | 1h 10m |
| 2026-07-03 | - | Jul 3, 16:15 UTC | Jul 3, 18:30 UTC | 2h 15m |
| 2026-07-02 | GRU → AEP | Jul 2, 23:05 UTC | Jul 3, 14:45 UTC | 15h 40m |
| 2026-07-02 | - | Jul 2, 03:20 UTC | Jul 2, 21:40 UTC | 18h 20m |
| 2026-07-02 | - | Jul 2, 03:05 UTC | Jul 2, 21:40 UTC | 18h 35m |
| 2026-07-01 | - | Jul 1, 04:50 UTC | Jul 1, 20:55 UTC | 16h 5m |
| 2026-07-01 | - | Jul 1, 03:00 UTC | Jul 1, 03:15 UTC | 15m |
| 2026-06-30 | - | Jun 30, 08:45 UTC | Jun 30, 23:00 UTC | 14h 15m |
| 2026-06-30 | - | Jun 30, 01:19 UTC | Jun 30, 23:00 UTC | 21h 41m |
| 2026-06-30 | - | Jun 30, 00:45 UTC | Jun 30, 23:00 UTC | 22h 16m |
| 2026-06-29 | - | Jun 29, 09:10 UTC | Jun 29, 19:29 UTC | 10h 20m |
| 2026-06-28 | - | Jun 28, 21:34 UTC | Jun 29, 19:29 UTC | 21h 55m |
| 2026-06-28 | - | Jun 28, 17:50 UTC | Jun 28, 18:44 UTC | 55m |
| 2026-06-28 | SSA → VIX | Jun 28, 15:20 UTC | Jun 28, 16:29 UTC | 1h 10m |
| 2026-06-28 | - | Jun 28, 12:35 UTC | Jun 28, 12:44 UTC | 10m |
Specifications
| Registration | PR-XMU |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | E49525 · 71112445 (octal) |
Looking for transponder-level data? View the Mode-S E49525 page for country allocation, callsign history, and ADS-B signal details.
PR-XMU frequently asked
What type of aircraft is PR-XMU?
PR-XMU is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for PR-XMU?
PR-XMU broadcasts on Mode-S (ICAO 24-bit) address E49525 (octal 71112445). View the transponder page.
What route does PR-XMU typically fly?
PR-XMU most frequently flies between CGH and CGH based on observed flights.
Where is PR-XMU right now?
PR-XMU is not currently being tracked; last seen 5h ago.