Channel
@bscgemslock
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
74subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001749004188 |
|---|---|
| Type | Channel |
| Username | @bscgemslock |
| Description | Find the Next 100x coins for free. DYOR Please, Auto scan can't detect all scam. ETH :- @ethgemslock |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/bscgemslock |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 21:46 | 74 | no change |
| 7 Aug 2026, 08:53 | 74 | first reading |
20 posts held, back to 25 June 2023 — the 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 20 posts for this entry, the most recent from 25 June 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
🔒 New Token Locked in PinkLockv2 | FuckPutin (FUCKPUTIN) Contract: 0xD3C5001308e2CDF73037e7550271834B68Dca0d1 Liquidity: Unknown 💰 Supply: 1,000,000,000 Locked LP: 5.62% of Token is locked in PinkLockv2 🔑 Owner: 0xe227546BEF7a1f88f5F8b4671184b6F1bAbB67C0 Unlocked Date: 2023-8-26 18:0 PM (in 2 months) 🧾 Tax: 0% BUY | 0% SELL 🍯 HoneyPot: YES ___________________________________ 🔗 Telegram | …
🔒 New LP Locked in Mudra | BUSD GROW (BUSD GROW) Contract: 0x4b40fd7308dA223018b92557Ae86e27A680dbe2e Liquidity: 237,748,699.88 BUSD GROW / 2.03 WBNB 💰 Supply: 1,000,000,000 Locked LP: 99.39% of Liquidity is locked in Mudra 🔑 Owner: 0x8CeB37F800b94a761969A1a6717c40cA9fd5775e Unlocked Date: 2023-7-9 16:0 PM (in 14 days) 🧾 Tax: 10% BUY | 11.9% SELL 🍯 HoneyPot: NO ______________________________…
🔒 New LP Locked in Mudra | BABYPSYOPCAT (BPSYOPCAT) Contract: 0x2f48B682aDe480BD7F6528A40BE4f46048a84c33 Liquidity: 599,060,294.58 BPSYOPCAT / 1.25 WBNB 💰 Supply: 1,000,000,000 Locked LP: 99.50% of Liquidity is locked in Mudra 🔑 Owner: 0xD8d4a0DB14349B70c75f719e3b86Bc87D6C76493 Unlocked Date: 2023-7-1 10:26 AM (in 6 days) 🧾 Tax: 8% BUY | 8.7% SELL 🍯 HoneyPot: NO _____________________________…
🔒 New Token Locked in PinkLockv2 | FuckPutin (FUCKPUTIN) Contract: 0xD3C5001308e2CDF73037e7550271834B68Dca0d1 Liquidity: Unknown 💰 Supply: 1,000,000,000 Locked LP: 15.00% of Token is locked in PinkLockv2 🔑 Owner: 0xe227546BEF7a1f88f5F8b4671184b6F1bAbB67C0 Unlocked Date: 2023-8-26 18:0 PM (in 2 months) 🧾 Tax: 0% BUY | 0% SELL 🍯 HoneyPot: YES ___________________________________ 🔗 Telegram | …
🔒 New LP Locked in PinkLockv2 | HONGKONG COIN (HKCN) Contract: 0xEbB280c8cF5Df9785E74bA89826c58aA8c6B9824 Liquidity: 979,020,000 HKCN / 92 WBNB 💰 Supply: 1,000,000,000 Locked LP: 100.00% of Liquidity is locked in PinkLockv2 🔑 Owner: 0x0d28bD0aE092b00d06F5614c482b47AefA2DC731 Unlocked Date: 2024-7-9 10:31 AM (in a year) 🧾 Tax: 0.1% BUY | 0.1% SELL 🍯 HoneyPot: NO ______________________________…
🔒 New LP Locked in PinkLockv2 | Move Wallet (MOVE) Contract: 0xcB4087d2fB407c98a5294A351738d521C6EbBF00 Liquidity: 900,000,000 MOVE / 0.5 WBNB 💰 Supply: 1,000,000,000 Locked LP: 100.00% of Liquidity is locked in PinkLockv2 🔑 Owner: 0xdd89f61bF2FD283C05a454f3D1A0Cb6b5e7575CF Unlocked Date: +56450-1-22 8:41 AM (in 54427 years) 🧾 Tax: 0% BUY | 0% SELL 🍯 HoneyPot: NO ____________________________…
🔒 New Token Locked in PinkLockv2 | OPN (OPN) Contract: 0xF03495D29c2aF69c64ca824F5008e9F1082E5Ddc Liquidity: Unknown 💰 Supply: 1,000,000,000 Locked LP: 0.00% of Token is locked in PinkLockv2 🔑 Owner: 0x3b7981626e37d2133228DA35FC2725D9Dfde31d9 Unlocked Date: 2023-6-26 8:0 AM (in a day) 🧾 Tax: 0% BUY | 0% SELL 🍯 HoneyPot: YES ___________________________________ 🔗 Telegram | Twitter | 👯 H…
🔒 New LP Locked in PinkLockv2 | Avalanche Protocol (AVP) Contract: 0x32DeD94a6297bB4987213DBb2D3F2294ac5c7C3D Liquidity: 979,020,000 AVP / 36 WBNB 💰 Supply: 1,000,000,000 Locked LP: 100.00% of Liquidity is locked in PinkLockv2 🔑 Owner: 0x5ffC714bFA471c2ce132Ddd5eA350bcA20057e47 Unlocked Date: 2024-7-9 10:17 AM (in a year) 🧾 Tax: 0.1% BUY | 0.1% SELL 🍯 HoneyPot: NO ___________________________…
🔒 New LP Locked in PinkLockv2 | WixCare (WICA) Contract: 0x44A83192Baa5d277Cc724d0865550b6EEd726742 Liquidity: 979,020,000 WICA / 29 WBNB 💰 Supply: 1,000,000,000 Locked LP: 100.00% of Liquidity is locked in PinkLockv2 🔑 Owner: 0xF6dedCeBf18Fa7277C17aeB3C59b5aF41994A248 Unlocked Date: 2024-7-9 10:10 AM (in a year) 🧾 Tax: 0.1% BUY | 0.1% SELL 🍯 HoneyPot: NO ___________________________________ …
🔒 New Token Locked in PinkLockv2 | VibeZoneOnline (VZO) Contract: 0xF394C9F6b719E4756fEa32F7436c43c71cd8297A Liquidity: Unknown 💰 Supply: 10,000,000,000 Locked LP: 20.00% of Token is locked in PinkLockv2 🔑 Owner: 0x98fB052c12052c42fF0d43437860511D83957Eb9 Unlocked Date: 2023-6-30 12:0 PM (in 5 days) 🧾 Tax: 0% BUY | 0% SELL 🍯 HoneyPot: NO ___________________________________ 🔗 Telegram | Tw…
🔒 New LP Locked in PinkLockv2 | BUGS BUNNY (BUGS) Contract: 0x2c73601441d187944Ad51fd15D6D32FB68df705E Liquidity: 891,180,190.17 BUGS / 4.49 WBNB 💰 Supply: 1,000,000,000 Locked LP: 100.00% of Liquidity is locked in PinkLockv2 🔑 Owner: 0x2037c89b337f2f37A254B27caD151CE2E29cC6cE Unlocked Date: 2023-9-28 9:58 AM (in 3 months) 🧾 Tax: 0% BUY | 0% SELL 🍯 HoneyPot: NO ______________________________…
🔒 New Token Locked in PinkLockv2 | VibeZoneOnline (VZO) Contract: 0xF394C9F6b719E4756fEa32F7436c43c71cd8297A Liquidity: Unknown 💰 Supply: 10,000,000,000 Locked LP: 20.00% of Token is locked in PinkLockv2 🔑 Owner: 0x98fB052c12052c42fF0d43437860511D83957Eb9 Unlocked Date: 2024-6-25 12:0 PM (in a year) 🧾 Tax: 0% BUY | 0% SELL 🍯 HoneyPot: NO ___________________________________ 🔗 Telegram | Tw…
Showing the 12 most recent of 20 posts we hold for @bscgemslock. 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 — 281,878 of 1,627,068entries 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.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@bscgemslock named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“BSC Gems Lock” (@bscgemslock), 74 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/bscgemslock.
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.