Channel
VSG LINE - MARKET STATS
@Crick
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,157subscribers
-93 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001125756167 |
|---|---|
| Type | Channel |
| Username | @Crick |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/Crick |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 5 Nov 2026, 10:30 | 4,157 | -1 |
| 2 Nov 2026, 03:36 | 4,158 | +10 |
| 30 Oct 2026, 06:39 | 4,148 | -4 |
| 27 Oct 2026, 11:54 | 4,152 | +15 |
| 24 Oct 2026, 02:09 | 4,137 | +3 |
| 20 Oct 2026, 22:56 | 4,134 | -16 |
| 17 Oct 2026, 16:46 | 4,150 | +2 |
| 14 Oct 2026, 21:41 | 4,148 | -11 |
| 11 Oct 2026, 04:37 | 4,159 | -18 |
| 4 Oct 2026, 18:40 | 4,177 | -11 |
| 17 Sept 2026, 03:58 | 4,188 | +3 |
| 13 Sept 2026, 01:20 | 4,185 | -5 |
| 9 Sept 2026, 05:59 | 4,190 | -1 |
| 4 Sept 2026, 22:09 | 4,191 | no change |
| 4 Sept 2026, 08:59 | 4,191 | -5 |
| 31 Aug 2026, 13:41 | 4,196 | -5 |
| 28 Aug 2026, 23:54 | 4,201 | -1 |
| 26 Aug 2026, 10:33 | 4,202 | -7 |
| 23 Aug 2026, 14:06 | 4,209 | -2 |
| 19 Aug 2026, 14:07 | 4,211 | 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.
@OfficialTheGodFather · 42,932
Telegram ranks this channel #12 of 30 here — alongside 29 others — read 16 August 2026
@CSA_T20_CHALLENGE_PREDICTIONS · 34,466
Telegram ranks this channel #16 of 23 here — alongside 22 others — read 18 September 2026
@Aryan_Bettings · 78,388
Telegram ranks this channel #31 of 57 here — alongside 56 others — read 28 August 2026
@upssscpetbystudyforcivilservices · 21,210
Telegram ranks this channel #52 of 63 here — alongside 62 others — read 23 September 2026
This channel appears in 4 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“VSG LINE - MARKET STATS” (@Crick), 4,157 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/Crick.
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.