👨🏻💻 Bought💰267.89302254 LYXe for 0.78114415 ETH ($1544.29) on 🦄 Uniswap 🟢 @Price 0.00291588 ETH ($5.7646) 🪐MerkleNetwork | Etherscan |🔔Price Alerts

Channel
LUKSO (LYXE) Price Channel
@lukso_price_channel
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
2subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001154683960 |
|---|---|
| Type | Channel |
| Username | @lukso_price_channel |
| Created | Between 1 December 2018 and 21 May 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/lukso_price_channel |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 21:33 | 2 | no change |
| 6 Aug 2026, 23:44 | 2 | first reading |
Engagement
20 posts held, back to 21 May 2022 — 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 20 posts for this entry, the most recent from 22 May 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- ≈4,720
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.
Recent posts
👨🏻💻 Bought💰761.73106713 LYXe for 2.14499503 ETH ($4240.59) on 🦄 Uniswap 🟢🟢 @Price 0.00281594 ETH ($5.5670) 🪐MerkleNetwork | Etherscan |🔔Price Alerts
👹 Sold💰761.73106713 LYXe for 2.17149740 ETH ($4292.98) on 🦄 Uniswap 🔴🔴 @Price 0.00285074 ETH ($5.6358) 🪐MerkleNetwork | Etherscan |🔔Price Alerts
👨🏻💻 Bought💰267.89302254 LYXe for 0.78114415 ETH ($1544.29) on 🦄 Uniswap 🟢 @Price 0.00291588 ETH ($5.7646) 🪐MerkleNetwork | Etherscan |🟢Trade Alerts
👨🏻💻 Bought💰761.73106713 LYXe for 2.14499503 ETH ($4240.59) on 🦄 Uniswap 🟢🟢 @Price 0.00281594 ETH ($5.5670) 🪐MerkleNetwork | Etherscan |🟢Trade Alerts
👨🏻💻 Bought💰89.83329203 LYXe for 0.24583 ETH ($486.56) on 🦄 Uniswap 🟢 @Price 0.00273651 ETH ($5.4162) 🪐MerkleNetwork | Etherscan |🔔Price Alerts
👨🏻💻 Bought💰333.52125590 LYXe for 0.9 ETH ($1784.90) on 🦄 Uniswap 🟢 @Price 0.00269847 ETH ($5.3516) 🪐MerkleNetwork | Etherscan |🔔Price Alerts
👹 Sold💰337.5 LYXe for 0.90539962 ETH ($1795.61) on 🦄 Uniswap 🔴 @Price 0.00268266 ETH ($5.3203) 🪐MerkleNetwork | Etherscan |🔔Price Alerts
👹 Sold💰337.5 LYXe for 0.90539962 ETH ($1795.61) on 🦄 Uniswap 🔴 @Price 0.00268266 ETH ($5.3203) 🪐MerkleNetwork | Etherscan |⚡️️Boost LYXe Volume
👨🏻💻 Bought💰151.73080724 LYXe for 0.41198334 ETH ($816.84) on 🦄 Uniswap 🟢 @Price 0.00271522 ETH ($5.3835) 🪐MerkleNetwork | Etherscan |⚡️️Boost LYXe Volume
👹 Sold💰380.06308199 LYXe for 1.03359089 ETH ($2049.32) on 🦄 Uniswap 🔴 @Price 0.00271952 ETH ($5.3920) 🪐MerkleNetwork | Etherscan |🔔Price Alerts
👨🏻💻 Bought💰9.16167968 LYXe for 0.02537476 ETH ($50.08) on 🦄 Uniswap 🟢 @Price 0.00276966 ETH ($5.4664) 🪐MerkleNetwork | Etherscan |🔔Price Alerts
Showing the 12 most recent of 20 posts we hold for @lukso_price_channel. 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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@lukso_price_channel named 1 handle 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 20 posts, 14 August 2026 – 14 August 2026
Cite this entry
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“LUKSO (LYXE) Price Channel” (@lukso_price_channel), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/lukso_price_channel.
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.