Telegram RegisterThe public register of Telegram
Telegram profile photo for 广州天河软软

Channel

广州天河软软

@STQ8886

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

389subscribers

+2 since we began measuring on 11 November 2026

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

Register entry

Telegram ID-1004452336599
TypeChannel
Username@STQ8886
CreatedBetween 1 June 2026 and 21 October 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 November 2026
Last confirmed live13 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/STQ8886

Growth

38738938811 November 2026 — 387 subscribers13 November 2026 — 389 subscribers11 November 202613 November 2026
2 measurements spanning 2 days, net +2. 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 387–389 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 12:57389+2
11 Nov 2026, 20:22387first reading

Engagement

18 posts held, back to 21 October 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
187.5%
avg views ÷ 389 subscribers
Avg views / post
729
18 posts measured
Reaction rate
0.141%
reactions ÷ views · ER floor
Posts in window
18
of 18 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 5 of 18 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 11 November 2026
Posts held18 (21 October 2026 – 11 November 2026)
Views total13,130
Reactions total5
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 20: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 07s
Average length
13s

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

Reaction mix

5 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 60.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤360.0%
👍240.0%

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

Measured over the 18 most recent posts we hold, published 21 October 2026 to 11 November 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

Telegram’s own ‘edited’ marker: 0 of 18 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

5 Nov 2026, 04:56 UTC588 viewsread 11 November 2026

最近都在家陪家人当乖乖女,不上课哟,上课了会在频道更新,宝宝们

5 Nov 2026, 04:55 UTC577 views2 reactionsread 11 November 2026
Video

在家无聊来练习一下手感🥰

👍2

31 Oct 2026, 10:53 UTC791 views0 reactionsread 11 November 2026

万圣节快乐,宝宝们,今天装办你的邪恶小恶魔女友

31 Oct 2026, 07:32 UTC680 viewsread 11 November 2026

频道里没更新就是没上班,因为兼职平常上班不确定时间哦,看频道更新为主,哥哥们

27 Oct 2026, 06:32 UTC594 views0 reactionsread 11 November 2026
Forwarded from @Fourlove_marszjPhoto

4i战记 #软软 @STQ8884 2026/10 价格 1800p-优惠券 真人跟图一较为相似,更成熟。身材如图二,全身更加丰满!能乳交,听话。 颜值 人照8成,相对照片更加老成。还是不错的。 身材 脂肪🐻型,正常微垂度。真d+奶,手感超级柔软。身材更加丰满,有点偏向bbw,喜欢这类型的会很喜欢,喜瘦的酌情考虑。 妹子有纹身,用遮纹粉底遮挡。个人感觉不遮更好,也是没办法。 床感 大圈来的,口技出乎意料的好!69看看,是大🦋bb,也很敏感。提议想试试乳交,被大奶子完全包裹着,太舒服了,女上体力不错,双乳晃得人陶醉。各种姿势都十分配合。由于一天3客,bb还是很紧的。大🐻控值得体验 情绪价值 情绪价值可以,交流挺多不会冷场。 综合体验 B+

25 Oct 2026, 09:28 UTC808 views2 reactionsread 11 November 2026

羊城晚报报告模板 【出击报告】(https://t.me/yangchengEveningnew ) 【位置坐标】 #广州 #天河 【优势】 双峰手感松软非BBW 【劣势】 脸型没头像显得这么小 【妹子花名】:#软软 【联系方式】:@STQ8884 【妹子年龄】: 【验证留名】:佛山分晏🐔哥 【验证时间】: 【修车水费】:18P-券 【颜值】: 颜值评分: 12分(满分15分) 【身材】: 身材评分: 13分(满分15分) 【服务态度】: 服务评分: 15分( 满分15分) 【情绪价值】:沟通愉快 情绪评分: 15分 (满分15分) 【时间管理】:10课位/课时安排是否合理 时间评分: 10分 (满分10分) 【同价位合理性】:符合价位 价位评分: 7分 (满分10分) 【卫生环境】: 环境评分: 10分(满分10分) 【流程小文】: 见面人照相符 也的确如第一位工兵kingsley说的和拿着…

❤2

Showing the 12 most recent of 18 posts we hold for @STQ8886. 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 13 November 2026 — this entry's latest reading, not the date you are reading this.

“广州天河软软” (@STQ8886), 389 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/STQ8886.

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.