Telegram RegisterThe public register of Telegram
Telegram profile photo for Ивенты FunTime | Ивенты фантайм | FunTime | Бот

Bot

Ивенты FunTime | Ивенты фантайм | FunTime | Бот

@FunTimeEventsBot_bot

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

15,047monthly users

+455 since we began measuring on 6 August 2026

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

Register entry

Telegram ID7553985196
TypeBot
Username@FunTimeEventsBot_bot
First recorded18 August 2026
Last confirmed live24 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/FunTimeEventsBot_bot

Growth

14,59215,57015,0816 August 2026 — 14,592 monthly users8 August 2026 — 14,883 monthly users10 August 2026 — 14,857 monthly users11 August 2026 — 14,616 monthly users13 August 2026 — 14,973 monthly users14 August 2026 — 15,014 monthly users16 August 2026 — 15,031 monthly users17 August 2026 — 15,101 monthly users18 August 2026 — 15,002 monthly users18 August 2026 — 15,002 monthly users19 August 2026 — 15,359 monthly users20 August 2026 — 15,435 monthly users22 August 2026 — 15,570 monthly users23 August 2026 — 15,388 monthly users24 August 2026 — 15,047 monthly users15,0476 August 202624 August 2026
15 measurements spanning 18 days, net +455. 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 14,445–15,717 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
24 Aug 2026, 23:5515,047-341
23 Aug 2026, 13:0715,388-182
22 Aug 2026, 01:5915,570+135
20 Aug 2026, 19:4315,435+76
19 Aug 2026, 17:0215,359+357
18 Aug 2026, 20:5015,002no change
18 Aug 2026, 13:2715,002-99
17 Aug 2026, 13:4815,101+70
16 Aug 2026, 07:5415,031+17
14 Aug 2026, 21:3615,014+41
13 Aug 2026, 11:4714,973+357
11 Aug 2026, 09:5214,616-241
10 Aug 2026, 13:1814,857-26
8 Aug 2026, 14:0114,883+291
6 Aug 2026, 20:1714,592first 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 5 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 24 August 2026 — this entry's latest reading, not the date you are reading this.

“Ивенты FunTime | Ивенты фантайм | FunTime | Бот” (@FunTimeEventsBot_bot), 15,047 monthly users as measured 24 August 2026. Telegram Register, tgregister.com/channel/FunTimeEventsBot_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.