Channel
@TwistCalls
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001883430223 |
|---|---|
| Type | Channel |
| Username | @TwistCalls |
| Description | ETH, BSC, ARB, PULSE.... For promotion: @LeonardPlug | @KendoCryptoo 🚨 Do not fall for scam accounts |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/TwistCalls |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 18:33 | 7 | no change |
| 7 Aug 2026, 10:12 | 7 | first reading |
20 posts held, back to 12 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 pageof 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.
| Window | Rolling 30 days · latest post in window 21 July 2026 |
|---|---|
| Posts held | 20 (12 July 2026 – 21 July 2026) |
| Views total | 16 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 18:33 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.
Lifetime counters from Telegram’s own channel header, read 12 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.
What am I skipping today? New names, mostly. Everything's green together, tempting to skip the checks and size in fast because it feels safe. Market cap near $2.35T, up about three percent today, volume up over twenty. That's the whole board rallying at once, not one token proving anything on its own. I still pull up the pool page before the chart. Same five minutes whether it's red or green out there. Skip that …
Ever actually pull up the burn address instead of trusting the badge on the dashboard? Did that once, saw "LP locked" and moved on, only to find the lock expired in nine days and nobody mentioned it. Pool got pulled the day after. Now I check the unlock date myself before I size in, and if I can't find one I treat the position as small enough that losing it doesn't touch the rest of the stack.
Volume printed $72B tonight, up 77% while the market cap barely moved, 0.62% and change. Doesn't change what I check first. LP lock before the chart, sized small enough that being wrong there only costs me the one position, not the stack.
Had a name a while back sitting around $180k marketcap on the dashboard, chart looked calm, felt like an ordinary small cap I'd bought a dozen times before. Never checked the pool itself. Turned out there was maybe 4 SOL sitting under that number, enough that one real sell could take a third of the price out in a single print, and I found that out after I was already in. Sold into me within the hour. Bid just wasn't…
Spot volume up 21% while cap is down for the day. Most people read that as buyers stepping back in. I read it as position turnover, longs and exits both showing up as volume on the tape. Doesn't tell me direction. Just tells me more hands are moving. Late Sunday into Monday my time is exactly when a thin pool can print a wick that looks like real flow and isn't. Takes less size than people think to fake that. I'm…
Everyone piling into PUMP at #1 trending is exactly why I'm not adding here. Crowded green candles are the ones that give it all back fast if I'm wrong about timing.
PUMP trending again tonight, +23% and change according to CoinGecko. I remember the first time I thought graduation meant safety. Curve filled, hit the AMM pool, I read that as the risky part being over and went in heavier than I should have. Wrong read. Liquidity there was thinner than it looked, one wallet unwound into it, price gave back most of the move in under an hour. I wasn't reading a chart, I was the exit…
PUMP up close to 18% tonight and half the timeline reads that as a green light for anything launched on it. I'd rather stay small and let the first hour of thin liquidity prove itself before I size up into it.
Cap's up 2.84% today, tape looks strong on the board. Tried filling a fresh graduate this morning and the liquidity three rows down just wasn't there, that's how a small stack turns into one you're stuck holding.
Funny how nobody's talking about ADI anymore. Same terminal tab for two days now, sitting in the same spot on the curve without moving, while the wider tape's up near 3% this morning and every other tile on the board is loud green. A stall that long on a bonding curve usually breaks fast once it finally goes. I'm not adding into it. My sizing stays small enough that being wrong here just costs me a shrug, not a real …
Spot volume up 14% tonight against a 3% cap move. That's not conviction, that's noise trading through thin books. Everyone reads the green number and forgets to check what's actually sitting under it three levels deep on some fresh graduate. I've seen this exact gap before a flush. Loud tape, quiet liquidity, and the last one out holding the bag nobody wanted. Small size tonight. Being wrong here costs more than …
Volume's up 13.7% tonight, market cap barely moved 2.75%. That's turnover, not fresh money coming in. So I'm not touching size tonight. Not adding, not rotating into whatever's green on the board. A loud tape up top says nothing about liquidity three levels down on some fresh graduate, and that's exactly where a fill turns into a bag you can't move. Sitting still costs me nothing. Guessing wrong there costs real …
Showing the 12 most recent of 20 posts we hold for @TwistCalls. 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 — 1,048,459 of 1,350,102entries 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Twist Calls” (@TwistCalls), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/TwistCalls.
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.