Telegram RegisterThe public register of Telegram
Telegram profile photo for Moliyachi | Oylikbot

Bot

Moliyachi | Oylikbot

@Oylik_hisoblaydigan_bot

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

45,724monthly users

+23,531 since we began measuring on 6 August 2026

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

Register entry

Telegram ID6275698272
TypeBot
Username@Oylik_hisoblaydigan_bot
First recorded14 August 2026
Last confirmed live7 November 2026
Measurements held49
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/Oylik_hisoblaydigan_bot

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 the other topics.

Growth

22,19376,83349,5136 August 2026 — 22,193 monthly users7 August 2026 — 22,487 monthly users8 August 2026 — 22,619 monthly users9 August 2026 — 22,871 monthly users10 August 2026 — 24,887 monthly users11 August 2026 — 25,275 monthly users12 August 2026 — 25,226 monthly users14 August 2026 — 27,139 monthly users14 August 2026 — 27,139 monthly users15 August 2026 — 28,120 monthly users16 August 2026 — 30,550 monthly users17 August 2026 — 31,221 monthly users19 August 2026 — 32,292 monthly users20 August 2026 — 37,561 monthly users23 August 2026 — 39,154 monthly users24 August 2026 — 40,831 monthly users25 August 2026 — 43,942 monthly users26 August 2026 — 45,455 monthly users27 August 2026 — 47,767 monthly users28 August 2026 — 50,160 monthly users31 August 2026 — 57,278 monthly users1 September 2026 — 58,508 monthly users2 September 2026 — 60,138 monthly users5 September 2026 — 62,557 monthly users9 September 2026 — 64,554 monthly users11 September 2026 — 68,494 monthly users13 September 2026 — 69,668 monthly users15 September 2026 — 72,286 monthly users17 September 2026 — 74,137 monthly users25 September 2026 — 71,959 monthly users3 October 2026 — 72,745 monthly users8 October 2026 — 76,833 monthly users12 October 2026 — 75,554 monthly users14 October 2026 — 73,448 monthly users15 October 2026 — 72,938 monthly users17 October 2026 — 73,173 monthly users20 October 2026 — 69,197 monthly users21 October 2026 — 68,553 monthly users22 October 2026 — 67,988 monthly users24 October 2026 — 65,866 monthly users25 October 2026 — 65,795 monthly users28 October 2026 — 60,924 monthly users31 October 2026 — 57,952 monthly users1 November 2026 — 55,040 monthly users2 November 2026 — 54,048 monthly users3 November 2026 — 53,021 monthly users5 November 2026 — 50,271 monthly users6 November 2026 — 47,878 monthly users7 November 2026 — 45,724 monthly users45,7246 August 20267 November 2026
49 measurements spanning 93 days, net +23,531. 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 13,997–85,029 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 49
Measured (UTC)Monthly usersChange
7 Nov 2026, 17:4745,724-2,154
6 Nov 2026, 13:2647,878-2,393
5 Nov 2026, 12:5950,271-2,750
3 Nov 2026, 16:1853,021-1,027
2 Nov 2026, 16:4454,048-992
1 Nov 2026, 18:1155,040-2,912
31 Oct 2026, 15:4657,952-2,972
28 Oct 2026, 16:4560,924-4,871
25 Oct 2026, 16:1665,795-71
24 Oct 2026, 13:0665,866-2,122
22 Oct 2026, 13:3967,988-565
21 Oct 2026, 05:3868,553-644
20 Oct 2026, 02:3869,197-3,976
17 Oct 2026, 04:0173,173+235
15 Oct 2026, 08:0472,938-510
14 Oct 2026, 09:2773,448-2,106
12 Oct 2026, 20:5975,554-1,279
8 Oct 2026, 09:3676,833+4,088
3 Oct 2026, 22:0172,745+786
25 Sept 2026, 02:4071,959first 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 19 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 7 November 2026 — this entry's latest reading, not the date you are reading this.

“Moliyachi | Oylikbot” (@Oylik_hisoblaydigan_bot), 45,724 monthly users as measured 7 November 2026. Telegram Register, tgregister.com/channel/Oylik_hisoblaydigan_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.