Telegram RegisterThe public register of Telegram
Telegram profile photo for BSC Checker

Channel

BSC Checker

@bscchecker

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

903subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001346728970
TypeChannel
Username@bscchecker
CreatedBetween 1 March 2018 and 28 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/bscchecker

Growth

9019039026 August 2026 — 901 subscribers6 August 2026 — 901 subscribers14 August 2026 — 903 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net +2. 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 901–903 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 14:56903+2
6 Aug 2026, 23:16901no change
6 Aug 2026, 23:04901first reading

Engagement

15 posts held, back to 28 July 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 15 posts for this entry, the most recent from 17 May 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

17 May 2023, 08:05 UTC780 viewsread 6 August 2026
Photo

❗️Hello everyone. Here is the audit of Pepe Dash AI token, which currently is in the PRESALE phase. ✅ Overall rating of 6.5/10 ❌ Hidden 3% marketing sell fee that can't be changed ❌ Half-assed website and functionalities ❌ Contract hasn't been renounced ✅ Active community and ~900 presale contributors ✅ Active presale marketing More about this in the pdf 👉

Signed al

13 May 2023, 11:45 UTC578 viewsread 6 August 2026

Preparing a new format of audits. Something unseen. Stay tuned.

Signed al

8 Oct 2022, 14:57 UTCviews —

BSC Checker pinned «📌 Token name: Laeeb Football (LAEEB) 📌 BSCLink: https://bscscan.com/address/0x31D91887fabC81690525c25b76022796D4091E8a 📌 PCS Buy link: PRESALE PHASE 📌 LIQUIDITY : PRESALE PHASE ✅ 📌 PROJECT START : Contract was deployed 11 days ago on BSCScan. The initial…»

8 Oct 2022, 14:56 UTC≈1,410 viewsread 6 August 2026

📌 Token name: Laeeb Football (LAEEB) 📌 BSCLink: https://bscscan.com/address/0x31D91887fabC81690525c25b76022796D4091E8a 📌 PCS Buy link: PRESALE PHASE 📌 LIQUIDITY : PRESALE PHASE ✅ 📌 PROJECT START : Contract was deployed 11 days ago on BSCScan. The initial phases of the project (Telegram/Twitter) date back to 22 August 2022. ✅ 📌 PRESALE : PRESALE PHASE ✅ 📌 SITE: https://www.laeeb.football/| SITE IS POORLY CREATED

Signed al

8 Oct 2022, 14:40 UTC869 viewsread 6 August 2026

Coming up with an audit for @laeebfootball, trending presale token

Signed al

4 Oct 2022, 16:07 UTC907 viewsread 6 August 2026

‼️Honest tip for the Pinkie Inu. ‼️ The fees go to marketing wallet (6-8% from ‼️EVERY TRANSACTION‼️ and can be increased to 12% by the developer). This is ‼️A LOT‼️ for the marketing wallet. 50% of total supply is also locked and will be given back to the developer after some time. The presale tokens are ‼️DOUBLE‼️ the amount of the liquidity tokens (IT WILL DUMP HARD ONCE IT LISTS AND PEOPLE START BUYING FROM PA

Signed al

4 Oct 2022, 16:01 UTC852 viewsread 6 August 2026

📌 Token name: Pinkie Inu (PINKIE) 📌 BSCLink: https://bscscan.com/address/0x628e3a6FD5E78564dA8de2aa7386d57B84902380 📌 PCS Buy link: PRESALE PHASE 📌 LIQUIDITY : PRESALE PHASE ✅ 📌 PROJECT START : Contract was deployed 9 days ago on BSCScan. The initial phases of the project (Telegram/Twitter) date back to July 2022. The project has been in the inception phase for a very long time and the presale started on 30th of

Signed al

4 Oct 2022, 15:25 UTC714 viewsread 6 August 2026

‼️‼️‼️ANNOUNCEMENT‼️‼️‼️ As many of you asked me to, I will perform an audit on @pinkieinu1

Signed al

3 Oct 2022, 07:06 UTC782 viewsread 6 August 2026

Send me the projects you want to be audited @npc669

Signed al

6 Nov 2021, 11:47 UTCviews —

BSC Checker pinned «📌 Token name: XSPACEGAME (XSPACE) 📌 BSCLink: https://bscscan.com/token/0x90f16381b25b80e55ae772e7bc7485a4f8ecd7f3 📌 PCS Buy link: PRESALE PHASE 📌 LIQUIDITY : PRESALE PHASE ✅ 📌 PROJECT START : 3 DAYS AGO (listed on bscscan) 📌 H/T ratio : 0.3 ✅ 📌 PRESALE…»

Showing the 12 most recent of 15 posts we hold for @bscchecker. 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.

Citation-graph rank

Citation-graph rank — 614,296 of 1,481,306entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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

“BSC Checker” (@bscchecker), 903 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/bscchecker.

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.