I wonder which ethnicity is behind all this 😄😏
❤2

Channel
@BlocCalls
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
867subscribers
-13 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001238195991 |
|---|---|
| Type | Channel |
| Username | @BlocCalls |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/BlocCalls |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 08:15 | 867 | -4 |
| 4 Sept 2026, 16:38 | 871 | -5 |
| 28 Aug 2026, 01:39 | 876 | -1 |
| 20 Aug 2026, 01:17 | 877 | -1 |
| 13 Aug 2026, 17:37 | 878 | -2 |
| 7 Aug 2026, 14:38 | 880 | no change |
| 6 Aug 2026, 21:31 | 880 | first reading |
20 posts held, back to 6 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 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 15 July 2026. An engagement rate over an empty window would be a number about nothing.
9 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 55.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 55.6% | |
| 🙈 | 2 | 22.2% | |
| 💯 | 1 | 11.1% | |
| 🤣 | 1 | 11.1% |
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 5 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 9 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 July 2026 to 15 July 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.
I wonder which ethnicity is behind all this 😄😏
❤2
second vamp attack on a coin I believed in btw
🤣1
This is proof, btw, that nobody cares if you push or not in 2026, 😂😂😂 Pushed every day, nonstop tweets, nonstop raids, and yet this one dumped to 47k. Crazy, ngl. 😦
❤2💯1
The company is called Tiger, Inc. The Ticker is $MEOW. The Official CA is: 0x2e9c3B1C6E7703D1784b2B8F80ef4e99D76b3E56 Proof: https://robinhood.com/us/en/learn/articles/a-big-little-primer-on-options/ https://x.com/TigerIncMeow/status/2075901419270324459?s=20
How many more hints do you need for $MEOW? api.robinhood.com/marketdata/ So far, we have: - Appears in most Robinhood articles (Tiger, Inc. with the $MEOW symbol) - Appears in the Robinhood API - Appears when setting up the Robinhood widget on Android's home screen
7x in a h hi
ok
330k entry gud dip
$ROBINHOOD- 0x79fe86b963255ce884bdcac6388c50a599ba277f its next to cashcat's viral post and was used as a mascot of Robinhood, vlad even interacted with it in the last 24h https://x.com/haych_que/status/2075495145798279204?s=20
some gambles catwifhat: 0x5970642Fb980ccA8Bf4dbBaFbcb24b13AefA0E0a https://x.com/vladtenev/status/1482119863774580740?s=20 robinhoofwifhat: 0x5970642Fb980ccA8Bf4dbBaFbcb24b13AefA0E0a (requote): https://x.com/RobinhoodApp/status/1861142914996257081?s=20 hat: 0x295f74Ef052931E0F63bf202EcF558318E40A44E https://x.com/RobinhoodApp/status/1861142914996257081?s=20
After 2 years of failed CTOs... it finally worked. Is my curse finally over, God?
robinhood chain at least act as a robinhood not like pump fun who is literally the corrupt Sheriff of Nottingham (Israel btw) https://x.com/Blocboybenji/status/2075537248062259219?s=20
🙈2
Showing the 12 most recent of 20 posts we hold for @BlocCalls. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Bloc Calls 🚀ABS | BNB | ETH” (@BlocCalls), 867 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/BlocCalls.
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.