Telegram RegisterThe public register of Telegram
Telegram profile photo for 少爷专注/快手/查档/拼多多👨🏿‍🎤

Channel

少爷专注/快手/查档/拼多多👨🏿‍🎤

@synb66644

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

417subscribers

+402 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004425036995
TypeChannel
Username@synb66644
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 September 2026
Last confirmed live15 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/synb66644

Growth

154172168 August 2026 — 15 subscribers8 August 2026 — 40 subscribers16 August 2026 — 195 subscribers22 August 2026 — 237 subscribers28 August 2026 — 262 subscribers7 September 2026 — 302 subscribers9 September 2026 — 302 subscribers15 September 2026 — 417 subscribers8 August 202615 September 2026
8 measurements spanning 38 days, net +402. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 01:22417+115
9 Sept 2026, 19:22302no change
7 Sept 2026, 18:35302+40
28 Aug 2026, 18:34262+25
22 Aug 2026, 15:13237+42
16 Aug 2026, 03:06195+155
8 Aug 2026, 20:5640+25
8 Aug 2026, 03:4715first reading

Engagement

16 posts held, back to 8 September 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
16.7%
avg views ÷ 417 subscribers
Avg views / post
69.4
16 posts measured
Reaction rate
3.12%
reactions ÷ views · ER floor
Posts in window
16
of 16 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 9 of 16 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 September 2026
Posts held16 (8 September 20269 September 2026)
Views total1,111
Reactions total20
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Sept 2026, 19: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
11s
Average length
11s

Measured directly from 1 video 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.

Reaction mix

20 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 35.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍735.0%
630.0%
😭525.0%
👏15.00%
🤩15.00%

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

Measured over the 16 most recent posts we hold, published 8 September 2026 to 9 September 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

9 Sept 2026, 17:16 UTC7 views1 reactionsread 9 September 2026
Forwarded from @chinb6666Photo

📱微信专徒封禁反馈 包法与教学质量依旧一流 有心者无需多教 拜师 @chifh0

👍1

Signed

9 Sept 2026, 17:16 UTC7 views1 reactionsread 9 September 2026
Forwarded from @chinb6666Photo

📱qq徒封禁反馈 端内直举稳定 路子同出 拜师 @chifh0

👍1

Signed

9 Sept 2026, 17:03 UTC5 views1 reactionsread 9 September 2026
Forwarded from @shennb520File

圣 9.9公益双系统包 sub打法 公益思路不做无脑解释 不会玩的话找我拜师 微信领域教学什么东西之类的任何问题可以找我询问不会因为你口水而辱骂你 公益频道 https://t.me/shennb520 拜师/反馈 @shenfh666 必须反馈必须进公益频道领取更多公益思路

👍1

Signed

9 Sept 2026, 09:32 UTC68 viewsread 9 September 2026

千粉秒了笑死我了

Signed 执念 支机/查档/封号/码反/全国头

9 Sept 2026, 09:32 UTC68 viewsread 9 September 2026

你的本子

Signed 执念 支机/查档/封号/码反/全国头

9 Sept 2026, 09:31 UTC68 viewsread 9 September 2026
Video

反馈拜师联系 @sviplIIl Comply with EU laws and Telegram regulations. All content in the group is AI-generated without any negative impact and is for reference only.

Signed 少爷

9 Sept 2026, 09:31 UTC64 viewsread 9 September 2026
Photo

反馈拜师联系 @sviplIIl Comply with EU laws and Telegram regulations. All content in the group is AI-generated without any negative impact and is for reference only.

Signed 执念 支机/查档/封号/码反/全国头

9 Sept 2026, 09:28 UTC65 viewsread 9 September 2026
Photo

😍终于有反馈了 拜师联系 @sviplIIl Comply with EU laws and Telegram regulations. All content in the group is AI-generated without any negative impact and is for reference only.

Signed 少爷

9 Sept 2026, 03:42 UTC98 views5 reactionsread 9 September 2026
Photo

毛泽东(1893年12月26日-1976年9月9日),湖南湘潭人,是伟大的马克思主义者,伟大的无产阶级革命家、战略家、理论家,是马克思主义中国化的伟大开拓者,是中国共产党、中国人民解放军、中华人民共和国的主要缔造者和领导人,党的第一代中央领导集体的核心,近代以来中国伟大的爱国者、民族英雄 。

😭5

Signed 少爷

8 Sept 2026, 17:03 UTC89 views1 reactionsread 9 September 2026
Sticker

Sticker, posted without a caption

👍1

Signed 少爷

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

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

“少爷专注/快手/查档/拼多多👨🏿‍🎤” (@synb66644), 417 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/synb66644.

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.