Telegram RegisterThe public register of Telegram

Bot

INDOVIRALYA

@lNDOVlRALYABOT

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

18,139monthly users

+2,220 since we began measuring on 15 August 2026

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

Register entry

Telegram ID8718625251
TypeBot
Username@lNDOVlRALYABOT
First recorded17 August 2026
Last confirmed live16 September 2026
Measurements held17
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/lNDOVlRALYABOT

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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

15,91919,31417,616.515 August 2026 — 15,919 monthly users17 August 2026 — 17,208 monthly users17 August 2026 — 17,208 monthly users18 August 2026 — 17,789 monthly users20 August 2026 — 17,271 monthly users22 August 2026 — 17,072 monthly users25 August 2026 — 17,039 monthly users27 August 2026 — 17,683 monthly users28 August 2026 — 17,553 monthly users30 August 2026 — 17,860 monthly users31 August 2026 — 18,131 monthly users3 September 2026 — 19,286 monthly users5 September 2026 — 19,293 monthly users9 September 2026 — 19,314 monthly users11 September 2026 — 18,699 monthly users14 September 2026 — 18,276 monthly users16 September 2026 — 18,139 monthly users18,13915 August 202616 September 2026
17 measurements spanning 32 days, net +2,220. 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 15,410–19,823 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
16 Sept 2026, 17:3718,139-137
14 Sept 2026, 21:3918,276-423
11 Sept 2026, 15:1718,699-615
9 Sept 2026, 02:4019,314+21
5 Sept 2026, 21:4119,293+7
3 Sept 2026, 20:4219,286+1,155
31 Aug 2026, 14:4318,131+271
30 Aug 2026, 12:3717,860+307
28 Aug 2026, 11:3317,553-130
27 Aug 2026, 08:2917,683+644
25 Aug 2026, 03:4317,039-33
22 Aug 2026, 08:3717,072-199
20 Aug 2026, 22:3517,271-518
18 Aug 2026, 18:2417,789+581
17 Aug 2026, 21:0217,208no change
17 Aug 2026, 20:5417,208+1,289
15 Aug 2026, 07:0215,919first 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.

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

“INDOVIRALYA” (@lNDOVlRALYABOT), 18,139 monthly users as measured 16 September 2026. Telegram Register, tgregister.com/channel/lNDOVlRALYABOT.

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.