Who we are
OILSPECguide.com is a reference website built to help people understand lubricant specifications—not guess them.
We are part of the StrongMocha News Group. A number of experts from the StrongMocha News Group have moved their work to OILSPECguide.com to build this new site as a dedicated, tool-first “spec decoder” for engine oils, transmission fluids, gear oils, and related automotive fluids.
Our mission
Our mission is simple:
Make lubricant specs understandable, verifiable, and usable—so you can choose the right fluid for the right application with confidence.
That means translating technical labels and approvals into plain language, showing how standards relate to each other, and highlighting where confusion commonly leads to wrong-fluid mistakes.
What this site focuses on
OILSPECguide.com is designed to feel like a trusted reference tool—a blend of “spec encyclopedia + calculators”—with a strong emphasis on clarity and neutrality.
You’ll primarily find:
- Spec Decoder pages explaining standards and categories (API, ACEA, ILSAC, JASO, SAE viscosity grades, DEXRON, and more)
- OEM approval reference pages (e.g., manufacturer approval codes and what they imply)
- Decision-support tools (viscosity/climate helpers, approval lookups, compatibility guardrails)
- Glossary definitions of technical terms (HTHS, SAPS, NOACK, LSPI, and more)
- Myth-busting pages that separate spec reality from marketing language
How we work (Germany/EU)
We primarily operate from Germany / the EU, building the site for a global audience. Our goal is to present information in a way that’s structured, consistent, and easy to verify—especially when specs vary by vehicle, region, and model year.
AI transparency: how content is created
To be transparent:
All content on OILSPECguide.com is created by AI.
We use AI to:
- draft structured explanations,
- standardize formatting across hundreds of pages,
- help maintain consistent terminology,
- and support fast updates as specs evolve.
Because AI-generated content can still contain mistakes or omissions, we design our pages to be:
- source-driven (with references where possible),
- versioned (with update notes when changes are made),
- and clear about uncertainty when a topic is not definitive without OEM documentation.
If you spot an error or unclear explanation, we want to improve it—please contact us through the site’s contact options.
What we are not
OILSPECguide.com is not:
- an OEM or an official approvals database,
- a replacement for your owner’s manual or service documentation,
- a place for brand hype, vague “meets/exceeds” claims without context, or unverified assertions.
Our role is to help you understand what the specs mean, what they apply to, and what you should double-check before deciding.