Telegram RegisterThe public register of Telegram
Telegram profile photo for 四海会|全国葆养反馈

Channel

四海会|全国葆养反馈

@sihaifk

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

1,528subscribers

-21 since we began measuring on 16 August 2026

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

Register entry

Telegram ID-1001664829311
TypeChannel
Username@sihaifk
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 August 2026
Last confirmed live26 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/sihaifk

Topic

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 17 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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.

Growth

1,5221,5611,541.516 August 2026 — 1,549 subscribers16 August 2026 — 1,549 subscribers17 August 2026 — 1,544 subscribers20 August 2026 — 1,542 subscribers24 August 2026 — 1,541 subscribers27 August 2026 — 1,543 subscribers30 August 2026 — 1,555 subscribers2 September 2026 — 1,561 subscribers6 September 2026 — 1,553 subscribers11 September 2026 — 1,547 subscribers15 September 2026 — 1,522 subscribers26 September 2026 — 1,528 subscribers1,52816 August 202626 September 2026
12 measurements spanning 41 days, net -21. 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,516–1,567 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
26 Sept 2026, 12:381,528+6
15 Sept 2026, 05:591,522-25
11 Sept 2026, 09:381,547-6
6 Sept 2026, 12:211,553-8
2 Sept 2026, 02:231,561+6
30 Aug 2026, 10:551,555+12
27 Aug 2026, 07:041,543+2
24 Aug 2026, 07:431,541-1
20 Aug 2026, 11:461,542-2
17 Aug 2026, 14:051,544-5
16 Aug 2026, 19:151,549no change
16 Aug 2026, 19:001,549first reading

Engagement

5 posts held, back to 13 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 5 posts for this entry, the most recent from 15 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

15 Aug 2026, 15:55 UTC397 viewsread 16 August 2026
Photo

🤥😄🙃😕 😊🙃😐😃😂 😲【 8.15成交】😲 老板已和妹妹成功见面,女生来到大哥的城市早早到达赴约地点等待,见面顺利大哥给与满意评价,期待您的后续反馈👏 祝你家里永远有鲜花,窗外常有好风景🤗🤗 🙂‍↕️🙂‍↕️🙂‍↕️😂🫤😅🥺 😊😊🥰@sihaihuizhushou_bot

15 Aug 2026, 15:55 UTC387 viewsread 16 August 2026
Photo

🤥😄🙃😕 😊🙃😐😃😂 😲【 8.15成交】😲 老板已和妹妹成功见面,女生赴约路程中发生了点小插曲,大哥接到女生沟通了解够满意收下👏 愿你的旅程既有诗和远方,也有眼前的温暖时光🤗🤗 🙂‍↕️🙂‍↕️🙂‍↕️😂🫤😅🥺 😊😊🥰@sihaihuizhushou_bot

14 Aug 2026, 15:59 UTC621 viewsread 16 August 2026
Photo

🤥😄🙃😕 😊🙃😐😃😂 😲【 8.14成交】😲 老板已和妹妹成功见面,女生早早到达赴约地点,大哥工作原因姗姗来迟,好在见面顺利沟通也比较满意,牵手成功👏 迎着朝阳意气风发地出发,夜幕低垂时满载福气踏光回家🤗🤗 🙂‍↕️🙂‍↕️🙂‍↕️😂🫤😅🥺 😊😊🥰@sihaihuizhushou_bot

13 Aug 2026, 15:05 UTC982 viewsread 16 August 2026
Photo

🤥😄🙃😕 😊🙃😐😃😂 😲【 8.13成交】😲 老板已和妹妹成功见面,同城安排大哥当天下单当天见面,顺利接收女生双方沟通满意,牵手成功👏 祝你被爱意和幸福紧紧包围,快乐不打烊🤗🤗 🙂‍↕️🙂‍↕️🙂‍↕️😂🫤😅🥺 😊😊🥰@sihaihuizhushou_bot

13 Aug 2026, 15:05 UTC969 viewsread 16 August 2026
Photo

🤥😄🙃😕 😊🙃😐😃😂 😲【 8.13成交】😲 老板已和妹妹成功见面,女生按时出发来到大哥指定的见面位置赴约,沟通过程有点小插曲,好在不影响大哥满意收下女生,期待您的后续反馈👏 愿你的时间,更多的“浪费”在美好的事物和深爱的人身上🤗🤗 🙂‍↕️🙂‍↕️🙂‍↕️😂🫤😅🥺 😊😊🥰@sihaihuizhushou_bot

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

“四海会|全国葆养反馈” (@sihaifk), 1,528 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/sihaifk.

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.