Compare gaming partners around a defined product and audience.
gamescom connects gaming communities and industry businesses. Consumer discovery and professional partnership goals differ; separate publisher, developer, platform and service-provider research.
Aim to produce: A game-to-partner shortlist and production-risk brief. The comparison below helps you decide what to investigate, which evidence to request and when to advance an option.
Explore the ecosystem, with context.
These figures describe Lensmor research coverage for the matched event record. They are not organizer registrations or an official attendance total.
Research coverage does not certify registration or future attendance.
Industry mix
50-record visible previewLargest stored industry groups within this research scope.
Counts cover 50 visible records, not all 1834 event records. The preview is not a representative survey.
Companies to start with
Illustrative recordsParis-Lyon-Singapour 2026
Information TechnologyPeruMY.GAMES
Performing Arts and Spectator SportsNLPingPong
Credit IntermediationUnited KingdomSelected across different returned industries; not a ranking, an official roster or proof of attendance.
Use resources from the correct edition.
Keep the year and location attached to programme, exhibitor and learning materials. An organizer homepage may now describe another edition; a company research record does not establish participation, access or meeting availability.
Official edition resourcesCheck the edition and location in the organizer’s programme before selecting a session or relying on access.
Official planning resources
Source links retain their original CMS provenance. Confirm the edition, participation, access and specific resource before relying on a listing.
Four ways to test the fit
Lensmor’s suggested research framework for games and interactive entertainment. These are evaluation lenses, not an organizer’s session list or confirmed exhibitor capabilities.
Product and audience
Define platform, audience, gameplay proposition and the intended partnership.
Evidence to requestA playable or recorded example with explicit development status.
Leave withA game-to-partner fit brief.
Production capability
Compare tools, performance, content pipeline and team dependencies.
Evidence to requestA representative build and a production-workflow demonstration.
Leave withA technical and production-risk register.
Publishing and rights
Clarify distribution, territories, intellectual-property boundaries and support.
Evidence to requestA non-confidential publishing or service scope.
Leave withA rights and responsibility checklist.
Commercial evidence
Keep player testing, wishlists, sales and projections separate.
Evidence to requestA metric definition and the conditions under which it was collected.
Leave withAn evidence-led commercial discussion brief.
Work through a concrete decision.
Illustrative exercise: A studio is mapping publishing or service partners for a game project. This is a preparation framework, not a report of an actual purchase, experiment or meeting.
Define the hard constraint
Platform, development status, rights and responsibility fit.
Ask for the deciding evidence
A representative build and a non-confidential partnership scope.
Make the next step explicit
A game-to-partner shortlist and production-risk brief.
Leave with a comparison you can act on.
Keep the requirement, source material, evaluation and follow-up in one file. The worksheet below starts with this edition’s brief and leaves unverified findings blank.

- 01
Write the boundary
Write your actual operating or research context. Separate a requirement that would exclude an option from a preference you could trade off.
- 02
Build a capability shortlist
Start with edition-labelled organizer resources and the scoped company records above. Identify a specific capability and the organization responsible for it.
- 03
Resolve one evidence gap
For the claim that would change your decision, save the original source, its edition, method or configuration, and the condition you still need to verify.
- 04
Assign the follow-through
Agree on a specific document, demonstration, reading task or trial. Save the responsible person and the review point so that the next discussion resolves an open question.
A comparison you can use after Gamescom 2026
Keep one row per organization and specific capability or piece of research. Reuse the same decision criteria when you compare alternatives.
Pass the boundary test
Condition to resolveWrite the context, required capability and the condition that would rule an option out.
Decision ruleKeep an unresolved hard constraint out of the qualified shortlist. Record what evidence could change that decision.
Separate claim from evidence
Material to recordSave the original URL, edition, author or organization, and the method or configuration behind the statement.
Decision ruleLabel each statement as source material, a demonstrated result or your own validated observation. Save its context and limitations.
Check the next handoff
Output to agreeName the document, trial, reading task or specialist discussion that will resolve the next open question.
Decision ruleAssign a person and a specific next artifact. An interesting conversation becomes actionable when that handoff is clear.
Gamescom 2026 research worksheet
A CSV prefilled with this research brief and the four comparison lanes. Organization, evidence, fit and follow-up fields are blank for your own research. No signup required.
Two follow-ups with a clear request
Replace the bracketed details and remove anything that does not match your context.
Request a comparable demonstration
We are comparing options in the context of Gamescom 2026. Our requirement is [specific use case], with this constraint: Platform, development status, rights and responsibility fit. Could you share [the relevant specification or evidence] and show [one representative task] using our stated conditions?
Ask for a scoped next step
Our intended output is: A game-to-partner shortlist and production-risk brief. Before arranging a broad meeting, could you confirm [capability, implementation boundary and responsible role], list [the relevant exclusions or dependencies], and suggest [a bounded trial or comparable proposal]?
Access information for the archive.
This edition has ended. Historical badge details do not establish availability or pricing for a future edition.
Open edition resourcesFrequently asked questions
When and where did this edition take place?
Cologne: August 26–30, 2026 at TBA.
What should I ask before comparing organizations?
A representative build and a non-confidential partnership scope. Keep the method, configuration and context attached to the answer.
What should I leave with after researching Gamescom 2026?
A game-to-partner shortlist and production-risk brief. Record unresolved constraints separately from demonstrated capabilities.
Are the Lensmor figures official attendance counts?
These figures describe Lensmor research coverage for the matched event record. They are not organizer registrations or an official attendance total. Research profiles do not certify a person’s registration, attendance or meeting availability.
Check the details behind your research.
- Lensmor event researchCompany and profile research; individual metrics retain their own source dates above.Source read Oct 15, 2026
- Organizer edition informationEdition-specific organizer material.Source read Oct 17, 2026
Independent Lensmor guide. Editorial advice is separate from organizer facts. Source dates describe saved reads, not a whole-page verification today.






