Channel
@lasersell
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
17subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003441260774 |
|---|---|
| Type | Channel |
| Username | @lasersell |
| Description | The official channel for updates on LaserSell and all products within our ecosystem. https://lasersell.io |
| Created | Between 1 November 2025 and 25 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/lasersell |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 20:46 | 17 | no change |
| 7 Aug 2026, 21:47 | 17 | first reading |
20 posts held, back to 25 February 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.
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 24 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
10 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ⚡ | 4 | 40.0% | |
| ❤ | 4 | 40.0% | |
| 🔥 | 2 | 20.0% |
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 4 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 10reactions 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 25 February 2026 to 24 March 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.
We released an update to our SDK giving users more granular controls for copy trading. 🚀 This will help you copy trade safely with LaserSell and set mitigations to prevent you from being burned by the wallet you’re mirroring. 🛡️ https://github.com/lasersell/lasersell-sdk/releases/tag/v1.1.0 The desktop app will be receiving an update shortly! More information about this update can be found in our documentation h…
❤1
You can see your PnL in the menu bar
⚡2
https://x.com/lasersellhq/status/2034892888597770730
⚡2
A lot has changed in the past 2 weeks, and LaserSell is now in v1.0.x What's New: - LaserSell Desktop app for macOS: https://www.lasersell.io/download - Analytics: https://docs.lasersell.io/features/analytics - Behavioral Insights: https://docs.lasersell.io/features/insights - Achievements: https://docs.lasersell.io/features/achievements - Exit Ladder: https://docs.lasersell.io/api/stream/strategy-configuration#exit…
❤3🔥2
https://www.lasersell.io/blog/benchmark-results
🚀 LaserSell v0.4.4 • Remove recommended defaults Full Changelog: https://github.com/lasersell/lasersell/compare/v0.4.3...v0.4.4 View release on GitHub
🚀 LaserSell SDK v0.3.0 SDK 0.3.0 Liquidity Snapshots and Slippage Bands Professional and Advanced tier subscribers now receive real time liquidity snapshots alongside PnL updates. Each snapshot includes: • Slippage bands at 1%, 2%, 5%, and 10% thresholds showing maximum sellable token amounts at each price impact level • Liquidity trend indicator (`growing`, `stable`, `draining`) so you can detect when pool depth…
🚀 LaserSell SDK v0.2.3 • Add amount parameter to /v1/buy Full Changelog: https://github.com/lasersell/lasersell-sdk/compare/v0.2.2...v0.2.3 View release on GitHub
🚀 LaserSell v0.4.3 • bump lasersell-sdk to 0.2.2 and update sell request fields to match new required types Full Changelog: https://github.com/lasersell/lasersell/compare/v0.4.2...v0.4.3 View release on GitHub
🚀 LaserSell SDK v0.2.2 Release notes • align buy/sell request types with backend • rename amount_quote_units to amount_in_total • add input field • make slippage_bps and output required Full Changelog: https://github.com/lasersell/lasersell-sdk/compare/v0.2.1...v0.2.2 View release on GitHub
Okay after a long month, the new LaserSell is ready for use! This was a major architectural and product change, so it took a while. And this takes things to a new direction where LaserSell can be implemented anywhere and become adopted as a new standard trading feature. What's new in the ecosystem: - LaserSell API: https://docs.lasersell.io/api/overview - LaserSell SDK: https://github.com/lasersell/lasersell-sdk - L…
Okay everything should be good and stable now. If you notice any bugs, please report them directly to me or post in the Discord: discord.gg/lasersell Get a free API key to use the new LaserSell at https://app.lasersell.io
Showing the 12 most recent of 20 posts we hold for @lasersell. 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 — 811,871 of 1,169,250entries 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“LaserSell Announcements” (@lasersell), 17 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/lasersell.
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.