Telegram RegisterThe public register of Telegram
Telegram profile photo for Raging Furious

Channel

Raging Furious

@RagingFuriousCalls

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

15subscribers

+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-1002431962954
TypeChannel
Username@RagingFuriousCalls
CreatedBetween 1 September 2024 and 6 February 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live5 September 2026
Measurements held2
On Telegramt.me/RagingFuriousCalls

Growth

157 August 2026 — 15 subscribers11 August 2026 — 15 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 14–16 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 23:3115no change
7 Aug 2026, 14:5815first reading

Engagement

20 posts held, back to 6 February 2025the 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 19 April 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
18
Links
8

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

3 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 1 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 February 2025 to 19 April 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

19 Apr 2025, 17:28 UTC58 viewsread 11 August 2026
Photo

$TRUST x3 From my call! ✨ ATH: 30K KOTH REACHED🚀 EwT4hDqgWkCG5jRFJ9ab2GC1iCwkpJ9FUoYKDpiVpump

19 Apr 2025, 16:23 UTC58 viewsread 11 August 2026
Photo

Found $TRUST while hunting some token on pump.fun. it's got a good sarcastic name to it. Goodluck!✨ 10k MC ca: EwT4hDqgWkCG5jRFJ9ab2GC1iCwkpJ9FUoYKDpiVpump NFA/DYOR

18 Apr 2025, 02:41 UTC57 views3 reactionsread 11 August 2026
Photo

🔈$pep on pump.fun "CTO" call Find your entry! MC 27K✨ DYOR/NFA CA:BJEwNZUKRbYrWSDsYz9cMKu7vKFMBrfKts1nKu8spump

🔥3

14 Feb 2025, 21:56 UTC104 viewsread 11 August 2026
Photo

look at that chart $BROC is 3x from my call! ATH: 210K as always DYOR! NFA

14 Feb 2025, 17:27 UTC72 viewsread 11 August 2026
Photo

$BROC is now x2 from my call! Chart is still going strong ATH:150k as always, DYOR! NFA

14 Feb 2025, 15:47 UTC63 viewsread 11 August 2026
Photo

Broccoli Inu Gambled some here! 70k and following the current trend(CZ's Dog)! might get some eyes as always, DYOR! NFA 8JxMw6f8omU9oboG6CMjfkTH4kn2vZkxCDPziEqpGSjD X (Twitter) : https://x.com/BroccoliInu_ Telegram : https://t.me/BroccoliInuPortal Website : https://broccoliinu.com/

13 Feb 2025, 12:31 UTC52 viewsread 11 August 2026
Photo

Just made 7-8x from my call on $CUPID. Charts js getting higher and higher maybe because of the upcoming Valentines Day. As always, DYOR! NFA ATH: 450k

12 Feb 2025, 19:27 UTC96 viewsread 11 August 2026
Photo

Cupid Coin is now 4x from my call! ATH: 265K as always DYOR! NFA

12 Feb 2025, 17:06 UTC62 viewsread 11 August 2026
Photo

Cupid coin is now x2 From my call ATH: 120K as always DYOR!

12 Feb 2025, 15:54 UTC41 viewsread 11 August 2026
Photo

Cupid Coin Gambled some here! Good name and following the upcoming meta. MC: 60K as always, DYOR! https://x.com/CupidCoin_X https://t.me/CupidCoin_Portal https://cupidsol.xyz/

10 Feb 2025, 19:39 UTC68 viewsread 11 August 2026
Photo

$AFROPEPE hits X2 From my call! ath 170k as always, DYOR!

10 Feb 2025, 17:57 UTC48 viewsread 11 August 2026
Photo

Good narrative and current trend. 80k mc! as always DYOR! In the wild world of crypto, $AFROPEPE rises as a true leader! A fusion of African culture, fearless hustle, and unstoppable energy, he’s here to shake the blockchain and lead the meme tribe to greatness, with the advocacy "We’re all gonna make it!" https://t.me/AfroPepe_Portal https://x.com/AfroPepe_Coin https://afropepe.com/

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“Raging Furious” (@RagingFuriousCalls), 15 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/RagingFuriousCalls.

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.