CS2 Majors: official calendars, invitations and format checks

A CS2 Major has an edition, an organiser and a rule set. The word Major alone does not establish its exact match format, invitation date or venue schedule. Use this guide to separate the official calendar from ranking snapshots and to record the upcoming Singapore event with its stated scope.

Use the organiser’s current event page

On the 23 October 2026 reference check, PGL’s Singapore event page states 24 November–13 December 2026, 32 teams and a best-of-five Grand Final. Its final four days are assigned to Singapore Indoor Stadium. These are announced event details, not results. A ticket for an arena session should not be interpreted as access to every earlier stage. Before arranging attendance, reopen the organiser’s page and follow its ticket link. Save the particular session date and venue in your plan; the tournament’s overall date range is too broad to serve as an admission instruction.

Separate invitations from people appearing in the bracket

The Valve Major supplemental rulebook describes 32 entries: 16 invited into Stage 1, eight into Stage 2 and eight into Stage 3. This is an entry structure, not three additional independent fields of 32 teams. Its regional and roster provisions should be read with the edition’s confirmed participant notice. Do not treat a ranking screenshot as proof that an invitation has been accepted. A team name can also survive a roster change, so preserve the actual roster reference and the date of the relevant invitation. If the organiser has not confirmed a place, label it unconfirmed in your own notes.

Data table with a clear evidence hierarchy

CS2 Major references checked 23 October 2026
FieldOfficial referenceInterpretation
Singapore date window24 November–13 December 2026, PGLAnnounced future dates; reconfirm before travel
Singapore field32 teams, PGLOverall event field
Generic invitation split16 / 8 / 8, ValveEntries into Stages 1 / 2 / 3
Singapore Grand FinalBest of five, PGLEvent-specific match length

The generic rulebook contains older edition examples and match-length text. Do not apply every paragraph mechanically to a later event when its organiser publishes a different explicit format. Resolve that difference with the current event rules and a dated organiser clarification. Record which document supports each field instead of silently combining the most convenient parts of several pages.

Read rankings as dated observations

Valve’s Regional Standings repository is the primary starting point for the ranking system and its dated resources. A ranking is not a completed tournament table, and a live ranking is not necessarily the snapshot used for invitations. For your own comparison, store the ranking date, region, roster identity and source file separately. Compare like with like: moving between a regional list and a global list changes the set of teams being ranked. If a club changes branding, keep an alias field instead of creating a false new team or merging different line-ups without explanation.

A practical series and map comparison

Imagine two fictional teams each winning one best-of-three series. One wins 2–0 and the other 2–1. Both have one series victory, but the first has two map wins from two maps and the second two from three. That difference describes these samples; it does not prove which team is stronger overall. Record map names, opponents and the stage before comparing map records. A withdrawn team or a match awarded administratively should receive a status field. Do not invent round scores to make the table look complete. For a historical comparison, preserve the event’s actual game version and map pool instead of applying the current one retrospectively.

Checklist for a Major viewing or attendance plan

  • Confirm the year, organiser, stage and session. Keep the announcement date separate from the date on which you last checked it.
  • Use the event-specific format for that stage. Check the final separately, because its best-of length can differ from earlier rounds.
  • Follow official links to viewing channels and ticketing. A community event calendar can help discovery but should not override the organiser’s updated notice.
  • After any rescheduling, update your personal reminder and retain the change note. Confirm the venue, local time and admission rules again before setting off.

Frequently asked questions

Does the generic Valve rulebook settle every 2026 match length?

No. Its retrieved version includes older examples. Use it for the provisions that apply and check the current organiser’s edition-specific rules; PGL explicitly describes Singapore’s final as best of five.

Does a VRS ranking guarantee a Major place?

A ranking snapshot and an accepted invitation are separate records. Check the relevant rules and organiser confirmation, including roster eligibility and the edition’s invitation date.

Why does this guide use 24 November for Singapore?

That is the date stated on PGL’s own event page at the reference check. Reopen that primary source for any revision before booking; this guide does not freeze a future schedule.

Sources and verification