Telegram RegisterThe public register of Telegram
Telegram profile photo for Mlm onchain

Channel

Mlm onchain

@mlmonchain

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

28,227subscribers

+348 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002677926273
TypeChannel
Username@mlmonchain
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live9 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/mlmonchain

Topic

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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.

Growth

27,83228,22728,029.56 August 2026 — 27,879 subscribers6 August 2026 — 27,879 subscribers6 August 2026 — 27,875 subscribers7 August 2026 — 27,870 subscribers8 August 2026 — 27,859 subscribers9 August 2026 — 27,853 subscribers10 August 2026 — 27,847 subscribers11 August 2026 — 27,843 subscribers12 August 2026 — 27,832 subscribers13 August 2026 — 27,870 subscribers14 August 2026 — 27,885 subscribers16 August 2026 — 27,881 subscribers17 August 2026 — 27,894 subscribers18 August 2026 — 27,903 subscribers19 August 2026 — 27,943 subscribers20 August 2026 — 27,972 subscribers22 August 2026 — 27,976 subscribers23 August 2026 — 27,974 subscribers25 August 2026 — 27,978 subscribers26 August 2026 — 27,972 subscribers27 August 2026 — 28,035 subscribers28 August 2026 — 28,070 subscribers29 August 2026 — 28,073 subscribers30 August 2026 — 28,079 subscribers31 August 2026 — 28,080 subscribers1 September 2026 — 28,076 subscribers2 September 2026 — 28,068 subscribers3 September 2026 — 28,145 subscribers6 September 2026 — 28,183 subscribers9 September 2026 — 28,227 subscribers6 August 20269 September 2026
30 measurements spanning 34 days, net +348. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 27,773–28,286 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
9 Sept 2026, 11:4128,227+44
6 Sept 2026, 01:1928,183+38
3 Sept 2026, 22:4028,145+77
2 Sept 2026, 11:5728,068-8
1 Sept 2026, 11:2828,076-4
31 Aug 2026, 08:4328,080+1
30 Aug 2026, 06:3828,079+6
29 Aug 2026, 04:2828,073+3
28 Aug 2026, 01:2828,070+35
27 Aug 2026, 00:4328,035+63
26 Aug 2026, 03:0827,972-6
25 Aug 2026, 03:3327,978+4
23 Aug 2026, 23:1427,974-2
22 Aug 2026, 03:5527,976+4
20 Aug 2026, 17:2427,972+29
19 Aug 2026, 20:4227,943+40
18 Aug 2026, 21:1227,903+9
17 Aug 2026, 19:3827,894+13
16 Aug 2026, 14:0527,881-4
14 Aug 2026, 23:4327,885first reading

Engagement

44 posts held, back to 26 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 60 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
49.3%
avg views ÷ 28,227 subscribers
Avg views / post
13,900
24 posts measured
Reaction rate
1.01%
reactions ÷ views · ER floor
Posts in window
24
of 44 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held44 (26 June 20263 September 2026)
Views total334,090
Reactions total3,376
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Sept 2026, 07:00 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.

Reaction mix

6,122 reactions across 44 posts, in 7 distinct kinds. The most used accounts for 33.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2,03433.2%
🔥1,33321.8%
🤯1,00416.4%
🤣66610.9%
😭63510.4%
👍4286.99%
👀220.359%

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 44 of the 44 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 6,122 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 44 most recent posts we hold, published 26 June 2026 to 3 September 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.

Telegram Stars

Stars received
87
across the posts below
Posts paid on
18
of 44 we hold a reading for · 41%
Most on one post
52
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mlmonchain. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 44 most recent posts we hold for this entry, published 26 June 2026 to 3 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

3 Sept 2026, 10:20 UTC≈15,900 views149 reactionsread 4 September 2026

Loracle is betting heavily against Robinhood coins, shorting 9.13M PONS ($5M) and 22.5M CASHCAT ($5.7M), making him the largest shorter in both markets on Hyperliquid. He is currently down a combined $1.4M on the two shorts. https://hypurrscan.io/address/0xefe4c06b6d310978bead596e1798a4fc1d9d194b

🤣106🤯43

31 Aug 2026, 16:44 UTC≈7,590 views146 reactions1 Starread 4 September 2026

*HYPERLIQUID IN TALKS WITH KRAKEN PARENT ON US MARKET ENTRY: BBG Link

🔥11333

29 Aug 2026, 08:55 UTC≈13,800 views82 reactions1 Starread 4 September 2026

Two days later, this entity is still unshielding ZEC and selling it on Hyperliquid. Over the past three days, it has unshielded a total of 112.8K ZEC ($90M), of which 13.05K ZEC ($10.4M) remains unsold. The ZEC wasn’t shielded for long. This entity shielded it just minutes before unshielding it and depositing it into Hyperliquid, presumably to obscure the trail. All of the ZEC appears to have been withdrawn from Bi

58😭24

29 Aug 2026, 08:39 UTC≈10,300 views66 reactions1 Starread 4 September 2026

Outcome has deployed the first DEX on HIP-4, called “OUT.” https://app.hyperliquid.xyz/explorer/tx/0xac56fb89c1c8203aadd0044338c77801fc00136f5ccb3f0c501fa6dc80cbfa25

48🤯18

28 Aug 2026, 22:00 UTC≈10,900 views134 reactions1 Starread 4 September 2026

Unit deposited $15M USDC into Hyperliquid over the past three hours and has bought 136K HYPE ($10.9M) so far, while continuing to buy HYPE with the remaining USDC. https://hypurrscan.io/address/0x3842544417dd7aaddeb83dc699484dcc4e5b9b9a With Unit testing HIP-4 stuff on testnet and already holding 350K HYPE, this purchase would give it roughly the 500K additional HYPE needed to launch a HIP-4 DEX. It is therefore pr

103👍31

28 Aug 2026, 16:41 UTC≈10,500 views113 reactions1 Starread 4 September 2026

HIP-4 permissionless deployments will be enabled on the next network upgrade. Templates will become available over time through validator vote.

🔥8726

28 Aug 2026, 14:30 UTC≈12,900 views84 reactionsread 4 September 2026

https://x.com/hyenatrade/status/2093345265247797530

😭70🤯14

28 Aug 2026, 09:23 UTC≈11,000 views141 reactionsread 4 September 2026

Over the past 60 hours, Hyperliquid Strategies has bought roughly $60M worth of $HYPE on HyperCore and roughly $16M worth of HYPE on CEXs. This amounts to roughly 920K–950K HYPE.

112👍29

27 Aug 2026, 15:28 UTC≈11,200 views88 reactionsread 4 September 2026

Two wallets I believe are linked to Hermeneutic have sold ~$15M worth of HYPE over the past three days. They still hold 660K HYPE ($56M), which they are slowly selling. https://hypurrscan.io/address/0x0a8494f70031623c9c0043aff4d40f334b458b11 https://hypurrscan.io/address/0xfc1ccff3fa575ce4297ac24aa00c06946bcf40da

👍55🤣33

27 Aug 2026, 08:08 UTC≈10,900 views89 reactionsread 4 September 2026

The wallets above are still unshielding ZEC and selling it on Hyperliquid. They have unshielded a total of 65.82K ZEC ($51.6M), or roughly 0.4% of ZEC’s circulating supply and 1.37% of all currently shielded ZEC, and sold 53.9K ZEC ($42.3M) while buying 536.7 BTC so far. The unshieldings are still ongoing, and they have placed sell orders for another 8.37K ZEC ($6.6M) on Hyperliquid.

👍67👀22

26 Aug 2026, 15:30 UTC≈14,100 views193 reactions5 Starsread 4 September 2026

According to my estimates, Hyperliquid Strategies has bought 430K–450K HYPE (~$35M) over the past 26 hours and continues to buy.

136🤯57

26 Aug 2026, 15:10 UTC≈12,200 views102 reactions1 Starread 4 September 2026

A wallet cluster possibly related to Sakolkorn Sakavee, the co-founder and former chairman of Bitkub (Thailand’s largest crypto exchange), unshielded 34.1K ZEC ($26.1M) over the past day and deposited it to Hyperliquid. He then sold 24.1K ZEC ($18.5M) and bought 238 BTC. There is still 10K ZEC ($7.6M) on Hyperliquid, with sell orders placed around $780. 0x614e08cf0b6ab0248b040e0103be6ba61716b8e3 0x59ad11e7eb8de6b

77😭25

Showing the 12 most recent of 44 posts we hold for @mlmonchain. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@mlmonchain edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
21 August 2026
Most recent edit
28 August 2026

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

Named by 13 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.

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.

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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“Mlm onchain” (@mlmonchain), 28,227 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/mlmonchain.

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.