Telegram RegisterThe public register of Telegram

Channel

比特冲刺-通知频道

@dashbitTel

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

142subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003788192475
TypeChannel
Username@dashbitTel
Description关注比特冲刺谢谢喵😋😋
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
On Telegramt.me/dashbitTel

Growth

1401421416 August 2026 — 140 subscribers6 August 2026 — 142 subscribers8 August 2026 — 142 subscribers6 August 20268 August 2026
3 measurements spanning 3 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 140–142 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 21:47142no change
6 Aug 2026, 09:41142+2
6 Aug 2026, 04:08140first reading

Engagement

20 posts held, back to 12 July 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
234.9%
avg views ÷ 142 subscribers
Avg views / post
334
18 posts measured
Reaction rate
0.426%
reactions ÷ views · ER floor
Posts in window
19
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 8 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 7 August 2026
Posts held20 (12 July 20267 August 2026)
Views total6,003
Reactions total11
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 21:47 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
12
Links
3

Lifetime counters from Telegram’s own channel header, read 8 August 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

12 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
975.0%
👍18.33%
💩18.33%
😁18.33%

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 12reactions 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 12 July 2026 to 7 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

7 Aug 2026, 22:32 UTC86 viewsread 8 August 2026

用自家节点上不去官网的请更新订阅,路由规则的问题,现已修复

7 Aug 2026, 00:29 UTC138 viewsread 8 August 2026

香港A组节点被俩香港IP 182.239.92.195 和 203.160.86.113 给dos了,现在已恢复正常

6 Aug 2026, 19:53 UTC141 views1 reactionsread 8 August 2026
Photo

全部被墙节点已恢复,请更新订阅拉取最新配置,为您带来不便深感歉意。本次受影响的客户可以发工单申领额外5天的订阅时长(截至8.9 22:00)

👍1

6 Aug 2026, 17:28 UTC147 views1 reactionsread 8 August 2026

节点被墙,CMI和电信优化恢复了,AWS机器今天凌晨会搞定

😁1

3 Aug 2026, 06:04 UTC252 views2 reactionsread 8 August 2026

刚才CMI节点有波动,现已修复,如节点timeout请更新订阅

2

31 Jul 2026, 22:59 UTC309 viewsread 8 August 2026

刚才服务器有一些状况,节点timeout请更新订阅获取最新配置

30 Jul 2026, 19:16 UTC380 views2 reactionsread 8 August 2026

服务器数据已迁移完毕,没有问题,现在访问官网的速度应该会更快了

2

29 Jul 2026, 11:42 UTC372 viewsread 8 August 2026

另外,重要通知,为了更好的节点速度,本站将在 7.31凌晨3:00 对服务器进行停机转移数据,届时节点服务将不可用,预计维护时间在15分钟以内

29 Jul 2026, 11:32 UTC358 viewsread 8 August 2026
Photo

本次节点升级热更新结束 更新内容有: 1.升级了 三网优化 和 BGP-CMI 线路中转VPS的配置 2.升级了台湾落地节点的机器配置 3.升级了韩国节点的机器,现在换AWS了 近期我们会给落地都加上电信优化的线路,预计8.2-8.3完成升级 ———— 另外接下来的几个月会增加更多小众的节点和AWS落地 (版本号为Ver3.0,及时更新订阅获取最新的节点列表)

29 Jul 2026, 09:11 UTC301 viewsread 8 August 2026

现在对机场的三网优化和BGP-CMI节点进行不断线升级,期间可能会有网络波动,更新完会通知更新订阅

24 Jul 2026, 19:06 UTC431 views2 reactionsread 8 August 2026
Photo

上了个公益节点,每月共享1T流量,用完即挂

1💩1

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

Citation-graph rank

Citation-graph rank — 96,376 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 9 registered channels — 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.

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

“比特冲刺-通知频道” (@dashbitTel), 142 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/dashbitTel.

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.