Telegram RegisterThe public register of Telegram
Telegram profile photo for InfiniteWhale

Channel

InfiniteWhale

@infinitewhale

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

844subscribers

+5 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-1001361569221
TypeChannel
Username@infinitewhale
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/infinitewhale

Growth

839844841.57 August 2026 — 839 subscribers7 August 2026 — 839 subscribers15 August 2026 — 844 subscribers7 August 202615 August 2026
3 measurements spanning 9 days, net +5. 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 838–845 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 17:17844+5
7 Aug 2026, 22:19839no change
7 Aug 2026, 01:17839first reading

Engagement

20 posts held, back to 5 May 2026the 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.

ERR · 30 days
4.03%
avg views ÷ 844 subscribers
Avg views / post
34.0
2 posts measured
Reaction rate
2.13%
reactions ÷ views · ER floor
Posts in window
2
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 August 2026
Posts held20 (5 May 20262 August 2026)
Views total68
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 01:17 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

454 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 15.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤩6815.0%
🎉6614.5%
👏6614.5%
🏆6213.7%
🍾5712.6%
🙏5512.1%
👍449.69%
🥰357.71%
🔥10.22%

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 16 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 454reactions 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 5 May 2026 to 2 August 2026, 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

2 Aug 2026, 08:37 UTC21 viewsread 7 August 2026
Video

Achievement Unlocked: Back In Town 🤠 @infinitewhale made a x2+ call for LOADING CAT on ROBINHOOD after a time away from the chain. $101K ➡️ $204K 👁 View Call 📊 View Stats ➡️Catch plays like this early with SpyDefi Filters!

Signed Uncle Ripple I Infinitewhale

26 Jul 2026, 07:53 UTC47 views1 reactionsread 7 August 2026

Aped looking cat on RB chain @ 100k mcap 0x792e272ee45cfbea4d43df8180098fd8f857bd94

🔥1

Signed Uncle Ripple I Infinitewhale

10 Jul 2026, 12:42 UTC62 viewsread 7 August 2026

Aped juggernaut on Robinhood 0xf2915d1e3C1B0c769d0c756Ec43F1c1f6c99cD03

Signed Uncle Ripple I Infinitewhale

5 Jul 2026, 12:38 UTC106 views25 reactionsread 7 August 2026

Aped CZ @ 70m https://dexscreener.com/bsc/0xd55Fa2c5E63eCAC3A158ca3fED4c8C2185ED45b2

🎉4👏4🤩4🙏4🏆3🍾2👍2🥰2

Signed Uncle Ripple I Infinitewhale

4 Jul 2026, 01:32 UTC205 views30 reactionsread 7 August 2026

Freedom 250 @ 300k mcap J9xS5vH4W9WnxtbJD4AshJsmHLniPFDq8vXa556apump

🎉5🤩5🙏5🍾4🏆4👏3👍2🥰2

Signed Uncle Ripple I Infinitewhale

3 Jul 2026, 22:41 UTC200 views26 reactionsread 7 August 2026

Apeing robinhood chain with $hoodrat @200k mcap https://dexscreener.com/robinhood/0xd5278381d510c134c94aeb358ed097d7abc68766

👍6🤩6🍾4🎉3🙏3🏆2🥰2

Signed Uncle Ripple I Infinitewhale

3 Jul 2026, 13:30 UTC186 views25 reactionsread 7 August 2026

$America - 500k mcap Loading up again on America Is Back @ 500k, people talking about it again. More importantly, altcoin are outperforming btc. https://dexscreener.com/solana/E9Pq8h8CN2cK3uZxsQ6LhkwGbyaAnLgAh4YwczNqdU3f

🎉4👏4🤩4🍾3👍3🙏3🏆2🥰2

Signed Uncle Ripple I Infinitewhale

3 Jul 2026, 13:25 UTC178 views1 reactionsread 7 August 2026
Photo

BITCOIN Rose by +6%, now seats at 62,000 Mulla

🥰1

Signed Uncle Ripple I Infinitewhale

28 Jun 2026, 17:19 UTC184 views29 reactionsread 7 August 2026
Forwarded from @overdose_gems_calls

The Ethereum Foundation just announced they're firing 20% of their staff. In traditional markets, when a company announces layoffs and restructuring the stock pumps almost EVERY SINGLE TIME. Wall Street sees it as the company getting serious, Cutting the bloat, reducing overhead, reallocating capital, adopting to the AI age etc.. Microsoft did it, Meta did it, Google did it - and every single one pumped after the

🎉6🏆5🙏5🍾3👏3🤩3🥰3👍1

Signed Uncle Ripple I Infinitewhale

23 May 2026, 12:17 UTC205 views80 reactionsread 7 August 2026

Hype bringing bull market back

🏆14🎉12🤩11🙏11👍9👏9🍾8🥰6

Signed Uncle Ripple I Infinitewhale

22 May 2026, 14:48 UTC197 views26 reactionsread 7 August 2026
Forwarded from @overdose_gems_calls

Now that our $HYPE bags are flying, It makes me wonder if this is the perfect setup for CZ to start pushing $ASTER? $ASTER has been acting like a stablecoin for months, Doing absolutely nothing whilst $HYPE runs. And if you know CZ, there's a good chance he's trying to cook something. After all - I am sure that all of his team sees $HYPE all over the timeline while almost no one is talking about $ASTER. Could b

🏆6👍5🤩4🙏3🍾2🎉2👏2🥰2

Signed Uncle Ripple I Infinitewhale

13 May 2026, 05:27 UTC215 views42 reactionsread 7 August 2026

8x on Asteroid now. That's a 3/3 so far.

🤩8👏7🍾6🎉6🏆5🙏5👍3🥰2

Signed Uncle Ripple I Infinitewhale

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

Citation-graph rank — 1,317,023 of 1,550,220entries 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

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

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.

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

“InfiniteWhale” (@infinitewhale), 844 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/infinitewhale.

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.