by Michael Eckenfels, 25 May 2026
This is an operational-scale historical wargame with two scenarios published by the Polish wargame house Taktyka i Strategia as part of their Great Battles 1939-45 (WB-95) system, designed by Wojciech Zalewski. Released under the WB-95 system umbrella (as of 2018 for the system rules, which is the PDF version I received – more on this later), these scenarios depict the German summer 1942 drive on Stalingrad. The two scenarios are Don, covering the broader operational push from July 23 to August 10, and Onto Stalingrad, covering the closer approach battles from August 10 to August 31.
This game sits squarely in the traditional European hex-and-counter operational wargame tradition, in the same lineage as classic SPI, GMT, and Avalon Hill titles, but with the distinctly Eastern European flavor that Polish and Russian designers bring to Eastern Front games. Think regimental-to-divisional scale, one-day turns, IGOUGO sequencing, and a focus on the operational problem rather than tactics or grand strategy. The scale (one regiment/division per counter, one day per turn) places it alongside games like GMT’s Stalingrad ’42, MMP’s Case Blue, or the older SPI Streets of Stalingrad in terms of ambition, though WB-95 sits at a notably lower complexity tier than the latter two.
Background
Taktyka i Strategia is a long-running Warsaw-based publisher specializing in WWII Eastern Front and Polish military history wargames, with a catalog stretching back to the 1990s. Their WB-95 system – the name itself a callback to the publisher’s heritage – was formalized in 2018 as a unifying ruleset for a series of operational battles including Moscow, Kursk, Korsun, Normandy, and now Stalingrad. The system explicitly aims to let the same rules drive multiple historical games, which is a common design philosophy (compared to Vae Victis or the various Strategy & Tactics house systems).
I haven’t previously covered Taktyka i Strategia titles, so this review stands alone rather than continuing prior preview coverage. It is worth pointing out, though, that the system rules document is dated 2018 as mentioned above, while the Stalingrad scenarios appear to be a more recent addition to the WB-95 catalog; the rules feel mature and battle-tested, having clearly been refined across multiple titles in the series.
click images to enlarge
Components and Design
The counter art is functional rather than beautiful, and I believe that’s a deliberate choice for this market. Counters carry infantry, artillery, and armor symbols rather than NATO style symbols, with strength points and movement points clearly readable, alignment markers (division/corps/army), and unit nomenclatures. Some wargames tend to favor information density over aesthetic flourish, and WB-95 is no exception. The artillery counters particularly, for example, with one side for combat and the other for transport, is a nice touch, though the rules acknowledge older games in the series used blank reverses instead, which is a minor inconsistency that long-time collectors of the line will already be familiar with.
The portrait counters for HQ units (Paulus, Strecker, Wietersheim, Langermann, Heitz, Seydlitz, Schwedler, Kempf for the Germans; Chuikov, Gordov, Trufanov, Moskalenko, Kriuczenkin, Nikishev for the Soviets) add historical character. The “starred” units system, with black, white, yellow, and blue stars denoting special capabilities, is an elegant way to handle unit quality without bloating the strength point values, though it does require players to memorize what each color does.
Documentation: Where the Trouble Lives
Here’s where I have to be direct: the English version of the rulebook is rough. The system rules are functional, but the translation reads as a working draft rather than a polished product. You’ll find typos (such as “OBJAŒNIENIA” left untranslated in the Onto Stalingrad scenario notes, as well as “SOIETS” instead of “SOVIETS”), as well as grammatical hiccups and occasionally ambiguous phrasing.
One particular issue I had, with initiative determination, is a perfect example of this problem. The scenario notes do say “Initiative: Germans” (in Don) and “Initiative: Germany” (in Onto Stalingrad), but the rulebook’s explanation of what “initiative” really means is buried in a single line at section 2.2: “Individual games and scenarios will declare which side has the Initiative, and therefore starts first.” So yes, the Germans go first in both scenarios, but you have to cross-reference the scenario card against a passing mention in the phase sequence to confirm it. A clearer rulebook would have a dedicated section on turn structure that says “The player with Initiative completes all six phases, then the opposing player completes all six phases,” for example, in unambiguous terms, instead of leaving it as an implication.
There are a number of other spots worth pointing out. For example, the reference to “Order 277” in the Onto Stalingrad historical text is almost certainly a typo for Order 227 (Stalin’s famous “Not One Step Back” directive of July 28, 1942). The Don scenario gets the title right but doesn’t number it. Also, the Combat Result examples on page 3 reference “A1D => Attacker Retreats by 1 hex and Disorganized,” but the combat table on the same page shows results like “A1•/-” – so the relationship between the example notation and the table notation requires inference. Additionally, stacking is stated as “8 CELs per hex” but the implications for artillery (with 1 CEL each) versus full divisions get only one passing example.
That is not to say the rules are without good examples. For one, the Big River bridge-building procedure on pages 11–12 is genuinely well explained with a three-turn worked example, which makes it stand out as one of the better sections.
Regardless of bright spots, I think a learner of this game will need to read the rulebook twice. The first pass to get the gist of it, and the second to hunt down the rules missed because they were embedded in a sub-clause of an example. Be prepared to bring your highlighter, just in case.
Opponents
Considering my penchant for solo gaming, it’s important to note that this is not a solo game. It is a two-player game, full stop. There is no solo system, no AI, no co-op variant, and the rules don’t even acknowledge the possibility of multi-player team play. Unit Masking, in a ‘Fog of War’ section, is built around hidden stacks and nationality markers, which is of course great for face-to-face two-player games but means solo play requires significant house-ruling to keep one side’s deployment honest.
One thing I will say about a lack of solo potential – which I know, many will read this and think “so what?” – is honestly a weakness in 2026. The hobby has moved decisively toward including some kind of solo support, even simple bot systems like Case Blue’s solitaire variant or the flowchart-style opponents in Compass Games and GMT titles. A Stalingrad game with no solo support is leaving a significant audience on the table.
Learning Curve and Ease of Use
Despite the rulebook’s roughness, the underlying system is genuinely accessible, probably a 4 or 5 out of 10 on a wargame complexity scale. If you’ve played any classic hex-and-counter operational game, you’ll recognize 80% of WB-95 immediately: ZoCs that lock units in place, must-attack rules, retreat-and-pursue, combat ratios with column shifts for terrain and modifiers, supply traced from a map edge, and so on. The 2d6 combat resolution (rather than 1d6) gives a nicer bell curve than the SPI classics and lets the designer pack more granular results into the table.
This familiarity that an experienced wargamer may have with such things, means there are genuinely system-specific concepts that can be internalized quickly. For example, the Out of Supply Level mechanic is more interesting than typical binary supply/no-supply systems, as this game stipulates that units can voluntarily push their supply level higher to gain full movement and full attack strength for a turn, but pay for this with elevated surrender risk later. This is, in my opinion, the best idea in the system.
Also, Combat Efficiency Levels (or CELs) as a unit hardiness mechanism should be very familiar, as most units have two CELs. One hit means their counter is flipped to its other side, and another hit eliminates it. This is familiar from many other systems and cleanly executed.
Another familiarity should be Tactical Concentration, where getting three units of the same division into a single combat grants a combat modifier, which encourages historically realistic divisional employment rather than dispersing regiments across the steppe.
One thing I will mention is, the starred-unit system for special abilities is easy to use once internalized, but a legend or note of some kind would be very useful to have right there on the map so you can learn what each of these means quickly.
A first game will take 90 minutes of rules reading and probably 4–6 hours to play through a scenario like Onto Stalingrad. By the second play, that drops dramatically.
Replay Value and Scenario Design
For this Stalingrad version of the game system specifically, you get only two historical scenarios of differing length (19 days for Don, 21 days for Onto Stalingrad). The orders of battle are strictly historical; there is no “what if Manstein arrived early” or “what if the Soviets had committed reserves differently” alternate set-ups. The WB-95 system’s marketing copy promises that some games in the series include hypothetical scenarios, but the Stalingrad module doesn’t capitalize on that promise. This is a missed opportunity. The Stalingrad campaign is full of plausible and fascinating counterfactuals, such as what if 4th Panzer Army hadn’t been diverted south to help Army Group A in July, what if Paulus had pushed harder before the Soviets organized the city defense, what if Hoth had attacked from a different axis, and on and on it goes. As Stalingrad is one of my ‘favorite’ subjects of military history to read about and I have many games on this very subject – not to mention several books – I was disappointed that none of this was included. Even one of these would have added a lot of additional replay value. As shipped, once you’ve played each scenario from each side, you’ve seen most of what the module has to offer.
The two scenarios are discrete rather than linked, as they do not form a campaign together; this is somewhat odd as the Don scenario ends August 10 and Onto Stalingrad begins that same day. The game does not provide rules for carrying results from the first into the second, unfortunately. The orders of battle in Onto Stalingrad reflect the historical state of forces on August 10, not whatever state the Don scenario produced. A linking campaign rule, even a simple one allowing losses to carry forward, would have been welcome and is a notable omission compared to systems like OCS that explicitly support stitching scenarios together.
The orders of battle themselves are well-researched. The German side correctly shows Paulus’s 6th Army with its full corps structure (XI, XIV, XXIV, LI, and VIII) and Hoth’s 4th Panzer Army (with XXXXVIII Corps under Kempf) arriving from the southwest in the Don scenario. The Soviet reinforcement schedule tracks the historical arrival of the 62nd Army (under Chuikov), as well as the 64th Army and the elements of 1st Guards Army. Compare this to Stalingrad ’42, which covers the broader summer campaign at a higher level of abstraction (and includes both historical and tournament optional rules for OOB variation), and you can see that WB-95 chose granularity and faithfulness over flexibility and variation. Both are valid design choices, but only one of them serves replay value.
The deeper replay argument here, I think, is that WB-95 is a system, not a single game. If you enjoy Don/Onto Stalingrad, the same ruleset opens the door to Moscow, Kursk, Korsun, Normandy, and others in the catalog, and the cross-compatibility is perfect in this case.
How It Works as a Whole
The WB-95 system here captures something important about the operational level of war that finer-grained games miss: the German player constantly feels the tension between pushing forward fast (and risking Out of Supply surrender) versus consolidating supply (and letting the Soviets dig in). That Out of Supply mechanic does a real number on the German side as it forces that player to make exactly the kind of decisions Paulus actually faced, where every day of delay strengthens the defender but every day of overextension risks catastrophe.
The Soviet player, meanwhile, gets to feel the awful weight of Order 227. The victory conditions reward preventing German advance toward Stalingrad in escalating tiers (10 VP for holding the Germans 1 hex away, all the way up to 35 VP for 6 hexes away), which mechanically captures why Soviet commanders could not trade space for time. They were rewarded for standing and dying. The disorganization on retreat mechanic compounds this: even when you can retreat, the cascade of disorganization tests punishes any kind of mobile defense.
Mechanics in Comparison
It’s worth digging into specific subsystems because for me, it helps to really see WB-95’s design priorities.
Logistics versus Stalingrad ’42: Simonitch’s Stalingrad ’42 uses a wonderfully elegant supply system where supply is essentially traced through ZoC-free paths to a railhead, with a railhead extension sub-game where the Germans physically move their supply infrastructure forward each turn. It’s deterministic; you’re either supplied or you’re not. WB-95’s approach is rather more granular and more dramatic, as its OoS Level mechanic is a spectrum (0 through whatever your dice can sustain), and the surrender check mechanic means even a marginally supplied unit might survive or might collapse depending on a 2d6 dice roll. The cost is fiddliness (you’re tracking OoS markers and modifying them constantly); the benefit is that supply feels like a continuous pressure rather than a binary switch. I prefer WB-95’s approach for the operational level. I believe Simonitch’s system is cleaner, but WB-95’s is more interesting turn-to-turn.
Combat versus Streets of Stalingrad: SPI’s old Streets of Stalingrad is a tactical bloodbath, with combat between regiments and battalions decided on heavily-modified CRTs with significant lethality, and a single bad combat can destroy a major formation. WB-95 is substantially less bloody but considerably more mobile. The CEL system here means even a clobbered unit usually retreats and survives at half-strength. Full eliminations are relatively rare outside of OoS surrender. The retreat and disorganization cascade does most of the heavy lifting, because units don’t die so much as they get shaken, lose effectiveness, and have to spend a turn recovering. This is much closer to operational reality (where divisions rarely evaporated overnight but routinely became combat ineffective) than the SPI bloodbath approach.
Movement and terrain versus Case Blue: MMP’s Case Blue (the OCS system) handles terrain with extreme granularity, as every hex side and hex type has its own cost, mode changes affect movement, and the interaction between movement, supply, and combat is dense. WB-95 is dramatically less math-intensive. Terrain costs are listed on a single table with perhaps a dozen entries. Movement allowances are small enough (4 to 7 MPs for most units) that you’re not doing extensive route-planning math. The tradeoff here is that Case Blue lets you model logistical bottlenecks at terrain features (a single bridge can paralyze a whole army), where WB-95 can’t really capture that level of detail. If you want to feel like a corps commander making operational decisions in about an evening, WB-95 wins. If you want to feel like the operations officer of a panzer army planning a week-long offensive, Case Blue is the better tool.
Historical Fidelity
Does the game actually let history happen? Mostly yes, with one important caveat: the German player in Onto Stalingrad can plausibly reach the outskirts of Stalingrad by the end of the scenario, which is what historically happened (German troops reached the Volga north of Stalingrad on August 23, 1942). The victory point structure even rewards exactly that historical outcome: Germans get VP for city hexes, Soviets get escalating VP for keeping Germans away. Both sides have plausible paths to their historical performance.
The caveat I mentioned is, the “instant victory if Germans capture all Stalingrad hexes” rule is essentially unachievable in either scenario’s timeframe, which is historically correct. The Germans never captured all of Stalingrad despite four months of trying. But it means German players essentially can’t win a decisive victory; they’re playing for incremental VP gains while the Soviet player is playing for the VP defensive tiers. This matches history but can feel anticlimactic.
One thing the game does not model that’s central to the historical campaign is the gradual Soviet buildup of reserves north and south of Stalingrad in preparation for Operation Uranus. The scenarios end before Uranus matters, so this isn’t a flaw per se, but a player coming to this game hoping to see the full strategic shape of the campaign won’t find it here. For that, you need a higher-scope game.
However, while good, I think WB-95 falters in actual play in a few ways. For one, the mandatory attack rule with the must be attacked corollary (in sections 5.2.1 and 5.2.2) creates situations where players spend a LOT of time figuring out who has to fight whom before they can plan what they want to do. Also, the artillery transport/combat set-up distinction is realistic but fiddly; you will likely forget to flip counters and have to retrofit decisions. Finally, Strategic Movement (in section 12) is potentially powerful, but the prohibition on starting in an enemy ZoC means it rarely matters in dense Stalingrad-area combat where everyone is locked in.
Further Reading and Viewing
As mentioned, I have spent an inordinate amount of time in my life reading and re-reading content about this campaign and battle. If this game whets your appetite for the historical campaign, and I think a good wargame should, here’s where I suggest to go next.
For the summer 1942 approach phase specifically, which is what these scenarios cover, David Glantz and Jonathan House’s To the Gates of Stalingrad: Soviet-German Combat Operations, April–August 1942 is the indispensable reference. It’s volume one of their three-volume Stalingrad Trilogy (Armageddon in Stalingrad, September–November 1942, covers the city fighting, and Endgame at Stalingrad covers Operation Uranus and after). Glantz’s access to Russian archives after 1991 makes his work qualitatively different from older Western accounts, because he can tell you which Soviet division was where on which day, and the orders of battle in the WB-95 scenarios visibly draw on this kind of granular research. Be warned: Glantz’s content is dense. These are reference works as much as narratives.
For a more readable single-volume narrative, Antony Beevor’s Stalingrad: The Fateful Siege 1942–1943 (1998) remains the standard recommendation. Beevor is a more accessible storyteller than Glantz, and his ability to weave individual human stories into the operational narrative is unmatched. Glantz has criticized some of Beevor’s Soviet operational details, but for a player who wants to feel the campaign before diving into Glantz, Beevor is where to start.
For an absolutely excellent and well-produced video series, the YouTube creator TIK (TIKhistory) has produced an extraordinary series called Battlestorm Stalingrad, with over 30 hours of day-by-day battle animation documentaries covering the entire campaign from July 21, 1942 onward, backed by over 100 sources. If you want to watch the historical context of Don unfold day by day while you play, TIK’s early-to-mid season episodes cover exactly the period and operations these scenarios depict. The “Was Reaching the Volga North of Stalingrad the WRONG move?” episode is particularly relevant for Onto Stalingrad players thinking about German operational choices.
For shorter video introductions, both Kings and Generals and World War Two (the Indy Neidell-led Time Ghost channel) have good Stalingrad coverage, though without TIK’s tactical depth.
For fiction and primary source feel, Vasily Grossman’s Life and Fate is the great Soviet novel of Stalingrad; it is Tolstoyan in scope, written by a war correspondent who was actually there. Grossman’s earlier reportage, collected as A Writer at War, gives you the immediate ground-level perspective. Neither will improve your gameplay but both will deepen your engagement with what the cardboard counters are abstracting.
For Wehrmacht perspective, Joachim Wieder’s Stalingrad and the Responsibility of the Soldier (Wieder served in Paulus’s 6th Army and was one of the ‘lucky’ few that survived captivity) is a sober and morally serious memoir worth the time.
Fun Factor and Final Rating
I genuinely enjoyed working through these scenarios, but with caveats.
The fun is real when the system clicks. There’s a moment in the Don scenario somewhere around July 28 or 29, where the German player has to decide whether to push 6th Army’s armor toward Stalingrad and accept that infantry won’t catch up for two turns, or pause and let the line consolidate. That decision absolutely feels like 1942. The supply mechanic punishes the first choice without forbidding it, and the VP track rewards the second choice without making it safe. That’s good design.
The fun is harder to access because of the documentation problems. I lost about an hour of my first session to rules questions that a cleaner rulebook would have resolved instantly; my issue with determining initiative being a representative example. For a Polish-language native player with access to the original rules and a community to ask, this is probably a non-issue. For an English-speaking player buying this cold, it’s a meaningful tax on enjoyment.
The scenarios themselves are well-designed historically. The orders of battle look correct against my reference material, the reinforcement schedules track the historical arrival of Soviet armies (28th, 51st, 57th, 62nd, 64th all appear with appropriate timing), and the German order of battle correctly shows 6th Army (Paulus) and 4th Panzer Army (Hoth) elements converging from west and southwest. The research is absolutely well done and accurate, which deserves praise.
This is, at its heart, a genuinely good operational engine with the OoS Level innovation, functional yet unremarkable components, English documentation that could benefit from a native speaker doing an editing pass, excellent scenario design with historically credible meaningful decisions for both sides to make, and I think is at a mid-complexity level but harder than it needs to be due to the English documentation’s challenges. Replay value is relatively strong even with only two scenarios, and the system itself extends to other titles which can be great if you want to try others in this series. Unfortunately, solo support is lacking.
I would recommend this game for experienced hex-and-counter wargamers who like operational scale, as well as any Eastern Front specialists and players who already enjoy other WB-95 titles. That all said, any native English speakers willing to forgive a rough rulebook for solid underlying design will find a good system underneath. I of course cannot speak to the strengths of the Polish language version, unfortunately.
If you are a newcomer to wargaming, a solo player, someone who needs polished production values, or are a player who already own Stalingrad ’42, I would say you might not need another take on the same campaign. But that said, it never stopped me from buying anything with “Stalingrad” on the game box.
The bones of a very good game are here. With a cleaned-up English rulebook and an added solo bot, this game would be an easy 8/10. As shipped, it’s a game I respect more than I love, but given my affinity for the subject matter, I’ll be coming back to it.
You can chat about this game in the Modern World section of our discussion forums
Thank you for visiting the Regiment of Strategy Gaming and riding with The Armchair Dragoons.
Rather than list a bunch of social media links, the easiest thing to do is to check out our LinkTree, which connects you to all of our various locales around the web.
You can also support The Armchair Dragoons through our Patreon, and find us at a variety of conventions and other events.
Feel free to talk back to us either in our discussion forum, or in the comments below.
