Got listed on robinhood

Channel
Shrimpy's Calls (no paid calls)
@shrimpycall
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
5,042subscribers
+51 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001557872576 |
|---|---|
| Type | Channel |
| Username | @shrimpycall |
| 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 | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/shrimpycall |
Topic
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 19:18 | 5,042 | -13 |
| 9 Sept 2026, 06:36 | 5,055 | -20 |
| 4 Sept 2026, 01:21 | 5,075 | +28 |
| 31 Aug 2026, 11:02 | 5,047 | +14 |
| 28 Aug 2026, 05:54 | 5,033 | +17 |
| 25 Aug 2026, 00:54 | 5,016 | +5 |
| 21 Aug 2026, 17:47 | 5,011 | +5 |
| 18 Aug 2026, 11:42 | 5,006 | -9 |
| 15 Aug 2026, 20:06 | 5,015 | +34 |
| 12 Aug 2026, 13:37 | 4,981 | -5 |
| 9 Aug 2026, 22:21 | 4,986 | -5 |
| 7 Aug 2026, 06:30 | 4,991 | no change |
| 7 Aug 2026, 06:26 | 4,991 | first reading |
Engagement
20 posts held, back to 28 July 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 8 pages 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Holy cashcat
Cashcat 135 mil again, robinhood is the place to be rn
Meme: $Frong (Uniswap launchpad mascot) $Liluni (Uniswap mascot) Utility: $WTH (best utility by far on robinhood, with solid af floor)
Good support from whales on this one, no PVP too.
All the hype is around Uniswap rn, it only makes sense to bid the main uniswap lore runner $Liluni https://dexscreener.com/robinhood/0x1f00bab0dfb60102287e2508b7d41a0a97a9dec2c9317bc9c81a4fb91a731be3 MC: 2 mil
Just touched ATH of 250k, huge support behind this guy, around 13m views on twitter, definitely looks like only up from here.
Real good lore here, a man lost everything after his wife left and is now receiving tons of love on reddit. Sol community has donated more than $8k to him and he’s spreading his blessing around with other families while documenting it. Could gigasend. https://dexscreener.com/solana/HUNGpbLA4U6edwSWXM8AJkbkEJgJwawJAkh5DA9rUgEP MC: 70k
I keep accumulating $WTH on this run-up. It's a Uniswap v4 Hook that captures arbitrage before MEV bots do and redistributes the profits to traders and LPs instead of letting bots extract the value. 0xb8fa8010833463aac5595b55b9045479239eff79 For the first time, projects have arbitrage working for them, not against them. That's one of the cleanest real-world use cases I've seen for v4 Hooks. The scaling potential…
Sometimes you just have to top blast
I just managed to find entry here on $WTH. It’s the an arbitrage bot that’s first to utilize Uniswap V4 hook. Literally the first project ever to have an arbitrage integrated in its code, it will snowball as the bot generates fees and adds it to LP or funds marketing (risk-free) Scalability is unlimited since projects can have have installed and make trading very efficient as no MEVs or bots in jump in on the price…
Holy Cate just nuked
Showing the 12 most recent of 20 posts we hold for @shrimpycall. 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
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.
Mentions
Named by 7 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.
Appears in Telegram’s recommendations for other channels
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.
@Caesars_Calls · 39,380
Telegram ranks this channel #35 of 82 here — alongside 81 others — read 30 August 2026
@gubbinscalls · 25,900
Telegram ranks this channel #41 of 80 here — alongside 79 others — read 13 September 2026
@bruiserscalls · 33,412
Telegram ranks this channel #44 of 80 here — alongside 79 others — read 5 September 2026
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Shrimpy's Calls (no paid calls)” (@shrimpycall), 5,042 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/shrimpycall.
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.