Yesterday, in beautiful Pacific Northwest weather, I picked up a good friend -- who is very ill, and needed a lift -- and we drove to Paradise on Mt. Rainier, elevation 5400 feet. The car performed superbly, making the curvy mountain roads smooth and comfortable. We made the 242 mile trip in a single charge, returning home with 18 rated miles to spare. Here are the stats:
Starting rated miles: 266 (range charge)
Outbound distance: 121.8 miles
Outbound energy use: 45.1 kWh
Outbound average energy use: 370 wh/m
Arriving rated miles: 106
Return trip starting rated miles: 104 (i.e., lost 2 miles; software version 4.3)
Ending rated miles: 18
Total distance: 242.0 miles
Total energy use: 68.6 kWh
Overall average energy use: 283
I generally drove at the speed limit. Heavy traffic for part of the trip slowed me down, but I made up for that elsewhere. I used very little climate control. Outside temperatures ranges from 46 F when I left, to 39 F at the top, to 59 F when I returned. Weight payload was about 350 pounds. We stopped a few times in both directions, including some minor detours. Interestingly, we left Paradise with 104 rated miles, but when we stopped to eat at Longmire, 11 miles down the road, we had 110 rated miles.
One interesting thing I will note is that the factor used in computing "rated miles," -- i.e., 308 wh/m -- does not work. Whether you look at each leg of the trip or the trip as a whole, the rated miles I used cannot be accurately computed without using a factor considerably lower than 308 wh/m. At least on this drive, the factor was 282 wh/m on the outbound leg, 273 wh/m on the return leg, and 277 wh/m overall. I think it is possible that, among the changes wrought by software version 4.3, TM has changed the formula for computing Rated Miles.