Jump to content

What’s it worth?

RonaldA
 Share

Recommended Posts

RonaldA Enthusiast

RonaldA

Posted
Posted

So I’ve got a 2020 Silverado 3500 LT. Z71 package, 6.6 gas motor. 4100 miles. White in color, 5th wheel package, truck is of course excellent. Thinking I’m wanting to order a 2022 3500 LTZ. Dealer really wants my truck on trade, but told me honestly I should sell my truck myself as I “ should” be able to get 50,000. He of course couldn’t give me that. Seeing as there appears to be a shortage on this model, how hard will it be to get 50?

gSwift Enthusiast

gSwift

Posted
Posted

I just sold my 2500 AT4 Duramax with 7800 miles for 73k... $5k more than i paid for it but I did have about $3700 in the leveling kit and 37's.

 

The market is pretty strong if you're patient. I listed mine on eBay and it sold in about 3 weeks

Thankful Enthusiast

Thankful

Posted
Posted

Find another dealer!  Last month, I got $63,600 trade in for my 2020 GMC Sierra HD Denali with 11,351 miles and diesel engine for a new 2021 model.  KBB shows the median trade in value for your 2020 with a gas engine to be right at $50,000.

2020 Chevy.JPG

maynard9089 Enthusiast

maynard9089

Posted
Posted

I traded in a 2020 Denali gas for an identical 2021 Denali gas.  I am a GM employee so I get employee pricing but the dealer priced my trade for more than I paid for the 21 and sold it withing a couple days.  If you are looking for a 2022 you will be waiting another 7 months or so though and the market may change by then.

 

Dunn Senior Enthusiast

Dunn

Posted
Posted (edited)

yeah HD trucks are slim pickings.......thought about trading mine as well, similar to yours, but i dont have 4wd.....only issue is we dont get tax credit on trades and i have to pay TTL again on new truck....ugh!

Edited by Dunn

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...