Skip, RouteMap's route guideRouteplanner.app
Routeplanner.app

EvanderLenasia

Distance: 89 mi·Duration: 1 h 45 min

Save for offline?

We'll download this route and its map area so it works without a connection. This can take a moment -- you can keep using the app while it finishes.

Driving from Evander to Lenasia takes about via N17. The distance is 89 mi. The straight-line distance is 78 mi. EV charging is available along the route, including in Kinross, Katlehong, Alberton, Diepdale. Driving directions

Driving directions

19 · 89 mi
  1. 1 Depart right 47 yd
  2. 2 At end of road, turn left onto Bologna Road 1 mi
  3. 3 At end of road, turn right onto Solly Zwane Street 132 yd
  4. 4 Turn left onto Rotterdam Road 1 mi
  5. 5 Turn right 3 mi
  6. 6 Take ramp slightly left 1 mi
  7. 7 Merge slightly right 64 mi
  8. 8 Take exit slightly left 1 mi
  9. 9 Merge slightly right onto Southern Bypass 14 mi
  10. 10 Keep slightly left 5 mi
  11. 11 Take exit slightly left 1 mi
  12. 12 Keep slightly left 97 yd
  13. 13 Turn straight onto Klipspruit Valley Road 2 mi
  1. 14 Turn left onto Nirvana Drive 1 mi
  2. 15 Turn right onto Capella Street 159 yd
  3. 16 Continue left onto Capella Street 54 yd
  4. 17 Turn left onto Corona Avenue 1 mi
  5. 18 Turn right onto Pegasus Street 147 yd
  6. 19 Arrive onto Pegasus Street

The return trip from Lenasia to Evander covers roughly the same distance, 89 mi.

Questions and answers

Lenasia lies roughly to the west of Evander.

How far is it from Evander to Lenasia?

The distance between Evander and Lenasia is 89 mi by road.

How long does it take to drive from Evander to Lenasia?

The drive from Evander to Lenasia takes approximately 1 h 45 min by car.

What is the best route from Evander to Lenasia?

The fastest route from Evander to Lenasia covers 89 mi with a driving time of approximately 1 h 45 min.

What is the shortest route from Evander to Lenasia?

The shortest driving route from Evander to Lenasia is about 89 mi by road.

Sources

Distance and drive time are computed from OpenStreetMap road data with the OSRM routing engine. Updated .