Channel
S'lil vibe🌶
@badsweartimes
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,381subscribers
+40 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001964355342 |
|---|---|
| Type | Channel |
| Username | @badsweartimes |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/badsweartimes |
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 14 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 12:20 | 3,381 | +4 |
| 2 Nov 2026, 02:21 | 3,377 | +1 |
| 30 Oct 2026, 03:57 | 3,376 | -11 |
| 27 Oct 2026, 03:40 | 3,387 | +8 |
| 24 Oct 2026, 00:29 | 3,379 | -1 |
| 14 Oct 2026, 07:46 | 3,380 | +6 |
| 10 Oct 2026, 17:39 | 3,374 | +2 |
| 4 Oct 2026, 18:56 | 3,372 | +11 |
| 24 Sept 2026, 22:21 | 3,361 | -7 |
| 16 Sept 2026, 23:20 | 3,368 | +2 |
| 13 Sept 2026, 09:01 | 3,366 | +1 |
| 9 Sept 2026, 04:57 | 3,365 | +8 |
| 9 Sept 2026, 00:09 | 3,357 | no change |
| 4 Sept 2026, 01:01 | 3,357 | +2 |
| 31 Aug 2026, 13:17 | 3,355 | +5 |
| 28 Aug 2026, 05:15 | 3,350 | +8 |
| 25 Aug 2026, 04:03 | 3,342 | -1 |
| 22 Aug 2026, 00:27 | 3,343 | +2 |
| 21 Aug 2026, 12:30 | 3,341 | 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.
@Icouldnttellyou · 20,354
Telegram ranks this channel #19 of 63 here — alongside 62 others — read 29 September 2026
@urfavhelliya · 22,615
Telegram ranks this channel #19 of 56 here — alongside 55 others — read 21 September 2026
@abi_magazine · 20,111
Telegram ranks this channel #28 of 82 here — alongside 81 others — read 27 September 2026
@llbeelll · 29,602
Telegram ranks this channel #35 of 64 here — alongside 63 others — read 11 September 2026
@lldalall · 22
Telegram ranks this channel #47 of 63 here — alongside 62 others — read 21 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“S'lil vibe🌶” (@badsweartimes), 3,381 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/badsweartimes.
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.