Jump to content
SAU Community

Recommended Posts

A few months ago I purchased an R33 rolling shell and have been working on restoring it. After some bodywork and checks, I've been able to identify it as a 1994 Nissan Skyline R33 GTS-25T Type M, and found out it was imported into Australia back in 2005 by a previous owner. I found the dashboard and gauge cluster were Nismo, and just assumed the previous owner had put them in for some reason. However, I recently discovered that they had made GTS-25T Type Ms in Nismo spec, something I hadn't known before. I want to verify, so does anyone know of any other indenfiers or defining features that can confirm whether or not its a Nismo? Note: No engine, transmission, exhaust, spoiler, or bodykit. All had been removed when I purchased it. 

Link to comment
https://www.sau.com.au/forums/topic/483764-identifying-nismo-gts-25t/
Share on other sites

On 14/06/2022 at 4:32 PM, Duncan said:

I am reasonably sure there was no "nismo" r33 gtst, what information did you have on such a beast? If you check your vin in FAST it might tell you if there is something special

I'd found these while doing research on the gauge cluster 

images (1).jpeg

116652764_10158910177877112_761590868198701898_n.jpg

As others have mentioned it's most likely the Nismo package option.

I do remember many years ago there was a guy on this forum who owned a Nismo optioned gunmetal grey series 1. it was a Nismo pre-production concept car which was set to be a GTS25t equivalent of the 400R. it was pulled from the assembly line and never made it. it was only discovered from official nissan marketing material left in the boot.

On 14/06/2022 at 10:12 PM, dyl33 said:

That nismo wing is filthy.

Well, let's just say it was "period correct". You would have been the coolest person in the carpark under the freeway in 1995

  • Like 2
On 14/06/2022 at 10:23 PM, mlr said:

I new I seen something somewhere 

Build this, call it the long lost number 4

 

 

 

On 15/06/2022 at 6:15 AM, Duncan said:

Well, let's just say it was "period correct". You would have been the coolest person in the carpark under the freeway in 1995

So was this so called 2500R actually a thing ? As in did this car infact come from Omori ?

On 6/14/2022 at 4:41 PM, BK said:

 

So was this so called 2500R actually a thing ? As in did this car infact come from Omori ?

It's maybe plausible in some regards, but the pictures show some pretty obvious modifications that wouldn't have been how Nismo does things. The missing fan shroud is a weird one.

On 15/06/2022 at 9:41 AM, BK said:

So was this so called 2500R actually a thing

yeah, saw it myself in real life. Was in Sydney many years ago, no idea where it went.

 

OP, you can search your VIN in gtr-registry.com and see what comes up. But you will find it's a regular GTS25t with some Nismo aftermarket parts (fairly common).

 

On 15/06/2022 at 11:38 AM, niZmO_Man said:

yeah, saw it myself in real life. Was in Sydney many years ago, no idea where it went.

 

OP, you can search your VIN in gtr-registry.com and see what comes up. But you will find it's a regular GTS25t with some Nismo aftermarket parts (fairly common).

Wow - just read the whole thread on that so called 2500R prototype. I get it is a real car, but it didn't actually go back to Nismo for anything did it ?

What a really, really shit thread to read... so confusing and contradictory on the claims made.

On 15/06/2022 at 1:24 PM, BK said:

Wow - just read the whole thread on that so called 2500R prototype. I get it is a real car, but it didn't actually go back to Nismo for anything did it ?

No idea, very good point. It was a good dream though hehe.

Yeah, seems the whole Nismo thing was just a kit. Not too disappointed, still my dream car either way, and the gauge cluster is sweet. I have fallen in love with the idea of a GTS-25T Type M Nismo though, so I might pursue a Nismo-inspired build! Chassis no. is ECR33-017724 if anyone was curious. 

20220614_171045.jpg

20220614_171047.jpg

4b25b06928432efb25162a9ac44c4146.jpg

  • Like 1
On 15/06/2022 at 5:35 PM, GTSBoy said:

Imagine all that love and attention paid to a car that actually looks good. Like a 32 or a 34?

While I disagree with your implication that the R33 looks bad, perhaps this R34 GTT Nismo kit tickles your fancy? I find the wing particularly beautiful for the car 

RDT_20220615_1814555871650123261301206.jpg

image_5092b26c-d6fe-4c8b-b114-72fbf9edb24e_1024x1024.jpg

10286658_201422520137.jpg

Oh no. That R34 wing is dreadful. Looks like it belongs on a Honda. The whole back of the kit is bad actually. Only the front is OK.

I belong to the "R33s are boats that look like a Maxima aggressively rear ended a Magna" camp. The profile of the car is poor. The length between the back edge of the door and the rear wheel arch is just too long on a 33. The front is bland in a Magnaesque way and the rear is just f**ked up.

The R32 maintains the correct proportions from the cars that created the look (ie, the early Mustangs, and to an extent the earliest Skylines) that sort of survived in the 70s Skylines but definitely was solidly in the design language of the 80s Skylines. The R32s only blemish is really the front end of the bonnet. But that can be changed.

The R34 brought back the correct profile and proportions. It was actually confrontingly square when it first came out, but that soon passed. The only blemish is the slightly incorrect taillights, but they are much better than the very wrong lights on the 33 (and the lower end and Aussie built 31s). Equal sized stoveplate rear lights are a requirement for a proper Skyline.

You have to slap a lot of tupperware onto a 33 to mask all the problems.

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


  • Similar Content

  • Latest Posts

    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
    • Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
×
×
  • Create New...