Channel
Бося Печенюшкин
@bosyago
On this record: Growth · Engagement · Cite this entry
4,245subscribers
-47 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002337647363 |
|---|---|
| Type | Channel |
| Username | @bosyago |
| Description | Вещи : @bosyafashion Inst : @bully_bosya TikTok : @bully_bosya |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 11 |
| On Telegram | t.me/bosyago |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 13:20 | 4,245 | no change |
| 3 Sept 2026, 17:20 | 4,245 | -2 |
| 31 Aug 2026, 11:47 | 4,247 | -7 |
| 28 Aug 2026, 13:06 | 4,254 | -1 |
| 25 Aug 2026, 18:52 | 4,255 | -10 |
| 22 Aug 2026, 21:17 | 4,265 | -7 |
| 19 Aug 2026, 17:35 | 4,272 | -4 |
| 16 Aug 2026, 19:09 | 4,276 | -7 |
| 13 Aug 2026, 11:58 | 4,283 | -4 |
| 10 Aug 2026, 21:02 | 4,287 | -5 |
| 7 Aug 2026, 15:12 | 4,292 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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.
“Бося Печенюшкин” (@bosyago), 4,245 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/bosyago.
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.