Team17
video game developer based in Wakefield
Team 17 Digital Limited (Team17) is a British video game developer and publisher based in Wakefield, England. The venture was created in December 1990 through the merger of British publisher 17-Bit Software and Swedish developer Team 7. At the time, the two companies consisted of and were led by Michael Robinson, Martyn Brown and Debbie Bestwick, and Andreas Tadic, Rico Holmes and Peter Tuleby, respectively. Bestwick later became Team17's chief executive officer until 1 January 2024. After its first game, Full Contact (1991) for the Amiga, the studio followed up with multiple number-one releases on that platform and saw major success with Andy Davidson's Worms in 1995, the resulting franchise of which still remains as the company's primary development output, having developed over 20 entries in it.
Through a management buyout performed by Bestwick, both Robinson and Brown departed from Team17 in 2010, leaving Bestwick as the sole manager. In 2013, Team17 initiated a publishing venture focusing on indie games. The first game to release of this venture was Light (2013). Following a large investment from Lloyds Development Capital in September 2016, Team17 sought corporate expansion through various actions, including the acquisition of Mouldy Toof Studios, the developer behind Team17-published The Escapists (2015), and the hiring of multiple new key staff. In May 2018, the company was organized under the Team17 Group (later renamed Everplay), which became a public company listed on the Alternative Investment Market, valued around £230 million.
The public source identifies “Team17” as video game developer based in Wakefield. This brief keeps that definition visible, then builds a research path around Team17, video and game.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Team17”, the useful work is to connect “video game developer based in Wakefield” to the records capable of establishing context and consequence.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jun 15, 2026. The linked authority identifier is Q1384984. 1 of 2 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 1990, 2024, 1991 and 1995.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Team17”, its source revision and the description used here.
- Expand the search: follow Team17 primary sources, Team17 archive and Team17 research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Team17”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Team17” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.