Japan Steam Radar Research phase

Japan Steam Radar — Sample Report (Full Version v0.2)

Title: PEAK (AppID 3527290) — Team PEAK / Landfall + Aggro Crab Type: Full sample report. Built to meet the six v0.2 acceptance conditions set by the independent red-team review of v0.1 (2026-11-18). Date of this sample: 2026-11-19 Price point this sample is testing: $49/month (Solo, 1 title) / $99/month (Studio, up to 5 titles) Research note: Research-phase sample. No sales claim is made. Every figure below cites its source and snapshot date. Where a figure is an estimate, the method and its limits are stated next to it. Sections that could not be verified are labelled as such, rather than filled in.

0. What changed from v0.1 — and a correction to the pilot

v0.1 could not publish a direct classification of Japanese reviews. v0.2 is built on a full census, not a sample: all 1,113 Japanese-language Steam reviews for PEAK were retrieved on 2026-11-19 through Valve's official Web API (IUserReviewsService/GetAppReviews, keyless, ¥0) and classified.

Correction that matters (read this before quoting the pilot):

Method note for production: day_range is capped at 365 in this API, except that day_range=0 means "no limit". A full-history pull therefore requires day_range=0 plus cursor pagination (13 calls for PEAK: 12 pages + 1 empty terminator page). Using 365 silently truncates the launch period — for PEAK that would have dropped 689 of 1,113 reviews.

1. At a glance — Japan in the global picture (same-day, same-method snapshot)

All rows below were pulled on 2026-11-19 via the same official API, purchase_type default (Steam purchases), so the rows are comparable.

MetricValueSource / snapshot
Total Steam reviews (all languages)313,072 (296,185 positive / 16,887 negative, 94.6% positive)Steam Web API query_summary, 2026-11-19
Japanese-language reviews1,113 (984 positive / 129 negative in query_summary; 983 / 130 in the fetched census — a 1-review difference, likely a vote changed between calls)Same, 2026-11-19
Japanese share of reviews0.356% (1,113 / 313,072)Calculated from the two rows above
Japanese positive rate88.4% vs 94.6% all-language and 95.6% English (142,425 / 148,912)Same, 2026-11-19
Release / price16 June 2025 / US $7.99; Japan Steam price ¥880; console versions (Switch 2 / PS5 / Xbox Series) released 22–23 Oct 2026 at ¥1,200 (Switch 2) / ¥1,210 (PS5) in JapanSteam store; Japanese guide Game Guide Scout, published 2026-10-29, updated 2026-11-13 (see §4)
Japanese review volume by month (census)Jun 2025: 74 / Jul: 96 / Aug 2025: 336 / Sep: 99 / Oct: 49 / Nov 2025: 145 / Dec: 34 / Jan–Nov 2026: 13–44 per monthFull census, §2

Reading: Japan is 0.356% of review volume, and Japanese reviewers rate PEAK 6.2 points lower than the global average on the same day, by the same method. That gap is now free to see since Valve added language-specific scores in August 2025 — what is not free is why the gap exists, whether it is moving, and what to do about it. That is what §2 answers. The August 2025 spike (336 reviews, 30% of all Japanese reviews ever) coincides with the Mountain Day period covered in v0.1; causation is not claimed.

Category comparison (same method, same day) — is PEAK's Japan share unusual?

Title (AppID)Total reviewsJapanese reviewsJP shareJP positiveAll-language positive
PEAK (3527290)313,0721,1130.356%88.4%94.6%
R.E.P.O. (3241660)350,7981,8040.514%92.6%96.1%
Lethal Company (1966720)412,2896160.149%91.1%97.0%
Content Warning (2881650)73,3131700.232%88.2%93.0%

Reading: PEAK sits in the middle of its co-op category on Japanese share. R.E.P.O. — which only added official Japanese in v0.5.0 on 29 Oct 2026 (see the R.E.P.O. short sample) — already shows a higher Japanese share and a smaller positive-rate gap. A monthly version of this table is the category watch a global dashboard does not sell by language.

2. What Japanese players are actually saying — full census classification

Population: 1,113 Japanese reviews, posted 2025-06-17 to 2026-11-17 (UTC). Stratification: Early window = 2025-06-17 to 2025-11-17 (689 reviews, 88.7% positive in the fetched census). Recent window = 2025-11-18 to 2026-11-17 (424 reviews, 87.7% positive). The split date is the pilot's window boundary, kept so pilot and census can be compared honestly. Counting: Two layers, both keyword-based and reproducible. Strict counts require an explicit word (e.g. 難易度/難しい). Broad counts use a wider keyword set per theme and overlap (one review can count in several themes). Keyword lists are in the production log. These are mention rates, not sentiment scores — a difficulty mention can be praise.

2a. Strict counts (explicit words only)

IndicatorAll 1,113Early 689Recent 424Negative reviews only
Difficulty explicit (難易度/難しい etc.)158 (14.2%)99 (14.4%)59 (13.9%)25 / 130
Deep Forest biome explicit (深き森/深い森)27 (2.4%)8 (1.2%)19 (4.5%)14 / 130
Bug explicit (バグ)38 (3.4%)30 (4.4%)8 (1.9%)11 / 130
Performance narrow (重い/最適化/フリーズ/クラッシュ)22 (2.0%)21 (3.0%)1 (0.2%)11 / 130
"Japanese" explicit (日本語)10 (0.9%)10 (1.5%)0 (0.0%)1 / 130
Pause / save / session explicit28 (2.5%)20 (2.9%)8 (1.9%)4 / 130
No public matchmaking explicit (野良/マッチング)9 (0.8%)6 (0.9%)3 (0.7%)3 / 130
Motion sickness explicit (酔い incl. 画面酔い)18 (1.6%)13 (1.9%)5 (1.2%)2 / 130

2b. Broad themes (overlapping)

ThemeAllEarlyRecent
Co-op / friends mention365 (32.8%)223 (32.4%)142 (33.5%)
Core praise words363 (32.6%)230 (33.4%)133 (31.4%)
Solo mention223 (20.0%)149 (21.6%)74 (17.5%)
Difficulty / biome / balance (broad)201 (18.1%)120 (17.4%)81 (19.1%)
Network / matchmaking (broad)139 (12.5%)96 (13.9%)43 (10.1%)
Session length / time125 (11.2%)74 (10.7%)51 (12.0%)
Bug / performance (broad)103 (9.3%)78 (11.3%)25 (5.9%)
Update / new content mention94 (8.4%)61 (8.9%)33 (7.8%)
Language / UI / settings (broad)35 (3.1%)28 (4.1%)7 (1.7%)

2c. What this proves — and what changed over time

  1. v0.1's implied story was an early-window story. In the early window, bug mentions (4.4% strict, 11.3% broad), performance mentions (3.0% strict) and language mentions (all 10 "日本語" reviews in the whole census) are concentrated. A report written at launch would correctly have said "fix bugs, performance and language defaults first".
  2. That is no longer the centre of Japanese dissatisfaction. In the recent window, strict performance mentions fall to 1 review (0.2%), language mentions fall to zero, and bug mentions halve. What rises is one specific biome: Deep Forest goes from 1.2% to 4.5% of all reviews, and accounts for 11 of 52 recent negative reviews (14 of 130 negatives overall). The Japanese complaint has narrowed from "the game is rough" to "Stage 2's Deep Forest is mis-tuned".
  3. Difficulty itself is not rejection. Difficulty is mentioned at a stable ~14% in both windows, and most short difficulty mentions in positive reviews frame it as the appeal ("even the easiest difficulty is properly hard", §2d). The negative concentration is biome-specific, not difficulty-general. Treating "Japanese players find it too hard" as the takeaway would misdirect a balance patch.
  4. Shared-with-global vs Japan-visible: No-save / session length and no public matchmaking appear in Japanese reviews (2.5% and 0.8% strict) but also dominate the global theme lists (Niklas Notes, §6) — they are common complaints, not Japan-only ones. The Japan-visible signal in this census is the time shift (early tech/language → recent single-biome balance) and the positive-rate gap (§1), neither of which a one-off global theme list shows.

2d. Short quoted examples (Japanese original excerpt + translation)

Quotes are short excerpts from the census, trimmed, with posting date and the reviewer's recommendation. They illustrate the counts above; they are not a substitute for them.

Deep Forest / Stage-2 difficulty (negative):

Difficulty as appeal (positive):

Bug / backpack (early window):

Language default (early window — the complaint class that later disappears):

Session length / no save:

3. The money side — what 0.356% is worth for this title (estimate, method stated)

Red-team condition: give at least one money-side number, with source and method, as the answer to "why pay to watch 0.35%?".

4. Japanese media and community — primary mentions

At least two primary Japanese-language sources, not English summaries of them:

  1. Game Guide Scout (Japanese guide site) — PEAK console / crossplay guide. Published 2026-10-29, updated 2026-11-13. Reports, in Japanese and from the Japanese storefronts: console versions launched 22–23 Oct 2026 with crossplay via room codes, Steam ¥880 / Switch 2 ¥1,200 / PS5 ¥1,210, Japanese available on all platforms, online play requires each platform's subscription, and Steam progress does not carry to console. Why it matters: Japanese discovery for PEAK is now a console + crossplay story, not only a Steam story — a Radar issue that only tracks Steam reviews would miss the channel Japanese newcomers actually arrive through.
  2. Japanese player攻略 on note.com — 東雲奈緒, "PEAK攻略のポイントと難関実績解説" (2025-09-19). A long-form Japanese community guide: six major biomes, Mesa as the then-new biome, daily terrain rotation at 02:00 JST, and achievement breakage after the Mesa update. Why it matters: detailed Japanese攻略 existed and aged quickly as updates landed — the audience already produces its own Japanese information layer; a paid report competes on classification, timing and cross-title comparison, not on basic攻略.
  3. AUTOMATON / Shinjisan (Japanese primary utterance, via AUTOMATON WEST, 2025-08-21). Japanese streamer Shinjisan, quoted in Japanese in the article: 「どのゲームも日本のレビューがほぼダントツで低評価をしていました」 — "Whichever game I checked, Japanese reviews were by far the most negative." The article also cites the 2021–22 user analysis of 262 titles (Japanese negative share materially above the worldwide average). Why it matters: this is the cultural context for PEAK's 88.4% vs 94.6% gap in §1 — and Japanese players themselves are publicly debating whether the habit will cost them future Japanese support.

Not found (recorded honestly): A PEAK-specific news article on Famitsu or 4Gamer was not found in this session's searches. No such article is cited or implied above.

Held from v0.1 (still valid): Mountain Day (11 Aug 2025) — Nijisanji's "Yama no Hi PEAK Summer Festival" with 21 livers, after Japanese support was added in July 2025, followed by PEAK's all-time concurrent peak on 17 Aug 2025 (170,759, Steambase). Timing correlation only; causation not claimed.

5. Forward look — next 90 days in Japan (2026-11-19 to 2027-02-17)

Monthly billing needs a forward reason to exist. These are dated, named windows inside the next 90 days — not generic "Japan is active".

DateWindowWhy it is specific to PEAK / this category
23 Nov 2026Labor Thanksgiving Day (勤労感謝の日), national holidayImmediate long-weekend play window, four days after this report. Co-op sessions need friends free at the same time — holidays are when the "no friends included" friction (§2b, solo 20.0%) temporarily drops.
17 Dec 2026 – 4 Jan 2027Steam Winter Sale 2026 (Valve Steamworks calendar: 17 Dec 2026 – 4 Jan 2027, 10am Pacific)Longest sale of the year (18 days), crossing the Japanese New Year break. This is the first Winter Sale for PEAK's console versions (released Oct 2026) and the first with official Japanese in place from day one of the sale. Discount and Japanese store-copy decisions bind before the sale opens.
1–3 Jan 2027 + 11 Jan 2027New Year holiday period (1 Jan is a Friday, forming a 3-day break) and Coming of Age Day, Mon 11 Jan 2027 (3-day weekend 9–11 Jan; Cabinet Office 2027 holiday list)Two long weekends in eleven days. The 20-year-old cohort Coming of Age Day celebrates is core co-op / VTuber audience age. Creator and social beats timed to global patch dates will miss both if nobody converts them to JST holiday dates.
11 Feb 2027National Foundation Day (建国記念の日), Thursday (Cabinet Office 2027 list)A single mid-week holiday (a Friday off makes a 4-day break). Last dated holiday window inside the 90 days; Emperor's Birthday (23 Feb 2027) falls just outside it.

Sources for dates: Cabinet Office 2027 holiday list as reproduced in multiple 2027 calendar summaries checked 2026-11-19 (1 Jan Fri / 11 Jan Mon / 11 Feb Thu / 23 Feb Tue); Valve Winter Sale dates via Steamworks event documentation as reported by multiple sale trackers checked 2026-11-19.

6. Next moves (maximum 3 — each tied to a section above, each with execution cost)

General advice that could be written without this report's data has been removed, per the red-team condition.

  1. Before the Winter Sale, publish one Japanese-language post that names the Deep Forest problem and what rotation / difficulty options do about it — on the Steam news hub, in Japanese. Tied to: §2a–2c (Deep Forest = 19 recent mentions, 11/52 recent negatives; language complaints are now zero, so a Japanese post will be read as balance communication, not localisation apology). Execution cost: drafting + Japanese translation of a short post (~1,500–2,500 Japanese characters) ≈ 3–5 person-hours of bilingual staff time, or one small outsourced translation job if no bilingual staff exists; posting itself <1 hour. No media spend required.
  2. Set Japanese store and FAQ expectations for solo play and session length before the New Year console influx. Tied to: §2b–2d (solo mentions 20.0%, session-length 11.2%, save requests in both windows; §4 item 1 — console newcomers arrive via Japanese guides that already warn "friends only, no public matchmaking"). State plainly, in Japanese store copy / FAQ: no public matchmaking, typical run length, and what pause support exists in solo. Execution cost: copy edit on existing store / FAQ pages ≈ 2–4 person-hours including translation check; no build work. The cost of not doing it is measurable in the census: expectation-mismatch reviews are the ones that quote session length verbatim.
  3. Pitch one Japanese creator beat for the 9–11 Jan 2027 long weekend, with pitches out in early December — not a Mountain Day repeat. Tied to: §5 (Coming of Age weekend) + v0.1 §3 (the 2025 Mountain Day event proves Japanese creators will play this game when the date is native; §1 shows August is already PEAK's biggest Japanese month, so January is the untested, less crowded window). Execution cost: building a 15–25 name Japanese creator shortlist + Japanese pitch drafting ≈ 6–10 person-hours; keys/build access are marginal cost. Any paid sponsorship is a separate budget decision — this move is the unpaid pitching version only.

7. What you can get free or cheaper — and what you cannot (honest difference table)

NeedFree / cheaper routeWhat it actually gives youWhat it does not give you
"Is Japan rating us lower?"Steam language-specific review scores (free, Valve, since Aug 2025)The score per language. For PEAK today: JP 88.4% vs global 94.6%Why, whether the topics moved, or what to do next
Sales / player estimatesGamalytic (free tier; Starter $25/mo), SteamDB (free)Global units / revenue estimates, concurrent players, country breakdowns at the level those tools modelJapanese review content classification, Japanese media / creator context
Discovery / trend dataGameDiscoverCo Plus ($19/mo)Steam discovery data, weekly trend coverage, communityJapan-specific qualitative reading; it is 2.6× cheaper than Radar Solo and overlaps on everything except the Japanese qualitative layer
DIY readingSteam language filter + machine translation + a general AI assistant (≈¥0–a few dollars of API use)A rough gist of Japanese reviews, if you know which questions to ask and re-ask monthlyA reproducible census classification, a stratified time comparison, quoted evidence you can act on, and someone accountable for re-running it every month
Japanese posts on XManual spot checks (Radar's method)Occasional large, named events (e.g. a festival)Radar does not promise comprehensive X monitoring. Automated X collection is prohibited by X's terms for scraping and, via the official API, is pay-per-post ($0.005/post since Feb 2026) — at category scale it would consume a Solo subscription's revenue by itself. X is a manual auxiliary source only.
Japan Steam Radar (this report)—Full-census Japanese review classification with time stratification and quotes (§2), category comparison by language (§1), Japanese media / community primary sources (§4), a dated 90-day Japanese calendar converted into actions (§5–6)Global quantitative estimates better than Gamalytic's, comprehensive X coverage, or攻略 content Japanese players already produce for free (§4 item 2)

If the three Radar-only rows in the last line are not worth $49/mo to a given studio, the honest recommendation is GameDiscoverCo Plus + the free Steam language score — and this table says so.

8. What this sample proves — and does not prove

Proves:

Does not prove:

9. Production log (cost measurement)

10. v0.2 acceptance checklist (red-team conditions, 2026-11-18)

  1. Direct classification + quotes — Met: §2 (full census 1,113, strict + broad, stratified, quoted excerpts with translations).
  2. Forward calendar ≥3 dated items — Met: §5 (4 windows, named and dated).
  3. Money-side ≥1 number with source + method — Met: §3 (unit range + ¥19M–¥44M gross range, method and limits stated).
  4. Japanese media primary mentions ≥2 — Met: §4 (Game Guide Scout JP, note.com JP攻略, AUTOMATON/Shinjisan JP utterance; Famitsu/4Gamer absence recorded).
  5. Next Moves with no data-free generalities + execution cost — Met: §6 (3 moves, each tied to a section, each with person-hour cost).
  6. Free-alternative difference table — Met: §7 (including the honest "do not promise X coverage" row).

Status note: Meeting this checklist makes v0.2 eligible to be used as the paid-proof sample for the landing page and for outreach through permitted routes. It does not by itself move any sprint gate — gates move only on customer signals in the signal hierarchy (payment > prepayment > post-price registration > intent).