Telegram RegisterThe public register of Telegram
Telegram profile photo for Sol new gem (gambles)

Supergroup

Sol new gem (gambles)

@bsc_sol_gem

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

972members

-58 since we began measuring on 7 August 2026

21 online right now

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

Register entry

Telegram ID-1001475697853
TypeSupergroup
Username@bsc_sol_gem
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 October 2026
Last confirmed live30 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 30 October 2026
On Telegramt.me/bsc_sol_gem

Topic

Crypto & trading — 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 85% 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

9721,0301,0017 August 2026 — 1,030 members11 August 2026 — 1,023 members14 August 2026 — 1,021 members17 August 2026 — 1,020 members21 August 2026 — 1,017 members24 August 2026 — 1,011 members27 August 2026 — 1,007 members1 September 2026 — 1,003 members5 September 2026 — 1,000 members10 September 2026 — 998 members26 September 2026 — 994 members6 October 2026 — 991 members9 October 2026 — 991 members14 October 2026 — 987 members22 October 2026 — 980 members30 October 2026 — 972 members7 August 202630 October 2026
16 measurements spanning 84 days, net -58. 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 963–1,039 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
30 Oct 2026, 07:27972-8
22 Oct 2026, 23:29980-7
14 Oct 2026, 20:46987-4
9 Oct 2026, 05:06991no change
6 Oct 2026, 20:56991-3
26 Sept 2026, 03:01994-4
10 Sept 2026, 14:57998-2
5 Sept 2026, 15:201,000-3
1 Sept 2026, 21:351,003-4
27 Aug 2026, 01:441,007-4
24 Aug 2026, 10:551,011-6
21 Aug 2026, 01:131,017-3
17 Aug 2026, 20:231,020-1
14 Aug 2026, 14:181,021-2
11 Aug 2026, 14:171,023-7
7 Aug 2026, 18:221,030first 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 30 October 2026 — this entry's latest reading, not the date you are reading this.

“Sol new gem (gambles)” (@bsc_sol_gem), 972 members as measured 30 October 2026. Telegram Register, tgregister.com/channel/bsc_sol_gem.

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.