1 Aug 2026, 13:49 UTC5 viewsread 10 August 2026
https://t.me/ys0seri0us_bots
Channel
Call Trends
@calltrends
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
38subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001918537219 |
|---|---|
| Type | Channel |
| Username | @calltrends |
| Description | Call Trends the channel where you see what projects are trending daily on ETH & BSC! NFA - DYOR! If you wanna list your channel contact @silver_dagger |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/calltrends |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 20:45 | 38 | no change |
| 7 Aug 2026, 10:55 | 38 | first reading |
Engagement
20 posts held, back to 31 May 2024 — 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 page of 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 1 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈2
- Links
- ≈5,610
Lifetime counters from Telegram’s own channel header, read 10 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.
Recent posts
11 Jun 2026, 22:16 UTCviews —
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 20 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
3 Jun 2024, 05:56 UTCviews —
Call Trends pinned a photo
3 Jun 2024, 05:56 UTC73 viewsread 10 August 2026
Photo
🤖 TROJAN - SOLANA TRADING BOT 🤖 📢 Ready to maximize your trading gains? Meet Solana's ultimate Telegram Bot! Snipe new projects, automate DCA, mirror big whales' wallets, do limit orders and more. Invite friends for 10% fee savings. Trade over $10k weekly for a 35% referral fee share, or get a lifetime 25% share. Don't miss out, join today! ▶️ A MUST HAVE FOR EVERY SOLANA TRADER ▶️ Join the TrojanBot "Here"
2 Jun 2024, 19:42 UTC65 viewsread 10 August 2026
📊 Aggregated Message 🚀🚀 $SHOT is on fire, just received calls from 1 callers 🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥 👨💻 Called by: 1. 𝐓𝐄𝐒𝐋𝐀 𝐂𝐀𝐋𝐋𝐒 𝐎𝐅𝐅𝐈𝐂𝐈𝐀𝐋 | 02 Jun 19:42
2 Jun 2024, 19:42 UTC57 viewsread 10 August 2026
(First Call) $SHOT just now got the first call from: 𝐓𝐄𝐒𝐋𝐀 𝐂𝐀𝐋𝐋𝐒 𝐎𝐅𝐅𝐈𝐂𝐈𝐀𝐋 (0 seconds ago) Total calls: 1 Token Address: 0x398b98401b502c216e1844ef1aea6d03824477ae
2 Jun 2024, 04:45 UTC54 viewsread 10 August 2026
(Update) $HONK just now got one more call from: BlockChainBrothers Calls {BCB} (0 seconds ago) Total calls: 1 Token Address: 0xd8e8438cf7beed13cfabc82f300fb6573962c9e3
2 Jun 2024, 04:45 UTC50 viewsread 10 August 2026
(Update) $HONK just now got one more call from: BlockChainBrothers Calls {BCB} (0 seconds ago) Total calls: 1 Token Address: 0xd8e8438cf7beed13cfabc82f300fb6573962c9e3
2 Jun 2024, 03:20 UTC41 viewsread 10 August 2026
📊 Aggregated Message 🚀🚀 $HONK is on fire, just received calls from 1 callers 🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥 👨💻 Called by: 1. BlockChainBrothers Calls {BCB} | 02 Jun 03:20
2 Jun 2024, 03:20 UTC32 viewsread 10 August 2026
(First Call) $HONK just now got the first call from: BlockChainBrothers Calls {BCB} (0 seconds ago) Total calls: 1 Token Address: 0xd8e8438cf7beed13cfabc82f300fb6573962c9e3
1 Jun 2024, 22:39 UTC21 viewsread 10 August 2026
(Update) $APUGURL just now got one more call from: BlockChainBrothers Calls {BCB} (0 seconds ago) Total calls: 1 Token Address: 0x069f01cdd1e32d7bab5fc81527df191835136c9d
1 Jun 2024, 22:38 UTC16 viewsread 10 August 2026
(Update) $APUGURL just now got one more call from: BlockChainBrothers Calls {BCB} (0 seconds ago) Total calls: 1 Token Address: 0x069f01cdd1e32d7bab5fc81527df191835136c9d
Showing the 12 most recent of 20 posts we hold for @calltrends. 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
Names
Channels on the register whose handles appear in this channel's posts.
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.
“Call Trends” (@calltrends), 38 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/calltrends.
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.