Counter-Strike 2 Update
CS2 update · Community Announcements ·
Valve published "Counter-Strike 2 Update" on 30 September 2026 in Community Announcements. In the 7 days after it, prices across four venues moved −1.8 %, −0.4 % beyond the trend of the week before. A read is a comparison with a date, not a cause.
What this update did to prices
to , all 7 days in. Final.
In the 7 days after this post, CS2 prices across Buff, Skinport, CSFloat and Market.CSGO moved −1.8 %.
ShowHide
Take off the trend the week before was already running, and the move is −0.4 %. The biggest move beyond its own trend: cases, at −2.7 %. A comparison with a date, not proof the post caused it.
| Picture | Name | Moved | Trend predicted | Beyond trend | Names |
|---|---|---|---|---|---|
| Whole market−1.8 % | −1.8 % | −1.4 % | −0.4 % | all | |
| Knives−0.7 % | −0.7 % | −0.8 % | +0.1 % | 8478 | |
| Gloves−1.5 % | −1.5 % | −1.3 % | −0.2 % | 1350 | |
The market's move and the first slices are open. The trend and the move beyond it for every slice are on a free account. See every slice's depthOn Steam's own page. We never receive your Steam password or touch your skins.The button opens steamcommunity.com, so check the address bar. Steam may ask for your password there; it never reaches us. Steam only tells us your public ID. Read-only: we can't trade, sell or move a single item. Free, no card. Open this page in Safari or Chrome before signing in through Steam. On a phone Steam may ask for your login here, even with its app signed in. Approve in the app if it asks, then come back to this tab. | |||||
| Cases−3.1 % | −3.1 % | ||||
| Stickers−1.8 % | −1.8 % | ||||
| Souvenirs−4.7 % | −4.7 % | ||||
| Weapon skins−2.2 % | −2.2 % | ||||
ShowHide
Across Buff, Skinport, CSFloat and Market.CSGO, the market moved −1.8 % in the 7 days after the post. The week before the post was running at a pace that predicted −1.4 %, so the post's own share is −0.4 %. An ordinary week reaches ±1.00% on the same measure, so this reads flat. 37% of the skins that moved went up. A comparison with a date, not proof the post caused it.
ShowHide
The index has no read for this window: it needs at least three published days on each side of the post, between 2026-09-23 and 2026-10-07, and the composite has fewer. A post from the last week reads once the days publish.
The item types and weapons the post names, in the order it names them. A word match, not a reading of the post.
[ MISC ]
Various clipping fixes in Rush maps
Read the rest of the postHide
[ CROSSHAIR ]
Fixed visualization of weapon inaccuracy + spread
Added crosshair outline color option
Added a new style "Static Quadrant"
Enabled grenade crosshairs in freeze time for insta-smokes (just hold any grenade attack button)
Allowed negative gaps for classic dynamic crosshair style
Changed the classic dynamic crosshair alpha increments to 0.01
Scope dot scale and color preferences are now included in the new crosshair share code
Changed the format of the crosshair share code to accommodate newly included crosshair settings
Read the post on Steam. Text as Steam's news feed serves it.
How these reads work
How to read the number
ShowHide
The read compares the market index's median over the seven UTC days after the post with the seven days before it, the post's own day left out, and needs at least three published days on each side. The same measure taken on every day of the series is the drift a typical week shows; a read inside that drift is the market doing what it was doing. Neither is proof the post moved anything. The composite is on the market report, every basket under the indexes, and every update is on one list.
How the move is measured
ShowHide
Each venue's daily asks, the last snapshot before the post against the latest one: per venue the trimmed mean change over every name priced on both days, then the mean over the venues. The trend is the same slice's move over the week before the post, scaled to the same number of days. Names counts a name once per venue. A slice with fewer than 20 names on a venue skips that venue.