There were two bugs I reported in 1.2 that seem relevant. One was that crossing the date line was adding/subtracting 24 hours to arrival times when it shouldn't be. Sami said that'd be fixed for 1.3, I assume it has been. It certainly still exists in 1.2, I just created a DOTM route from UUEE-NTAA that takes off at 1220 Tuesday in Moscow (0920 Tuesday UTC) flies for 22 hours, and lands in Tahiti at 2115 Monday (0715 Tuesday UTC), which gives a flight time of -2 hours.
The other issue, which I don't think was going to be fixed (I remember not being able to convince Sami it was a bug, I'll try and find the thread), is that the *** to indicate +1, 2 or 6 days are measured from the tech stop, not the original departure.
If a flight leaves Singapore at 1155 Friday (355 Fri UTC), flies 21.40, it should land at Chicago at 1935 Friday (135 Sat UTC). If that first bug hasn't been fixed, then the plane would land at 1935 Thursday, which would explain the ******.
If the first bug has been fixed, but the second hasn't, that would also explain the ******. Leave Singapore 1155 Friday (355 Fri UTC), Leave Yakutsk at 0055 Saturday (1555 Fri UTC), reach Chicago at 1935 Friday (135 Sat UTC). All the flight times are then correct, the issue for the display is the flight has departed Yakutsk on Saturday, arrived in Chicago on Friday, hence the 6 stars.
Can't tell which of those two it is without a screenie of 'copy this route' showing which days it takes the slots from. Any chance we can have one?