About CrashLog
CrashLog reads crash sites the way a flight recorder reads a flight: after the fact, from the evidence.
Mission
CS GO crash is still the phrase most people search for, and the game is now CS2. Most pages that rank for it give a list of sites with little data behind it. We publish the method, the maths and the evidence, so you can judge a crash site yourself and see how sure we are about each fact.
What we are not
- We are not an operator. We do not run, host or promote any gambling service.
- We are not a financial or legal adviser. Nothing here is advice about money or about the law where you live.
- We are not a way to make money from crash. The house edge is built into every round, and no strategy beats it.
Editorial standards
- Every operator fact has a date. We publish a fact only when we have a source for it.
- Scores come from published weights, calculated by code. Nobody edits a position by hand.
- We never claim a test that was not run.
- Each operator page lists real weaknesses, including for the top-ranked site.
- We fix errors openly. See how corrections work.
Independence
CrashLog is independent and has no commercial relationship with any operator we cover. Our outbound links go only to each operator's official site, with no tracking parameters and no referral or promo codes of our own.
Editorial team
CrashLog is produced by an editorial team that works in four roles. The roles are separate so that nobody checks their own work.
Research
Collects operator facts and independent reports, and records the source and date.
Writing
Turns the evidence into reviews and guides, with the maths computed rather than estimated.
Fact-checking
Re-reads every claim against its source before a page is published or updated.
Corrections
Handles error reports sent through the contact page and updates the date.
Where to go next
Read the CrashLog blog for deep dives, check how we rate for the method, or contact us with a correction.