Telegram RegisterThe public register of Telegram

Channel

Чаты

@chat_gamea

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

19subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002478091662
TypeChannel
Username@chat_gamea
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/chat_gamea

Growth

197 August 2026 — 19 subscribers11 August 2026 — 19 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 18–20 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 17:1619no change
7 Aug 2026, 15:2719first reading

Engagement

20 posts held, back to 27 June 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 16 September 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
50

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

24 Aug 2025, 06:38 UTC159 viewsread 11 August 2026

https://docs.google.com/spreadsheets/d/1HN2GQWYs1zNQ-RcedvUia08trQPXt9_M/edit?usp=sharing&ouid=111102972144857986783&rtpof=true&sd=true

Showing the 12 most recent of 20 posts we hold for @chat_gamea. 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.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

🔗Ссылка на чат: FX💬Аффилиация
@affiliateforex · 5401 postProtraffic | Вход в чат
@protrafficcom · 1311 postPartnerkin | Арбитраж трафика
@thepartnerkin · 30,9541 post

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.

Cite this entry

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“Чаты” (@chat_gamea), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/chat_gamea.

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.