Telegram RegisterThe public register of Telegram
Telegram profile photo for FreeStarLis | бесплатные звёзды ⭐️

Bot

FreeStarLis | бесплатные звёзды ⭐️

@BotStarfreeBot

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

13,835monthly users

+1,388 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 ID8429792307
TypeBot
Username@BotStarfreeBot
First recorded22 August 2026
Last confirmed live4 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/BotStarfreeBot

Growth

10,47314,99412,733.57 August 2026 — 12,447 monthly users10 August 2026 — 12,617 monthly users13 August 2026 — 12,742 monthly users16 August 2026 — 11,828 monthly users19 August 2026 — 10,541 monthly users21 August 2026 — 10,473 monthly users22 August 2026 — 10,473 monthly users23 August 2026 — 11,586 monthly users25 August 2026 — 12,036 monthly users26 August 2026 — 12,273 monthly users28 August 2026 — 13,218 monthly users31 August 2026 — 14,839 monthly users2 September 2026 — 14,994 monthly users4 September 2026 — 13,835 monthly users13,8357 August 20264 September 2026
14 measurements spanning 27 days, net +1,388. 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 9,795–15,672 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
4 Sept 2026, 03:1713,835-1,159
2 Sept 2026, 20:1214,994+155
31 Aug 2026, 18:5914,839+1,621
28 Aug 2026, 19:3313,218+945
26 Aug 2026, 17:4412,273+237
25 Aug 2026, 17:2812,036+450
23 Aug 2026, 06:1411,586+1,113
22 Aug 2026, 18:2110,473no change
21 Aug 2026, 19:5810,473-68
19 Aug 2026, 16:5310,541-1,287
16 Aug 2026, 16:5511,828-914
13 Aug 2026, 13:2712,742+125
10 Aug 2026, 15:3612,617+170
7 Aug 2026, 17:3212,447first 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 16 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 4 September 2026 — this entry's latest reading, not the date you are reading this.

“FreeStarLis | бесплатные звёзды ⭐️” (@BotStarfreeBot), 13,835 monthly users as measured 4 September 2026. Telegram Register, tgregister.com/channel/BotStarfreeBot.

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.