iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Japan’s weekly video-game charts are estimated rankings of sales recorded during a defined Japanese reporting week—usually Monday through Sunday—not a complete scoreboard of every copy sold worldwide or every digital download. A number-one entry means that the listed game or platform SKU had the most units in that chart’s measured scope for that period. To interpret it correctly, check the chart publisher, reporting dates, sales scope, platform row, and whether you are looking at weekly or cumulative units.
What a Japanese weekly sales chart is—and is not
A weekly chart is a time-bounded ranking. It orders the entries observed or estimated for one reporting window, normally a Monday-to-Sunday week in the examples published by Media Create and Famitsu. The ranking answers a narrow question: which listed software titles or hardware models sold the most units in Japan during that window, according to that publisher’s estimation method?
That makes a chart position different from several measures readers often confuse with it. A rank is not automatically a worldwide-sales position, revenue ranking, profit ranking, review score, player-count ranking, or an audited count of every transaction. It also does not tell you how many copies a game has sold over its entire commercial life unless you read the cumulative-sales field.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Media Create describes a weekly package that includes Top 300 software retail sales data, hardware retail sales, market shares, and trend summaries. Its data description also explains that the weekly unit is Monday through Sunday. Famitsu’s weekly reports identify their own Monday-to-Sunday period and label the figures as estimates based on information available when the report was compiled.
#1 Best Overall
Start with the reporting window and geography
Read the dates before the rank
Every comparison should begin with the date range printed in the report. A game ranked first for September 28–October 4, 2026 is being compared with other entries in that same period; it is not being compared with the first-place game from an earlier week unless you deliberately make that cross-week comparison.
The week usually runs Monday through Sunday in the cited Media Create and Famitsu examples. A release late in the week therefore has fewer selling days than a title available from Monday, even if both appear in the same table. Launch-week rank is consequently affected by release timing as well as demand.
Keep the geography fixed
These are Japan charts. A Japanese number-one position says that an entry led the measured Japanese market for the stated period. It cannot be used as a worldwide ranking, and it should not be compared directly with a chart whose geography includes North America, Europe, or a global digital storefront unless the measurement scope is made equivalent.
Free tools Windows power users keep installed
One-click scans. No signup required.
How the estimates are assembled
Retail sampling and extrapolation
Media Create’s public description specifies retail sales data. Media Create’s estimate draws on information from several Japanese retail channels, including large chains, general-merchandise stores, electronics retailers, smaller game shops, and some online retailers, then produces a weekly estimate. The result is best described as estimated retail sales, not a transaction-by-transaction census of every Japanese sale.
Sampling matters because retailers differ in size, location, customer mix, and product availability. A chart estimate is intended to represent the market from the observed channels; it is not a promise that every store or every individual purchase was counted identically.
Famitsu’s compilation note
Famitsu places a similar qualification on its figures. Its note says: 掲載している数値は、集計時点において入手可能な情報に基づいた推計値です。 Famitsu identifies this as an estimate based on information available at the time of compilation. Treat the numbers as estimates when calculating differences, judging a launch, or comparing publishers.
What Famitsu software figures include
Famitsu states: 本ランキングの推定販売本数は、パッケージソフトおよびダウンロードカード、本体プリインストール版を合算したものです。 In English, the ranking’s estimated software units combine packaged software, download cards, and versions preinstalled on a console.
Rank #2
The note does not say that ordinary downloads bought directly from a console or PC digital store are included. Unless a separate statement establishes digital-store coverage, do not rewrite a Famitsu software figure as total physical-plus-digital sales. A download card is a retail product sold through the measured channel; it is not the same measurement as a digital purchase made directly from an online store.
Why this distinction changes interpretation
Digital sales can be a substantial part of a game’s business, but a retail chart may not capture them in the same way as boxed software or retail download cards. VGChartz’s methodology offers a useful warning: it stopped producing software estimates after 2018 because the growing digital share made retail estimates less representative, while its hardware estimates continued to use retail sampling and extrapolation. The lesson is methodological, not a replacement figure: identify exactly what a series measures before comparing it with another series.
How to read a software row
A typical row can contain the platform or hardware family, title, units for the week, cumulative units, publisher, and release date. Read the row from left to right and verify that you are comparing like with like.
| Field | What it tells you | What it does not tell you |
|---|---|---|
| Platform or SKU | Which console version or product entry the units belong to | The combined total for every version of the game |
| Title | The named game entry in the chart | All editions, bundles, or platforms unless the table aggregates them |
| Weekly units | Units attributed to the stated reporting window | Lifetime sales or total players |
| Cumulative units | Total reported units accumulated through the latest period | A guaranteed worldwide total or a complete digital total |
| Publisher | The publisher credited in that row | The developer’s sales, revenue, or profit |
| Release date | How long the entry has been available relative to other rows | The date on which every version launched in every region |
Why one game can appear on several lines
Platform versions are normally separate rows. Famitsu examples show the same game listed independently for Switch 2, Switch, and PS5. Each line measures the units attributed to that platform SKU, so adding the rows is an aggregation you perform—not necessarily a total supplied by the chart.
When adding platform rows is reasonable
You may add platform rows when you need an explicitly combined estimate and all rows share the same reporting week, geography, and measurement scope. State that you calculated the sum, preserve the platform breakdown, and do not imply that the publisher presented a single cross-platform number.
When not to add them
- Do not combine rows from different weeks.
- Do not mix a retail estimate with a separate digital-store figure.
- Do not merge a standard edition with a bundle or preinstalled version unless the chart defines them as one entry.
- Do not use a platform total to claim that one game outsold another when one game’s versions were combined and the other’s were left separate.
Weekly sales versus cumulative or lifetime sales
Weekly sales are the units attributed to the current reporting window. They are the right field for judging immediate momentum, a launch week, or the effect of a promotion during that period.
Cumulative sales—also called lifetime or total-to-date sales in many discussions—are the units reported from launch through the latest chart period. They answer a different question: how many units this chart has accumulated for that entry so far.
A title can fall in weekly rank while its cumulative total keeps increasing. For example, a new release may take the top position in its launch week, then move down as later releases arrive even though it continues to sell. Conversely, an older title can rank modestly for a week yet have a larger cumulative total because it has been available much longer.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →| Question | Use this field | Reason |
|---|---|---|
| Which game sold the most during this week? | Weekly units | It matches the stated reporting window. |
| How large is this title’s reported run so far? | Cumulative units | It includes earlier chart periods. |
| Which launch had stronger first-week demand? | Weekly units plus release date | Release timing and the same week definition matter. |
| Which game has the larger long tail? | Cumulative units and multiple weekly reports | A single week cannot show sustained sales. |
What number one actually means
Number one means first among the entries included in that chart for that week. If the table is a software retail ranking, it means the highest estimated software-unit total in that measured Japanese retail scope. It does not mean the game generated the most yen, had the largest worldwide audience, received the best reviews, or sold the most when direct digital downloads are added.
The same logic applies to hardware. A model at the top of a hardware table led the listed hardware entries under that report’s method and period. It does not automatically represent every unit shipped, every used-console sale, or a combined family total.
How to read hardware rows
Hardware tables should be read at the model level. Famitsu lists separate estimates for standard, Lite, OLED, Pro, digital-edition, and other variants, along with cumulative totals.
| Hardware entry | Interpretation |
|---|---|
| Standard model | Units assigned to that specific standard configuration. |
| Lite or OLED model | Units for that named variant, not automatically the whole console family. |
| Pro or upgraded model | Units for the upgraded SKU shown in the row. |
| Disc-free or digital edition | Units for that edition, separate from a disc-equipped model when listed separately. |
| Cumulative hardware units | Total reported for that model through the latest period. |
Only collapse variants into a family total when the source supplies that total or you clearly calculate it yourself. A family-wide statement can otherwise hide which model drove the result.
Recommended Free Tools
A reliable workflow for interpreting any weekly chart
- Identify the publisher. Note whether the table comes from Media Create, Famitsu, or another service. Their methods and labels are not interchangeable.
- Record the exact dates. Write down the Monday-to-Sunday period or other window shown in the report.
- Confirm geography. Keep the comparison to Japan unless another region is explicitly included.
- Read the scope note. Look for wording such as software retail sales, hardware retail sales, estimated units, or market share.
- Check inclusion rules. For Famitsu software figures, packaged software, retail download cards, and console-preinstalled versions are combined; ordinary digital-store downloads are not established by that note.
- Match the SKU. Compare Switch 2 with Switch 2, PS5 with PS5, and specific hardware variants with the same variants.
- Choose the correct unit field. Use weekly units for the period and cumulative units for the total-to-date question.
- Account for release timing. A late-week launch and a full-week release do not have equal opportunity to sell.
- Calculate only transparent aggregates. If you add platform rows, show the components and label the result as your calculation.
- State the limitation. When reporting a result, call it an estimated Japanese retail figure and identify any digital-sales exclusion or uncertainty that affects the conclusion.
How to compare two games without producing a misleading result
Use the following checklist before saying that one title performed better:
- Same week: Both figures cover the same reporting window.
- Same country: Both are Japan estimates.
- Same scope: Both are estimated retail software units, or both are another explicitly matching measure.
- Same SKU treatment: Either compare individual platforms or aggregate both games’ platforms consistently.
- Same time basis: Compare weekly with weekly or cumulative with cumulative.
- Comparable release context: Note whether one title launched midweek, received a later port, or has been available for substantially longer.
- Rank and units separated: A rank change does not reveal the size of the unit change without the underlying numbers.
If any item fails, narrow the wording. For example, say that one Switch SKU ranked above another in that week rather than claiming that the entire franchise sold more across all platforms.
Rank movement and absolute unit change
Rank is ordinal: it tells you position. Units are cardinal: they tell you how many estimated copies were attributed to the entry. A game can move from third to first because its own sales rose, because the two games above it fell, or because a new release changed the field. Without weekly-unit figures for both periods, rank movement alone cannot quantify growth.
Use cumulative totals to understand the stock of sales built over time, but do not treat a cumulative lead as proof of stronger current momentum. A long-established title may lead cumulatively while a newer title sells more units in the latest week.
Media Create and Famitsu: what can be compared
Both publishers produce recurring Japanese chart reporting and describe estimated figures, but a number from one publisher should not be merged casually with a number from the other. Confirm the date range, platform treatment, inclusion rules, and table definition first.
Media Create’s described package includes Top 300 software retail sales, hardware retail sales, market shares, and trend summaries. Famitsu’s weekly reports provide estimated software and hardware rows with weekly and cumulative fields in current examples. If two reports appear to disagree, that does not by itself prove that one is wrong; different retailer samples, compilation timing, category rules, or rounding can produce different estimates.
Common mistakes and how to correct them
Calling the chart a complete sales census
Mistake: Writing that the chart records every Japanese transaction.
Correction: Describe it as an estimate based on the publisher’s available retail information and sampling method.
Calling a Famitsu number total physical-plus-digital sales
Mistake: Treating the figure as all boxed copies plus every download.
Correction: Use Famitsu’s stated combination of packaged software, download cards, and console-preinstalled versions, and leave ordinary digital-store downloads unclaimed unless separately documented.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCombining every platform silently
Mistake: Adding Switch, Switch 2, and PS5 rows and presenting the sum as the chart’s own title total.
Correction: Keep the rows separate or show a clearly labeled calculation with matching scope and dates.
Best Value
Confusing rank with sales size
Mistake: Saying a game that rose five places sold five times as many units.
Correction: Report the unit figures and rank independently.
Comparing unlike time bases
Mistake: Comparing one title’s launch-week units with another title’s cumulative total.
Correction: Put both figures on the same weekly or cumulative basis.
Reading hardware families as single products
Mistake: Calling the combined total of standard, Lite, OLED, and Pro models a single row when the source lists them separately.
Correction: Preserve model-level rows or identify your own aggregation.
How to write a careful chart-based conclusion
A precise sentence contains four elements: the publisher, the reporting week, the measured scope, and the field being discussed. For example: “In Famitsu’s estimated Japanese software report for the stated Monday–Sunday week, the PS5 SKU ranked above the other listed software entries by weekly units.” If you add cumulative context, make it a separate statement so readers do not confuse the two time bases.
When the evidence does not establish digital-store coverage, say so directly. When a platform total is your own sum, identify it as a calculation. These small labels prevent a narrow retail estimate from being read as a universal sales total.
What the charts are useful for
- Tracking week-to-week retail momentum in Japan.
- Comparing launch performance when release timing and SKU scope are aligned.
- Seeing which platform variants are moving units.
- Following long-tail sales through cumulative totals.
- Observing market-share and hardware trends in reports that publish them.
- Identifying how a title’s position changes as new releases enter the chart.
They are less suitable for estimating worldwide revenue, measuring total players, or comparing a retail-only estimate with an all-digital figure. Those questions require a source that defines and covers the additional data.
Quick Recap
Key points to remember
- The reporting week is usually Monday through Sunday in the cited Media Create and Famitsu reports.
- The figures are estimates, not an audited census of every transaction.
- Famitsu’s stated software estimate combines packaged software, download cards, and console-preinstalled versions.
- Ordinary digital-store downloads should not be assumed to be included.
- Platform versions and hardware variants can appear as separate rows.
- Weekly units measure the current window; cumulative units measure the reported total through the latest period.
- Number one means first within that chart’s measured Japanese scope, not best-selling everywhere or by every possible business metric.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
