Departure (DP485 Flight Schedule)
Moscow, RussiaMSK 00:00:00 DAY
Arrival (DP485 Flight Schedule)
+04 00:00:00 DAY
Flight Radar Checker DP 485
Live Flight Tracker Map
Flight DP485 from Moscow to Ulyanovsk is operated by Pobeda. Scheduled time of departure from Vnukovo is 19:30 MSK and scheduled time of arrival in Barataevka is 21:05 +04. The duration of the flight is 1 hour 35 minutes.
0.5 out of 5 stars / 1 vote
Flight Finder
from Ulyanovsk to Moscow
History Flight Information for DP485 from Flight Scanner System
| Date | Flight | Departure Airport | Arrival Airport | Scheduled | Plane | Estimated | ||
|---|---|---|---|---|---|---|---|---|
| Departure | Arrival | Departure | Arrival | |||||
| Sun, 09 Mar | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Sat, 08 Mar | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Fri, 07 Mar | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Thu, 06 Mar | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Wed, 05 Mar | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Tue, 04 Mar | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Mon, 03 Mar | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Sun, 02 Mar | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Sat, 01 Mar | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Fri, 28 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Thu, 27 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Wed, 26 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Tue, 25 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Mon, 24 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Sun, 23 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Sat, 22 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Fri, 21 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Thu, 20 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Wed, 19 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Tue, 18 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Mon, 17 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Sun, 16 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Sat, 15 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Fri, 14 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Thu, 13 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Wed, 12 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Tue, 11 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Mon, 10 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Sun, 09 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Sat, 08 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Fri, 07 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Thu, 06 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Wed, 05 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Tue, 04 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Mon, 03 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Sun, 02 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
| Sat, 01 Feb | DP485 | Vnukovo (VKO) | Barataevka (ULV) | 19:30 MSK | 21:05 +04 | |||
Disclaimer for DP485 Flight Radar Data
Flight DP485 from Vnukovo to Barataevka data is collected from different sources. The data is for informational purposes only and PlaneMapper is not responsible for the accuracy and reliability of flight DP485 data.
