Channel
@pulsereview
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
1,312subscribers
-32 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001780653202 |
|---|---|
| Type | Channel |
| Username | @pulsereview |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/pulsereview |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 23:36 | 1,312 | -3 |
| 4 Oct 2026, 16:16 | 1,315 | -2 |
| 24 Sept 2026, 20:59 | 1,317 | -5 |
| 16 Sept 2026, 16:40 | 1,322 | -1 |
| 12 Sept 2026, 16:17 | 1,323 | -1 |
| 8 Sept 2026, 12:57 | 1,324 | -4 |
| 3 Sept 2026, 04:18 | 1,328 | -2 |
| 30 Aug 2026, 17:08 | 1,330 | -4 |
| 24 Aug 2026, 10:36 | 1,334 | -4 |
| 20 Aug 2026, 15:52 | 1,338 | -2 |
| 17 Aug 2026, 11:53 | 1,340 | -1 |
| 14 Aug 2026, 00:55 | 1,341 | -2 |
| 10 Aug 2026, 15:08 | 1,343 | -1 |
| 7 Aug 2026, 07:30 | 1,344 | no change |
| 7 Aug 2026, 07:25 | 1,344 | first reading |
17 posts held, back to 7 June 2023 — 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 17 posts for this entry, the most recent from 13 April 2025. An engagement rate over an empty window would be a number about nothing.
553 reactions across 17 posts, in 24 distinct kinds. The most used accounts for 18.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 100 | 18.1% | |
| 🤮 | 89 | 16.1% | |
| 💩 | 86 | 15.6% | |
| 👍 | 85 | 15.4% | |
| ❤ | 57 | 10.3% | |
| 🎉 | 33 | 5.97% | |
| 😢 | 18 | 3.25% | |
| 🖕 | 16 | 2.89% | |
| 👎 | 11 | 1.99% | |
| 🤣 | 11 | 1.99% | |
| 👀 | 8 | 1.45% | |
| 👏 | 6 | 1.08% | |
| 😁 | 6 | 1.08% | |
| ❤🔥 | 5 | 0.904% | |
| 🙏 | 4 | 0.723% | |
| 🤔 | 3 | 0.542% | |
| 🤬 | 3 | 0.542% | |
| 🥰 | 3 | 0.542% | |
| ⚡ | 2 | 0.362% | |
| 😱 | 2 | 0.362% | |
| 4 further kinds | 5 | 0.904% |
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 17 of the 17 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 553 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 7 June 2023 to 13 April 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
SPARTA MAINNET 0x52347C33Cf6Ca8D2cfb864AEc5aA0184C8fd4c9b 🚩 Owner admin key 🚩 Owner can black list addresses. 🚩 Owner can set treasury wallet (receives 5% of purchases) 🚩 Owner can set any address to AMM pair (receives 5% of transfers from theses addresses) ⚠️ Owner received total supply 2B Sparta ℹ️ 1.8B Sparta burnt. Owner retains 80M+ sparta.
🤮7🔥6👎4❤1🖕1🙏1
Yum Yum (YUMY) MAINNET 0x6367B21D23dBA93E932A87467318DC07CD24bC00 Simple ERC20 token contract. Whole Uniswap V3-like DEX review is out of scope. ⚠️ Deployer 0x9c130c26778dbfde428f2e9d7adb04f6086ab059 received total supply ℹ️ Supply is limited to 1,000,000,000,000,000. NO RED FLAGS
❤5👍2🖕1🙏1
Eazy Swap (EAZY) MAINNET 0x6cF99BAA0a4d079F960216d08cf9a1Bc7e4dd37C Simple ERC20 token contract. Whole Uniswap V2-like DEX review is out of scope. ⚠️ Owner 0x1430e243005a0d3934d592713b55f40da162b483 can mint new tokens. Owner is smart contract EasySwapDistributor, which is out of scope of this review. ℹ️ Supply is limited to 500,000. ℹ️ Deployer received initial supply of 1,000 (code comment states it's for initia…
❤5👍2🐳1🖕1🙏1
Xexican (XEX) MAINNET 0xD9AA8034D9f71a84F855A4da45A114728b33Cc56 Simple ERC20 token contract. ℹ️ Owner can withdraw other ERC20s sent to contract by accident, but ownership was renounced. ⚠️ Deployer 0xd901D74C8a5b4bdBF65c432771a1d06cbF1F95a4 received the total supply. NO RED FLAGS
🖕1🙏1
SuperStake: pHEX (pSSH) MAINNET 0xB5C4ecEF450fd36d0eBa1420F6A19DBfBeE5292e Tax token where the deployer received the total supply. ℹ️ Owner admin key 🚩 Owner can blacklist addresses (via setBot) REVOKED ℹ️ Owner can set taxes (max 20%) ⚠️ Deployer received total supply RED FLAGGED OWNER CAN NO LONGER BLACKLIST
💩14🔥8👀1🖕1
EazySwap Token MAINNET ℹ️ Owner admin key ℹ️ Owner is distribution contract ℹ️ Owner can mint 0x6cF99BAA0a4d079F960216d08cf9a1Bc7e4dd37C NO RED FLAGS --------------------------------------------- EazySwap Distribution MAINNET 0x1430E243005a0d3934d592713b55f40da162B483 ℹ️ Owner admin key ℹ️ Owner is timelock (min 24 hours) ℹ️ Owner can add / change reward pools ⚠️ Owner can mint EazySwap token using custom pool…
👍20❤8👏2🔥2😱2🖕1
PhuxAirdrop MAINNET Airdrop distribution contract. 0xF6e821028f133d71F2Fb67ab9e778D672b3a0797 NO RED FLAGS
🎉30👍9🔥6⚡2❤1👏1🖕1🤬1
HELGO MAINNET 0x0567CA0dE35606E9C260CC2358404B11DE21DB44 HEX meme / market maker token. NO RED FLAGS
🔥29💩12❤🔥5👎4❤2🥰2🖕1
PulseReflections PRS MAINNET 0xb6B57227150a7097723e0C013752001AaD01248F Reflection / tax token where the deployer received the total supply (locked for 1 year). ℹ️ Owner admin key (revoked) ℹ️ Owner could have paused transactions ⚠️ Deployer received total supply (rug risk) NO RED FLAGS
🔥18💩9❤3👍2🖕1
PulsePunks NFT collection on PulseChain 0xf886F928e317cfD4085137A7a755C23D87F81908 ℹ️ Owner admin key ℹ️ Owner could set NFT price/s ℹ️ Owner could freely mint NFTs ℹ️ No longer possible to mint NO RED FLAGS --------------------------------------------- PulsePunks NFT marketplace on PulseChain 0x7605Efc5bf982071EEA619dBcF360d8d555C4523 🚩 Owner admin key 🚩 Owner can pause market place ℹ️ When paused NFTs are l…
👍20💩14👀4🔥3😁3👏1🖕1
PulseArcade PARC MAINNET 0x96E400923Bde4D88fb626B5e897Cef3C9F025eec Reflection / tax token where the deployer received the total supply. ℹ️ Owner Admin Key (revoked) ℹ️ Owner could have paused transactions ℹ️ Deployer excluded from fees ⚠️ Deployer received total supply (rug risk) NO RED FLAGS
🤣11❤8💩4👍2🥴2🎉1🔥1🖕1
Daytona Finance TONI Mainnet (contract now verified) 0x9F8182aD65c53Fd78bd07648a1b3DDcB675c6772 ℹ️ Owner admin key (owner is MasterChef) ℹ️ Owner can mint unlimited tokens (used for rewards) ℹ️ devaddr receives 10% of all minted Toni Daytona Finance MasteChef 0xAc6fBc06C8c0477ba8fc117adb52881c1Cc580dA 🚩 Owner admin key (not contract) 🚩 Owner can delegate ownership 🚩 Owner can manage pools and set rewards 🚩 Owner…
😢17🤮14👍13🔥12💩9🤔3😁3👏2
Showing the 12 most recent of 17 posts we hold for @pulsereview. 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.
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 10 October 2026 — this entry's latest reading, not the date you are reading this.
“Pulse Police Review” (@pulsereview), 1,312 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/pulsereview.
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.