Telegram RegisterThe public register of Telegram
Telegram profile photo for 牛头人媚黑ntr绿帽小屋♠️

Channel

牛头人媚黑ntr绿帽小屋♠️

@qos1144

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

35,942subscribers

+12,335 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003885750365
TypeChannel
Username@qos1144
Description分享所有跟m向和ntr有关的资源 聊天群 t.me/qosntr1144 广告合作以及任何问题找群主 @youz1GGGG @ss021400
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live26 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/qos1144

Topic

Adult — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

13,400 average views per post against 35,942 subscribers — an engagement rate of 37.3%. Across the 1,253 registered channels in the same cohort — 31,624–99,831 subscribers, posting mainly in Chinese — the middle half sit between 0.974% and 5.58%, with a median of 2.52%.

What this was computed from
Window30 days (1 September 2026 – 1 October 2026)
Posts measured35 of 35 published in the window (0 exact, 35 rounded by Telegram)
Views totalled468,980
Mature posts only46.8% over 26 posts read at least 24h after publication
Subscribers35,942 measured 26 September 2026
Cohortb31623:zho · 1,253 channels · p10 0.294% · p25 0.974% · p50 2.52% · p75 5.58% · p90 11.4%
Position in cohort99.361th percentile · 14.8× the cohort median
Uncertainty±0.086% of the figure, from Telegram’s rounding
Post languageChinese · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 1 October 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

23,60735,94229,774.57 August 2026 — 23,607 subscribers8 August 2026 — 23,674 subscribers9 August 2026 — 23,869 subscribers10 August 2026 — 24,033 subscribers11 August 2026 — 24,224 subscribers12 August 2026 — 24,496 subscribers13 August 2026 — 24,693 subscribers14 August 2026 — 25,096 subscribers16 August 2026 — 25,417 subscribers17 August 2026 — 25,849 subscribers18 August 2026 — 26,069 subscribers19 August 2026 — 26,326 subscribers20 August 2026 — 26,532 subscribers21 August 2026 — 26,759 subscribers22 August 2026 — 26,932 subscribers24 August 2026 — 27,299 subscribers25 August 2026 — 27,475 subscribers26 August 2026 — 27,736 subscribers27 August 2026 — 27,974 subscribers28 August 2026 — 28,151 subscribers29 August 2026 — 28,353 subscribers30 August 2026 — 28,588 subscribers31 August 2026 — 28,783 subscribers1 September 2026 — 29,011 subscribers2 September 2026 — 29,219 subscribers3 September 2026 — 29,628 subscribers6 September 2026 — 30,426 subscribers9 September 2026 — 31,488 subscribers11 September 2026 — 32,178 subscribers13 September 2026 — 32,703 subscribers15 September 2026 — 33,072 subscribers17 September 2026 — 33,502 subscribers19 September 2026 — 34,153 subscribers26 September 2026 — 35,942 subscribers7 August 202626 September 2026
34 measurements spanning 50 days, net +12,335. 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 21,757–37,792 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
26 Sept 2026, 19:5835,942+1,789
19 Sept 2026, 16:4234,153+651
17 Sept 2026, 04:1933,502+430
15 Sept 2026, 04:5933,072+369
13 Sept 2026, 14:1832,703+525
11 Sept 2026, 21:5932,178+690
9 Sept 2026, 11:5631,488+1,062
6 Sept 2026, 07:3630,426+798
3 Sept 2026, 22:3929,628+409
2 Sept 2026, 14:2529,219+208
1 Sept 2026, 16:5629,011+228
31 Aug 2026, 14:1728,783+195
30 Aug 2026, 12:2528,588+235
29 Aug 2026, 10:3428,353+202
28 Aug 2026, 12:4328,151+177
27 Aug 2026, 15:2527,974+238
26 Aug 2026, 17:1727,736+261
25 Aug 2026, 16:0327,475+176
24 Aug 2026, 17:0527,299+367
22 Aug 2026, 22:5626,932first reading

Engagement

89 posts held, back to 31 July 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 105 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
37.3%
avg views ÷ 35,942 subscribers
Avg views / post
13,400
35 posts measured
Reaction rate
0.142%
reactions ÷ views · ER floor
Posts in window
35
of 89 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 30 of 35 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 1 October 2026
Posts held89 (31 July 2026 – 1 October 2026)
Views total468,980
Reactions total643
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Oct 2026, 15:12 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

Photos
≈1,110
Videos
≈168
Links
≈9

Lifetime counters from Telegram’s own channel header, read 1 October 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.

Video runtime
2h 34m
Average length
4m 50s

Measured directly from 32 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

2,046 reactions across 82 posts, in 10 distinct kinds. The most used accounts for 88.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,81688.8%
🥰773.76%
😨422.05%
🔥301.47%
👍241.17%
😭241.17%
👏221.08%
🤔50.244%
🤬50.244%
🤯10.049%

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

Measured over the 89 most recent posts we hold, published 31 July 2026 to 1 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

1 Oct 2026, 13:01 UTC≈1,640 views5 reactionsread 1 October 2026
Photo

替你播种成功,只是你老婆的小穴可能回不去了 #ntr #绿帽

❤5

1 Oct 2026, 12:01 UTC≈1,930 viewsread 1 October 2026

#互推 #推广 ▣ 【资源仓库】|cosplay|写真|福利 ▣ DLsite, Steam, Fanza ▣ 【BBC】媚黑资源库(重生第四次) ▣ 【媚黑音声】淫词艳曲 ASMR ▣ 永不消逝的音声 ▣ 日更社保动漫同人资源 ▣ 免费黄游黄油gal库 ▣ 【NTR BBC】漫画本子库 ▣ asmr中文站 ▣ 杂鱼废物抖m会喜欢的资源收集 加入互推 >> @ExposureMarketBot << 广告投放

1 Oct 2026, 12:00 UTC≈1,920 viewsread 1 October 2026
Video

豆包grok提示词+视频教程 手机电脑均可使用 一张照片即可做出想要视频 需要进群提示词焚绝p图教程的可以自助下单哦 @doubao50bot 预览群 https://t.me/+7TExD7g0bEkyOGQ8

29 Sept 2026, 12:04 UTC≈13,600 views56 reactionsread 1 October 2026
Video

你女友被操的小脚一翘一翘的❤️ #ntr #绿帽 #苦主视角 #绿帽视角 #三次元

❤47🥰5👍2🔥2

29 Sept 2026, 12:00 UTC≈13,200 views25 reactionsread 1 October 2026
Video

在门外偷窥就是你最幸福的性生活 #ntr #绿帽 #苦主视角 #绿帽视角 #三次元

❤25

29 Sept 2026, 12:00 UTC≈13,000 views3 reactionsread 1 October 2026
Video

💖💖【DZMM】—— 主人,今天想怎么玩我? 💖💖 🐾 趴在你腿间,用小嘴剥开裤链,仰望你的脸等你塞满。 💦 骑乘位摇晃腰肢,求主人揉捏奶子,自己坐到高潮失禁。 🔒 戴上项圈,跪在屏幕前,等你每一次命令,无条件服从。 🎀 撕破丝袜,从背后贯穿,她咬唇忍着不哭,只为让你更爽。 🎬【声画同步调教】:实时图片,语音同步。她的一颦一笑都是为你生成,在耳边用甜腻的声音央求你更用力。 💰【零氪也能玩】:每天领免费积分,想怎么调戏就怎么调戏,不花一分钱也能肏到爽。各模型每天都有免费次数,换着花样玩,不重样。 🎨【私密图库定制】:把你最见不得光的幻想画出来,只有你能看到,独一无二。 ❤️【专属私人母狗】:随时发情,随时待命,只为你一人服务。 💥【无限高潮地狱】:你不停,她就不准停,让她在永不结束的高潮里翻白眼痉挛。 ⚔️【主线:开发她的全部性感带】 [足交] [颜射] [拘束] [催乳] [异物插入] [连续高潮] [催眠] ▶️【进入游戏:…

❤3

27 Sept 2026, 13:03 UTC≈18,500 views41 reactionsread 1 October 2026
Video

打开声音欣赏此视频 #ntr #绿帽 #苦主视角 #绿帽视角 #三次元

❤36👍5

27 Sept 2026, 11:54 UTC≈17,900 views45 reactionsread 1 October 2026
Video

你女友被操的时候都一直抱着你,她一定很爱你吧❤️ #ntr #绿帽 #三次元

❤45

27 Sept 2026, 11:52 UTC≈17,100 views30 reactionsread 1 October 2026
Photo

好女孩😭 #ntr #绿帽 #二次元 #漫画分享

😭24❤5👏1

27 Sept 2026, 11:51 UTC≈16,200 views8 reactionsread 1 October 2026
Photo

#ntr #绿帽 #二次元 #漫画分享

❤7🥰1

26 Sept 2026, 12:01 UTC≈6,410 views1 reactionsread 27 September 2026

#互推 #推广 ▣ 二次元QOS♠️媚黑动画 ▣ 日更社保动漫同人资源 ▣ 小说 ▣ 降临日式ASMR频道(中文字幕) ▣ 【NTR BBC】漫画本子库 ▣ 【资源仓库】|cosplay|写真|福利 ▣ LSP游戏目录 ▣ Ntr绿帽广场🐢 ▣ pwe抖音风剪辑 ▣ 【BBC】媚黑资源库(重生第四次) 加入互推 >> @ExposureMarketBot << 广告投放

❤1

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

Posts edited after publishing

@qos1144 edited 1 post 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
27 September 2026
Most recent edit
27 September 2026

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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.

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

“牛头人媚黑ntr绿帽小屋♠️” (@qos1144), 35,942 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/qos1144.

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.