Channel
•|BIIGWESTT CHANNEL|•
@biigwestt
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,960subscribers
-109 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001912430964 |
|---|---|
| Type | Channel |
| Username | @biigwestt |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 2 times, most recently 5 November 2026 |
| On Telegram | t.me/biigwestt |
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 15 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 |
|---|---|---|
| 2 Nov 2026, 08:17 | 2,960 | -3 |
| 30 Oct 2026, 15:36 | 2,963 | -9 |
| 27 Oct 2026, 19:09 | 2,972 | -1 |
| 25 Oct 2026, 01:16 | 2,973 | -3 |
| 22 Oct 2026, 10:50 | 2,976 | -10 |
| 18 Oct 2026, 22:27 | 2,986 | -5 |
| 15 Oct 2026, 19:17 | 2,991 | -3 |
| 12 Oct 2026, 16:47 | 2,994 | -4 |
| 5 Oct 2026, 22:42 | 2,998 | -7 |
| 28 Sept 2026, 07:16 | 3,005 | -19 |
| 18 Sept 2026, 23:57 | 3,024 | -7 |
| 14 Sept 2026, 12:59 | 3,031 | -10 |
| 11 Sept 2026, 00:42 | 3,041 | no change |
| 10 Sept 2026, 15:41 | 3,041 | -8 |
| 5 Sept 2026, 02:16 | 3,049 | -10 |
| 1 Sept 2026, 07:38 | 3,059 | -4 |
| 29 Aug 2026, 17:34 | 3,063 | -6 |
| 26 Aug 2026, 20:30 | 3,069 | 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.
@soheil_mixx · 39,054
Telegram ranks this channel #11 of 50 here — alongside 49 others — read 5 September 2026
@sadddsongs · 18,778
Telegram ranks this channel #14 of 73 here — alongside 72 others — read 4 October 2026
@radioKoob · 21,366
Telegram ranks this channel #19 of 73 here — alongside 72 others — read 1 October 2026
@ahngefarsi · 83,469
Telegram ranks this channel #19 of 71 here — alongside 70 others — read 26 August 2026
@hadimusiic · 41,271
Telegram ranks this channel #58 of 66 here — alongside 65 others — read 30 August 2026
This channel appears in 5 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“•|BIIGWESTT CHANNEL|•” (@biigwestt), 2,960 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/biigwestt.
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.