Jump to content
SAU Community

Gtr-registry.com: Now All R32/r33/r34 Gtr Details - Full Registry - Submit Photos/info


Recommended Posts

Its good to see I'm not a rare sufferer from the 32-33-34 GTR Obsession disease.

Great stuff - just one question, why hasnt this been stickied yet?

Yes but surely there's some difference between

LMAA

LMZG

LMZH

LTAA

LTZG

Might these 4 digit codes be time period sensitive?

For example the BCNR33 N1s have either...

--C-- for early ones and then...

--N-- for later ones??

Might these 4 digit codes be time period sensitive?

For example the BCNR33 N1s have either...

--C-- for early ones and then...

--N-- for later ones??

Nah they are all in series 1 dispersed throughout :)

  • 2 weeks later...
  • 1 month later...
ANNOUNCEMENT: GTR-Registry.com is proud to announce the expansion of the "Registry" aspect of the website. Some of you will have seen that not only are there readers rides cars being added to the Registry (be sure to check them out), I have also added a whole bunch of cars in the R32, R33, R34 range.


At the moment I have been limiting the uploads to:

R34 - M-Spec, N1s, nur, midnight purple 2/3, and anything else that is rare.

R33 - N1.

R32 - N1.


Many of these came from auction results from the last couple of years. I've also been fortunate to have received many donations, from 2 people in particular. Jamie Noyz provided many of the midnight purple 3 cars, and some others, and an anonymous donor provided most of the N1 cars you will see on the site. Thanks very much to them.


I'm now seeking photos for other cars that fit the criteria above (in the future I will add in more but I don't want to get too flooded at the moment).


To help submit photos, please make sure it meets any of the following criteria:

a) You own the car.

b) It was advertised for sale with the VIN available.

c) The VIN was clearly displayed in an article (sample) or it was previously made public (ie in build threads, registry threads etc.)


Please try and provide a source, if possible/available. If you wish to remain anonymous be sure to let me know.


To let me know, either reply here, message me, tag me, etc and I will take it from there. Lastly, if anyone knows any sites with historical records (webpage/facebook page etc) of auctions please let me know.


Hope you find this useful and I have plenty more stuff coming to the site in the future.


Cheers,


Mark


PS: Like my FaceBook Page for lots more updates on GTRs.
  • Like 2
  • 3 weeks later...

GTR-Registry.com is proud to announce the release of the complete Nissan Skyline R34 Catalog, covering BNR34, ER34, ENR34 and HR34. This consists of a total of 67,261 cars of which we have complete records of 67,122 (99.79%).

You can find the information in the following links:

R34 Colours: http://gtr-registry.com/en-r34-colours.php
R34 Production: http://gtr-registry.com/en-r34-production.php

BNR34 VIN Table: http://gtr-registry.com/en-bnr34-vin-table.php (GTR, V-Spec, M-Spec etc)
ER34 VIN Table: http://gtr-registry.com/en-er34-vin-table.php (25GT, 25GT Turbo (GTT), GT-V)
ENR34 VIN Table: http://gtr-registry.com/en-er34-vin-table.php (25GT FOUR)
HR34 VIN Table: http://gtr-registry.com/en-er34-vin-table.php (20GT)

Plus all of the subvariants that exist.

There are some really interesting things to find.

In the ER34 range, the most interesting is the new country code of BR. At this time we believe BR is for Brunei but this is not certain. We're looking for proof so if you know something then please let me know. As in the BNR34 range, there are also some cars for the New Zealand market and Hong Kong market. There aren't any for Singapore. There is also 35 cars with the paint code of 3W9 which are police cars. There's actually 25 consecutive VIN from ER34-201551 > ER34-201575 of police cars.

The HR34 range sees some cars heading off to Brunei as well. There's no export cars in the ENR34 range.

On the colours page I've separated out the different body styles and transmissions for a greater breakdown.

The rarest colours in the R34 range goes to:
3W9 - 35 - Black #?/White #?
EY0 - 131 - Silica Breath
LX0 - 198 - Midnight Purple III
BV5 - 311 - Dark Metal Blue

I hope you guys find this information useful, as I have spent a lot of time obtaining and putting it all together. I would like to also acknowledge the help of several people in particular as this project would not have been possible without them:
Steve: Database construction 
Kristian Appelt at Iron Chef Imports: Tons of translations and advice.
Brendon: Original website and database design
As well as some others who helped in smaller ways.

Please like GTR-Registry.com on FaceBook for updates! Feedback, suggestions and lawsuits are most welcome!

Regards,

Mark Dodd

About GTR-Registry.com: GTR-Registry.com is the world's leading source of Nissan Skyline GTR and Nissan Stagea production information, which has led to the discovery of the true build numbers of many different versions which were previously inaccurate. The website currently stores the records of 319,845 cars. When using numbers or information obtained from the site please reference GTR-Registry.com.

  • Like 2
  • 4 weeks later...

Hey,

Register at http://gtr-registry.com/forum/ and then make a thread with some photos and info in the R32 section and I will do the rest :)

cheers

  • 3 weeks later...

Hey,

New Page: http://gtr-registry.com/en-bnr34-specs.php BNR34 Specifications with over 150 photos. List of options and changes between different models and types.

Mostly official Nissan photos are used except when unavailable.

Some photos provided by Terry Tung-Yep, Rajeel Deo and narface from gtr.co.uk.

Cheers

  • Like 1
13 hours ago, sin- said:

Hey,

New Page: http://gtr-registry.com/en-bnr34-specs.php BNR34 Specifications with over 150 photos. List of options and changes between different models and types.

Mostly official Nissan photos are used except when unavailable.

Some photos provided by Terry Tung-Yep, Rajeel Deo and narface from gtr.co.uk.

Cheers

Brilliant Mark!

Thank you for your cross referencing, your collating and of course, your dedication!!!

  • 2 months later...
  • 3 weeks later...
  • 1 month later...

Announcing the release of the entire R32 Catalog, covering HCR32 Series 1, HCR32 Series 2 (split due to the large number of cars), HNR32, ECR32, ER32, HR32 and FR32, to go with the existing and updated BNR32! Read more here.

Also there was 191 HNR32 Skyline26 produced (RB26DE engine) all in JK0, but not all JK0 HNR32s are Skyline26's.

  • Like 1
  • 7 months later...

IMPORTANT WEBSITE UPDATE: GTR-Registry.com has recently moved to new hosting courtesy of Justin from NismoR34GTR and Assured I.T. What this means is that now the VIN tables will load MUCH faster than with the previous hosting. Massive thank you to Justin who has spent a lot of his time and resources to help improve the site which everyone who uses the website will be able to notice.


SUGGESTIONS & FEEDBACK: If you have any suggestions or feedback for the site (excluding fixing the header design - working on that) then please let me know. If you have any suggesions for cars you'd like to see on the site then let me know.
Cheers, Mark
 

  • 2 years later...

Hi,

We've added a Nismo portal which contains information on 18 different Nismo RB26DETT engines! This portal contains links to all of our Nismo content, which is 66 pages in total.

We've also added a vast amount of new content throughout the rest of the website since the last update here.

Cheers

  • 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



  • Similar Content

  • Latest Posts

    • First up, I wouldn't use PID straight up for boost control. There's also other control techniques that can be implemented. And as I said, and you keep missing the point. It's not the ONE thing, it's the wrapping it up together with everything else in the one system that starts to unravel the problem. It's why there are people who can work in a certain field as a generalist, IE a IT person, and then there are specialists. IE, an SQL database specialist. Sure the IT person can build and run a database, and it'll work, however theyll likely never be as good as a specialist.   So, as said, it's not as simple as you're thinking. And yes, there's a limit to the number of everything's in MCUs, and they run out far to freaking fast when you're designing a complex system, which means you have to make compromises. Add to that, you'll have a limited team working on it, so fixing / tweaking some features means some features are a higher priority than others. Add to that, someone might fix a problem around a certain unrelated feature, and that change due to other complexities in the system design, can now cause a new, unforseen bug in something else.   The whole thing is, as said, sometimes split systems can work as good, and if not better. Plus when there's no need to spend $4k on an all in one solution, to meet the needs of a $200 system, maybe don't just spout off things others have said / you've read. There's a lot of misinformation on the internet, including in translated service manuals, and data sheets. Going and doing, so that you know, is better than stating something you read. Stating something that has been read, is about as useful as an engineering graduate, as all they know is what they've read. And trust me, nearly every engineering graduate is useless in the real world. And add to that, if you don't know this stuff, and just have an opinion, maybe accept what people with experience are telling you as information, and don't keep reciting the exact same thing over and over in response.
    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
×
×
  • Create New...