> For the complete documentation index, see [llms.txt](https://ludo-cities.gitbook.io/ludo-cities-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ludo-cities.gitbook.io/ludo-cities-whitepaper/game/market-statics.md).

# Market Statics

### **Comparable Games Overview**

A look at the top-performing Ludo and casual board games globally shows strong demand, massive retention, and proven monetization.

| **Game App**   | **Downloads (Play Store)**                         | **DAUs / MAUs**                                | **Known Revenue (Last Public Data)**                                   |
| -------------- | -------------------------------------------------- | ---------------------------------------------- | ---------------------------------------------------------------------- |
| **Ludo King**  | **1.13 Billion** total downloads (as of Sept 2024) | \~**32M DAUs**; \~**142M MAUs** at peak (2020) | **US $20M** revenue in 2020                                            |
| **Yalla Ludo** | Part of Yalla Group platform                       | **41.4M MAUs** in Q4 2024                      | Gaming revenue: **US $30.8M** in Q4 2024; **US $113.6M** total in 2024 |
| **Ludo Star**  | **100M+** downloads                                | **13M+** users                                 | (Revenue not publicly disclosed)                                       |

#### Key Insight

➡️ **Ludo King is the 5th most downloaded game in the world**, demonstrating the global demand for Ludo-style casual games.\
➡️ Games in this genre consistently reach **tens of millions** of Monthly Active Users and generate **multi-million dollar annual revenues**.

***

## **Web3 Gaming Market Projection**

| Year                 | Market Size       |
| -------------------- | ----------------- |
| **2022**             | **$4.6 Billion**  |
| **2027 (Projected)** | **$65.7 Billion** |
| **CAGR**             | **70%+**          |

#### Additional Web3 Market Signals

* **Player Spending:** Web3 gamers show **much higher engagement**, regularly purchasing NFTs, tokens, skins, and participating in P2E ecosystems.
* **VC Investment:** Web3 gaming raised **$4.5B in 2022** alone (DappRadar x BGA Report).
* **Trend:** Web3 gaming is the **fastest-growing segment in the blockchain industry**.

***

## **Positioning of LudoCities**

### **The First Web3 Ludo Game**

There is currently **no leading blockchain-powered Ludo game** in the global market.

This creates a **blue-ocean opportunity** where LudoCities becomes:

* **The category creator**
* **The first-mover advantage holder**
* **The only Web3 game in a genre with billions of players**
* **A bridge between Web2 casual gaming and Web3 token economies**

#### Why This Matters

* Ludo already has **proven product-market fit** with billions of players.
* Web3 adds **ownership, rewards, tradable assets**, and **economic incentives**.
* No competition yet = **high virality potential & massive early user capture**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ludo-cities.gitbook.io/ludo-cities-whitepaper/game/market-statics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.