Engagement
6 posts held, back to 24 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 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 27.1%
- avg views ÷ 244 subscribers
- Avg views / post
- 66.2
- 6 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 6
- of 6 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 1 of 6 measured posts that carry a reaction reading, and over those same posts' views.
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.
Recent posts
30 Aug 2026, 06:32 UTC33 viewsread 3 September 2026 Photo
✨瑞琳✨🔠🔠0️⃣5️⃣
🌸奶媽系列🌸🔣真人實拍 🔣
刚满月新人乃马,产地,东北人,巨乳肥臀,奶量大(500cc),漂亮温柔性格好,口好棒,人特别骚,欢迎老板❤️❤️❤️
年齡:2️⃣5️⃣
身高:1️⃣6️⃣4️⃣🔠🔠
體重:5️⃣3️⃣🔠🔠
三圍:3️⃣6️⃣🔠
服務項目:🔣陪浴 🔣親吻🔣69 🔣環保吹 🔣愛愛💗🔣
制服誘惑
💲🔣3️⃣0️⃣0️⃣0️⃣➗1️⃣🔠
❤️🔥北上广深當天🉑隨機安排❤️🔥
一线二三四五线城市都可安排次或包天、空降!✈️✈️✈️
🥰🥰🥰🥰🥰🥰🥰🥰
聯繫客服:👇
📱:@nyzhuanqu
Signed Gg gyer2000
30 Aug 2026, 06:00 UTC42 viewsread 3 September 2026 Photo
Photo, posted without a caption
Signed Gg gyer2000
29 Aug 2026, 06:17 UTC36 viewsread 3 September 2026 Photo
✨少数民族✨🔠🔠0️⃣🥰🥰
🌸转运珠系列🌸🔣真人實拍 🔣
年齡:2️⃣🥰
身高:1️⃣🥰🥰🔠🔠
體重:🥰🥰🔠🔠
三圍:🔠
服務項目:🔣陪浴 🔣舌吻🔣69 🔣環保吹 🔣愛愛💗🔣
制服誘惑
💲🔣🥰0️⃣0️⃣0️⃣➗1️⃣🔠
❤️🔥北上广深當天🉑隨機安排❤️🔥
一线二三四五线城市都可安排次或包天、空降!✈️✈️✈️
🥰🥰🥰🥰🥰🥰🥰🥰
聯繫客服:👇
📱:@nyzhuanqu
Signed Gg gyer2000
25 Aug 2026, 01:46 UTC100 views0 reactionsread 3 September 2026 Photo
✨少数民族✨🔠🔠0️⃣🥰🥰
🌸转运珠系列🌸🔣真人實拍 🔣
年齡:2️⃣🥰
身高:1️⃣🥰🥰🔠🔠
體重:🥰🥰🔠🔠
三圍:🔠
服務項目:🔣陪浴 🔣舌吻🔣69 🔣環保吹 🔣愛愛💗🔣
制服誘惑
💲🔣🥰0️⃣0️⃣0️⃣➗1️⃣🔠
❤️🔥北上广深當天🉑隨機安排❤️🔥
一线二三四五线城市都可安排次或包天、空降!✈️✈️✈️
🥰🥰🥰🥰🥰🥰🥰🥰
聯繫客服:👇
📱:@nyzhuanqu
Signed Gg gyer2000
24 Aug 2026, 11:59 UTC93 viewsread 3 September 2026 前一阵身体不适,没能及时回复信息,以后不会了,欢迎哥哥预约
Signed Gg gyer2000
24 Aug 2026, 11:59 UTC93 viewsread 3 September 2026 Photo
✨四川小美妞✨🔠🔠0️⃣🥰🥰
🌸奶媽系列🌸🔣真人實拍 🔣
稀缺资源,上下齐喷,哺乳期兼职,28岁,身高:163cm体重:55kg 罩杯:38H,宝宝两个月,奶水充足,口感清甜。肤白细嫩,温柔可人,三点粉,紧致💦多,可秒喷,配合度高,活好事少,期待邂逅,
年齡:2️⃣🥰
身高:1️⃣🥰🥰🔠🔠
體重:5️⃣🥰🔠🔠
三圍:3️⃣8️⃣🔠
服務項目:🔣陪浴 🔣舌吻🔣69 🔣環保吹 🔣愛愛💗🔣
制服誘惑
💲🔣3️⃣0️⃣0️⃣0️⃣➗1️⃣🔠
❤️🔥北上广深當天🉑隨機安排❤️🔥
一线二三四五线城市都可安排次或包天、空降!✈️✈️✈️
🥰🥰🥰🥰🥰🥰🥰🥰
聯繫客服:👇
📱:@nyzhuanqu
Signed Gg gyer2000
Showing the 6 most recent of 6 posts we hold for @nyquanguokefei. 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 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.
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 12 September 2026 — this
entry's latest reading, not the date you are reading this.
“LUCKY STRIKE 全国奶妈好运修车群” (@nyquanguokefei), 244 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/nyquanguokefei.
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.