Ok,
now after your video I see what you mean. But as Ramin already wrote, why would you force the "Rover" file as kinematic when it obviously is a static observation? The coordinates of those 3 single trajectories aren't spread that wide considering your long baselines of around 100 km. But anyway, once you've got single points from the trajectories you can select all of them, right click and "Average Points". That might get you close to what the baseline/network adjustment would compute.
But I would definitely not do it in this case.
In order to actually get points to be averaged out of the trajectory you'll have to change it in the project settings and re-run the base line processing. Setting trajectory to no will create single points.
See also this Trimble Power Hour video - "TBC Recap: Static GNSS and Baseline Processing". It's for free but on some of them you have to leave the email address.
https://register.gotowebinar.com/recording/8590671671074275083(
https://geospatial.trimble.com/webinars/trimble-business-center)
What I'm actually curious about is how you managed to have the T02 containing exactly 1 day of data and have start/stop time in all 4 of them exactly the same at a rather uneven time like 09:59:42. What program did you use to edit those files?
I know how to concatenate T02 files by using "copy /B *.T02 all.T02" on the command line, but I don't know how to cut them. I'm really interested how you did that.