Telegram RegisterThe public register of Telegram
Telegram profile photo for DINOMERAHASLI VIRAL

Bot

DINOMERAHASLI VIRAL

@viralpuas2_bot

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

176,003monthly users

+52,458 since we began measuring on 23 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID8700514646
TypeBot
Username@viralpuas2_bot
First recorded24 August 2026
Last confirmed live29 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/viralpuas2_bot

Topic

Other / unclassifiable — 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 24 August 2026 and assigned it the closest of 31 fixed categories, at 55% 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

123,545176,003149,77423 August 2026 — 123,545 monthly users24 August 2026 — 123,545 monthly users25 August 2026 — 136,375 monthly users26 August 2026 — 146,893 monthly users27 August 2026 — 157,251 monthly users28 August 2026 — 166,992 monthly users29 August 2026 — 176,003 monthly users23 August 202629 August 2026
7 measurements spanning 5 days, net +52,458. 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 115,676–183,872 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
29 Aug 2026, 11:07176,003+9,011
28 Aug 2026, 07:36166,992+9,741
27 Aug 2026, 06:07157,251+10,358
26 Aug 2026, 02:45146,893+10,518
25 Aug 2026, 02:34136,375+12,830
24 Aug 2026, 10:20123,545no change
23 Aug 2026, 23:15123,545first 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.

Mentions

Named by 3 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.

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

“DINOMERAHASLI VIRAL” (@viralpuas2_bot), 176,003 monthly users as measured 29 August 2026. Telegram Register, tgregister.com/channel/viralpuas2_bot.

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.