JUST IN: ⚠️ PREDICT FUN on BSC may have been exploited. Around $300K in potentially stolen funds reportedly moved from multiple contracts, through intermediary wallets, and on to Relay. CryptoEcho
🍌23🌭18🤣18🤗17🤝16👏13❤12🏆11

Channel
@pulse_pulsecrypto
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
70,036subscribers
+37,841 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002457953569 |
|---|---|
| Type | Channel |
| Username | @pulse_pulsecrypto |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 27 October 2026 |
| Measurements held | 44 |
| Confirmed unchanged | 1 time, most recently 27 October 2026 |
| On Telegram | t.me/pulse_pulsecrypto |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 45% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Oct 2026, 20:39 | 70,036 | -8 |
| 26 Oct 2026, 18:48 | 70,044 | -25 |
| 25 Oct 2026, 18:18 | 70,069 | +1,453 |
| 24 Oct 2026, 20:40 | 68,616 | +2,392 |
| 23 Oct 2026, 19:49 | 66,224 | +639 |
| 22 Oct 2026, 23:19 | 65,585 | +2,421 |
| 21 Oct 2026, 23:17 | 63,164 | +1,777 |
| 20 Oct 2026, 14:39 | 61,387 | +2,279 |
| 19 Oct 2026, 13:51 | 59,108 | +2,323 |
| 18 Oct 2026, 14:37 | 56,785 | -122 |
| 17 Oct 2026, 15:19 | 56,907 | -220 |
| 16 Oct 2026, 17:50 | 57,127 | +607 |
| 15 Oct 2026, 16:15 | 56,520 | +1,407 |
| 14 Oct 2026, 16:00 | 55,113 | +2,292 |
| 13 Oct 2026, 06:00 | 52,821 | +3,964 |
| 9 Oct 2026, 03:41 | 48,857 | +3,638 |
| 4 Oct 2026, 14:15 | 45,219 | +4,310 |
| 26 Sept 2026, 08:18 | 40,909 | +5,522 |
| 19 Sept 2026, 07:16 | 35,387 | +1,501 |
| 16 Sept 2026, 18:57 | 33,886 | first reading |
550 posts held, back to 11 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 165 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.
| Window | Rolling 30 days · latest post in window 27 October 2026 |
|---|---|
| Posts held | 550 (11 August 2026 – 27 October 2026) |
| Views total | 2,730,350 |
| Reactions total | 25,311 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Oct 2026, 16:56 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 7 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.
29,126 reactions across 545 posts, in 54 distinct kinds. The most used accounts for 4.41% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,285 | 4.41% | |
| 😎 | 993 | 3.41% | |
| 🏆 | 922 | 3.17% | |
| 😁 | 905 | 3.11% | |
| 🍾 | 881 | 3.02% | |
| 🌭 | 875 | 3.00% | |
| 🎉 | 855 | 2.94% | |
| 🤩 | 831 | 2.85% | |
| 👌 | 799 | 2.74% | |
| 🤷 | 796 | 2.73% | |
| 🤗 | 787 | 2.70% | |
| 👏 | 783 | 2.69% | |
| 😇 | 760 | 2.61% | |
| 😘 | 758 | 2.60% | |
| 🙏 | 755 | 2.59% | |
| 💯 | 736 | 2.53% | |
| 🦄 | 732 | 2.51% | |
| 💋 | 721 | 2.48% | |
| 👍 | 697 | 2.39% | |
| 🐳 | 694 | 2.38% | |
| 34 further kinds | 12,561 | 43.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 545 of the 550 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 29,126 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 550 most recent posts we hold, published 11 August 2026 to 27 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.
JUST IN: ⚠️ PREDICT FUN on BSC may have been exploited. Around $300K in potentially stolen funds reportedly moved from multiple contracts, through intermediary wallets, and on to Relay. CryptoEcho
🍌23🌭18🤣18🤗17🤝16👏13❤12🏆11
📊 Market Snapshot: BTC: $80,310 ETH: $2,335.16 BNB: $742.30 SOL: $100.91 📈 Market Cap: Total: $2.71T DeFi: $113.77B 24-hour trading volume: $66.85B ⚡ Sentiment & Activity: FGI: Neutral (48) Open interest: $55.17B 24-hour liquidations: $146.6M CryptoEcho
💋18🤷18🎉17👏15🤔15👀14🍌13🦄13
NEW: 💰 Binance has applied to Brazil’s central bank for approval to operate as a virtual asset service provider. CryptoEcho
🍾25💯18😡18❤16🤬16🥰16🔥15🗿15
JUST IN: ⚠️ China’s STAR 50 index has fallen 40% in less than four months, erasing around $480 billion in market value. CryptoEcho
👍21🍌20💔20💋19🤓17😁17😱17🥰15
Breaking: 💰🚨 Bitcoin miner MARA Holdings sold 1,000 BTC worth $80.19 million roughly six hours ago. CryptoEcho
👍26🔥24🌭23💯21👎20👏20🎄19😘18
JUST IN: 💰 Ripple receives final U.S. approval to operate a national trust bank. CryptoEcho
🌚28⚡26🗿26🎉25🙊24❤23💯23🏆20
🚀 Today’s Top Trending Coins 1. BTC 2. QTC 3. BTC 4. PEARL 5. HYPE 6. PENGU 7. QNT 8. ENA 9. CHIP 10. AERO 11. PONS 12. SOL 13. VVV 14. LINK 15. CARDS CryptoEcho
🤩58😁54💔52🐳50🤗50❤46😨41🎄37
JUST IN: 🇮🇱 Prediction markets put Benjamin Netanyahu’s chances of staying prime minister after Israel’s 2026 election at 25%. ~ Prediction Markets CryptoEcho
👏52🎄51😘45🥰39🍾38🌚37🤷36🏆33
JUST IN: 💰 Kraken parent Payward plans to become the first CFTC-regulated firm to launch markets on HIP-3*. It will use #Hyperliquid to offer perpetual futures markets to US customers. CryptoEcho
🐳38🤣38🌚37👻37😎37🎃32🤓32🤷31
BREAKING: 🇮🇷 Fox News reports that Iran is nearing the final stages of planning attacks targeting U.S. citizens. CryptoEcho
🥰40🍌34🏆32🤣32🙉32🍓30🤩30🎉29
📊 Market Snapshot BTC: $80,252 ETH: $2,322.55 BNB: $741.07 SOL: $101.53 📈 Market Cap Total: $2.71T DeFi: $113.97B 24-hour volume: $56.16B ⚡ Market Sentiment FGI: Neutral (50) Open interest: $54.02B 24-hour liquidations: $155.2M CryptoEcho
💋41🙏34🌭32🏆32🍓30😘29💔28😁28
JUST IN: 💰 Aviva Investors has launched a tokenized share class for its £22 billion Sterling Liquidity Fund on the XRP Ledger. CryptoEcho
🥰39😘35🍾33🌭27✍25🍓25😎25🙊25
Showing the 12 most recent of 550 posts we hold for @pulse_pulsecrypto. 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.
Named by 10 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.
@pulse_pulsecrypto named 2 handles 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.
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 27 October 2026 — this entry's latest reading, not the date you are reading this.
“CryptoEcho” (@pulse_pulsecrypto), 70,036 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/pulse_pulsecrypto.
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.