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