#互推 #推广 ▣ 🔞Rule34 / Futa🔞 ▣ 𒆜✿Traps | 南梁扶他射 | Fu ▣ (❤️ ω ❤️) 每日色色漫画 😍 ▣ 【资源仓库】|cosplay|写真|福利 ▣ 【BBC】媚黑资源库(重生第四次) ▣ 阿卡姆艺术院 ▣ 高清AV|黑丝调教|乱伦强奸 ▣ 【NTR BBC】漫画本子库 ▣ 日更社保动漫同人资源 ▣ 【关注频道炸了?】帮你回家导航站! 加入互推 >> @ExposureMarketBot << 广告投放
👍1

Channel
@ntrlvmaosquare11
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
3,369subscribers
+3,223 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003978912977 |
|---|---|
| Type | Channel |
| Usernames | @ntrlvmaobus @ntrlvmaosquare11 |
| Description | 本群作为新的Ntr绿帽广场🐢重生了! |
| Created | 22 August 2026 — measured — dated from the channel’s first post |
| First recorded | 22 August 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 11 |
| On Telegram | t.me/ntrlvmaosquare11 |
Other / unclassifiable — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 12:22 | 3,369 | no change |
| 5 Oct 2026, 11:47 | 3,369 | +2,974 |
| 27 Sept 2026, 23:19 | 395 | -1,508 |
| 18 Sept 2026, 11:55 | 1,903 | +123 |
| 13 Sept 2026, 18:57 | 1,780 | +91 |
| 9 Sept 2026, 19:35 | 1,689 | +182 |
| 4 Sept 2026, 07:38 | 1,507 | +215 |
| 31 Aug 2026, 13:13 | 1,292 | +920 |
| 23 Aug 2026, 20:06 | 372 | +226 |
| 22 Aug 2026, 19:45 | 146 | no change |
| 22 Aug 2026, 19:30 | 146 | first reading |
17 posts held, back to 22 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 2 pages of 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 5 October 2026 |
|---|---|
| Posts held | 17 (22 August 2026 – 5 October 2026) |
| Views total | 21,580 |
| Reactions total | 162 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Oct 2026, 12: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.
Lifetime counters from Telegram’s own channel header, read 5 October 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.
Measured directly from 7 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.
165 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 49.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 81 | 49.1% | |
| 👍 | 50 | 30.3% | |
| 🥰 | 10 | 6.06% | |
| 🔥 | 7 | 4.24% | |
| 😍 | 7 | 4.24% | |
| 👌 | 3 | 1.82% | |
| 🥱 | 3 | 1.82% | |
| 🤡 | 2 | 1.21% | |
| 💯 | 1 | 0.606% | |
| 🤮 | 1 | 0.606% |
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 16 of the 17 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 165 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 22 August 2026 to 5 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.
#互推 #推广 ▣ 🔞Rule34 / Futa🔞 ▣ 𒆜✿Traps | 南梁扶他射 | Fu ▣ (❤️ ω ❤️) 每日色色漫画 😍 ▣ 【资源仓库】|cosplay|写真|福利 ▣ 【BBC】媚黑资源库(重生第四次) ▣ 阿卡姆艺术院 ▣ 高清AV|黑丝调教|乱伦强奸 ▣ 【NTR BBC】漫画本子库 ▣ 日更社保动漫同人资源 ▣ 【关注频道炸了?】帮你回家导航站! 加入互推 >> @ExposureMarketBot << 广告投放
👍1
为什么娇艳美丽的妈妈会和陌生男人上床 #ntr #绿母 #剪辑 #抖音风 #投稿
❤7
来一次百破女绿 #ntr #女绿 #乐子
👍6
🚀加入极搜互推一起赚钱🚀
👍5👌2
好兄弟,来你家过节真是对的。在你不知道的地方把你全家女人都调教成母狗,一排排排在一起真爽啊❤️ #ntr #绿母 #绿帽 #肉便器 #肥臀 #母猪 #绿全家 #群p #母狗 #投稿
❤18👍6🥱2
妈妈这是在跟叔叔们做什么游戏啊 #群p #ntr #绿母
👍7🔥1
又一个发小结婚了,我要更新婚专辑🥳 #群主の碎碎念
🔥6
你妈和你爸操逼一直怀不上但想要二胎的她国庆出去旅游,提前联系了你的大鸡巴卵蛋同学,一到酒店的你妈和你的同学野爹立马开始造人,同学把浓精狠狠射进你妈子宫里,为你将来的弟妹播下了种
👍8❤2👌1🤮1
绿主野爹几把好大,直接给我女朋友种付了
❤13💯1
小时候就钻裤裆,长大了不得阿姨屄操烂啊 #ai
😍7
转发即代表:想在结婚那天让老婆穿成这样去敬酒 每个男人都得往你老婆逼里随两发精液,让她夹着满骚逼的白浆跟你洞房,记得操之前先把客人们的浓精都先舔干净,那可都是他们对你们这对贱狗夫妻的祝福。 #绿帽 #绿奴 #淫妻 #ntr #投稿 依旧新婚专辑
🥰9❤6👍2🥱1
自从爸爸出差后,没人管教的妈妈不运动就是吃,屁股和腿上都骚肉,奶子也涨起来了,时不时刻意露出来勾引你,不爱洗澡身上还有一股雌臭味,今天她还是躺在你床上自拍,只穿了一条内裤,阴毛都从里探出来了,你该怎么教育她 #母子 #乱伦
❤9🤡2
Showing the 12 most recent of 17 posts we hold for @ntrlvmaosquare11. 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.
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.
@ntrlvmaosquare11 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“Ntr绿帽广场🐢” (@ntrlvmaosquare11), 3,369 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/ntrlvmaosquare11.
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.