LIVE INDEX·21,054 channels
15:17 UTC
Rank#66 in indexNo safety flags

Будь в Тренде

Join Channel →t.me/trends_ok
Composite score
69.9/100

Cohort-normalised vs 0 channels.

Subscribers
526.9K
7d growth
+45K
30d growth
+7.2K
Last post
—
Tracked since
May 2026
Our read

What is Будь в Тренде?

Будь в Тренде is a Telegram channel. With over 526.9K subscribers, it is a steadily growing community.

Score inputs · v3.2 · 5 componentsMETHODOLOGY →

What goes into the 69.9

×2.0Size
526.9K subs
×1.0Activity
—
×1.5Growth
+45.5K (7d)
×0.5Trust
Clear
×1.0Category fit
—
bars show each component's weight; values are this channel's inputsweighted, then scored out of 100
Activity · last 30 days

Channel activity.

Activity data not yet enriched. MTProto sync runs every ~20 min.

Subscriber growth · 50 days tracked

Subscriber growth · last 90 days

30d90dAll
Subscribers now
526.9K
7-day change
+45K
+9.4%
30-day change
+7.2K
+1.4%
Period peak
579.7K
30 May 2026
Days tracked
50
since 30 May 2026
Trend
↘ Falling
over the period: -9.1%source: channel_history · daily

Frequently asked questions.

What is Будь в Тренде?▾

Будь в Тренде is a Telegram channel. With over 526.9K subscribers, it is a steadily growing community.

How many subscribers does Будь в Тренде have?▾

Будь в Тренде has 526.9K subscribers. It has gained 7.2K subscribers in the last 30 days.

Is Будь в Тренде legit?▾

Будь в Тренде carries no safety flags in our index, though it is not verified by Telegram. Treat unsolicited financial advice with caution.

How do I join Будь в Тренде?▾

Open t.me/trends_ok in the Telegram app, or use the Join Channel button on this page. Telegram Rankings is an independent index and is not affiliated with Будь в Тренде.

Data provenance
Last synced
11h ago
Methodology
v3.2
Sync cadence
~20 min
Days tracked
50

Sources: Telegram MTProto (channel metadata, posts) · channel_history (daily subscriber snapshots). Composite score recomputed each sync against the index cohort.

The network

Part of the CommunityRankings network.

RSSNewsletterAPIStatus