Channel
πππ³π©π«ππππ₯ π¦
@crouges
On this record: Topic Β· Growth Β· Engagement Β· Telegram's recommendations Β· Cite this entry
1,953subscribers
-38 since we began measuring on 7 September 2026
Risers and fallers across the register Β· movement among entries of 1,000β3,162.
Register entry
| Telegram ID | -1001197359005 |
|---|---|
| Type | Channel |
| Username | @crouges |
| Created | Between 1 March 2018 and 31 July 2021 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 3 times, most recently 5 November 2026 |
| On Telegram | t.me/crouges |
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Oct 2026, 15:49 | 1,953 | -6 |
| 24 Oct 2026, 09:36 | 1,959 | -5 |
| 21 Oct 2026, 11:57 | 1,964 | -3 |
| 18 Oct 2026, 05:37 | 1,967 | -2 |
| 15 Oct 2026, 08:26 | 1,969 | -3 |
| 12 Oct 2026, 11:56 | 1,972 | -2 |
| 5 Oct 2026, 10:55 | 1,974 | -3 |
| 27 Sept 2026, 08:15 | 1,977 | -4 |
| 21 Sept 2026, 01:55 | 1,981 | no change |
| 18 Sept 2026, 01:21 | 1,981 | -11 |
| 14 Sept 2026, 04:17 | 1,992 | -1 |
| 10 Sept 2026, 03:38 | 1,993 | +2 |
| 7 Sept 2026, 15:17 | 1,991 | 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.
Appears in Telegramβs recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly β each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone elseβs query is independent of having been queried itself.
@adamyan_777 Β· 21,779
Telegram ranks this channel #30 of 37 here β alongside 36 others β read 22 September 2026
@gadji_gadjiewww Β· 30,090
Telegram ranks this channel #37 of 37 here β alongside 36 others β read 7 September 2026
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegramβs list for THAT channel, not this one β see how this is measured.
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 30 October 2026 β this entry's latest reading, not the date you are reading this.
βπππ³π©π«ππππ₯ π¦ β (@crouges), 1,953 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/crouges.
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.