Telegram RegisterThe public register of Telegram
Telegram profile photo for 潍坊上门约

Channel

潍坊上门约

@moszhmoyn

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

1,259subscribers

-108 since we began measuring on 5 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003084033120
TypeChannel
Username@moszhmoyn
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 September 2026
Last confirmed live16 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/moszhmoyn

Growth

1,2591,3671,3135 September 2026 — 1,367 subscribers5 September 2026 — 1,367 subscribers8 September 2026 — 1,356 subscribers13 September 2026 — 1,291 subscribers16 September 2026 — 1,259 subscribers5 September 202616 September 2026
5 measurements spanning 11 days, net -108. 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 1,243–1,383 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 20:181,259-32
13 Sept 2026, 06:011,291-65
8 Sept 2026, 23:561,356-11
5 Sept 2026, 21:221,367no change
5 Sept 2026, 20:471,367first reading

Engagement

7 posts held, back to 25 August 2026the 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
0.556%
avg views ÷ 1,259 subscribers
Avg views / post
7.0
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
7
of 7 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 September 2026
Posts held7 (25 August 20265 September 2026)
Views total49
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Sept 2026, 21: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
24s
Average length
8s

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.

Recent posts

5 Sept 2026, 21:20 UTC1 viewsread 5 September 2026

AD:♻️🟣🍎夫妻绿帽多人🟢🔞 💛 🔥白冰互推A8车队🔥 1. ⭐️神木丽全裸体育测试 2. 💒我把这骚货按床上从后面猛干 3. 👁肥臀挨着重拍啪啪响 4. ⚡️妹子偷情操逼,男朋友查岗 5. ❤️办公室桌下她跪着猛吞鸡巴❤️ 6. 国产_日韩福利精选 7. 🌷无法拒绝前辈的大屌 8. 潍坊上门约 9. 真实学生反差母狗萝莉 10. 🕶我的内裤很能装逼 11. ✨小玫深夜长途列车上忍不住跟男人激情缠绵 12. 💫风骚人妻,骚气十足,床上功夫一流 13. 骚货小母狗 14. ✨图书馆厕所里激情操逼 15. 🎀嘴巴张大吞下整根粗屌 16. 💋胖爷旅行路上遇见个浪妹 17. 高颜值母狗 18. 👅金主戴面具找来两个JK学生妹子双飞 19. 极品白虎萝莉嫩穴 BAD:㊙️💕黑色性感内衣小姐姐了💕㊙️ BAD:🉐✅🌺猛插19岁乖乖女🌺

5 Sept 2026, 07:17 UTC2 viewsread 5 September 2026
Photo

🔥TeleTop 频道推荐 📢(汕头)外围兼职精选 📢广州 美腿 街拍 偷拍 丝袜 📢SS 金三角私密影院 🎬 📢偷拍学生清纯素人中出探花 📢烟台上门约 📢漫声AI配音语音|游戏动漫国漫二次元|原... 📢长春外卖上门频道 📢厦门福州抓龙筋 女王调教 📢中文字幕-绿帽NTR-日本AV 📢AV福利中心| 每日高清资源更新 💎广告推荐 📢⚽️注册送138🧧百家乐/棋牌/电竞体... 📢🔥最强平台强势来袭,掀起智能合约新风暴... 📢飞哥数据🌍SDK·DPI⚙️钉钉💰支... 🔍互推公示 🪧流量互推说明

31 Aug 2026, 21:19 UTC5 viewsread 5 September 2026
Photo

🚀帮助您找到感兴趣的群组、频道和机器人 📊频道分析 📢官方频道

26 Aug 2026, 16:14 UTC15 viewsread 5 September 2026
Photo

身高166 绝美冷白皮🥛 婴儿肌肤吹弹可破 态度好服务赞 脾气好 懂事乖巧 真人真照 ⚡️出门 气质甜美 清纯可爱 ❣️无需提前任何费用即可安排 🈶照片可选人,低消费,高质量❗️ 🏅信誉商家,合作一次,永远不用担心被骗子套路了 💯专业资源💯安全靠谱💯合作愉快💯 🌹唯一客服🛫TG:@chayuanyuan1 🌹双向限制🛫TG: @chayuanyuan1bot

26 Aug 2026, 16:11 UTC10 viewsread 5 September 2026
Photo

• 𝐇𝐞𝐢𝐠𝐡𝐭身高/1.66净足 • 𝐁𝐮𝐬𝐭胸围/真🐻B • 𝐀𝐠𝐞年龄/99 🌈甜美声线高学历情商高 皮肤雪白💡 洋气五官精致 自然脸

26 Aug 2026, 16:10 UTC7 viewsread 5 September 2026
Photo

05年,165 C 身体柔软,温柔体贴 纯天然mm,刚来不久,紧致 ❣️无需提前任何费用即可安排 🈶照片可选人,低消费,高质量❗️

25 Aug 2026, 19:01 UTC9 viewsread 5 September 2026
Photo

🐻C天然无整 皮肤白皙 性格温柔 温柔体贴 ❤️专治神挑 给你女友般感觉 高情商 音超甜 听话不事。 ❣️无需提前任何费用即可安排 🈶照片可选人,低消费,高质量❗️

Showing the 7 most recent of 7 posts we hold for @moszhmoyn. 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 6 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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“潍坊上门约” (@moszhmoyn), 1,259 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/moszhmoyn.

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.