400k btw
❤20

Channel
@dippy_calls
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
24,375subscribers
-826 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001538340900 |
|---|---|
| Type | Channel |
| Username | @dippy_calls |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 October 2026 |
| Measurements held | 47 |
| Confirmed unchanged | 1 time, most recently 25 October 2026 |
| On Telegram | t.me/dippy_calls |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Oct 2026, 18:07 | 24,375 | -6 |
| 24 Oct 2026, 16:25 | 24,381 | -14 |
| 23 Oct 2026, 19:46 | 24,395 | -14 |
| 22 Oct 2026, 21:06 | 24,409 | -14 |
| 20 Oct 2026, 16:27 | 24,423 | -14 |
| 19 Oct 2026, 17:35 | 24,437 | -13 |
| 18 Oct 2026, 13:59 | 24,450 | -5 |
| 17 Oct 2026, 14:59 | 24,455 | -3 |
| 16 Oct 2026, 15:37 | 24,458 | -15 |
| 15 Oct 2026, 15:28 | 24,473 | -10 |
| 14 Oct 2026, 13:01 | 24,483 | -25 |
| 12 Oct 2026, 22:00 | 24,508 | -59 |
| 8 Oct 2026, 13:57 | 24,567 | -44 |
| 4 Oct 2026, 03:21 | 24,611 | -49 |
| 25 Sept 2026, 09:39 | 24,660 | -110 |
| 17 Sept 2026, 10:40 | 24,770 | -26 |
| 15 Sept 2026, 09:39 | 24,796 | -21 |
| 13 Sept 2026, 18:40 | 24,817 | +2 |
| 11 Sept 2026, 20:59 | 24,815 | -33 |
| 9 Sept 2026, 08:59 | 24,848 | first reading |
433 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 105 pages of Telegram’s post history, 20 posts per page.
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 144 of 148 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 24 October 2026 |
|---|---|
| Posts held | 433 (5 August 2026 – 24 October 2026) |
| Views total | 590,857 |
| Reactions total | 4,379 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Oct 2026, 10:48 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.
Measured directly from 11 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
12,535 reactions across 424 posts, in 6 distinct kinds. The most used accounts for 38.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 4,852 | 38.7% | |
| ❤ | 4,840 | 38.6% | |
| 🎉 | 2,709 | 21.6% | |
| 👀 | 68 | 0.542% | |
| 👏 | 43 | 0.343% | |
| 🏆 | 23 | 0.183% |
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 424 of the 433 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 12,535 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 433 most recent posts we hold, published 5 August 2026 to 24 October 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.
400k btw
❤20
Marc Andreessen in
❤19
800k views on $CLAUDIA's new video, and you still believe the token is dead? They're forcing you out by any means necessary They'll keep pushing you out of your position until you give up or find your faith > devs on board and active > literally not a single theses has changed GLOBALLY That's the only way to test your conviction https://x.com/anabology/status/2113239948144890235
🔥22🎉15
Here's the reflexive loop $NET is about to restart > price at backing: no emissions, nobody sells into dilution > products earn, fees flow in, backing per NET grows > price follows backing up, premium appears > premium turns on dividends and the bond engine > bonds sell above backing, treasury grows faster The loop is paused at the bottom right now Buying at the pause is how you catch the next full cycle
🔥25🎉15❤2
okay I think the issue is actually more to do with market conditions the coins don't go as high, or you don't spot them as early and so you should expect to be making 5x+ on every trade there were bunch of 70%-250% trades out there that you missed/roundtripped because you wanted higher returns out of the trade so I guess when market is choppy like it is right now, the best thing to do is to not oversize and just st…
❤15
just read https://x.com/dr3yaaaa/status/2113205348261900349 CLAUDIA x SLOPCORE (our bags)
❤18
If kimchi1x doesn't approve this token, PumpFun will just show its true colors yet again Would that be surprising? Absolutely not But it's about time you did something useful for the community, even though you already have some REALLY GOOD initiatives in that direction
❤20
And people still call Kimchi a legend? lmao
$LCMM thesis, fully transparent > Bull: a real data product for the trenches, daily shareable content, clean labelled tokenomics, and a narrative everyone in crypto instantly gets > Risk: it's tiny and early > Plan: small, early, patient. Watching for the daily prints to start getting reposted by bigger accounts > Invalidation: the dashboard stops updating, or a governor seat dumps and nobody steps in Early is unco…
🔥28🎉19
THE FIRST MEMECOIN THAT ACTUALLY TELLS YOU THE TRUTH ABOUT THE TRENCHES ticker is $LCMM The Federal Meme Reserve prints the numbers nobody else will, every day > how many coins launched in the last 24h > how many already died on the curve > how many actually bonded > how much the trenches lost today, per second > who pump.fun actually pays to call Memes go viral once. Data goes viral every single day CA: DqBXBtP…
🔥28🎉17
Every product NetNet ships exists to move two numbers: backing per $NET and USDG per $NET > Real World Bonds: proceeds buy tokenized stocks > NetNet Credit: Morpho vault lending USDG against stock tokens and wsNET > Loopback: borrow against your staked NET > NET LONG: leverage with wsNET margin, every fee buys and burns NET > NET ADVANCE: 5% of every close to the treasury > Predict and THE BOOK: markets on the treas…
❤34🔥27🎉15
another fundamental miss match set up on Robinhood the first time $NET hit $600, the treasury was under $2M today the treasury is around $25M, 90%+ of supply is staked and it is one of the strongest cult on Robinhood same way we had $BOW catch up to it's TVL, we will have $NET get its price appreciation we’re not staying under treasury value for long💪 0xca9c78dd337a67f6e0077f65f5e9218719d30edf
🔥25
Showing the 12 most recent of 433 posts we hold for @dippy_calls. 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.
@dippy_calls edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@dippy_calls named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 15 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 October 2026 — this entry's latest reading, not the date you are reading this.
“🐧Dippy Alpha Calls” (@dippy_calls), 24,375 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/dippy_calls.
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.