Telegram RegisterThe public register of Telegram
Telegram profile photo for @BSCTRENDING (LIVE)

Channel

@BSCTRENDING (LIVE)

@BSCTRENDING

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

31,912subscribers

-286 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001807989566
TypeChannel
Username@BSCTRENDING
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live22 August 2026
Measurements held17
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/BSCTRENDING

Growth

31,78732,19831,992.56 August 2026 — 32,198 subscribers6 August 2026 — 32,169 subscribers7 August 2026 — 32,130 subscribers8 August 2026 — 32,106 subscribers9 August 2026 — 32,058 subscribers10 August 2026 — 32,009 subscribers11 August 2026 — 31,978 subscribers12 August 2026 — 31,930 subscribers13 August 2026 — 31,930 subscribers14 August 2026 — 31,889 subscribers15 August 2026 — 31,843 subscribers17 August 2026 — 31,787 subscribers18 August 2026 — 31,863 subscribers19 August 2026 — 31,962 subscribers20 August 2026 — 31,940 subscribers21 August 2026 — 31,947 subscribers22 August 2026 — 31,912 subscribers31,9126 August 202622 August 2026
17 measurements spanning 16 days, net -286. 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 31,725–32,260 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 06:0531,912-35
21 Aug 2026, 01:0531,947+7
20 Aug 2026, 03:0231,940-22
19 Aug 2026, 03:5731,962+99
18 Aug 2026, 07:1131,863+76
17 Aug 2026, 09:5531,787-56
15 Aug 2026, 20:1431,843-46
14 Aug 2026, 06:3531,889-41
13 Aug 2026, 20:3731,930no change
12 Aug 2026, 19:4331,930-48
11 Aug 2026, 20:0131,978-31
10 Aug 2026, 23:3132,009-49
9 Aug 2026, 21:2132,058-48
8 Aug 2026, 23:0232,106-24
7 Aug 2026, 21:3732,130-39
6 Aug 2026, 20:4632,169-29
6 Aug 2026, 08:1832,198first reading

Engagement

No public post preview. We read this entry on 14 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Citation-graph rank

Citation-graph rank — 357 of 1,583,249entries 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.

AVATAR.FI - CHANNEL
@AVATARFICHANNEL · 18
5 posts
𝕏 Original Version I 𝕏OV
@xovofficiall · 64
3 posts
𝗔𝘀𝗵 𝗖𝗮𝗹𝗹𝘇𝘇 🪐
@ashcallzz · 91
2 posts
BNB Callz
@bnbcallz · 118
2 posts
⚽CryptoSoccer channel
@CryptoSoccer_channel · 44
2 posts
Grumpy Token $GRUM Channel
@Grumpy_catBSC · 6
2 posts
Husky Announcement
@HuskyChannelBSC · 7
2 posts
KimociCat Meme Official - KIMOCICAT
@kimocicat · 33
2 posts
LadyPepeCeo Channel| 女佩佩CEO|🪙 Low Cap| 🍴Re-Ownership
@ladypepeceochannel · 18
2 posts
🎅 SANTABNB - $SANTA
@SantaBnbPortal · 62
2 posts
SAX NEWS
@SaxToken · 18
2 posts
The Reservoir Devs
@thereservoirdevs · 10
2 posts
Trekz CALLS DEGEN
@trekzcalls · 3
2 posts
.dead
@whalesuneo · 133
2 posts
King Arthur Call Eth l Bsc
@arthurcall · 47
1 post
Baby Trump Chanel
@BabyTrumpchanel · 83
1 post
Beast | 公平的开始
@beastfairlaunches · 27
1 post
BlocBit
@Blocbit_Network · 28
1 post
Burn Shiba $BUSHI
@BushiPortal · 6
1 post
Buzz Inu Announcement
@buzzinuofficial · 23
1 post
Caelum Calls 🚨
@CaelumCalls · 43
1 post
VENTURE'S @CAPITAL INVS..
@capitalistinvs · 1,912
1 post
Century Call BSC | ETH
@centurycall · 43
1 post
CEO DADDY | Community Token 3/3% tax
@CeoDaddyBsc · 13
1 post
Conan Edogawa Call
@conanedogawacall · 22
1 post
Eth Cash
@Ethcashecosystem · 8
1 post
Ethereum Inu Portal
@EthereumInuPortal · 15
1 post
FAST X BSC 0 TAX RENOUNCED
@FASTX_BSC · 11
1 post
FLOKA Announcements Portal
@floka_portal · 231
1 post
Floki Rich
@FlokiRichBSC · 4
1 post
FoxBonk Announcements Portal
@foxbonkportal · 14
1 post
FROSTBNB ❄️
@Frostbnb · 13
1 post
Gary the Snail Channel
@Gary_the_snail_Channel · 14
1 post
GEAR 5 CHANNEL
@Gear5Channel · 4
1 post
GEM FINDER ( BSC / SOL / ETH )
@GemFinder101 · 117
1 post
🧞‍♂️ Genies Apes 🦍
@Genie_Apes · 754
1 post
Hisokas calls
@hisokascalls · 12
1 post
Laura Caller BSC I SOL I ETH
@laura_call · 40
1 post
Magnet’s Calls | 🧲📞
@magnetsbsc · 9
1 post
MINOCALL
@minocalls · 125
1 post
OctoFrog Portal
@octofrogportal · 15
1 post
Pepe Hulk Bsc | 0 tax play
@PepeHulk_Bsc · 2
1 post
Planet2049 Portal
@planet2049 · 25
1 post
Four-Kun
@portal4kun · 15
1 post
The Prophet
@prophetcall · 84
1 post
Santa BSC 圣诞老人
@SantaBSC666 · 13
1 post
Scary Teddy Bnb Portal
@ScaryTeddyBnbPortal · 12
1 post
Shiba Lord Channel [Audit]
@shibalordbsc · 14
1 post
Shiba Love ❤ 5/5 Tax { Official }
@shibaloveofc · 16
1 post
Spicy Network 🌶️
@spicybscgroup · 1,706
1 post
🕷️🕸️Spiderman Call🕸️🕷️
@spidermancaller · 9
1 post
Squid 2.0 Channel🦑
@squid20channel · 79
1 post
$INU BSC Portal | Low Tax | ETH Version 4M
@TheRealInuBSC · 7
1 post
VALENTINE CAT
@Valentinecat · 4
1 post
Virtual Trader Annoucement 📣
@VirtualTraderANN · 1,481
1 post

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 1,045 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“@BSCTRENDING (LIVE)” (@BSCTRENDING), 31,912 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/BSCTRENDING.

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.