seed 20260905
Voltorb · Tyranitar · Dunsparce · Tangela · Lickitung · Dratini
10 of 18 pure types covered; 1 shared weaknesses (Fighting).
Generate a reproducible one-to-six-member roster from the local 255-species snapshot and immediately test its STAB coverage and shared type weaknesses.
input channel
live result
Seed 20260905 · shared: Fighting
seeded roster
Uncovered: Normal, Electric, Grass, Fighting, Poison, Dark, Steel, Fairy.
These examples use six draws, no type-repeat constraint, and the committed 255-record order. They document this exact snapshot rather than claiming an average for every possible random team.
seed 20260905
10 of 18 pure types covered; 1 shared weaknesses (Fighting).
seed 151
11 of 18 pure types covered; 1 shared weaknesses (Psychic).
This random Pokémon team generator uses a numeric seed, not an opaque server response. The same seed, size, and repeat rule always produce the same roster, so copying the URL preserves the exact draw. Each roll samples without replacement from the local 255-record species snapshot, then sends the chosen typings through the same defensive and STAB coverage audit used by the team builder. The result turns a novelty roll into a plan you can inspect, reproduce, and improve.
Mulberry32 is a small deterministic pseudo-random number generator. It converts the seed to an unsigned 32-bit state, advances that state by a fixed constant, mixes its bits with shifts and integer multiplication, and returns a fraction from zero up to but not including one. The implementation assigns each pool record a generated key and orders by that key with the original index as a stable tie-break. A new seed produces a new order; repeating a seed produces the same order in this committed snapshot. It is suitable for repeatable selection, not security, gambling, or cryptography.
Sampling without replacement means one species record cannot occupy two slots. The size control takes the first one through six valid records in seeded order. When the optional repeat constraint is enabled, a candidate is skipped if choosing it would make any one of its stored types appear on more than two members. The rule counts both halves of dual typings, so a Fire/Flying selection contributes once to Fire and once to Flying. Because the pool contains varied typings, the local snapshot can fill ordinary teams under this constraint without inventing or duplicating records.
After the draw, offensive coverage pools every selected native type as a possible STAB attack. A pure defending type is covered only when at least one pooled attack reaches 2×. The defensive pass tests all 18 incoming types against each selected single or dual typing and flags an attack when it hits at least three members above 1×. This score does not inspect moves, abilities, stats, evolutions, roles, items, formats, or whether several records belong to one evolutionary family. Use it as a measurable starting point, then move the roster into the manual team builder and replace weak links deliberately.
With a fixed seed, size six, and the repeat constraint off, the generator maps six deterministic fractions to six distinct positions in the 255-record pool. Copying that URL repeats both the roster and its coverage count. Enabling the type-repeat rule may skip an otherwise early candidate, so the resulting team can change even though the seed stays fixed. The page reports the exact fixed-seed examples verified by the local tests below the tool, including their covered totals and shared weaknesses rather than inventing an average score.
A higher covered count means more pure types are weak to at least one selected native type. Fewer shared weaknesses means fewer attacking types pressure three or more members through ordinary typing. Neither figure proves that a random team is playable: move access, base stats, evolution stage, speed, defensive roles, recovery, hazards, abilities, and format legality can dominate. The useful output is a reproducible candidate roster plus explicit gaps. Roll again for exploration or keep the seed and refine the same six choices in the team builder.
Formula and table references are named with the review year. The calculations run entirely from the reviewed local snapshot; no third-party service is called when you change an input.