Japan Vehicle Data
Japanese-language primary sources, aggregated for buyers outside Japan

Method: How We Aggregate Japanese Owner Maintenance Logs — And What It Gets Wrong

Published 2026-07-31

This page documents the method behind our per-chassis analyses, including a significant correction we made to it on 2026-07-31. Every article using this method links here.

If you only read one thing: our first two analyses reported “zero rust posts.” That was an artifact of how we sampled, not a fact about the cars. Both articles have been corrected. The diagnosis is below, because how a method fails is more useful than a claim that it doesn’t.


The source

Minkara (みんカラ), operated by Carview, is Japan’s largest car owner community. Its 整備手帳 (seibi techō, “maintenance logbook”) section holds user-posted repair and maintenance records with step-by-step photos — over 126,000 for the Jimny nameplate alone.

This is a body of first-hand mechanical evidence about Japanese-market cars that is effectively invisible to English-speaking buyers. That’s the whole reason this project exists.

URL structure

https://minkara.carview.co.jp/car/<make>/<model>/note/?bi=<category>&mg=<chassis>&pn=<page>
ParameterMeaning
mg=Chassis/model filter. JB23W 3.5432 · JB64W 3.13263 · JA12/JA22 3.5431 · S15 3.2245 · S14 3.2249 · S13 3.2248
bi=Category. 1 running gear · 2 audio · 3 security · 4 exterior · 5 reinforcement · 6 interior · 7 engine bay · 8 electrical · 9 car care · 10 accessories · 11 inspection · 12 other
pn=Page number. ~9 posts per page.

Published here because readers should be able to check our work and run their own searches.


Mode 1: Chronological sampling (what we did first)

Take the newest N pages per category, classify each post title, count clusters.

What it’s good for: establishing what owners routinely deal with, and surfacing failure patterns nobody has named in English. It found the JB23’s ISCV and the S15’s AAC valve — the same idle-control component under two manufacturers’ names, absent from every English guide we checked.

What it is structurally bad at — and this is the correction:

A newest-first sample counts posting events, not failure incidence. Those diverge badly:

So a rare-but-severe job is crowded out of a chronological sample by definition — no matter how important it is. Our JB23 and S15 analyses each returned zero rust posts from 18 exterior entries. We flagged this as suspicious and offered three hypotheses. We were right to be suspicious and wrong about the reason: it wasn’t shop-work bias or category placement. It was frequency.

Read every frequency table we publish with this in mind: rank reflects how often owners post about something, which tracks how often it needs doing — not how much it matters.


Mode 2: Term search (what we added)

Search for the failure term directly, scoped to the chassis, rather than reading category listings.

One methodological note worth passing on: Minkara’s own internal search performed poorly for this. Searching JB23 錆 on-site returned a handful of loosely related posts and displayed hit counts of “(0)” across all categories. An external site-scoped search (site:minkara.carview.co.jp plus the chassis and failure terms) returned ten dense, directly relevant repair logs immediately. Use the latter.

Japanese rust terms that work: (sabi, rust) · サビ (katakana variant) · 腐食 (fushoku, corrosion) · 穴あき (ana-aki, holed through) · 板金 (bankin, panel/body work) · 防錆 (bōsei, rustproofing) · 錆転換剤 (rust converter).

What Mode 2 immediately found

JB23 Jimny — ten detailed frame-corrosion repair logs, including one owner’s summary titled jb23 錆びやすい所一覧 (“list of places JB23s rust”), plus welded frame patch repairs, floor pan and body mount replacement, and ladder-frame treatment.

S15 Silvia — ten rust repair logs including roof rust-through, C-pillar corrosion documented across a four-part series, cowl-top, rear bumper lower section, front hood ridge, and rear suspension member pin corrosion.

That last one matters: our S15 analysis found a five-post rear subframe cluster and hypothesised that rust was driving it, while noting we couldn’t prove it from titles. Mode 2 confirms the link.


What Mode 2 found that Mode 1 could never have

These are substantive buying findings, not just methodology.

JB23 — where they actually rot

From owners’ own inspection summaries:

The recurring inspection technique in these logs is a hammer tap, not a visual check. Several owners describe tapping a “slightly suspicious” area and going straight through it.

And the finding with the biggest buying consequence: one owner’s regional summary states that a snow-region car at 100,000 km will reliably have something rotted through, while a western-Japan car can be clean underneath at 200,000 km. Salt exposure — coastal and winter de-icing — is repeatedly named as the cause, with one log attributing a nearly-severed body mount to salt rather than off-road use.

We flagged region-of-registration as an untested hypothesis in our S15 article. Owners in Japan already treat it as the dominant variable. If you are choosing between two JB23s, the prefecture it lived in may tell you more than its mileage.

S15 — where they actually rot


Standing limitations

Corrected or not, this method still has boundaries we don’t paper over:

Use both modes together. Mode 1 tells you what owners live with. Mode 2 tells you what kills the car. Neither alone is a picture of the chassis.


Corrections log

2026-07-31 — Rust. JB23 and S15 analyses originally reported zero rust posts from exterior-category sampling and presented three candidate explanations. Term search established that extensive rust documentation exists for both chassis and that the cause was chronological sampling frequency, not any of the three hypotheses offered. Both articles corrected; rust sections rewritten with Mode 2 findings. The original claim and its correction are both retained in those articles rather than quietly edited out.


Not affiliated with Minkara or Carview. Post titles are quoted for research and attributed; we link to source rather than reproducing post content.