Telegram RegisterThe public register of Telegram
Telegram profile photo for (не)Адекватные Тематики 🔞

Channel

(не)Адекватные Тематики 🔞

@bdsmshchiki

Has discussion group

On this record: Topic · Growth · Engagement · Cite this entry

3,470subscribers

-11 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-1001156206222
TypeChannel
Username@bdsmshchiki
Created2 November 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 September 2026
Last confirmed live10 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/bdsmshchiki

Topic

Adult — 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 69% 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

3,4693,4853,4776 August 2026 — 3,481 subscribers9 August 2026 — 3,477 subscribers12 August 2026 — 3,476 subscribers16 August 2026 — 3,477 subscribers19 August 2026 — 3,478 subscribers23 August 2026 — 3,482 subscribers29 August 2026 — 3,485 subscribers31 August 2026 — 3,483 subscribers4 September 2026 — 3,479 subscribers8 September 2026 — 3,479 subscribers9 September 2026 — 3,477 subscribers13 September 2026 — 3,476 subscribers16 September 2026 — 3,473 subscribers1 October 2026 — 3,477 subscribers8 October 2026 — 3,481 subscribers13 October 2026 — 3,483 subscribers17 October 2026 — 3,480 subscribers20 October 2026 — 3,475 subscribers23 October 2026 — 3,476 subscribers26 October 2026 — 3,473 subscribers1 November 2026 — 3,472 subscribers4 November 2026 — 3,469 subscribers10 November 2026 — 3,470 subscribers3,4706 August 202610 November 2026
23 measurements spanning 96 days, net -11. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,467–3,487 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
10 Nov 2026, 06:543,470+1
4 Nov 2026, 12:593,469-3
1 Nov 2026, 21:563,472-1
26 Oct 2026, 07:553,473-3
23 Oct 2026, 11:053,476+1
20 Oct 2026, 03:283,475-5
17 Oct 2026, 07:203,480-3
13 Oct 2026, 22:393,483+2
8 Oct 2026, 08:173,481+4
1 Oct 2026, 17:013,477+4
16 Sept 2026, 20:203,473-3
13 Sept 2026, 02:013,476-1
9 Sept 2026, 04:203,477-2
8 Sept 2026, 13:253,479no change
4 Sept 2026, 07:183,479-4
31 Aug 2026, 23:593,483-2
29 Aug 2026, 03:443,485+3
23 Aug 2026, 10:433,482+4
19 Aug 2026, 19:273,478+1
16 Aug 2026, 19:593,477first 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“(не)Адекватные Тематики 🔞” (@bdsmshchiki), 3,470 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/bdsmshchiki.

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.