Not currently tracked · last seen 54m ago
- Flights observed
- 112 showing last 50
- Avg flight time
- 2h 31m
- Typical route
- SDU → CGH
- Last seen
- 54m ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-05-30 | GYN → CGH | May 30, 09:35 UTC | May 30, 10:10 UTC | 35m |
| 2026-05-16 | GRU → CNF | May 16, 01:35 UTC | May 16, 01:55 UTC | 20m |
| 2026-05-15 | GRU → SSA | May 15, 18:35 UTC | May 15, 23:40 UTC | 5h 5m |
| 2026-05-15 | ASU → GRU | May 15, 15:25 UTC | May 15, 16:50 UTC | 1h 25m |
| 2026-05-15 | GRU → ASU | May 15, 12:30 UTC | May 15, 14:10 UTC | 1h 40m |
| 2026-05-15 | MGF → GRU | May 15, 07:05 UTC | May 15, 09:35 UTC | 2h 30m |
| 2026-05-15 | VIX → CGH | May 15, 02:50 UTC | May 15, 05:25 UTC | 2h 35m |
| 2026-05-14 | GYN → GRU | May 14, 19:35 UTC | May 14, 20:00 UTC | 25m |
| 2026-05-14 | GRU → CAC | May 14, 16:55 UTC | May 14, 17:20 UTC | 25m |
| 2026-05-14 | GRU → POA | May 14, 11:35 UTC | May 14, 15:05 UTC | 3h 30m |
| 2026-05-06 | CGH → JPA | May 6, 14:30 UTC | May 6, 15:25 UTC | 55m |
| 2026-05-06 | SDU → CGH | May 6, 12:05 UTC | May 6, 12:50 UTC | 45m |
| 2026-05-06 | CGH → SDU | May 6, 10:25 UTC | May 6, 11:00 UTC | 36m |
| 2026-05-05 | NAT → CGH | May 5, 22:30 UTC | May 5, 23:15 UTC | 45m |
| 2026-05-05 | GRU → POA | May 5, 20:35 UTC | May 5, 20:55 UTC | 20m |
| 2026-05-05 | CGH → GYN | May 5, 13:30 UTC | May 5, 17:40 UTC | 4h 10m |
| 2026-05-05 | CNF → CGH | May 5, 11:25 UTC | May 5, 12:10 UTC | 45m |
| 2026-05-05 | CGH → CNF | May 5, 00:20 UTC | May 5, 01:00 UTC | 40m |
| 2026-05-04 | VIX → CGH | May 4, 18:30 UTC | May 4, 23:10 UTC | 4h 41m |
| 2026-05-04 | BSB → GIG | May 4, 11:35 UTC | May 4, 16:15 UTC | 4h 40m |
| 2026-04-30 | IGU → GIG | Apr 30, 21:10 UTC | Apr 30, 21:20 UTC | 10m |
| 2026-04-30 | VIX → GIG | Apr 30, 14:35 UTC | Apr 30, 19:55 UTC | 5h 20m |
| 2026-04-29 | CGH → FOR | Apr 29, 20:35 UTC | Apr 30, 13:00 UTC | 16h 25m |
| 2026-04-29 | CGH → REC | Apr 29, 14:40 UTC | Apr 29, 19:00 UTC | 4h 20m |
| 2026-04-29 | SDU → CGH | Apr 29, 11:55 UTC | Apr 29, 12:45 UTC | 50m |
| 2026-04-28 | CGH → JPA | Apr 28, 23:54 UTC | Apr 29, 00:30 UTC | 35m |
| 2026-04-28 | SDU → CGH | Apr 28, 22:10 UTC | Apr 28, 22:40 UTC | 30m |
| 2026-04-28 | CGH → SDU | Apr 28, 20:00 UTC | Apr 28, 20:35 UTC | 35m |
| 2026-04-28 | SDU → CGH | Apr 28, 18:05 UTC | Apr 28, 18:50 UTC | 45m |
| 2026-04-28 | CGH → SDU | Apr 28, 16:20 UTC | Apr 28, 16:55 UTC | 35m |
| 2026-04-28 | SDU → CGH | Apr 28, 14:40 UTC | Apr 28, 15:10 UTC | 30m |
| 2026-04-28 | CGH → SDU | Apr 28, 10:55 UTC | Apr 28, 11:25 UTC | 30m |
| 2026-04-28 | BSB → CGH | Apr 28, 00:10 UTC | Apr 28, 01:10 UTC | 1h 0m |
| 2026-04-27 | POA → GIG | Apr 27, 22:00 UTC | Apr 27, 22:45 UTC | 45m |
| 2026-04-27 | GIG → POA | Apr 27, 19:25 UTC | Apr 27, 20:40 UTC | 1h 15m |
| 2026-04-27 | GIG → IGU | Apr 27, 03:20 UTC | Apr 27, 10:35 UTC | 7h 15m |
| 2026-04-27 | GRU → GIG | Apr 27, 01:45 UTC | Apr 27, 02:25 UTC | 40m |
| 2026-04-26 | VIX → BSB | Apr 26, 20:00 UTC | Apr 26, 23:45 UTC | 3h 45m |
| 2026-04-26 | GIG → REC | Apr 26, 13:15 UTC | Apr 26, 18:40 UTC | 5h 25m |
| 2026-04-26 | VIX → SDU | Apr 26, 09:10 UTC | Apr 26, 12:05 UTC | 2h 55m |
| 2026-04-25 | CGH → GYN | Apr 25, 21:55 UTC | Apr 26, 00:55 UTC | 3h 0m |
| 2026-04-25 | IOS → GRU | Apr 25, 19:15 UTC | Apr 25, 19:45 UTC | 30m |
| 2026-04-25 | IOS → GRU | Apr 25, 16:35 UTC | Apr 25, 18:25 UTC | 1h 50m |
| 2026-04-25 | CGH → REC | Apr 25, 12:40 UTC | Apr 25, 15:40 UTC | 3h 0m |
| 2026-04-24 | BSB → SSA | Apr 24, 21:35 UTC | Apr 25, 09:55 UTC | 12h 20m |
| 2026-04-24 | IGU → GIG | Apr 24, 15:20 UTC | Apr 24, 19:35 UTC | 4h 15m |
| 2026-04-24 | UDI → CGH | Apr 24, 13:10 UTC | Apr 24, 13:55 UTC | 45m |
| 2026-04-24 | CGH → UDI | Apr 24, 01:20 UTC | Apr 24, 02:00 UTC | 40m |
| 2026-04-23 | GRU → SSA | Apr 23, 18:45 UTC | Apr 23, 23:50 UTC | 5h 5m |
| 2026-04-23 | SJP → CGH | Apr 23, 12:30 UTC | Apr 23, 15:45 UTC | 3h 15m |
Specifications
| Registration | PR-GUR |
| Aircraft type | BOEING 737-800 (B738) |
| Mode-S code | E48C04 · 71106004 (octal) |
Looking for transponder-level data? View the Mode-S E48C04 page for country allocation, callsign history, and ADS-B signal details.
PR-GUR frequently asked
What type of aircraft is PR-GUR?
PR-GUR is a BOEING 737-800 (ICAO type code B738).
What is the Mode-S transponder code for PR-GUR?
PR-GUR broadcasts on Mode-S (ICAO 24-bit) address E48C04 (octal 71106004). View the transponder page.
What route does PR-GUR typically fly?
PR-GUR most frequently flies between SDU and CGH based on observed flights.
Where is PR-GUR right now?
PR-GUR is not currently being tracked; last seen 54m ago.