Channel
@zippfeed
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
14,302subscribers
-2,269 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003717924131 |
|---|---|
| Type | Channel |
| Username | @zippfeed |
| Description | Crypto news, zipped. 👀 The fastest way to stay on top of what’s moving in crypto! From news and on-chain data to regulation and shipping projects.. Visit Website: https://zippfeed.com Follow on X: https://x.com/zippfeed |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/zippfeed |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 09:44 | 14,302 | -1,051 |
| 11 Aug 2026, 08:37 | 15,353 | -854 |
| 10 Aug 2026, 05:40 | 16,207 | -39 |
| 9 Aug 2026, 03:51 | 16,246 | -244 |
| 8 Aug 2026, 05:57 | 16,490 | -38 |
| 7 Aug 2026, 09:21 | 16,528 | -28 |
| 6 Aug 2026, 08:30 | 16,556 | -15 |
| 6 Aug 2026, 02:51 | 16,571 | first reading |
231 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 17 pagesof 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 13 August 2026 |
|---|---|
| Posts held | 231 (5 August 2026 – 13 August 2026) |
| Views total | 428 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 02:01 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 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
🩸 BEARISH France’s Wrench Attacks Keep Hitting the Wrong Home A couple in France's Somme department has endured three home invasions in a single month, with attackers hunting for roughly €1 million in crypto the residents don't actually own. The previous owners were crypto millionaires whose tax records and address leaked onto the dark web. Criminals keep showing up at the wrong address. ⚖ On Monday, the Amiens c…
🩸 BEARISH ASIC shuts down Yepbit websites as investors report frozen… 🚨 Australia's ASIC has taken down multiple Yepbit websites and placed the platform on its Investor Alert List after investors reported they could not withdraw their funds. Yepbit holds no Australian Financial Services Licence and is not registered on AUSTRAC's Virtual Asset Service Provider Register, meaning it was operating entirely outside Aus…
🔥 BULLISH CFTC Orders Kalshi to Keep Operating Amid New York Lawsuit After New York AG Letitia James sued Kalshi, the CFTC invoked emergency authority to keep the prediction-market platform operating under federal rules. James seeks restitution, disgorgement and civil penalties that could total at least $36B. Kalshi warned a temporary restraining order could trigger an “imminent market emergency.” ⚖ James alleges …
🩸 BEARISH BTC Income ETF Offset Under 30% of $1.2M Losses BlackRock's spot Bitcoin ETF wrapper, sold as a hedged-income product, offset less than 30% of its $1.2M in crypto losses via options premiums, per Farside Investors flow data dated June 28, 2026. 📉 The 'Bitcoin income' framing was meant to deliver a yield buffer that softened drawdowns for traditional allocators parking BTC exposure through a regulated veh…
🩸 BEARISH CFTC Warns Prediction Markets Over Incentive Abuse Risks The CFTC issued new guidance Wednesday, warning prediction-market platforms such as Kalshi and Polymarket about incentive programs ⚖. The agency said filings for those programs are increasingly procedurally or substantively deficient, making it harder to determine whether platforms gave adequate notice of the terms and properly assessed compliance. …
🔥 BULLISH Russia Plans $58K Retail Cap for BTC, ETH and USDT Russia is preparing a legal public-trading route for Bitcoin, Ethereum and USDT, with retail participation facing a $58,000 cap. The planned December launch would put a state-owned bank in charge of custody 🏛 as the gatekeeper. That is a major adoption signal, but access would be controlled rather than open-ended. The bank, retail limit and compliance ru…
🔥 BULLISH Kalshi streams full order books on DoubleZero Edge! Kalshi just became the first prediction market to stream real-time full-depth order book data over DoubleZero Edge, the dedicated-fiber market-data service. The feed launches with full book depth for Kalshi's most active sports and crypto perpetuals contracts. ⚡ DoubleZero Edge uses multicast to publish data once and deliver it simultaneously to every c…
🔥 BULLISH Polymarket Hires Ex-Uber Executive VanderZanden as CGO 📈 Polymarket hired Travis VanderZanden, founder of Bird and former growth exec at Uber and Lyft, as chief growth officer, CEO Shayne Coplan announced Wednesday. Coplan framed it as a blitzscaling hire: VanderZanden ran growth under Uber's Kalanick and was CRO of Yammer under David Sacks. 'When it comes to growing marketplaces, nobody does it better,'…
🩸 BEARISH HIVE Faces $80M Swedish Tax Problem After $79M Quarter HIVE's $79M quarter now sits beside an $80M tax problem in Sweden. 📉 The tax issue is larger than the quarter figure, putting jurisdictional exposure alongside the Bitcoin miner's operating results. The wider U.S. debate around Trump's push to make Bitcoin mining in America adds a separate constraint: power. 🏛 The Tax Clarity for Mining and Staking A…
🩸 BEARISH Trump Faces Lawsuit Over Truth Social’s $100K Fast Feed ⚖ President Trump, Deputy Chief of Staff Dan Scavino and the Executive Office of the President were sued Wednesday in SDNY over Truth Social's Truth API, a paid feed delivering Trump's posts faster than they reach the public. The Intercept and Freedom of the Press Foundation filed the complaint, alleging the service gives paying subscribers preferen…
🩸 BEARISH XRP ETF Loses 54% of Assets and Posts $13.4M Loss Redemptions cut 21Shares' XRP ETF assets by 54% and locked in a $13.4M loss. 📉 Institutions also dumped Bitcoin and Ethereum ETFs, with those outflows dwarfing XRP's weekly inflow. The broad crypto ETF bid is under pressure. 🏛 Demand was not a blanket exit, however. Institutions bought XRP and HYPE wrappers again, showing selective interest in targeted a…
🔥 BULLISH Kraken Adds 24/7 S&P 500 Perpetuals to Funded Trading Kraken has added 24/7 S&P 500 perpetuals to its funded trading program, bringing a major US equity benchmark into an always-on derivatives format. ⚡ Perpetuals provide exposure without a fixed expiry, linking traditional equity exposure with crypto's continuous-trading model. Commodities are planned next, which would broaden the program beyond a singl…
Showing the 12 most recent of 231 posts we hold for @zippfeed. 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 — 280,572 of 1,160,990entries 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Zipp 👀” (@zippfeed), 14,302 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/zippfeed.
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.