Before playing Race for Berlin what the design promises, and what I’ll be watching for
Written 20 August 2026, from the rulebook, before the first counter moved. Published unedited. The review of what actually happened follows. AI was used to pull research from my library.
The manipulation
On 16 April 1945 two Soviet fronts went at Berlin. Zhukov’s 1st Belorussian came at it head-on through the Seelow Heights. Koniev’s 1st Ukrainian came up from the south across the Neisse. Between them ran a boundary line on the Stavka map, and the interesting thing about that line is where it stopped.
Stalin, in Glantz’s words, “rather pointedly failed to define the boundary line between 1st Belorussian Front and 1st Ukrainian Front beyond the initial stage of the operation” (When Titans Clashed, p. 292). The line was drawn as far as the approaches and then simply ended. Late on 17 April he went further and amended the map “by erasing the front boundary line between them in the vicinity of Berlin, leaving the capture of the capital to whomever got there first” (p. 297).
He did not tell both men equally. Stavka authorised Koniev into the city without informing Zhukov — Osprey Command 22 calls it “a clear sign of his diminished status” — and Zhukov found out when his tank crews ran into Koniev’s advance guard coming the other way (pp. 54–56).
That is the operation’s signature, and it is a strange thing to try to put in a box. Most designs treat Berlin 1945 as Soviets against Germans, which it obviously was. The competition between the two marshals then has nowhere to live, because a single Soviet player has no rival to race.
Race for Berlin, from Battles magazine, takes the other road. It is not Soviets against Germans. It is Zhukov against Koniev, and each player is handed a slice of the Red Army and a slice of the Wehrmacht. You are not trying to beat the Germans. You are trying to beat the other marshal, and the German army is a shared instrument you both push around.
Everything below follows from that one decision.
Five things I’ll be watching
1. Whether the boundary actually binds
This is the one that matters most, because it is the thing the concept lives or dies on.
Soviet units may not voluntarily cross the line separating the two fronts, and if a retreat forces one over, it has to come back as soon as it can be activated. The designer’s note gives the reason plainly: the marshals’ zones were defined by Stalin as far as Berlin and left deliberately vague once the capital was reached, to intensify the competition.
There is a sharper rule underneath it. Units from the two camps may not voluntarily end up in the same zone at all — and a unit forced by retreat into the rival’s zone does not help defend it. If that zone falls, the unit is eliminated outright. Not reduced. Gone.
So the question is whether the line is felt or forgotten. A restriction you route around without noticing is scenery. A restriction that costs you a formation is Stalin’s manipulation rendered as a rule.
2. A victory condition that makes you need your rival
The scoring is comparative, not absolute. The job is not to capture Berlin; it is to out-perform the other marshal.
Two small prizes go to whoever is first rather than strongest a point for the first player to bring a unit up beside a Berlin zone and immediately stand it down, which is the shelling of Berlin, and two points for the first to raise a City Progress level above zero.
The big prize is five points for the highest City Progress at the end, and it carries a condition that is the best joke in the design: it only pays if all six Berlin zones hold at least one Soviet unit, from either camp. Your prize does not pay unless your rival has done his share of closing the ring.
That is the historical priority in VP points. Encirclement came first; getting into the city counted for nothing until Berlin was cut off. I want to see the moment where I have to help Koniev in order to get paid!
3. Supply as a currency you spend, not a tax you pay
Each player gets one replacement point a turn. He may decline it and convert it into a support point instead — and he may generate further support points by voluntarily placing his own supplied units out of supply.
Support points are what buy the rolls that push City Progress into Berlin, and a second point on the same roll buys a modifier. Nothing carries between turns. Unspent, it is lost.
So the currency of the endgame is the condition of your own army. You wreck formations on purpose to buy your way into the city, and you cannot bank the proceeds. That is a real decision if the pressure ever arrives to make it one, and a gimmick if it doesn’t. I want to know which.
The historical case for modelling supply at all is strong. Twenty-nine Soviet armies had to reposition inside fifteen days, fifteen of them up to 385km and three between 300 and 530km, while the rail network struggled to build the fuel and ammunition stocks to sustain the offensive (Glantz, p. 292). Osprey puts it at two weeks to mount an operation that would normally need two to three months (Campaign 159, p. 44). On the other side, ammunition shortages “undermined the German defence which otherwise might have held at least some sectors” (Command 22, p. 54).
4. Whether the Germans have anything to do
The lazy version of this campaign is a German retreat exercise. The record does not support that, and this design builds the alternatives in as rules.
Hitler’s Orders run through the first five turns. A d6 each turn; a 5 forces a counterattack in the north, a 6 in the south. The forced attack needs at least two divisions with one armoured, and if nothing is adjacent to the Soviets, units must be moved adjacent to comply.
The no-retreat order is a die roll. A German unit in movement mode has to pass a test to move freely; fail it and the unit may not move westward. The threshold eases as the game goes on and the restriction lapses from turn 7 — Hitler’s grip loosening as a mechanic rather than a lecture.
Wenck’s Twelfth Army can be released from turn 4, two units a turn, arriving at random. The design note is honest about what it was for: its commander’s real intent was to break Ninth Army out so it could cross the Elbe and surrender to the Americans.
The counterattacks were real. Ninth Army attacked toward Küstrin with four divisions on 27 March; a three-division attack on 17 April tried to cut the Berlin–Küstrin highway behind Katukov’s spearheads (Glantz, pp. 289, 296); the Kurmark Panzergrenadiers stopped 11th Guards Tank Corps at Friedersdorf and Dolgelin (Osprey, p. 37). The question is whether the forced attacks here feel like Hitler, or like a tax.
5. The Americans as a clock, and a shared way to lose
Three American tracks advance on a die roll each turn, faster from turn 4 and faster again from turn 9. An American zone is closed to Soviets and Germans alike. If the Americans reach a zone containing a Soviet unit, their advance stops permanently on all three tracks.
And if the Americans reach a Berlin city zone, both players lose.
That is the anxiety Stalin actually had. Glantz records the Soviet concern that despite the agreements, the Allied armies would advance on the city, and that this accelerated the preparations (p. 290). Here it is a countdown that can end the game over the heads of both marshals — the one thing that turns two rivals into allies. I want to see whether it changes tempo or just ticks in the background.
The problem I already know about
The engine is the rivalry, and I am playing solo. That means running both marshals against each other, which is my usual thing and normally fine.
The complication is the Event Chits. Each player draws one in secret, and the Koniev player starts holding Heinrici. Hidden information does not work when both hands belong to the same person, so it has to be decided in advance — play them open, or invent some dodge — and whatever gets chosen has to be declared, because it changes what the review is worth.
There is a second risk worth naming before rather than after. I have just come off a different game on this same battle, and a fresh design that is visibly doing more will flatter itself by comparison. They are not aiming at the same thing. Each gets judged against what it set out to do, and the head-to-head can wait for its own piece.
What would make this work
If the boundary bites, if the five-point prize forces me to help my rival, if I burn my own units to buy a way into the city, and if the Germans get to do something other than fall back — then this is the design that found a mechanism for the thing every other Berlin game can only print on the map.
If none of that happens, it is a straightforward advance with an unusual seating plan.
That is the bet, registered before the first roll. What actually happened goes in the review.
Sources: Glantz & House, When Titans Clashed, pp. 288–299 · Osprey Campaign 159, Berlin 1945 (Antill), pp. 36–46 · Osprey Command 22, Georgy Zhukov, pp. 52–56 · Battles #4. Rule detail from the Race for Berlin rulebook.