Column John Vanderaart – The not so fastest route

Just a Tuesday afternoon well before four. I started in Alphen a/d Rijn in the morning at half past six. Nice in the morning. Nice on my own in the office. Yes, that is two hours of enjoyment in silence. That has the consequence that I travel to Haarlem again around a quarter past three. By car, because public transport also sputtered something again.

Anyway, I on the way back. When turning the provincial road I experience a hustle and bustle that should not be there at that time. But: the A12 is closed, the Coentunnel is closed and on the ring road of Amsterdam it is misery anyway. Admittedly, all that should be a far from my bed show on the provincial road at Alphen a/d Rijn. That is not the case! Apparently, many travelers have adjusted their times and their routes in order to make their commuting as optimally as possible. They hope …

Understandable, but that is clearly at the expense of my optimum. In the meantime, Google Maps is becoming gloomy and gloomy via Android Auto. The road turns redder and redder. Already at Leimuiden I get stuck. Then I have to let the bridge shoot at Hillegom to get to Zwaanshoek across the Drie Merenweg. There also a bridge: “Open!” And then four times traffic light-delay before I end up in Bennebroek. Google Maps gives me the next route adjustment because of a new Vastgloper on the Rijksstraatweg and sends me along the Leidsevaart. Even before the old office of the Waterleidingduinen it turns red again. I am now through all my detours …

Anyway, a ride that could take 40 minutes, finally took 100 minutes. Fully inside and apparently also via the fastest route. Am I very curious how long I would have been on the road without current route information? Unfortunately, Google Maps does not tell me that.

Can take 40 minutes. At the time of planning this route it is 11:22 in the morning. Nothing on the hand. Not yet…