---
title: "Discussion on \"Why Valorant Runs 128-Tick Servers and CS:GO Was Stuck at 64\" | Hashnode"
description: "Discussion on \"Why Valorant Runs 128-Tick Servers and CS:GO Was Stuck at 64\". What tick rate actually means, why it matters for competitive shooters, and how CS2 tried to sidestep the problem entirely"
url: "https://hashnode.com/posts/why-valorant-runs-128-tick-servers-and-cs-go-was-stuck-at-64/6a0c9d3a883727741179a1c6"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why Valorant Runs 128-Tick Servers and CS:GO Was Stuck at 64](https://haseebansari.blog/why-valorant-runs-128-tick-servers-and-cs-go-was-stuck-at-64?utm_source=hashnode&utm_medium=feed)

What tick rate actually means, why it matters for competitive shooters, and how CS2 tried to sidestep the problem entirely

May 19 · 8 min read · haseebansari.blog  
Read the article

## Written by

[Haseeb Ansari](https://hashnode.com/@haseebxd)

@haseebxd · Pakistan

  
[View profile](https://hashnode.com/@haseebxd)

Breaking down complex systems into simple and clear ideas.

Breaking down complex systems into simple and clear ideas.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
