The TTR Value (Table Tennis Rating) is a number that represents your current playing strength in official, TTR-relevant singles. The principle is similar to Elo: You gain points if you win more often or "better" than statistically expected – and lose points if you lose more often than expected. The key is the Profit Expectation: Against stronger opponents it is low, against weaker ones high. That's exactly why an upset feels so good – and is also more rewarding rating-wise.

This calculator shows you two perspectives: In "Event (Official)" mode, a team match or tournament is calculated as a block. You enter your opponents, the tool sums up the expectations P (i.e., expected wins across all matches) and compares them with your real wins V. The change is then ΔTTR = (V − P) · k. Important: In this block mode, it doesn't matter against which opponent you get the wins – only how many you get is decisive, because P is derived from all opponent values and your start TTR.

In "Live (Match by Match)" mode, however, you see how an intermediate score would feel if a partial change were applied after each match. This is great for following along at the table or for "What happens if I win the next one..." scenarios. Officially, values are kept as integers at the end – so you can set whether rounding happens only at the end or after each game.

The parameter k (Change Constant) determines how strongly your TTR can react. Standard is k=16, but in practice, k can vary depending on the situation (e.g., with very few rated games or certain age/development cases). To ensure the calculator remains useful for you, you can choose k as a preset or set it freely. Also, the scaling (Standard 150) is visible: It controls how quickly the profit chance tips with the TTR difference.

The added value here is transparency: You see your win probability against a specific opponent, the Sum of Expectations, and via the scenarios immediately the Best and Worst Case. This allows you to realistically assess why a 2:0 against weaker opponents moves "less" than a 1:1 against significantly stronger ones. And you can set goals: "About how many wins do I need to make +10 points?" – without having to wait for the next update.

Privacy: All calculations happen locally in your browser. No data is sent to servers.

1) Why does the calculator show a "k" value – isn't it fixed?

Often k=16 is used. In reality, however, k can be higher depending on conditions. To allow you to calculate meaningfully, k is deliberately selectable here (Standard remains 16).

2) Does it really not matter who I win against?

In "Event" mode, only the Count of Wins and the Sum of Expectations count for the final change. The expectations result from all opponents together – therefore, in this block model, the specific win-opponent is not relevant.

3) Why did I get only a few points despite winning?

If your win expectation was high (you were clearly favored), then a win is "normal" – so there is little plus. A surprising win against stronger opponents is rare – therefore usually significantly more points.

4) What is the use of Live Mode?

It is ideal for following along and for motivation ("If I take the next one..."). Officially, it is usually calculated as a block, but Live is great for the feeling and quick intermediate statuses.

5) Why does it say "Rounding at end"?

TTR is kept as an integer. To remain traceable, we calculate internally with decimals and round (recommended) at the end, so you don't see "phantom points" due to rounding artifacts.

6) Can I also just enter the opponent TTR and set the wins later?

Yes: Use the Scenario Area and slide "Simulate Wins" from 0 to N. This is often faster than clicking each result individually.

7) Why are inactivity or initial rating not calculated?

These are special rules that require additional data and cut-off dates. The calculator is intended as a clear, fast simulator – with a focus on expectation, wins, and k.

8) How can I enter values "like a real match day"?

Enter all opponents (e.g., 2–4 singles in a league match or several rounds in a tournament) and set the results. For multiple days/events, it is best to use multiple separate calculations.