Jump to content

Recommended Posts

Posted

I am considering adding a BedRug Classic Bed Liner to my 2023 GMC Sierra, Crew, 4X4, 3500HD, Shortbed.

I found one site showing it fits, and one site showing it does not fit.

Has anyone installed this BedRug in the same truck and can confirm fitment?

Part# #BRC20SBMPK

Thanks!

Below are the sites that show conflicting info....

BedRug

RealTruck

Posted (edited)

I don’t have anything to offer about how well the bed rug fits.  
 

Did you get the factory spray-in bedliner?  For general bed and load protection, as opposed to a liner inside a topper, I’d suggest also considering the OEM rubber mat just for the bottom instead of a bed rug. It’s 3/8 thick, tough as a tire, and fits well. I bought mine through my dealer for $155 (8 foot bed).  That was cheaper than the on line places when shipping was added.  

Edited by Another JR
Posted
On 9/4/2023 at 11:26 PM, Another JR said:

I don’t have anything to offer about how well the bed rug fits.  
 

Did you get the factory spray-in bedliner?  For general bed and load protection, as opposed to a liner inside a topper, I’d suggest also considering the OEM rubber mat just for the bottom instead of a bed rug. It’s 3/8 thick, tough as a tire, and fits well. I bought mine through my dealer for $155 (8 foot bed).  That was cheaper than the on line places when shipping was added.  

I’ll one up this and recommend just going to tractor supply or a farm store like fleet farm and picking up a horse stall mat. They are very thick, over 5/8” and insanely tough you will never damage it. They are 4’x6’ so there is a bit of uncovered area but not ever going to be an issue and they are 39.99. 
 

it will outlast the truck. Close to 100lbs

Posted (edited)
On 9/4/2023 at 7:07 PM, SoCal Angler said:

I am considering adding a BedRug Classic Bed Liner to my 2023 GMC Sierra, Crew, 4X4, 3500HD, Shortbed.

I found one site showing it fits, and one site showing it does not fit.

Has anyone installed this BedRug in the same truck and can confirm fitment?

Part# #BRC20SBMPK

Thanks!

Below are the sites that show conflicting info....

BedRug

RealTruck

 

I get the part number BRI-BRC20SBMPK off both sites. They are the same company art the end of the day so im sure the info is good. If you have the factory spray in make sure you get the adhesion kit.

 

I have a bed rug in my 2024 with an 8' bed and mp tailagte. It fits really well and i am super happy with it.

Edited by nitro882
Posted

I have one, fits great.  Nice option if you're not really throwing alot of nasty stuff in back.  if so, it'd stick with bed liner and thick rubber mat.

  • Like 1
Posted

This is my 3rd or 4th one in different trucks, really love them super easy on the knees for an old man Lol. Just watch they will melt really easy, took a while to figure what was going on but that polished stainless on my horse trailer gooseneck front acks like a magnifying glass.

  • Like 1

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 2,066 Guests (See full list)

  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...