Channel
@nmcnm66
On this record: Growth · Engagement · Posts · Citations · Cite this entry
343subscribers
+7 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004366831870 |
|---|---|
| Type | Channel |
| Username | @nmcnm66 |
| Created | Between 1 June 2026 and 9 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/nmcnm66 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 20:36 | 343 | +7 |
| 10 Aug 2026, 06:16 | 336 | first reading |
11 posts held, back to 9 August 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.
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.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 11 (9 August 2026 – 10 August 2026) |
| Views total | 58 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 06:16 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.
南风全网互推 点击一键加入全网最强挂圈封号圈 点击一键加入全网最强挂圈封号圈 点击一键加入全网最强挂圈封号圈 点击一键加入全网最强挂圈封号圈 点击一键加入全网最强挂圈封号圈 广告位 全网最真实低价的卡网 里面有低价飞机号和国外微信 支付宝 https://gganh.226618.xyz 互推联系 @NFNB66667 频道 https://t.me/NFNBYYD66
Signed 南风 （收广告位）
能不能用
Signed 雾欢
公益全国头思路 苹果快捷指令使用📥 https://www.icloud.com/shortcuts/399539d5d68a42759e752d82a61c8749
Signed 天天开心
打色情本和稍微擦边的，打掉反馈 尊敬的快手审核工作人员： 现正式举报快手违规用户🆔，该账号长期大量发布软色情、低俗擦边作品，依靠刻意制造诱惑氛围博取流量，严重违反社区规范，污染网络环境。 该用户作品无直接裸露违规画面，但全程属于典型软色情引流。视频中频繁出现刻意妩媚姿态、撩人眼神、扭摆肢体、贴身特写、过度性感的动作举止，搭配暧昧文案、低俗氛围感滤镜。通过各种刻意诱惑、搔首弄姿的妩媚动作制造性暗示效果，游走在平台规则边缘，打擦边博取关注，内容低俗不堪。 该账号所有作品全部公开推送，快手平台包含大量中小学生及未成年群体。心智尚未成熟的青少年频繁刷到此类软色情、妩媚擦边内容，极易被不良风气误导，扭曲审美观念与身心健康认知，严重违背未成年人网络保护准则，对青少年身心成长造成极大负面影响。 该用户并非单次违规，而是批量、持续性发布同类软色情擦边内容，刻意利用审核漏洞反复传播低俗风气，刻意制造诱惑、暧昧、挑逗的不良氛围，长期破坏平台清…
Signed 雾欢
南风全网互推 点击一键加入全网最强挂圈封号圈 点击一键加入全网最强挂圈封号圈 点击一键加入全网最强挂圈封号圈 点击一键加入全网最强挂圈封号圈 点击一键加入全网最强挂圈封号圈 广告位 全网最真实低价的卡网 里面有低价飞机号和国外微信 支付宝 https://gganh.226618.xyz 互推联系 @NFNB66667 频道 https://t.me/NFNBYYD66
Signed 南风 （收广告位）
#编号5 邮箱手机号我的 减去其他 6颗宝石任意兑换 价格38 联系 @GGHGANH 频道 https://t.me/GGANHYYDS
Signed 南风 （收广告位）
✉️你还在苦恼找不到Telegram优质资源而发愁吗 想找公益封号思路的频道？想找经常送福利可以白嫖各种账号 靓号 nft 红包的频道？ 🔗一键加入Telegram优质频道 点击我一键加入所有优质频道 点击我一键加入所有优质频道 点击我一键加入所有优质频道 飞机账号源头卡网 ⬇️ https://tgsss.com/23BAD69A/ 互推联系 @fox_caller 双向联系 @xuaoqbot 此条消息可在一小时后删除 请勿秒删 多次秒删踢出互推
这是哪个傻逼，逗死了
Signed lemmon
✉️你还在苦恼找不到Telegram优质资源而发愁吗 想找公益封号思路的频道？想找经常送福利可以白嫖各种账号 靓号 nft 红包的频道？ 🔗一键加入Telegram优质频道 点击我一键加入所有优质频道 点击我一键加入所有优质频道 点击我一键加入所有优质频道 飞机账号源头卡网 ⬇️ https://tgsss.com/23BAD69A/ 互推联系 @fox_caller 双向联系 @xuaoqbot 此条消息可在一小时后删除 请勿秒删 多次秒删踢出互推
单月会员😍 ❤️❤️❤️❤️❤️ 代开联系 @LuYou520
Signed 天天开心
#编号1 经典70地铁30薇拉满级 手机号和邮箱都是我的 因手机号丢失质保手机号登录(两天后换绑) 鸭子圣装 骚圣装 满星云 其他自己看 价格 : 128 联系 @GGHGANH 频道 https://t.me/GGANHYYDS
Signed 南风 （收广告位）
Showing the 11 most recent of 11 posts we hold for @nmcnm66. 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 — 871,343 of 1,160,990entries 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.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“柠檬主频道” (@nmcnm66), 343 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/nmcnm66.
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.