
Bot
Казань Коттедж видео
@homavipbot
On this record: Growth · Engagement · Cite this entry
37,910monthly users
+14,353 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | 8835809143 |
|---|---|
| Type | Bot |
| Username | @homavipbot |
| First recorded | 15 August 2026 |
| Last confirmed live | 26 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/homavipbot |
Growth
| Measured (UTC) | Monthly users | Change |
|---|---|---|
| 26 Aug 2026, 22:57 | 37,910 | +15,265 |
| 25 Aug 2026, 22:02 | 22,645 | +974 |
| 25 Aug 2026, 00:34 | 21,671 | +4,138 |
| 23 Aug 2026, 10:06 | 17,533 | -1,464 |
| 19 Aug 2026, 19:55 | 18,997 | -1,950 |
| 16 Aug 2026, 18:08 | 20,947 | -1,550 |
| 15 Aug 2026, 20:08 | 22,497 | no change |
| 15 Aug 2026, 02:17 | 22,497 | -2,119 |
| 11 Aug 2026, 17:07 | 24,616 | -327 |
| 8 Aug 2026, 19:34 | 24,943 | +1,386 |
| 7 Aug 2026, 15:01 | 23,557 | 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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“Казань Коттедж видео” (@homavipbot), 37,910 monthly users as measured 26 August 2026. Telegram Register, tgregister.com/channel/homavipbot.
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.