Telegram RegisterThe public register of Telegram
Telegram profile photo for 雪花内核官方频道🇨🇳

Channel

雪花内核官方频道🇨🇳

@snowDDDdabao

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Cite this entry

58,602subscribers

+1,576 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001680400591
TypeChannel
Username@snowDDDdabao
Description雪花内核频道通知群(破60k)
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live26 October 2026
Measurements held49
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/snowDDDdabao

Topic

Technology — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 45% 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

56,80362,39159,5977 August 2026 — 57,026 subscribers7 August 2026 — 57,026 subscribers7 August 2026 — 57,018 subscribers8 August 2026 — 56,936 subscribers9 August 2026 — 56,849 subscribers10 August 2026 — 56,803 subscribers11 August 2026 — 58,327 subscribers12 August 2026 — 59,858 subscribers14 August 2026 — 61,182 subscribers15 August 2026 — 61,154 subscribers17 August 2026 — 60,943 subscribers18 August 2026 — 60,864 subscribers19 August 2026 — 60,786 subscribers20 August 2026 — 60,710 subscribers21 August 2026 — 60,656 subscribers22 August 2026 — 60,563 subscribers24 August 2026 — 60,389 subscribers25 August 2026 — 60,281 subscribers26 August 2026 — 60,192 subscribers27 August 2026 — 60,149 subscribers28 August 2026 — 60,084 subscribers29 August 2026 — 60,022 subscribers30 August 2026 — 59,971 subscribers31 August 2026 — 59,890 subscribers1 September 2026 — 59,819 subscribers2 September 2026 — 59,725 subscribers4 September 2026 — 59,622 subscribers6 September 2026 — 59,371 subscribers10 September 2026 — 59,047 subscribers12 September 2026 — 58,814 subscribers14 September 2026 — 57,576 subscribers16 September 2026 — 58,183 subscribers18 September 2026 — 61,031 subscribers1 October 2026 — 62,391 subscribers6 October 2026 — 61,961 subscribers10 October 2026 — 61,673 subscribers13 October 2026 — 61,475 subscribers15 October 2026 — 61,357 subscribers16 October 2026 — 61,312 subscribers17 October 2026 — 61,259 subscribers18 October 2026 — 61,219 subscribers19 October 2026 — 61,118 subscribers20 October 2026 — 61,056 subscribers21 October 2026 — 60,965 subscribers22 October 2026 — 58,951 subscribers23 October 2026 — 58,863 subscribers24 October 2026 — 58,732 subscribers25 October 2026 — 58,704 subscribers26 October 2026 — 58,602 subscribers58,6027 August 202626 October 2026
49 measurements spanning 80 days, net +1,576. 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 55,965–63,229 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 49
Measured (UTC)SubscribersChange
26 Oct 2026, 13:0458,602-102
25 Oct 2026, 14:0558,704-28
24 Oct 2026, 17:3658,732-131
23 Oct 2026, 19:2758,863-88
22 Oct 2026, 19:0658,951-2,014
21 Oct 2026, 15:3660,965-91
20 Oct 2026, 10:3961,056-62
19 Oct 2026, 10:5161,118-101
18 Oct 2026, 10:0661,219-40
17 Oct 2026, 06:4761,259-53
16 Oct 2026, 06:1861,312-45
15 Oct 2026, 03:1061,357-118
13 Oct 2026, 23:2161,475-198
10 Oct 2026, 22:1561,673-288
6 Oct 2026, 21:2161,961-430
1 Oct 2026, 20:3862,391+1,360
18 Sept 2026, 10:5661,031+2,848
16 Sept 2026, 00:1858,183+607
14 Sept 2026, 05:5757,576-1,238
12 Sept 2026, 11:2058,814first reading

Engagement

66 posts held, back to 8 July 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 167 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.52%
avg views ÷ 58,602 subscribers
Avg views / post
1,480
16 posts measured
Reaction rate
0.864%
reactions ÷ views · ER floor
Posts in window
16
of 66 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 21 October 2026
Posts held66 (8 July 2026 – 21 October 2026)
Views total23,620
Reactions total204
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Oct 2026, 20:35 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

Photos
66
Videos
1
Links
278

Lifetime counters from Telegram’s own channel header, read 26 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

482 reactions across 62 posts, in 5 distinct kinds. The most used accounts for 83.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍40283.4%
❤7515.6%
🎉20.415%
🥰20.415%
🙏10.207%

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

Measured over the 66 most recent posts we hold, published 8 July 2026 to 21 October 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 66 we hold a reading for · 2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @snowDDDdabao. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 66 most recent posts we hold for this entry, published 8 July 2026 to 21 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

19 Oct 2026, 12:30 UTC≈1,690 views10 reactionsread 26 October 2026

回归,价格依旧

👍10

Signed 雪花原作者

19 Oct 2026, 12:29 UTC≈1,660 views12 reactionsread 26 October 2026

👊❤️🔈🧐🟢🔊😃😀😃 雪花 #定制内核 有意找在线客服 定制王者苹果750 和平苹果650 苹果支持全系统 安卓支持所有版本 王者588-100=488(不偏框) 和平550-100=450 暗区 600 使命召唤 500 cfm 500 本季度名额有限下单的抓紧了 三角洲安卓 600 三角洲苹果800 三角洲端游1600 兼容所有手机内核 有意找我 在线客服 @mamman1v100 @mamman1v100 备用联系方式: @hlaquxhehs1 如果双向了或者弹出英文界面 那就请你联系这个: @xhdabaoBot 3小时制作好

👍11❤1

Signed 雪花原作者

19 Oct 2026, 12:29 UTC≈1,670 views11 reactionsread 26 October 2026

目前支持微信支付支付宝支付USDT支付 ❗️❗️❗️❗️❗️❗️ 📩💵📱🥇 名额有限

👍11

Signed 雪花原作者

18 Oct 2026, 10:48 UTC≈1,640 views12 reactionsread 26 October 2026

目前支持微信支付支付宝支付USDT支付 ❗️❗️❗️❗️❗️❗️ 📩💵📱🥇 名额有限

👍11❤1

Signed 雪花原作者

18 Oct 2026, 10:47 UTC≈1,630 views13 reactionsread 26 October 2026

👊❤️🔈🧐🟢🔊😃😀😃 雪花 #定制内核 有意找在线客服 定制王者苹果750 和平苹果650 苹果支持全系统 安卓支持所有版本 王者588-100=488(不偏框) 和平550-100=450 暗区 600 使命召唤 500 cfm 500 本季度名额有限下单的抓紧了 三角洲安卓 600 三角洲苹果800 三角洲端游1600 兼容所有手机内核 有意找我 在线客服 @mamman1v100 @mamman1v100 备用联系方式: @hlaquxhehs1 如果双向了或者弹出英文界面 那就请你联系这个: @xhdabaoBot 3小时制作好

👍12❤1

Signed 雪花原作者

18 Oct 2026, 09:17 UTC≈1,500 views16 reactionsread 26 October 2026

👊❤️🔈🧐🟢🔊😃😀😃 雪花 #定制内核 有意找在线客服 定制王者苹果750 和平苹果650 苹果支持全系统 安卓支持所有版本 王者588-100=488(不偏框) 和平550-100=450 暗区 600 使命召唤 500 cfm 500 本季度名额有限下单的抓紧了 三角洲安卓 600 三角洲苹果800 三角洲端游1600 兼容所有手机内核 有意找我 在线客服 @mamman1v100 @mamman1v100 备用联系方式: @hlaquxhehs1 如果双向了或者弹出英文界面 那就请你联系这个: @xhdabaoBot 3小时制作好

👍16

Signed 雪花原作者

18 Oct 2026, 09:17 UTC≈1,320 views16 reactionsread 26 October 2026

现在开始开放名额,开始接定制

👍13❤3

Signed 雪花原作者

18 Oct 2026, 09:10 UTC≈1,340 views10 reactionsread 26 October 2026

我要接临时root的定制了 做大做强再创辉煌

👍9❤1

Signed 雪花原作者

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

Posts edited after publishing

@snowDDDdabao edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
2 September 2026
Most recent edit
2 September 2026

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“雪花内核官方频道🇨🇳” (@snowDDDdabao), 58,602 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/snowDDDdabao.

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.