Telegram RegisterThe public register of Telegram
Telegram profile photo for 捆绑.紧缚.地牢😈!(绳艺

Channel

捆绑.紧缚.地牢😈!(绳艺

@shibariD

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

3,756subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001924984508
TypeChannel
Username@shibariD
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 September 2026
Last confirmed live9 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/shibariD

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 77% 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,7333,7703,751.57 August 2026 — 3,760 subscribers10 August 2026 — 3,759 subscribers13 August 2026 — 3,755 subscribers16 August 2026 — 3,753 subscribers19 August 2026 — 3,749 subscribers23 August 2026 — 3,742 subscribers26 August 2026 — 3,739 subscribers28 August 2026 — 3,735 subscribers31 August 2026 — 3,734 subscribers4 September 2026 — 3,733 subscribers6 September 2026 — 3,733 subscribers10 September 2026 — 3,734 subscribers13 September 2026 — 3,750 subscribers17 September 2026 — 3,754 subscribers4 October 2026 — 3,770 subscribers11 October 2026 — 3,763 subscribers14 October 2026 — 3,760 subscribers17 October 2026 — 3,759 subscribers21 October 2026 — 3,762 subscribers24 October 2026 — 3,766 subscribers27 October 2026 — 3,762 subscribers30 October 2026 — 3,758 subscribers2 November 2026 — 3,755 subscribers9 November 2026 — 3,756 subscribers3,7567 August 20269 November 2026
24 measurements spanning 94 days, net -4. 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,727–3,776 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
9 Nov 2026, 03:003,756+1
2 Nov 2026, 19:383,755-3
30 Oct 2026, 22:363,758-4
27 Oct 2026, 23:563,762-4
24 Oct 2026, 14:503,766+4
21 Oct 2026, 07:583,762+3
17 Oct 2026, 23:163,759-1
14 Oct 2026, 21:193,760-3
11 Oct 2026, 21:393,763-7
4 Oct 2026, 22:563,770+16
17 Sept 2026, 12:393,754+4
13 Sept 2026, 10:423,750+16
10 Sept 2026, 00:413,734+1
6 Sept 2026, 23:143,733no change
4 Sept 2026, 11:203,733-1
31 Aug 2026, 16:463,734-1
28 Aug 2026, 23:143,735-4
26 Aug 2026, 05:253,739-3
23 Aug 2026, 10:253,742-7
19 Aug 2026, 21:223,749first 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 9 November 2026 — this entry's latest reading, not the date you are reading this.

“捆绑.紧缚.地牢😈!(绳艺” (@shibariD), 3,756 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/shibariD.

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.