Telegram RegisterThe public register of Telegram

Channel

BSC100x Gems & Presale

@BSC100x

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

3,731subscribers

-3 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-1001412644641
TypeChannel
Username@BSC100x
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/BSC100x

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@BSC100x/375 · this entry5 Mar 2022, 07:48 UTC@gameofgems/3995 Mar 2022, 07:49 UTC1.0072 seconds
@BSC100x/377 · this entry6 Mar 2022, 14:44 UTC@gameofgems/4016 Mar 2022, 14:46 UTC1.0072 seconds
@BSC100x/379 · this entry7 Mar 2022, 14:05 UTC@gameofgems/4037 Mar 2022, 14:33 UTC1.0028 minutes
@BSC100x/381 · this entry8 Mar 2022, 16:53 UTC@gameofgems/4058 Mar 2022, 16:55 UTC1.002 minutes
@BSC100x/383 · this entry11 Mar 2022, 06:30 UTC@gameofgems/40711 Mar 2022, 06:33 UTC1.002 minutes
@BSC100x/371 · this entry3 Mar 2022, 17:57 UTC@gameofgems/3953 Mar 2022, 17:59 UTC0.992 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@gameofgems7 (7/7 hand-verifiable sample passed)1.002 minutesthis entry (70)
@presalehunt5 (5/5 hand-verifiable sample passed)1.003 minutesthis entry (50)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 1 March 2022 to 9 April 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @gameofgems. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

3,7313,7343,732.56 August 2026 — 3,734 subscribers6 August 2026 — 3,734 subscribers10 August 2026 — 3,731 subscribers6 August 202610 August 2026
3 measurements spanning 3 days, net -3. 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,731–3,734 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 01:313,731-3
6 Aug 2026, 23:003,734no change
6 Aug 2026, 22:543,734first reading

Engagement

20 posts held, back to 1 March 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 April 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

9 Apr 2026, 19:19 UTCviews —

The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

19 Mar 2026, 18:04 UTCviews —

The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

26 Mar 2022, 14:18 UTC≈10,400 viewsread 8 August 2026
Photo

@BSC100x INTRODUCING LET’S Earn 💎 Let’s Earn is the first sustainable auto-compounding & auto-staking protocol on the Binance Smart Chain (BEP20). Setting a new standard in the industry where $LETSEARN holders earn high returns just by holding, but in a highly sustainable way compared to existing protocols. The Let’s Earn Protocol gives the $LETSEARN token automatic staking and compounding features. While maintain

11 Mar 2022, 06:30 UTC≈5,350 viewsread 8 August 2026
Photo

Gameyoo announces 3 IDO Launchpads 🔷 Trustpad IDO Date : Mar 18, 11:00 – 16:00 UTC 🔷 Solster IDO Date : Mar 15, 07:00 AM UTC 🔷 DAOStarter IDO Date : TBA Project Overview GameYoo is a bridge for traditional and blockchain gaming. It seeks to rebalance the industry by bringing more traditional gamers into the GameFi fold. GameYoo strongly believes that in the Web 3.0 era, the true ownership of

8 Mar 2022, 16:53 UTC≈4,470 viewsread 8 August 2026
Photo

🔥 Let's take a look at the key events of Hydraverse's triple-IDOs on March 9, 2022 to set your alarm for it ⏰ 📍 Make sure you know how to get your name written in the whitelist results & not miss the sale on 9th March 😉 1️⃣ BinStarter 💎 Whitelist Details ($BSR Staking Required): https://bit.ly/3pyNYAg 🥳 Gleam Competition Here (No $BSR Required): https://gleam.io/g7D8e/binstarter-hydraverse-whitelist 2️⃣ EnjinStar

7 Mar 2022, 14:05 UTC≈4,590 viewsread 8 August 2026
Photo

🕹Colizeum ($ZEUM) is launching on TrustPad! 🚀 A blockchain-based mobile gaming esports ecosystem. 🗓 Sale Date: March 8th 2022 - 11:00 AM UTC on @TrustPad 😎 We are excited to announce our next confirmed IDO Sale coming to TrustPad - Colizeum! 🔥 Colizeum is a virtual Play to Earn driven environment that, similar to Steam, hosts various games and other applications, thereby creating the general outline of a user fu

6 Mar 2022, 14:44 UTC≈4,460 viewsread 8 August 2026
Photo

🟣DOTPad is the home-base focused on unifying the Polkadot ecosystem ⚡️DOTPad has been custom-built to be the 1st to embrace the power of multi-chain interoperability, scalability and decentralization!! 🔥 While we are preparing for the DOTPad IDO, we keep on building! DOTPad currently supports: ✅ Polkadot ✅ Substrate ✅ Kusama ✅ Moonbeam 🎯Are you ready for the biggest launch of 2022? With the biggest raise yet,

Showing the 12 most recent of 20 posts we hold for @BSC100x. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 August 2026 — this entry's latest reading, not the date you are reading this.

“BSC100x Gems & Presale” (@BSC100x), 3,731 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/BSC100x.

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.