davidwhodge
I’m not rejecting the claims in the article, but they sure are pretty surprising. Two ideas that seem far fetched but more likely to me:
1. Some intelligence agency running voice recognition on YouTube videos. 2. Parallel construction, where he was actually caught via another source (like a tip) and they decided to say they detected via YouTube to obscure the true source.
In my data right now I see a few examples of an $80 purchase match to $56 in proceeds (70%) matched to $56 of a refund.
I can't say I think the 30% fee is appropriate anymore, but this particular case being made about refunds does not appear to be accurate for me at least.
What happens in reality is developers either capitulate and / or sneakily separately contact their users and get them to pay through another payment processor.
From what I've seen in forums and user groups, etc, owners tend to just break things down by major feature. AP1 / AP2 / AP3, or I have X type of wheel, or I don't have the retractible roof, but there are obviously so many other changes that aren't easy to detect
(Since the data is smoothed, an outlier datapoint could influence speeds 2mph in each direction)
My guess is it's often cold enough for the battery to need to warm up to be efficient, but not cold enough to make it worth it to turn on the battery heater. (Your point still holds in that case)
A piece of data I happen to remember, far fewer than 10% of supercharges have the battery heater on for any period of time at all.
the reason for the cutoff is that because it's pretty hard to have a trip with an AVERAGE speed above 80mpg. It's very rare in my large dataset.
As a bit of anecdata here: Parking inside vs. outside seems to have a big affect. A slightly chilly garage vs. a cold soak outdoors understandably are quite different.
While I love sentry mode and think it's a great feature, it keeps the electronics awake. In some cases this can cause double digit per day mileage drain. Tesla has clearly been working on this though, as the numbers have improved.
My general takeaway is to see the EPA range as a useful, albeit unrealistic, indicator. Essentially nobody gets the EPA range, either because they choose not to go the speed limit, they accelerate harder than the EPA test factored in, or the vehicles drain some juice while parked.
The data: For the hundreds of Nikola trips with an average speed of 60 mph, the actual MPGe was about 102. Once you get up to a 75 MPH average trip speed, the MPGe drops to 94. And by 80 MPH the MPGe drops to 77. (avg over all Tesla types)
As a bit of "anecdata", I've driven trips where I hit my range on the nose, just to show I could, but the driving is less fun and I was going slower than traffic. I don't drive that way anymore.
What's most striking to me as someone who has heard over and over again about how air resistance is a X^2 property, is the extent to which short (and presumably slow) trips punch above their weight in terms of range consumed per mile. From what I can tell, the actual cost here is the fixed cost of booting up some systems and electronics, and the variable costs of running them over fewer miles can make the MPGe drop. Starting and continuing to run the AC adds up!
edit: have had some people ask. The app can be found at https://download.nikolaapp.com
I can also post data / graphs or make a blog post about that if people have more requests. Let me know what you'd like to see!
Our acquisition actually ended up with the spirit of our product living on in a way that I am proud of.
At Embark, we innovated by taking a regionally nuanced and tailored transit App and giving it scale. When Embark operated from 2008 to 2013, there were small bespoke apps and there were larger more generic experiences (like Google) and we filled a void in between.
Apple's approach was quite similar. Like Embark, Apple Maps Transit has a more regionally tailored experience than many bespoke transit Apps out there, but they're also able to bring it to scale. It's now at a scale we never got close to reaching at Embark.
If you're curious, Apple talks about their city-by-city approach in this WWDC video. https://developer.apple.com/videos/play/wwdc2016/241/
Also, while it sounds silly, disabling copy doesn't mean a user can't type the PW somewhere else and paste it in. I've totally done that before and suspect it's not super uncommon.