Telegram RegisterThe public register of Telegram
Telegram profile photo for Match money game

Bot

Match money game

@MatchMoney_gamebot

On this record: Topic · Growth · Engagement · Citations · Cite this entry

26,662monthly users

-5,721 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID6806809646
TypeBot
Username@MatchMoney_gamebot
First recorded13 August 2026
Last confirmed live23 October 2026
Measurements held34
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/MatchMoney_gamebot

Topic

Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 83% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

26,56932,84329,7066 August 2026 — 32,383 monthly users7 August 2026 — 32,709 monthly users9 August 2026 — 32,444 monthly users11 August 2026 — 32,458 monthly users13 August 2026 — 32,459 monthly users13 August 2026 — 32,459 monthly users14 August 2026 — 31,967 monthly users17 August 2026 — 32,843 monthly users18 August 2026 — 32,581 monthly users20 August 2026 — 32,345 monthly users22 August 2026 — 32,255 monthly users24 August 2026 — 31,340 monthly users27 August 2026 — 31,240 monthly users28 August 2026 — 31,098 monthly users29 August 2026 — 31,000 monthly users31 August 2026 — 31,177 monthly users1 September 2026 — 31,121 monthly users4 September 2026 — 30,850 monthly users7 September 2026 — 31,285 monthly users10 September 2026 — 32,333 monthly users12 September 2026 — 32,527 monthly users14 September 2026 — 32,574 monthly users15 September 2026 — 32,340 monthly users30 September 2026 — 29,071 monthly users6 October 2026 — 29,888 monthly users10 October 2026 — 30,046 monthly users13 October 2026 — 28,755 monthly users15 October 2026 — 28,128 monthly users17 October 2026 — 27,798 monthly users18 October 2026 — 27,563 monthly users19 October 2026 — 27,103 monthly users20 October 2026 — 26,834 monthly users23 October 2026 — 26,569 monthly users23 October 2026 — 26,662 monthly users26,6626 August 202623 October 2026
34 measurements spanning 79 days, net -5,721. 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 25,628–33,784 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 34
Measured (UTC)Monthly usersChange
23 Oct 2026, 22:5026,662+93
23 Oct 2026, 00:2126,569-265
20 Oct 2026, 18:0826,834-269
19 Oct 2026, 21:0927,103-460
18 Oct 2026, 00:3627,563-235
17 Oct 2026, 03:3027,798-330
15 Oct 2026, 02:2728,128-627
13 Oct 2026, 21:2128,755-1,291
10 Oct 2026, 09:1730,046+158
6 Oct 2026, 06:0029,888+817
30 Sept 2026, 23:4129,071-3,269
15 Sept 2026, 21:2132,340-234
14 Sept 2026, 03:1832,574+47
12 Sept 2026, 13:1832,527+194
10 Sept 2026, 09:1832,333+1,048
7 Sept 2026, 01:5631,285+435
4 Sept 2026, 11:5930,850-271
1 Sept 2026, 22:0331,121-56
31 Aug 2026, 21:5731,177+177
29 Aug 2026, 22:0531,000first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 134 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“Match money game” (@MatchMoney_gamebot), 26,662 monthly users as measured 23 October 2026. Telegram Register, tgregister.com/channel/MatchMoney_gamebot.

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.