惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

D
Docker
人人都是产品经理
人人都是产品经理
小众软件
小众软件
博客园 - Franky
WordPress大学
WordPress大学
Jina AI
Jina AI
Google DeepMind News
Google DeepMind News
I
InfoQ
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
F
Fortinet All Blogs
博客园 - 【当耐特】
IT之家
IT之家
G
Google Developers Blog
J
Java Code Geeks
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
云风的 BLOG
云风的 BLOG
Recent Announcements
Recent Announcements
有赞技术团队
有赞技术团队
V
Visual Studio Blog
U
Unit 42
阮一峰的网络日志
阮一峰的网络日志
月光博客
月光博客
GbyAI
GbyAI
雷峰网
雷峰网

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Analyzing Steam Games 2025: Genres, Players and User Ratings
Daniel Sánch · 2026-05-09 · via DEV Community

As part of my Master in Data Science & AI at Evolve, I worked on a data analysis project using a real Steam games dataset from 2025.

The goal of the project was to practice the full workflow of a data analysis project: understanding the dataset, cleaning it, transforming variables, creating visualizations and explaining the results in a way that is easy to understand.

The main question I wanted to answer was:

Which Steam genres have the highest average estimated users per game, and which ones have the highest average playtime?

Later, I expanded the analysis with two additional questions:

  • Are there clear differences between free and paid games?
  • Is there any relationship between positive ratings, estimated users and average playtime?

Dataset

The dataset used in this project was Steam Games dataset 2025, downloaded from Kaggle.

It contains around 95,000 games and 47 columns, including information such as:

  • game name;
  • release date;
  • genres;
  • price;
  • estimated owners;
  • average playtime;
  • positive and negative reviews.

One important detail is that the original CSV file is not included in the GitHub repository because it is too large. Instead, the repository explains where the file should be placed in order to reproduce the project.

Data cleaning and transformation

Before analyzing the data, I had to transform several columns.

For example, the estimated_owners column does not contain an exact number of users. It contains ranges such as 100000 - 200000. To work with this variable, I used the midpoint of each range as an approximation.

I also converted average_playtime_forever from minutes to hours, separated games with multiple genres, translated the main genre names into Spanish for the final report, and created summary tables for the analysis.

One of the most important decisions was not to use total estimated users by genre as the main metric. A single game can belong to several genres, so summing users by genre can produce inflated numbers. Instead, I focused on average estimated users per game, which gave a more realistic comparison between genres.

Main findings

Bar chart showing the top Steam genres by average estimated users per game, with Massively Multiplayer leading, followed by Free To Play, Action, RPG and Strategy

Among genres with at least 1,000 games, the genres with the highest average estimated users per game were:

  1. Massively Multiplayer
  2. Free To Play
  3. Action
  4. RPG
  5. Strategy

This showed that popularity is not only about how many games a genre has, but also about how many users an average game in that genre can attract.

Bar chart showing the Steam genres with the highest average playtime, with Simulation leading, followed by Massively Multiplayer, Casual, Adventure and Action

When analyzing average playtime, the ranking changed. The genres with the highest average playtime were:

  1. Simulation
  2. Massively Multiplayer
  3. Casual
  4. Adventure
  5. Action

This was one of the most interesting parts of the project. The genres with the most estimated users were not always the same genres with the highest playtime. In other words, popularity and retention are related, but they are not the same thing.

Free games vs paid games

Comparison chart between free and paid Steam games showing that free games have more average estimated users while paid games have higher average playtime

I also compared free and paid games.

Free games had a higher average number of estimated users. This makes sense because they have no economic barrier to entry, so more users can try them.

However, paid games had higher average playtime. My interpretation is that users who pay for a game may be more likely to spend more time playing it.

Interestingly, the average positive rating was very similar between free and paid games.

Ratings and popularity

In the last part of the project, I analyzed whether positive ratings were strongly related to estimated users or average playtime.

To make this analysis more reliable, I filtered games with at least 50 reviews. This was important because games with very few reviews can have extreme percentages that are not representative.

The result was that positive ratings had a very weak relationship with both estimated users and playtime. A game can be popular without having exceptionally high ratings, and a highly rated game does not necessarily have a massive number of users.

Technical Notes

Some methodological decisions were important for keeping the analysis consistent:

  • estimated_owners was converted from ranges into approximate numeric values using the midpoint of each range.
  • Genres were exploded so that each game could be counted once per genre.
  • Genres with fewer than 1,000 games were filtered out in the main genre comparison to avoid unstable rankings.
  • Games with fewer than 50 reviews were excluded from the ratings analysis to reduce noise.
  • Correlation was interpreted carefully, since it does not imply causation.

What I learned

One of the main things I learned is that in data analysis, getting a result is not enough. The result also needs to make sense.

At one point, the total estimated users by genre produced very large numbers. Instead of accepting them directly, I reviewed the metric and realized that using average users per game was a better approach for the question I was trying to answer.

I also practiced:

  • cleaning and transforming real-world data;
  • creating new variables;
  • working with grouped summaries;
  • building visualizations;
  • explaining limitations;
  • preparing a project to be shared publicly.

I also used AI support during the project, mainly to help structure the work, review code, improve explanations and detect possible interpretation issues. The analysis decisions and final interpretation were reviewed step by step as part of the learning process.

GitHub repository

You can find the full project here:

https://github.com/DaniSanchezDevx/Proyecto-Master-DataScience-Evolve-Daniel-Sanchez-Moares

This academic project was developed during the Master in Data Science & AI at Evolve.

https://evolve.es