Bot

my.vega.ua

@myVegaBot

On this record: Growth · Engagement · Cite this entry

11,681monthly users

-31 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	1055973671
Type	Bot
Username	@myVegaBot
First recorded	21 August 2026
Last confirmed live	26 August 2026
Measurements held	7
Confirmed unchanged	3 times, most recently 26 August 2026
On Telegram	t.me/myVegaBot

Growth

7 measurements spanning 16 days, net -31. 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,647–11,940 and does not start at zero.

Measurement log — every monthly users count we have recorded
Measured (UTC)	Monthly users	Change
24 Aug 2026, 09:52	11,681	-68
21 Aug 2026, 10:15	11,749	no change
19 Aug 2026, 21:47	11,749	-34
16 Aug 2026, 14:45	11,783	-5
13 Aug 2026, 10:17	11,788	-118
10 Aug 2026, 09:00	11,906	+194
7 Aug 2026, 22:31	11,712	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.

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

“my.vega.ua” (@myVegaBot), 11,681 monthly users as measured 24 August 2026. Telegram Register, tgregister.com/channel/myVegaBot.

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.