Telegram RegisterThe public register of Telegram

Channel

地鼠机场

@dishujichang_pd

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

858subscribers

+8 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-1002196787783
TypeChannel
Username@dishujichang_pd
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/dishujichang_pd

Growth

849858853.56 August 2026 — 850 subscribers6 August 2026 — 850 subscribers7 August 2026 — 849 subscribers14 August 2026 — 858 subscribers6 August 202614 August 2026
4 measurements spanning 8 days, net +8. 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 848–859 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 03:27858+9
7 Aug 2026, 02:24849-1
6 Aug 2026, 14:50850no change
6 Aug 2026, 04:16850first reading

Engagement

18 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
62.0%
avg views ÷ 858 subscribers
Avg views / post
532
13 posts measured
Reaction rate
0.631%
reactions ÷ views · ER floor
Posts in window
13
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 13 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 2 August 2026
Posts held18 (12 July 20262 August 2026)
Views total6,915
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 14:50 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

20 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 55.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1155.0%
👏315.0%
👍210.0%
🤔210.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 8 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 20reactions 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 12 July 2026 to 2 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

2 Aug 2026, 07:56 UTC339 viewsread 6 August 2026

目前aws入口的节点频繁墙,被墙IP会自动更换,大概几分钟时间 建议善用mihomo的故障转移和自动选择功能,目前我们已经上线了多个高可用的备用节点以供使用

1 Aug 2026, 18:08 UTC369 views2 reactionsread 6 August 2026

我他妈说白了,2026年还在明文存储密码的傻逼商家不是鸡巴坏就是父母双亲死完了 ak发那个“某IDC数据库泄露”前2天我就发现我自己的aklie账号被莫名登录,吓的我马上绑了2fa 过了俩天ak发了"某IDC数据库泄露"后虽然没明说是哪个商家,但是结合鸭子去年发的,很明显就能猜出来是哪家,当然因为事情还没被锤,我就不说具体是哪个商家了,感兴趣的自己去问傻逼鸭子 明文密码这个东西能在2026年遇到也是神完了,哪怕你随便用个什么框架都不会有明文密码这个东西,github随便翻几个开源项目,除了某些单用户项目,几乎完全没有使用明文密码的,都是只存加盐md5 bcrypt啥的 就拿机场圈常用的v2b(及其衍生物)以及ssp,还有idc常用的whmcs,没有一个是明文存储的 ssp虽然使用的md5加盐这一种不太安全(但是想要暴力破解单个密码也需要几千年往上这种无意义时间) v2b之后的现代项目基本上都使用bcrypt这种更安全的

👍2

1 Aug 2026, 11:39 UTC397 views5 reactionsread 6 August 2026

准备多上几个ech节点来应对近期疯狂墙的问题,ech是一个tls扩展,用于加密sni使中间人无法得知你在访问什么域名,ech过cloudflare目前是无法被墙的,因为开启ech后中间人无法看到你真实sni,同时cf的IP在gfw的白名单内 目前aws节点一天大概会墙个几十次,相当于一个小时平均墙个2-3次,自动换IP大概需要2-5分钟时间完成(有时候一次换IP可能无法换到没被墙的IP),这导致了这俩天节点稳定性非常差 现有的代理协议已经非常完美了,GFW无法有效(指几乎无误伤的情况)将正常https流量和翻墙代理流量区分开来 GFW选择了一条能让方先生妈更快飞出太阳系的路,也就是人工采集订阅,即人工购买机场订阅,然后测活,接着直接提交管局或者GFW,封端虽然能一定程度上防止人工,但终究是治标不治本,GFW完全可以通过抓包的方式获取到节点信息,同时还会造成用户使用不便,我们暂时没有封端的想法

5

31 Jul 2026, 09:58 UTC418 viewsread 6 August 2026
Photo

目前这一堆国模的价格已经是gpt的好几倍了😅 有点不知道何意味了,以前国模的代名词是低价高性价比,现在价格是gpt的好几倍了,这么急着收回成本吗

30 Jul 2026, 13:21 UTC409 views1 reactionsread 6 August 2026

我们上线了几个新的日本节点以解决目前日本节点速度慢的问题 你需要更新订阅以获取最新的节点 同时我把新上的几个节点的sni改成白名单sni了,如果你的网络能用这几个节点,但是无法使用其他节点就是你的运营商开始sni白名单了 新上的几个节点入口是aws,出口alice jp

1

29 Jul 2026, 15:22 UTC486 viewsread 6 August 2026

部分地区开始sni白名单了😇 准备换回 reality了

29 Jul 2026, 12:42 UTC482 views2 reactionsread 6 August 2026

telegram创始人帕维尔·杜罗夫 被俄罗斯通缉 Telegram联合创始人帕维尔·杜罗夫在俄罗斯被指控协助恐怖主义活动,已启动将其列入国际通缉名单的程序。俄罗斯联邦安全局公共关系中心(ЦОС)对此进行了通报。 事实证明每个独裁政权都会走上控制媒体控制舆论路子,如果独裁政权无法让一个类媒体类应用按照我的方式控制不利于我的舆论,那独裁政权就会通过各种手段让自己国民无法接触到这个类媒体类应用,乃至直接使用暴力机器强行控制这个类媒体类应用 类媒体类应用不单指传统媒体和社交媒体,而是指任何能传播信息的软件 你杜叔叔现在东西方都不讨好了😁

11

24 Jul 2026, 11:34 UTC720 views5 reactionsread 6 August 2026
Photo

不是,这些gui客户端这么喜欢改ui吗 工具栏位置从选择节点的那个地方改到了代理组那个地方 巨几把难受,好比你今天回家开门的时候发现门把手从门左边改到了门右边一样别扭

👏32

23 Jul 2026, 13:32 UTC301 viewsread 6 August 2026

大家应该都放暑假了吧,我给大家带来了一个暑假75折优惠码 折后价格51元/年(折合每月4.25元),每月200g流量(这是每月不是每年,相当于每年2400g流量) 点击复制优惠码: 暑假快乐 不限时套餐和户晨风套餐不可用此优惠码 月付/年付套餐每月重置已使用流量 不限时套餐不会到期也不会重置流量,直到你把流量用完 点击购买: nbvpn.top

Showing the 12 most recent of 18 posts we hold for @dishujichang_pd. 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 — 185,562 of 1,350,102entries 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.

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

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

“地鼠机场” (@dishujichang_pd), 858 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dishujichang_pd.

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.