Bot

𝗟𝗗𝗥 | 𝗡𝗨𝗠𝗕𝗘𝗥𝗦

@MVUCIBOT

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

14,710monthly users

+3,096 since we began measuring on 7 August 2026

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

Register entry

Telegram ID	8340273103
Type	Bot
Username	@MVUCIBOT
First recorded	19 August 2026
Last confirmed live	26 August 2026
Measurements held	16
Confirmed unchanged	1 time, most recently 26 August 2026
On Telegram	t.me/MVUCIBOT

Growth

16 measurements spanning 19 days, net +3,096. 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 11,150–15,174 and does not start at zero.

Measurement log — every monthly users count we have recorded
Measured (UTC)	Monthly users	Change
26 Aug 2026, 11:54	14,710	+371
25 Aug 2026, 08:55	14,339	-6
24 Aug 2026, 10:47	14,345	+250
22 Aug 2026, 18:35	14,095	+149
21 Aug 2026, 11:57	13,946	+139
20 Aug 2026, 10:25	13,807	+595
19 Aug 2026, 21:26	13,212	no change
18 Aug 2026, 12:04	13,212	-107
17 Aug 2026, 13:45	13,319	+211
16 Aug 2026, 06:48	13,108	+207
14 Aug 2026, 19:47	12,901	+788
13 Aug 2026, 07:16	12,113	+186
12 Aug 2026, 09:36	11,927	+136
10 Aug 2026, 12:52	11,791	+145
9 Aug 2026, 09:52	11,646	+32
7 Aug 2026, 19:03	11,614	first 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 4 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.

Named by

Channels on the register whose posts name this channel's handle.

𝗟𝗗𝗥 | 𝗡𝗨𝗠𝗕𝗘𝗥𝗦
@M5_qwvv · 22,44087 posts 𝗟𝗗𝗥 | 𝗙𝗜𝗟𝗘𝗦 𝗡𝗨𝗠𝗕𝗘𝗥𝗦
@LDRNUMBERFILES · 1,97117 posts توزيــــع آࢪقــــآم وهـــــمـــيــــه
@abdullh_5_0 · 8951 post ʟᴇᴀᴅᴇʀ
@M5_HOKM · 1731 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 26 August 2026 — this entry's latest reading, not the date you are reading this.

“𝗟𝗗𝗥 | 𝗡𝗨𝗠𝗕𝗘𝗥𝗦” (@MVUCIBOT), 14,710 monthly users as measured 26 August 2026. Telegram Register, tgregister.com/channel/MVUCIBOT.

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.