🎰 商家海参祝大家国庆快乐 📮 参与条件: 🌏️ 归属地 辽宁 🪪 必须设置用户名 🎫 加入-海参公主的日常 🎫 加入-大连精品修车 └ 🎟️ 发言数大于 50 条 🎁 奖品内容: 💰️ 红包100 × 1 ⚠️ 抽奖说明: 提示:禁止无脑刷屏,自言自语,删除消息,发纯数字和表情,短句发送,小号互搏等内容,发现全部取消中奖资格! 🔋 人品加成:⚡️⚡️ 规则 📅 开奖日期:(北京时间) 2026年10月03日 17时28分00秒

Channel
海参公主的日常
@haishengongzhu
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
47subscribers
+28 since we began measuring on 30 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004334375837 |
|---|---|
| Type | Channel |
| Username | @haishengongzhu |
| Created | Between 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 September 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/haishengongzhu |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Oct 2026, 15:59 | 47 | +28 |
| 30 Sept 2026, 10:22 | 19 | no change |
| 30 Sept 2026, 09:47 | 19 | first reading |
Engagement
12 posts held, back to 24 September 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
- 62.1%
- avg views ÷ 47 subscribers
- Avg views / post
- 29.2
- 12 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 12
- of 12 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.
| Window | Rolling 30 days · latest post in window 30 September 2026 |
|---|---|
| Posts held | 12 (24 September 2026 – 30 September 2026) |
| Views total | 350 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Sept 2026, 10: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
- 1m 43s
- Average length
- 34s
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
【时间】:2026-09-30 【老师】:海参 【留名】:阿虎 【人照】:10 【颜值】:10 【身材】:10 【服务】:10 【态度】:10 【环境】:10 【综合】:10 【过程】:天越来越冷了,出门买菜的时候发现大家在屯秋白菜,是时候该补补身体了,我也屯点川子的海参,先屯三十斤,留着冬天炖白菜慢慢吃 但是该说不说这海参品质确实不错,要说还是得岛里的参,参刺黄白,刺形粗壮圆钝,价格也合适,出击一趟千八百块钱,身体精华都给老师了,千八百块钱能买二斤海参,够吃半个月,精华都留给自己了,必须得对自己好点! 回见吧各位,我补一阵身体,看我出山后下一篇车评我桩死谁!
感谢tg~感谢修车~感谢老板选购~早起开单~需要礼盒请告知~
感谢tg 感谢修车 感谢老板选购~早起就开单~ 需要礼盒请告诉我~
【时间】:2026-09-29 【老师】:海参 【留名】:小鱼人Zone(🐮小、事少)八 【人照】:10 【颜值】:10 【身材】:10 【服务】:10 【态度】:10 【环境】:10 【综合】:10 【过程】:海参买不对,努力全白费。 俗话说,“选海参、辽参最佳” 现在俺说:“选辽参、喜多川最好” 正好川子海参到货了,先吃为敬。 📷人照指数:10 实物和商品照完全符合,无假照情况。 👄颜值气质:10 包装大气,送礼有面。 🩱身材综合:10 个头统一,多刺,且刺头坚挺,肉厚,呈纺锤形,标准的辽参。 🍽️口感等级:10 肉质紧实,弹脆均佳,适合多种烹饪方式 🦞综合打分:10 推荐指数:🌟🌟🌟🌟🌟 必吃榜 非常出色,来连必吃 总结:买海参找川子,安全又放心
把每一位顾客的饮食安全放在心上才是真正的品质保障!发出去的每一份海参产品都配有原产地地理标志码和专用检测试纸。确保每一位顾客的健康安全。
【时间】:2026-09-29 【老师】:海参 【留名】:闰土 【人照】:10 【颜值】:10 【身材】:10 【服务】:10 【态度】:10 【环境】:10 【综合】:10 【过程】:一分价钱一分货,好货只卖给懂得人! 这次买的川子海参,果然是正宗长海县刺参,肉质厚实、刺排整齐、色泽自然,一眼就能看出品质。口感脆嫩有弹性,没有一点腥味。 用过很多海参,真正懂行的人一看就知道这货不一样。价格是贵一点,但绝对对得起这个品质,8个头直接安排600根。干就完了!
【时间】:2026-09-29 【老师】:海参 【留名】:貔柴 【人照】:10 【颜值】:10 【身材】:10 【服务】:10 【态度】:10 【环境】:10 【综合】:10 【过程】:没想到在这里还能买海参,而且比市场便宜很多,因为常年吃,货到后就感觉品质超出预期,是在天然海底环境自然生长,不靠人工饲料喂养。海参参刺挺拔,底足密集,剪开后参筋粗壮饱满,肉壁厚实。泡发效果很好,泡发之后个头饱满,肉质紧实Q弹,嚼起来有韧劲,只有淡淡的海味,没有刺鼻腥味。 自己一直在吃,每天温水化开蘸料食用,滋补省心。包装严实,真空独立分装,干净卫生,存放方便。对比圈养海参,底播参生长周期更长,营养更好。性价比很不错,无论是日常自家滋补,还是过节送礼都合适,已经推荐给亲友,后续会回购。
干参展示~所见所得~
山东走起~
在在在~
京城走起喽~
Showing the 12 most recent of 12 posts we hold for @haishengongzhu. 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.
Forward network
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.
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.
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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“海参公主的日常” (@haishengongzhu), 47 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/haishengongzhu.
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.