Telegram RegisterThe public register of Telegram
Telegram profile photo for Strip Chat Tokens Buy

Supergroup

Strip Chat Tokens Buy

@StripChatTokenBuy

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

983members

-43 since we began measuring on 8 August 2026

2 online right now

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001741140429
TypeSupergroup
Username@StripChatTokenBuy
DescriptionTokens Buy Contact @Stripchat_Buy_Token
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 October 2026
Last confirmed live9 October 2026
Measurements held15
On Telegramt.me/StripChatTokenBuy

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 9 October 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 why it has no browse page of its own yet.

Growth

9831,5871,2858 August 2026 — 1,026 members11 August 2026 — 1,025 members14 August 2026 — 1,019 members17 August 2026 — 1,587 members21 August 2026 — 1,586 members24 August 2026 — 1,581 members27 August 2026 — 1,578 members30 August 2026 — 1,574 members2 September 2026 — 1,567 members6 September 2026 — 1,556 members11 September 2026 — 1,549 members15 September 2026 — 1,419 members26 September 2026 — 1,002 members5 October 2026 — 983 members9 October 2026 — 983 members8 August 20269 October 2026
15 measurements spanning 62 days, net -43. 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 892–1,678 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
9 Oct 2026, 05:50983no change
5 Oct 2026, 00:00983-19
26 Sept 2026, 00:551,002-417
15 Sept 2026, 04:011,419-130
11 Sept 2026, 15:581,549-7
6 Sept 2026, 23:171,556-11
2 Sept 2026, 13:481,567-7
30 Aug 2026, 21:251,574-4
27 Aug 2026, 20:431,578-3
24 Aug 2026, 11:331,581-5
21 Aug 2026, 00:411,586-1
17 Aug 2026, 18:081,587+568
14 Aug 2026, 20:181,019-6
11 Aug 2026, 21:051,025-1
8 Aug 2026, 09:301,026first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 October 2026 — this entry's latest reading, not the date you are reading this.

“Strip Chat Tokens Buy” (@StripChatTokenBuy), 983 members as measured 9 October 2026. Telegram Register, tgregister.com/channel/StripChatTokenBuy.

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.