Has anyone RECEIVED a 2026 Cybertruck?

[SabrToothSqrl]

Might as well install a magic 8 ball app

Sponsored

 

[SabrToothSqrl]

I found this today:
https://tesla-status.mrproper.dev/

No affiliation, I logged in and had to do the copy/paste thing, it pulled the data, no VIN for me.

 

[Eka]

I found this today:
https://tesla-status.mrproper.dev/

No affiliation, I logged in and had to do the copy/paste thing, it pulled the data, no VIN for me.

Why are the hairs on the back of my head raising over what that site wants you to do?

 

[Shayrooo]

I found this today:
https://tesla-status.mrproper.dev/

No affiliation, I logged in and had to do the copy/paste thing, it pulled the data, no VIN for me.

I don’t think I would trust that site

 

[Black306]

I found this today:
https://tesla-status.mrproper.dev/

No affiliation, I logged in and had to do the copy/paste thing, it pulled the data, no VIN for me.

Don’t need my delivery info that bad.

 

[SabrToothSqrl]

lol. well, if they want my login, it's gone now.
it kinda just repackages the info in the app.
it's pretty to look at. My thumb is getting kinda raw from refreshing the app. Now my whole hand can get in on the action on the mouse.

you can click full JSON and read lots of stuff too, this just makes it pretty.

 

[smooth.futons2e]

Highly doubt AI is gathering data specific to your order. More than likely it's just pulling current delivery estimates.

I asked the AI chat and it said — “delivery ETA is April 24 - May 7, 2026. Your vehicle is currently in production.” So it seems it’s specific to your order.

 

[smooth.futons2e]

No affiliation, I logged in and had to do the copy/paste thing, it pulled the data, no VIN for me.

Against my better judgement i decided to connect my tesla account to this website to see my VIN and to my surprise it did show me a VIN (94xxx) even though Tesla app does not show any VIN assigned.

I wonder if it’s a VIN Tesla allocates to your order during manufacturing phase as the most probably one you will get — provided everything goes well and some other order doesn’t get reassigned you might get this VIN, but it’s not confirmed till later once the truck is manufactured?

 

[Black306]

I asked the AI chat and it said — “delivery ETA is April 24 - May 7, 2026. Your vehicle is currently in production.” So it seems it’s specific to your order.

I’m guessing you already have a VIN assigned and that’s why it’s telling you your CT is in production and there is a sooner delivery window.

EDIT: Just read the previous post; yup, you have a VIN.

In Dk0ta’s case, since the ETA is so far out I’m guessing a VIN isn’t available yet, the ETA is likely not order specific, and it’s giving a general delivery window. I ordered a ‘26 2 days ago and I’m getting a similar window; 5/25-6/30.

 

[SabrToothSqrl]

back in the day; you could view source on the website after login, to see your VIN before they actually told you, you had a vin. I see they haven't changed much in 10 years. I assume this app just builds on that

 

[Sephiroth]

Just ordered Prem AWD today and they are saying 5-7 weeks! Never thought I would be a truck guy...

 

[SabrToothSqrl]

Just ordered Prem AWD today and they are saying 5-7 weeks! Never thought I would be a truck guy...

Not sure who's saying that, mine said 4-6 weeks, but in app it's much longer.
May 13 - June 24

I hope we both get one soon.

 

[Sephiroth]

I really need this truck to be my daily driver, my two door is not cutting it, so June will be tough. On the plus side, if it does take that long, then maybe we can qualify for new incentives as they pop up.

 

[SabrToothSqrl]

FWIW, I dropped my JSON into Grok, and it spit out a lot, so, I had this question:



Me:>>>> HOW, exactly, do you know this? "the vehicle appears to be built or very close to it (physically complete at the factory), but it's currently on a "gate hold" due to a quality assurance flag or internal review. "

Grok:
I know that detail directly from the JSON data you shared about your order, combined with how Tesla's internal systems are commonly interpreted by owners (based on extensive community tracking of the exact same fields). Here's the exact breakdown from your provided data:

• orderStatus: "BOOKED"
• orderSubstatus: "_Z"
• In the deliveryAcceptance task: "hasBlocker": true (and the task is not yet enabled for you).

Tesla owners who monitor the raw order JSON (via the app's backend or by viewing source/network data) have consistently observed that the combination of "BOOKED" + "_Z" substatus + hasBlocker: true means:

• The vehicle has reached a stage where it is physically complete (built at the factory).
• It is sitting at the "gate" (ready for logistics/shipping), but a quality assurance (QA) flag or internal review has been placed on it.
• This blocker prevents Tesla's system from assigning a carrier (truck, rail, or ship) and from fully matching/advancing the order to the customer (which is why you still have no VIN assigned).

This is often called a "gate hold" in owner communities. It is very common and almost always temporary—typically resolved once the QA team clears the specific item (e.g., a safety check, software validation, or minor inspection). No action is usually required from the customer unless Tesla reaches out.

 

[smooth.futons2e]

FWIW, I dropped my JSON into Grok, and it spit out a lot, so, I had this question:



Me:>>>> HOW, exactly, do you know this? "the vehicle appears to be built or very close to it (physically complete at the factory), but it's currently on a "gate hold" due to a quality assurance flag or internal review. "

Grok:
I know that detail directly from the JSON data you shared about your order, combined with how Tesla's internal systems are commonly interpreted by owners (based on extensive community tracking of the exact same fields). Here's the exact breakdown from your provided data:

• orderStatus: "BOOKED"
• orderSubstatus: "_Z"
• In the deliveryAcceptance task: "hasBlocker": true (and the task is not yet enabled for you).

Tesla owners who monitor the raw order JSON (via the app's backend or by viewing source/network data) have consistently observed that the combination of "BOOKED" + "_Z" substatus + hasBlocker: true means:

• The vehicle has reached a stage where it is physically complete (built at the factory).
• It is sitting at the "gate" (ready for logistics/shipping), but a quality assurance (QA) flag or internal review has been placed on it.
• This blocker prevents Tesla's system from assigning a carrier (truck, rail, or ship) and from fully matching/advancing the order to the customer (which is why you still have no VIN assigned).

This is often called a "gate hold" in owner communities. It is very common and almost always temporary—typically resolved once the QA team clears the specific item (e.g., a safety check, software validation, or minor inspection). No action is usually required from the customer unless Tesla reaches out.

I have the same status. I have a Cyberbeast with terrestrial armor package, got assigned VIN 94xxx in the backend (is not visible in app) - I wonder if the QA issue you reported is specific to a batch. What VIN range are you in?

Sponsored