Telegram RegisterThe public register of Telegram
Telegram profile photo for 莫名一手微信号商🍉

Channel

莫名一手微信号商🍉

@maolmx619

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

119subscribers

+14 since we began measuring on 12 October 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002737339543
TypeChannel
Username@maolmx619
CreatedBetween 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 October 2026
Last confirmed live28 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/maolmx619

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 28 October 2026 and assigned it the closest of 31 fixed categories, at 48% 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.

Growth

10511911212 October 2026 — 105 subscribers14 October 2026 — 105 subscribers28 October 2026 — 119 subscribers12 October 202628 October 2026
3 measurements spanning 15 days, net +14. 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 103–121 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Oct 2026, 01:41119+14
14 Oct 2026, 07:28105no change
12 Oct 2026, 17:22105first reading

Engagement

12 posts held, back to 3 September 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
53.6%
avg views ÷ 119 subscribers
Avg views / post
63.8
8 posts measured
Reaction rate
1.90%
reactions ÷ views · ER floor
Posts in window
8
of 12 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. It is computed over the 4 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 October 2026
Posts held12 (3 September 2026 – 12 October 2026)
Views total510
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Oct 2026, 17:22 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.

What this channel posts

Video runtime
1m 39s
Average length
33s

Measured directly from 3 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.

Reaction mix

8 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 87.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤787.5%
👍112.5%

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

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

Recent posts

12 Oct 2026, 08:42 UTC34 viewsread 12 October 2026
Photo

企业微信绿标主体,二合一有货,已开获客,子账号,大量有货,有需要的老板联系!

12 Oct 2026, 07:53 UTC42 views1 reactionsread 12 October 2026
Photo

接预定 …每日更新15+ 😀工作室~(微信 )支付~零钱通~经营码 接预定 ✅✅✅[交易更安全] ✅✅✅ [有问题售后包退换]全网独家

❤1

12 Oct 2026, 05:05 UTC67 views2 reactionsread 12 October 2026
Photo

代加工,实名热门APP,有需要的联系!

❤2

11 Oct 2026, 07:59 UTC72 viewsread 12 October 2026
Photo

企业微信绿标主体,三合一,子账号,大量有货,有需要的老板联系!

11 Oct 2026, 07:43 UTC68 viewsread 12 October 2026
Photo

最新技术,国内年号已过二次人脸,安全验证,华为备份包包加人,包加人,无支付,省去邮寄风险,养24小时直接开工,原来的味道,需要的老板滴

9 Oct 2026, 11:37 UTC74 views1 reactionsread 12 October 2026

最新技术,国内年号已过二次人脸,安全验证,华为备份包包加人,包加人,无支付,省去邮寄风险,养24小时直接开工,原来的味道,需要的老板滴

❤1

9 Oct 2026, 11:37 UTC73 viewsread 12 October 2026

最新技术,国内年号已过二次人脸,安全验证,华为备份包包加人,包加人,无支付,省去邮寄风险,养24小时直接开工,原来的味道,需要的老板滴

8 Oct 2026, 11:59 UTC80 views1 reactionsread 12 October 2026
Photo

最新技术,国内年号已过二次人脸,安全验证,华为备份包包加人,包加人,无支付,省去邮寄风险,养24小时直接开工,原来的味道,需要的老板滴

❤1

19 Sept 2026, 09:41 UTC147 viewsread 12 October 2026
Video

$$顶级白号$$-可加好友,可进群 每天在线精养12小时以上,连续养了最低2个月,已经养到可以加好友的地步了,已绑卡《不能收付款》

5 Sept 2026, 15:04 UTC202 views1 reactionsread 12 October 2026
Video

大量,出去出!三个月,半年,一年白号,带设备,统一手机,华为mt10 来个老板打包!

👍1

4 Sept 2026, 01:21 UTC167 views1 reactionsread 12 October 2026
Video

大量,出去出!三个月,半年,一年白号,带设备,统一手机,华为mt10 来个老板打包!

❤1

3 Sept 2026, 03:56 UTC143 views1 reactionsread 12 October 2026
Photo

企业微信绿标主体,三合一,子账号,大量有货,有需要的老板联系!

❤1

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

Named by 3 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 28 October 2026 — this entry's latest reading, not the date you are reading this.

“莫名一手微信号商🍉” (@maolmx619), 119 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/maolmx619.

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.