Not currently tracked · last seen 7h ago
- Flights observed
- 67 showing last 50
- Avg flight time
- 5h 33m
- Typical route
- IST → CIT
- Last seen
- 7h ago
Last known area
Recent flights last 50
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-18 | - | Jul 18, 13:35 UTC | Jul 18, 16:30 UTC | 2h 55m |
| 2026-07-18 | CIT → BUD | Jul 18, 09:00 UTC | Jul 18, 12:25 UTC | 3h 25m |
| 2026-07-17 | CIT → BUD | Jul 17, 16:24 UTC | Jul 18, 12:25 UTC | 20h 1m |
| 2026-07-17 | LED → CIT | Jul 17, 15:00 UTC | Jul 17, 15:15 UTC | 15m |
| 2026-07-16 | - | Jul 16, 07:10 UTC | Jul 16, 07:35 UTC | 25m |
| 2026-07-16 | - | Jul 16, 04:50 UTC | Jul 16, 05:25 UTC | 35m |
| 2026-07-15 | - | Jul 15, 09:05 UTC | Jul 16, 05:25 UTC | 20h 20m |
| 2026-07-15 | - | Jul 15, 06:50 UTC | Jul 15, 07:15 UTC | 25m |
| 2026-07-14 | - | Jul 14, 17:10 UTC | Jul 15, 06:10 UTC | 12h 59m |
| 2026-07-13 | - | Jul 13, 10:10 UTC | Jul 13, 10:40 UTC | 30m |
| 2026-07-13 | - | Jul 13, 07:25 UTC | Jul 13, 07:55 UTC | 30m |
| 2026-07-10 | - | Jul 10, 12:35 UTC | Jul 10, 13:05 UTC | 30m |
| 2026-07-10 | - | Jul 10, 10:10 UTC | Jul 10, 10:45 UTC | 35m |
| 2026-07-09 | - | Jul 9, 07:15 UTC | Jul 9, 10:10 UTC | 2h 55m |
| 2026-07-09 | - | Jul 9, 05:15 UTC | Jul 9, 05:40 UTC | 25m |
| 2026-07-08 | - | Jul 8, 04:00 UTC | Jul 8, 04:25 UTC | 25m |
| 2026-07-07 | - | Jul 7, 15:35 UTC | Jul 8, 02:35 UTC | 11h 0m |
| 2026-07-07 | - | Jul 7, 13:40 UTC | Jul 7, 14:00 UTC | 20m |
| 2026-07-07 | - | Jul 7, 11:30 UTC | Jul 7, 12:15 UTC | 45m |
| 2026-07-06 | - | Jul 6, 10:20 UTC | Jul 6, 10:45 UTC | 25m |
| 2026-07-06 | - | Jul 6, 07:35 UTC | Jul 6, 08:05 UTC | 30m |
| 2026-07-03 | - | Jul 3, 11:55 UTC | Jul 3, 12:25 UTC | 30m |
| 2026-07-03 | - | Jul 3, 00:15 UTC | Jul 3, 10:20 UTC | 10h 5m |
| 2026-07-02 | - | Jul 2, 07:45 UTC | Jul 2, 21:55 UTC | 14h 10m |
| 2026-07-02 | CIT → MUC | Jul 2, 05:55 UTC | Jul 2, 06:15 UTC | 20m |
| 2026-06-30 | - | Jun 30, 15:50 UTC | Jun 30, 17:35 UTC | 1h 45m |
| 2026-06-29 | - | Jun 29, 22:05 UTC | Jun 30, 14:35 UTC | 16h 31m |
| 2026-06-29 | - | Jun 29, 20:09 UTC | Jun 29, 20:35 UTC | 25m |
| 2026-06-29 | - | Jun 29, 10:24 UTC | Jun 29, 19:24 UTC | 9h 0m |
| 2026-06-29 | - | Jun 29, 07:44 UTC | Jun 29, 08:14 UTC | 30m |
| 2026-06-25 | - | Jun 25, 07:15 UTC | Jun 25, 19:15 UTC | 12h 0m |
| 2026-06-25 | - | Jun 25, 03:10 UTC | Jun 25, 05:50 UTC | 2h 40m |
| 2026-06-17 | UKK → CIT | Jun 17, 04:00 UTC | Jun 17, 04:21 UTC | 20m |
| 2026-06-17 | CIT → UKK | Jun 17, 02:00 UTC | Jun 17, 02:25 UTC | 25m |
| 2026-06-16 | CIT → UKK | Jun 16, 03:39 UTC | Jun 17, 02:25 UTC | 22h 46m |
| 2026-06-15 | - | Jun 15, 23:25 UTC | Jun 16, 03:39 UTC | 4h 15m |
| 2026-06-15 | - | Jun 15, 17:25 UTC | Jun 15, 21:35 UTC | 4h 10m |
| 2026-06-14 | TBS → CIT | Jun 14, 07:15 UTC | Jun 14, 07:50 UTC | 35m |
| 2026-06-13 | BUS → NQZ | Jun 13, 13:10 UTC | Jun 14, 05:25 UTC | 16h 15m |
| 2026-06-12 | NQZ → BUS | Jun 12, 18:10 UTC | Jun 13, 12:05 UTC | 17h 54m |
| 2026-06-10 | IST → CIT | Jun 10, 07:45 UTC | Jun 10, 09:50 UTC | 2h 5m |
| 2026-06-10 | CIT → IST | Jun 10, 05:40 UTC | Jun 10, 06:00 UTC | 20m |
| 2026-06-10 | CIT → IST | Jun 10, 03:20 UTC | Jun 10, 05:00 UTC | 1h 40m |
| 2026-06-05 | IST → CIT | Jun 5, 21:10 UTC | Jun 5, 23:15 UTC | 2h 5m |
| 2026-06-04 | BKK → CIT | Jun 4, 23:35 UTC | Jun 5, 19:30 UTC | 19h 55m |
| 2026-06-04 | BKK → CIT | Jun 4, 23:15 UTC | Jun 5, 19:30 UTC | 20h 15m |
| 2026-06-04 | CIT → BKK | Jun 4, 07:05 UTC | Jun 4, 21:50 UTC | 14h 45m |
| 2026-06-04 | CIT → MUC | Jun 4, 05:00 UTC | Jun 4, 05:40 UTC | 40m |
| 2026-05-26 | IST → CIT | May 26, 16:50 UTC | May 26, 17:50 UTC | 1h 0m |
| 2026-05-26 | IST → CIT | May 26, 15:45 UTC | May 26, 15:54 UTC | 10m |
Specifications
| Registration | UP-B3720 |
| Aircraft type | BOEING 737 MAX 8 (B38M) |
| Mode-S code | 683266 · 32031146 (octal) |
Looking for transponder-level data? View the Mode-S 683266 page for country allocation, callsign history, and ADS-B signal details.
UP-B3720 frequently asked
What type of aircraft is UP-B3720?
UP-B3720 is a BOEING 737 MAX 8 (ICAO type code B38M).
What is the Mode-S transponder code for UP-B3720?
UP-B3720 broadcasts on Mode-S (ICAO 24-bit) address 683266 (octal 32031146). View the transponder page.
What route does UP-B3720 typically fly?
UP-B3720 most frequently flies between IST and CIT based on observed flights.
Where is UP-B3720 right now?
UP-B3720 is not currently being tracked; last seen 7h ago.