Channel
Loop Community
@LoopCommunity1
On this record: Topic · Growth · Engagement · Cite this entry
2,335subscribers
-31 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001781625660 |
|---|---|
| Type | Channel |
| Username | @LoopCommunity1 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/LoopCommunity1 |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 13:54 | 2,335 | +1 |
| 29 Sept 2026, 03:59 | 2,334 | -6 |
| 18 Sept 2026, 18:59 | 2,340 | -6 |
| 17 Sept 2026, 01:19 | 2,346 | no change |
| 14 Sept 2026, 10:20 | 2,346 | -2 |
| 10 Sept 2026, 16:39 | 2,348 | +2 |
| 5 Sept 2026, 05:36 | 2,346 | -4 |
| 1 Sept 2026, 12:38 | 2,350 | -1 |
| 26 Aug 2026, 13:38 | 2,351 | -2 |
| 23 Aug 2026, 18:18 | 2,353 | -7 |
| 16 Aug 2026, 16:23 | 2,360 | -4 |
| 12 Aug 2026, 15:33 | 2,364 | -2 |
| 7 Aug 2026, 10:11 | 2,366 | 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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“Loop Community” (@LoopCommunity1), 2,335 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/LoopCommunity1.
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.