Telegram RegisterThe public register of Telegram
Telegram profile photo for 濯于清涟

Channel

濯于清涟

@QingLianTalkChannel

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

3,883subscribers

+104 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-1002696513007
TypeChannel
Username@QingLianTalkChannel
CreatedBetween 1 April 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/QingLianTalkChannel

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 65% 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

3,7793,8833,8317 August 2026 — 3,779 subscribers7 August 2026 — 3,779 subscribers8 August 2026 — 3,780 subscribers11 August 2026 — 3,833 subscribers14 August 2026 — 3,872 subscribers18 August 2026 — 3,883 subscribers7 August 202618 August 2026
6 measurements spanning 10 days, net +104. 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 3,763–3,899 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 00:023,883+11
14 Aug 2026, 19:383,872+39
11 Aug 2026, 00:063,833+53
8 Aug 2026, 01:483,780+1
7 Aug 2026, 17:473,779no change
7 Aug 2026, 17:373,779first reading

Engagement

20 posts held, back to 18 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 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
673.4%
avg views ÷ 3,883 subscribers
Avg views / post
26,200
2 posts measured
Reaction rate
0.005%
reactions ÷ views · ER floor
Posts in window
3
of 20 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 1 of 2 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 3 August 2026
Posts held20 (18 June 20263 August 2026)
Views total52,300
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:13 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

33 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 42.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😢1442.4%
927.3%
🤗412.1%
🤔26.06%
👍13.03%
🔥13.03%
😨13.03%
🥰13.03%

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

Measured over the 20 most recent posts we hold, published 18 June 2026 to 3 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

3 Aug 2026, 15:16 UTC≈20,900 views1 reactionsread 8 August 2026
Photo

Photo, posted without a caption

🔥1

14 Jul 2026, 23:28 UTC≈32,500 viewsread 8 August 2026

喜欢软糯口感的可以把牛腩用高压锅压一个小时,我习惯在焯水后压30分钟,喜欢吃筋道一点的

14 Jul 2026, 23:26 UTC≈32,600 viewsread 8 August 2026

喜欢浓稠的汤汁的可以加淀粉勾芡,大火收汁,配面条和米饭都是很好的

14 Jul 2026, 23:24 UTC≈33,000 viewsread 8 August 2026

牛腩事先焯水,番茄2/3炖烂出汁,1/3切块炒软,中火炖煮30分钟,家里有番茄酱或者番茄罐头的可以下一点进去,注意翻动防止糊底

14 Jul 2026, 23:22 UTC≈33,300 viewsread 8 August 2026

我宣布番茄牛腩是怎么吃都吃不腻的美食,早上热一点配鸡蛋面给我香的迷糊了

14 Jul 2026, 01:15 UTC≈10,100 views1 reactionsread 8 August 2026

雨敲打着房顶,而你又知道你的家里没有沉闷乏味的人的时候,坐在家里是多么愉快啊。 Как приятно сидеть дома, когда по крыше стучит дождь и когда знаешь, что в доме твоем нет тяжелых скучных люде

👍1

13 Jul 2026, 14:03 UTC≈34,700 viewsread 8 August 2026

电磁炉和天然气都试过了,就是没有那种焦香味

13 Jul 2026, 14:02 UTC≈34,600 viewsread 8 August 2026

不是干了就是油了,吃起来也没有焦脆感,有点软烂

13 Jul 2026, 14:02 UTC≈35,000 viewsread 8 August 2026

我发现自己做的炒粉无论怎样都比不上外面的,哪怕调料的量都一样,就是吃不出锅气的感觉

11 Jul 2026, 10:52 UTC≈2,160 views2 reactionsread 8 August 2026

如果一个食物广为流传的食用方法是变成干果,那么它新鲜的时候大概率是比较难吃的

2

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

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

“濯于清涟” (@QingLianTalkChannel), 3,883 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/QingLianTalkChannel.

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.