-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
So this is freaking me out a little...
I camped out, was the very first reservation at the Denver store in the Mountain Time Zone and have two really high numbers!
3/31 @ 9:55am (I was let in early to take a picture as the first person)
#496xxx
#496xxx
Others who placed multiple orders reported their numbers are higher up, around 49XXXX, like yours.
Highly unlikely. There's an infinite number of numbers...so there's no need to mess up the data and attempt to re-use unique IDs. Few sane programmers would go through the trouble of doing this.
Most likely, the outliers are due to mistakes in recollection or data entry errors.
everman
Member
I have two friends I was in line with that were the third and fourth people in Mountain: #379xxx for both.
As an aside, I was first in line in Mountain and have two at #496xxx...?!?
Of the 191 responses for Instore between 10am EST and 10:30pm EST on 3/31 (Hours to order before Online opened)
East Coast - 70 (37%)
Central - 23 (12%)
Mountain - 12 (6%)
West Coast - 48 (25%)
Rest Of World - 38 (20%)
Total Orders Based on 50,000 orders during that time
East Coast - 18,325
Central - 6,021
Mountain - 3,141
West Coast - 12,565 (Seems low)
Rest Of World - 9,948
*Based on Time Zones
East Coast - 70 (37%)
Central - 23 (12%)
Mountain - 12 (6%)
West Coast - 48 (25%)
Rest Of World - 38 (20%)
Total Orders Based on 50,000 orders during that time
East Coast - 18,325
Central - 6,021
Mountain - 3,141
West Coast - 12,565 (Seems low)
Rest Of World - 9,948
*Based on Time Zones
Ideally you'd convert them all to a single zone, like GMT/UTC. And you're right it EDT should have been used from the beginning not EST. My mistake!
MassModel3
Member
Prior owner here. Reserved the 3 at around 10:12 to 10:15 AM Eastern time on 3/31. ReservationID is 371xxx.
Prior ownership doesn't appear to be a factor in these numbers, just sequence numbers. Position in the "configure your Model 3" queue or the delivery date queue will be based on numerous other factors, though. But this is a fun thing to look at just to get an idea of where we stand compared to each other in the "here's my $1,000" line-up.
Prior ownership doesn't appear to be a factor in these numbers, just sequence numbers. Position in the "configure your Model 3" queue or the delivery date queue will be based on numerous other factors, though. But this is a fun thing to look at just to get an idea of where we stand compared to each other in the "here's my $1,000" line-up.
alseTrick
Active Member
No reason for a sad face. You will be getting the car befor millions of other people, just after it gets through its first revisin fixing the most outstanding problems.
The strong correlation - the "pattern" has already been established beyond doubt. Have you not read this thread? What people do with it is another story.
Anyway you can get a general idea of reservations made over time using this data. No tea leaves - this is a useful thing.
You can get a very rough idea of likely order position that will ultimately be highly dependent on Tesla's internal production strategy. Some of this strategy has been announced in the form of customer region and prior-owner status prioritization. Production scheduling and delivery times may then be dependent on vehicle configuration.
Krugerrand
Meow
everman
Member
I wonder if the reason the folks with two reservations have a drastically higher number is when Tesla went through and scrubbed the DB and removed all the reservations that had way more than two reservations, like Anton who went and ordered 20 of them. Then when the legitimate two-pack reservations were allowed to stay, they had new numbers...?
When does the 496xxx timeframe fit? I am not sure when Anton actually placed his reservations, but his article came out on 4/29.
http://seekingalpha.com/article/3969630-put-20-refundable-deposits-tesla-model-3
When does the 496xxx timeframe fit? I am not sure when Anton actually placed his reservations, but his article came out on 4/29.
http://seekingalpha.com/article/3969630-put-20-refundable-deposits-tesla-model-3
I get that, but disagree. I try to program as efficiently as possible since my experience is with physics simulations that take days to finish meaning memory allocation and storing usefull data as compact as possible a priority. The ID's are ''small'' numbers though, but I still believe it to be good practice to do so. I see several advantages in this case.
Furthermore it explains the outliers in the last part of the graph where some people made a reservation days after the reveal when the reservation rate was far slower and easy to keep up with by a server (thus unlikely for it to be an overflow event) and the assigned ID is actually a far lower number than what they should have gotten. By your proposed method those lower numbers should have been uniqually assigned already, thus making the ID no longer unique. Based on the time of reservation Tesla could fix the ID, but why haven't they done so? In case of an overflow or some other problem the system should default to assign a far larger number than the highest assigned so far, not some random lower number that's already taken.
Did Tesla hide it? Just did a search for common_reservation_id and its not there
I think they must have because I'm not seeing it either
ummgood
Member
Try just reservation_idDid Tesla hide it? Just did a search for common_reservation_id and its not there
Similar threads
- Article
