Hello,
the problematic behavior is caused by an invalid pedestrian route.
The edge sequence 633 -629 leads to junction 476 which is not connected with next route edge -813
This causes the person to walk contrary to the expected direction and thus reach the arrival position earlier than expected.
In the latest development version of SUMO additional warnings have been implemented to make the faulty behavior more obvious.
A possible fix would be to either use the sequence
633 -629
-629 -813 or 633 -813
The network itself is problematic insofer that it deviates from the two possible styles for pedestrian network modelling:
2) without crossing and walkingAreas but with sidewalks that have no connections. In this case, pedestrians will assume a fully connected topology at each intersection but their paths are not modelled (they "jump" across). This type of network is generated automatically by netconvert when not generating crossings or walkingareas. Note, that "jumping" potentially causes negative timeLoss in the current version but this will only be noticable if the dwadling option is disabled.
In your case the network contains sidewalks that are connected but this forces awkward detours because there are no connections that allow changing the walking direction.
regards,
Jakob