Jump to content
SAU Community

FS: Damaged R33 GTS-t (black)

Pounce
 Share

Recommended Posts

Pounce Contributor

Pounce

Posted
Posted

Hit a pole from the front, everything is in excellent condition except for the front right part of the car. Car has done 103,000 and was in excellent condition before the crash, and I had just installed an exeedy HD clutch, (only 50kms old) :- (

Please pm me if your interested in the entire car: (melbourne buyers only) thankyou)

Repairable

Looking for around $8000

Mob: 0422119323

Link to comment
https://www.sau.com.au/forums/topic/35817-fs-damaged-r33-gts-t-black/
Share on other sites
urbanoperations Proficient

urbanoperations

Posted
Posted

looks like it needs alot of work if you were to repair it. prob cost 4-6K to repair it.. considering the parts for these things are not cheap... oh well good luck with the sale dude...

urbanoperations Proficient

urbanoperations

Posted
Posted

you would really need to weld/panelbeat a whole right hand front section onto the car.. that front it bent to the shithouse.. if you can find a straight halfcut you would prob be ok n shit....

whats the lowest you will go ???

sewid Grand Master

sewid

Posted
Posted

Just from those photos its impossible to tell if its repairable.

Did the crash extend past the strut tower. Is it bent up behind the strut?

Are the two rails that are at the front under the engine where the cross member bolts onto the chassis straight?

If its straight then urbanoperations is right, a straight front-cut would be required. You can simply drill out the inner guard panels spot welds and weld on a new front quarter inner guard panel and voila. straight again.

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


  • Similar Content

  • Latest Posts

    • GTSBoy
      Looking for someone with a R34 front bar

      By GTSBoy · Posted

      That looks good, but I think you're going to need much beefier side skirts now.
    • GTSBoy
      Most women will agree that parking is the most taxing part of driving

      By GTSBoy · Posted

      They are daft and there's a reason it never caught on. Steering feel? We don't need no stinking steering feel!
    • GTSBoy
      new 1.5 LSD issues/concerns

      By GTSBoy · Posted

      I gotta pull you up on this. It's driving me crazy. A shutter is something that closes, like over a window or in a cmera. The word you want is shudder. That LSD is clearly f**ked. Take it to a diff shop and get it disassembled and examined by an expert. YOu might have plates welded together or something equally crazy.
    • GTSBoy
      M35 Brake caliper replacement

      By GTSBoy · Posted

      Define "starting to fail". Wy not just rebuild them?
    • GTSBoy
      S1 rb25/s14 starting problem

      By GTSBoy · Posted

      Check the Nistune doco. There are a few assumptions being made here that might not be valid. I will list the things that occur to me: Base map. Base map for what? Base map for Z32? Then the cranking pulse width is probably wrong for an RB25. The extra 500cc of capacity might well be enough to prevent it from catching. Base map for RB25? I don't think you can load one of those into a Z32. You have to just make the settings correct for an RB25 in the Z32 base map. That is either K or the TIM to get the pulsewidth right. Loom. You bought a loom for an RB. And you plugged it into a Z32 ECU. Did you make sure that any iwre differences were swapped. From memory, there's at least a couple. And as per the others, I would suggest making sure that the fuel pressure is correct while cranking and that the injectors are actually flowing as expected. They really must come out and go on the bench, unless you do find that you have messed up as per above points. I would also suggest watching in Nistune to make sure that everything is reading correctly. That the correct binary flags are raised at the right time (like the crank signal), that there's no stupid values in K or TIM. That you have not got mismatched firmware for the ECU and/or a wrong image loaded.
×
×
  • Create New...