Channel
@chatwars
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
423subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002594760223 |
|---|---|
| Type | Channel |
| Username | @chatwars |
| Created | Between 1 March 2025 and 17 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/chatwars |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 17:38 | 423 | +2 |
| 6 Aug 2026, 19:31 | 421 | no change |
| 6 Aug 2026, 06:38 | 421 | first reading |
20 posts held, back to 17 July 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 2 March 2026. An engagement rate over an empty window would be a number about nothing.
255 reactions across 20 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 255 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 255reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 17 July 2025 to 2 March 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @chatwars. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 17 July 2025 to 2 March 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Fortress Battles patch • Fortress battles now run on a fixed bi-weekly schedule: Thursdays 16:00 UTC (starting March 5, 2026). • Fortress registration opens 24h before and closes 1h before the battle. • Fortress owners must keep 5+ defenders registered or the fortress is considered abandoned. • Added Fortress Vault which accumulates gold and GP from PvP activity on purple (Alliance) territory. • Vault payout added o…
👍12
• Rolled back from the Explorers model to the classic 🏰 4-Castle system. • Alliances are now an optional, late-game system (not removed), details in the wiki. • Compatibility reset: all tile ownership wiped, all alliances disbanded, all guild HQ tiles reset. • All players moved to the Forum: you must choose a Castle before continuing. • Castle selection is available to guild leaders (for their guild) and to players w…
👍7
• HQ coordinates have been reset for all guilds. • Double-tap movement in WebApp is now blocked (no accidental second move). Issue #178 #fix @ChatWarsBot
👍9
🦃 Thanksgiving Patch (served fresh) • Map rebalanced: borders reduced from 9 lines down to 7, several distant service spots (Taverns, Shops, Ruins etc) repositioned, resource layout updated. • Domain system revamped: now there is only one domain tile per Campfire - the new 🏜️Desert, introduced in this patch. Desert gives only gold, and all other resource tiles now drop only resources (gold removed from them). • WebA…
👍12
⚔️ Yet Another Claim Fix • Reworked Claim & Trigger rules - simplified branches, trimmed the logic, made it cleaner for both devs and players. Issue #153 Issue #154 • Full explanation article added (Claim & Trigger Rulers). Hopefully, this one sticks. • Fixed explorers unable to quest on non-colored tiles. Issue #130 Issue #100 • Fixed alliance overflow exploit (no more 105/100 members). Issue #128 • Fixed guild kic…
👍9
💊 Prescribed Patch (Take twice a day, no side effects) • Possible fix for Regional battle calculation deadlock. Issue #148 • Improvements to claim/trigger logic - should fix color alliance claims. Issue #154 • Fixed an issue where explorers couldn't quest on tiles adjacent to neutral ones (Tavern, Well, etc). Issue #130 #fix @ChatWarsBot
👍6
🌪️ Small but mighty fixes • Fixed claim ability bug when a colored alliance tries to claim a tile from another colored alliance. Issue #151 • Explorers Regional battle with trigger now assigns teams correctly - Explorers and their allies vs colored alliances. • Fixed Experience and item penalty issue during Regional battles with trigger. #fix @ChatWarsBot
👍16
☕️Warming patch (it’s getting cooler outside) • The Trigger command during a Regional fight now starts a basic Skirmish battle. Issue #124 • Gray Alliances can now claim colored tiles. Issue #127 • Fixed a bug where the tile didn’t change owner from a color alliance to an explorer. Issue #134 • If a colored tile is attacked but the owner doesn't change, no shield is added. #fix @ChatWarsBot
👍10
🩹Continue dealing with the alliance update aftermath • Alliance maintenance should now work if there’s enough gold on the balance. Issue #140 • Guild kick/leave penalties and role assignment prices are dramatically reduced, almost free. Issue #120 • Fixed a bug where battle results with mixed team winners (Explorers and non-colored alliances) were processed incorrectly. Issue #116 • Guild and Alliance kick/leave…
👍11
🌙 midnight update • Ownership of battles between alliances and color factions should now work correctly. I'm 80% poistive. Issue #106 • If you lost valuable items or want to go back to the state before the Alliance release, there's now a way to do that - if you make it to the well. It only works once and can’t be undone. #fix @ChatWarsBot
👍16
🚂 Fix Train has arrived at the station • Quest access validation fixed - Explorers can now do quests on Explorer lands Issue #92 • Alliance gold deposit now possible at any guild HQ or fortress (if your alliance has one) Issue #96 • Control of lands info /worldtop fixed Issue #97 • Trigger command fixed - battles can now only be initiated on borderlands Issue #91 • Fixed player faction distribution in Raid battles I…
👍14
🪲 Found a bug? Report it - get rewarded. For every clear, useful bug report you can receive Echo Orb. To qualify: • One ticket = one problem - keep it simple and focused • Describe what you expected vs what actually happened • Be the first to report it (no dupes) • If it gets fixed and closed, you get the reward ⚠️ Don't forget to include your Telegram @username / ID or in-game name so we know who to thank. Dr…
👍13
Showing the 12 most recent of 20 posts we hold for @chatwars. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank — 23,980 of 1,548,671entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 9 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Chat Wars News Hub” (@chatwars), 423 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/chatwars.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.