
Channel
Тело как ресурс
@telo_resource
On this record: Growth · Engagement · Cite this entry
6,455subscribers
-25 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 | -1002528751755 |
|---|---|
| Type | Channel |
| Username | @telo_resource |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/telo_resource |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 09:46 | 6,455 | -3 |
| 28 Aug 2026, 19:27 | 6,458 | no change |
| 26 Aug 2026, 08:33 | 6,458 | -1 |
| 23 Aug 2026, 18:15 | 6,459 | -4 |
| 20 Aug 2026, 03:55 | 6,463 | -6 |
| 16 Aug 2026, 20:26 | 6,469 | -6 |
| 13 Aug 2026, 15:38 | 6,475 | -3 |
| 10 Aug 2026, 20:57 | 6,478 | -2 |
| 7 Aug 2026, 17:37 | 6,480 | 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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“Тело как ресурс” (@telo_resource), 6,455 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/telo_resource.
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.