Data & Methodology

Operator: Kanaliiga ry (Business ID 2992559-2), registered in Finland. Contact: info@kanaliiga.fi · Discord

Data Sources

Kanahub displays statistics derived from verifiable competition data. Our primary sources include:

FACEIT — CS2 match results, player performance, and league standings where tournaments run on FACEIT.
Steam — player identity (Steam ID and nickname) linked to rosters and match participation.
PUBG / Krafton APIs — battle-royale match telemetry and placement data for PUBG seasons and game days.
Operator-entered data — season schedules, team registrations, roster assignments, reservations, and manual corrections entered by authorized league staff.
Discord — account linking for communication and role assignment within the Kanaliiga Discord server (not used as a stats source).

From Raw Data to Displayed Statistics

Competition data flows through ingestion pipelines into our database, then into the stats you see on Kanahub. We only publish metrics our platform actually tracks and renders, including:

Match scores, maps played, and head-to-head results (CS2)
Player and team leaderboards, season standings, and top-team rankings
Fantasy points and Sortter bracket outcomes where enabled
Map veto history and demo-derived round stats (CS2)
PUBG session placements, kill counts, and team standings
Organization, team, and roster affiliation records

Aggregations (season totals, win rates, placement averages) are computed from stored match and player records. We do not display metrics we have not ingested or calculated.

Accuracy and Limitations

Third-party APIs may update or correct data after initial ingestion; we re-sync on scheduled intervals but brief delays are possible.
Manual operator entries can contain human error; we audit and correct reported issues.
Historical seasons may use different data schemas; older stats may lack fields available in current seasons.
Steam ID anonymization (per our Privacy Policy) replaces identifiers in display but preserves aggregate history.

Report a Correction

If you believe a stat, match result, or roster entry is wrong, contact us with the page URL and details:

info@kanaliiga.fi

Include the match ID, player Steam ID, or team name so we can locate the underlying record quickly.

Data Sources

Kanahub displays statistics derived from verifiable competition data. Our primary sources include:

FACEIT — CS2 match results, player performance, and league standings where tournaments run on FACEIT.

Steam — player identity (Steam ID and nickname) linked to rosters and match participation.

PUBG / Krafton APIs — battle-royale match telemetry and placement data for PUBG seasons and game days.

Operator-entered data — season schedules, team registrations, roster assignments, reservations, and manual corrections entered by authorized league staff.

Discord — account linking for communication and role assignment within the Kanaliiga Discord server (not used as a stats source).

From Raw Data to Displayed Statistics

Competition data flows through ingestion pipelines into our database, then into the stats you see on Kanahub. We only publish metrics our platform actually tracks and renders, including:

Match scores, maps played, and head-to-head results (CS2)

Player and team leaderboards, season standings, and top-team rankings

Fantasy points and Sortter bracket outcomes where enabled

Map veto history and demo-derived round stats (CS2)

PUBG session placements, kill counts, and team standings

Organization, team, and roster affiliation records

Aggregations (season totals, win rates, placement averages) are computed from stored match and player records. We do not display metrics we have not ingested or calculated.

Accuracy and Limitations

Third-party APIs may update or correct data after initial ingestion; we re-sync on scheduled intervals but brief delays are possible.

Manual operator entries can contain human error; we audit and correct reported issues.

Historical seasons may use different data schemas; older stats may lack fields available in current seasons.

Steam ID anonymization (per our Privacy Policy) replaces identifiers in display but preserves aggregate history.