Telegram RegisterThe public register of Telegram
Telegram profile photo for 贝贝桑的频道

Channel

贝贝桑的频道

@beisangzhuan9

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

5,860subscribers

-13 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002018311429
TypeChannel
Username@beisangzhuan9
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/beisangzhuan9

Growth

5,8375,8735,8557 August 2026 — 5,873 subscribers7 August 2026 — 5,873 subscribers11 August 2026 — 5,862 subscribers15 August 2026 — 5,854 subscribers18 August 2026 — 5,852 subscribers20 August 2026 — 5,838 subscribers24 August 2026 — 5,848 subscribers27 August 2026 — 5,842 subscribers30 August 2026 — 5,837 subscribers2 September 2026 — 5,860 subscribers5,8607 August 20262 September 2026
10 measurements spanning 26 days, net -13. 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 5,832–5,878 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 20:445,860+23
30 Aug 2026, 09:245,837-5
27 Aug 2026, 16:345,842-6
24 Aug 2026, 06:565,848+10
20 Aug 2026, 19:285,838-14
18 Aug 2026, 00:415,852-2
15 Aug 2026, 02:445,854-8
11 Aug 2026, 12:255,862-11
7 Aug 2026, 17:165,873no change
7 Aug 2026, 17:075,873first reading

Engagement

19 posts held, back to 9 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.3%
avg views ÷ 5,860 subscribers
Avg views / post
1,070
1 post measured
Reaction rate
0.093%
reactions ÷ views · ER floor
Posts in window
1
of 19 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 4 August 2026
Posts held19 (9 June 20264 August 2026)
Views total1,070
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:46 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.

Reaction mix

76 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 38.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣2938.2%
👍2228.9%
1925.0%
💩33.95%
👎22.63%
😁11.32%

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 11 of the 19 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 76 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 9 June 2026 to 4 August 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

4 Aug 2026, 13:47 UTC≈1,070 views1 reactionsread 12 August 2026

#新谈的女朋友 #长的白 上课 @beibei999h

1

3 Aug 2026, 15:20 UTC≈1,380 views3 reactionsread 12 August 2026

我女儿现在送奶奶家了 开始工作 家人们 @beibei999h

👍21

27 Jul 2026, 08:20 UTC≈2,470 views1 reactionsread 12 August 2026

最近这几天都在家带娃 一号我女儿的奶奶 把我女儿接回去

1

21 Jul 2026, 11:06 UTC≈3,890 views0 reactionsread 12 August 2026

#一生挚爱 #我朋友 #小嫩批 #多人运动 上课热线 @beibei999h

19 Jul 2026, 10:40 UTC≈3,660 viewsread 12 August 2026

#高冷小嫩批 #为了她缝针15针的女人 上课热线 @beibei999h

17 Jul 2026, 07:20 UTC≈3,870 views2 reactionsread 12 August 2026

#比仙女还仙女 #一生挚爱 上课热线 @beibei999h

👎2

13 Jul 2026, 17:35 UTC≈4,720 views30 reactionsread 12 August 2026

自己老婆出轨了 原因是为啥和前任复合 看了我另一个手机发现我出轨前女友 然后她就找前任了 女儿也不管了 然后我一个人带娃 然后我女儿是我自己的 是亲生的才能上户口 现在我女儿还小 等她长大些能谈恋爱了 我肯定要带她 等我宝贝女儿长大 我现在 成为一个好爸爸 @beibei999h 我现在会认真工作 @beibei999h

🤣291

12 Jul 2026, 05:49 UTCviews —

贝贝桑的频道 pinned «老婆出轨了 跟她前任复合了 我现在自己在照顾我女儿 我妈妈也过来帮我照顾我女儿了 现在我属于单亲爸爸 照顾女儿 @beibei999h»

12 Jul 2026, 05:49 UTC≈4,280 views18 reactionsread 12 August 2026

老婆出轨了 跟她前任复合了 我现在自己在照顾我女儿 我妈妈也过来帮我照顾我女儿了 现在我属于单亲爸爸 照顾女儿 @beibei999h

👍17😁1

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

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

“贝贝桑的频道” (@beisangzhuan9), 5,860 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/beisangzhuan9.

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.