Telegram RegisterThe public register of Telegram
Telegram profile photo for LoopDNS资讯播报

Channel

LoopDNS资讯播报

@DNSPODT

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

73,241subscribers

+2,649 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001320622866
TypeChannel
Username@DNSPODT
DescriptionLoopDNS 综合资讯---简洁,及时,快速,准确 频道: @DNSPODT 电报讨论组: @LoopDNS 撤稿流程: https://t.me/loopdns/107752
Created13 September 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/DNSPODT

Topic

Technology — 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 20 August 2026 and assigned it the closest of 31 fixed categories, at 55% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 3 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@DNSPODT/14617 · this entry11 Aug 2026, 10:21 UTC@LoopDNSPODT/122111 Aug 2026, 10:21 UTC1.00under a minute
@DNSPODT/14620 · this entry11 Aug 2026, 15:44 UTC@LoopDNSPODT/122411 Aug 2026, 15:44 UTC1.00under a minute
@DNSPODT/14622 · this entry11 Aug 2026, 18:02 UTC@LoopDNSPODT/122611 Aug 2026, 18:02 UTC1.00under a minute
@LoopDNSPODT/122712 Aug 2026, 01:30 UTC@DNSPODT/14623 · this entry12 Aug 2026, 01:30 UTC1.00under a minute
@DNSPODT/14624 · this entry12 Aug 2026, 02:30 UTC@LoopDNSPODT/122812 Aug 2026, 02:30 UTC1.00under a minute
@DNSPODT/14629 · this entry12 Aug 2026, 10:27 UTC@LoopDNSPODT/123312 Aug 2026, 10:27 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@LoopDNSPODT14 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (14–0)
@qiushuinews9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (9–0)
@acgdaily11 (7/8 hand-verifiable sample passed)1.008 minutesthis entry (11–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 394 comparable posts for this entry, running 3 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @DNSPODT — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

70,59273,24171,916.56 August 202610 November 2026
64 measurements spanning 96 days, net +2,649. 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 70,195–73,638 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
10 Nov 2026, 06:0673,241+47
8 Nov 2026, 16:4473,194-24
7 Nov 2026, 12:3973,218+13
6 Nov 2026, 10:5973,205-23
5 Nov 2026, 07:2773,228+21
4 Nov 2026, 04:4573,207-1
3 Nov 2026, 04:4173,208-3
2 Nov 2026, 07:0473,211+26
1 Nov 2026, 04:1073,185+51
31 Oct 2026, 02:4673,134+27
29 Oct 2026, 23:1973,107+16
29 Oct 2026, 00:4573,091+54
28 Oct 2026, 00:4473,037+27
26 Oct 2026, 21:1673,010+177
25 Oct 2026, 21:4172,833+19
25 Oct 2026, 01:1672,814+1
23 Oct 2026, 03:1172,813-2
22 Oct 2026, 02:1772,815+26
20 Oct 2026, 20:0072,789+27
19 Oct 2026, 21:5572,762first reading

Engagement

561 posts held, back to 3 August 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 203 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
10.8%
avg views ÷ 73,241 subscribers
Avg views / post
7,890
153 posts measured
Reaction rate
1.14%
reactions ÷ views · ER floor
Posts in window
153
of 561 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 152 of 153 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 held561 (3 August 2026 – 11 November 2026)
Views total1,207,793
Reactions total13,718
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 23:03 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
≈2,840
Videos
≈390
Links
≈8,380

Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
9h 09m
Average length
16m 10s

Measured directly from 34 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

51,995 reactions across 548 posts, in 61 distinct kinds. The most used accounts for 19.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁9,93219.1%
🤡8,06315.5%
👍6,48012.5%
🤣4,9139.45%
💩3,0515.87%
❤1,6663.20%
🤮1,6173.11%
🐳1,3782.65%
👎1,3162.53%
🖕1,2332.37%
🙏1,1482.21%
🎉1,1182.15%
😱1,0221.97%
🍾9651.86%
🤯9261.78%
🥰6681.28%
👀6011.16%
😨5321.02%
🤔5080.977%
💊4920.946%
41 further kinds4,3668.40%

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

Measured over the 561 most recent posts we hold, published 3 August 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.

Telegram Stars

Stars received
17
across the posts below
Posts paid on
3
of 560 we hold a reading for · 0.5%
Most on one post
15
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @DNSPODT. 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 561 most recent posts we hold for this entry, published 3 August 2026 to 11 November 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

Telegram’s own ‘edited’ marker: 46 of 153 posts held from the last 30 days (30.1%) 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).

11 Nov 2026, 22:54 UTC124 viewsread 11 November 2026

中国财政供养人员规模估算与结构分析 ▎Source

11 Nov 2026, 22:46 UTC269 views14 reactionsread 11 November 2026

华尔街日报称,英伟达准备罢免CEO黄仁勋。 英伟达盘后跌幅扩大至8%。

🤯8👎3🤮2🖕1

11 Nov 2026, 14:15 UTC≈3,310 views121 reactionsread 11 November 2026

国家税务总局11日透露,目前离岸信托收益征税政策过渡期已平稳结束,绝大多数纳税人积极配合,累计申报离岸信托个人所得税超1600亿元,其中10月当月入库超1200亿元,带动了全国10月份个人所得税收入增长近90%。

🤮55👍31🤣25😁6❤2🖕1🥰1

11 Nov 2026, 05:24 UTC≈5,050 views16 reactionsread 11 November 2026

CoreWeave 财报电话会全文,旧款GPU租价环比再涨30-50%,27-28年30万张GPU合同到期,续约预计带来约100亿美元增量收入 ▎Source

😁10🍾2🤮2👍1👎1

11 Nov 2026, 03:08 UTC≈5,440 views49 reactionsread 11 November 2026
Photo

巴拉圭最大数字银行倒闭 总统辞职未成遭国会罢免后被捕 近日,巴拉圭最大的数字银行韦诺银行(Ueno Bank)倒闭引发巴拉圭政坛动荡。11月6日,于2023年当选、被特朗普视为盟友的巴拉圭总统培尼亚(Santiago Peña)因为这家银行倒闭被国会罢免,并正面临刑事指控。 同日,原副总统佩德罗·阿利亚纳(Pedro Alliana)接任总统职务。 11月7日,巴拉圭公共检察官办公室正式对培尼亚提起刑事诉讼。在当天的新闻发布会上,巴拉圭首席检察官南希·萨洛蒙(Nancy Salomón)表示,培尼亚将因背信罪和利用职权为个人牟利的罪行(breach of trust and administration for personal gain)接受调查。 消息来源: 财新

👍26😁20🤮2❤1

11 Nov 2026, 00:15 UTC≈6,520 views76 reactionsread 11 November 2026

隐匿的英伟达“白手套”:从世纪利通(利通电子)到Megaspeed ▎Source

😁54🤡11🍾6😭3👎1🤮1

10 Nov 2026, 04:54 UTC≈7,100 views103 reactionsread 11 November 2026
Photo

宏观边际MacroMargin 彭博周刊的这篇文章值得一读,聚焦中国“锈带”的部分青年现状。 如今的供强需弱、K型分化也在加大这些问题,况且,对于一个处于内卷、或说通缩的经济体,企业技术替代的倾向,会比通胀经济提要更强,对就业的破坏往往也会更大,青年就业问题,乃至全社会就业问题,可能会越来越严峻,对政策的倒逼力量也会越来越大。 全文bloomberg.com/news/featu...

🍾46😢17🕊14😭7👍6❤4💯4🤡3

10 Nov 2026, 02:44 UTC≈7,370 views103 reactionsread 11 November 2026

Anthropic失误发送并撤回IPO细节邮件 据路透社报道,人工智能企业Anthropic向银行发送了首次公开募股(IPO)的详细文件后不久便将其撤回。该邮件此前显示,公司拟以每股70至80美元的价格区间发售约8.67亿股股份。随后,Anthropic通过第二封邮件澄清相关定价细节并不准确,并表示将在稍后更新相关申报文件。 来源:路透社

🤡82🤣17💩2👎1🤮1

9 Nov 2026, 19:32 UTC≈6,990 views20 reactionsread 11 November 2026

https://www.anthropic.com/claude-fable-and-mythos-5-2

🤡14❤3🍾1👎1🤮1

9 Nov 2026, 14:14 UTC≈7,210 views115 reactionsread 11 November 2026

伊朗总统:伊朗最高领袖已下令结束“非战非和”状态 据伊朗塔斯尼姆通讯社、卡塔尔半岛电视台等媒体报道,伊朗总统佩泽希齐扬9日表示,伊朗最高领袖穆杰塔巴已下令结束“非战非和”状态,并称伊朗愿意进行谈判,但不会屈服于胁迫或霸凌。 来源:环球网

🤡88😁12👍4🖕4🥱3❤2🤮2

9 Nov 2026, 12:31 UTC≈8,710 views126 reactionsread 11 November 2026

杭州一店铺内发生刑案2人死亡,嫌犯畏罪自杀 杭州市公安局临平区分局11月9日发布警情通报:11月8日12时54分,我局接报辖区临平街道某临街店铺内发生一起刑事案件,造成2人死亡。 经公安机关全力侦查,迅速锁定犯罪嫌疑人为纪某某(男,57岁,临平人)。当日23时许,纪某某在被围捕时畏罪自杀,经送医抢救无效死亡。案件正在进一步侦办中。 来源:凤凰网

😨111❤3🍾3👌3👏3😁2🤮1

9 Nov 2026, 08:17 UTC≈9,530 views53 reactionsread 11 November 2026
File

文件记录显示,Megaspeed一直通过一系列看似空壳公司的渠道获得阿里巴巴的秘密注资。 Megaspeed的财务报表显示,从2023年底至2024年底,其资产负债表大幅扩张,总负债与权益从仅3300万美元激增至30亿美元,这一增长几乎完全由来自某未具名来源的29亿美元“收到的可退还押金”所驱动。 Megaspeed的财务数据显示有29亿美元“应收子公司款项”——这笔资金已转付给其运营子公司,如总部位于马来西亚的Speedmatrix。 马来西亚的备案文件显示,在2024年6月——即开始运营前两个月——Speedmatrix提交了一项抵押登记,将其全部业务作为抵押物抵押给Apex Enterprise Solutions。新加坡的备案文件披露,Apex的母公司是阿里巴巴,其唯一目的被列为“提供采购活动”。截至2025年3月31日,Apex报告的预付款项超过41亿美元,而应付给阿里巴巴的贷款为42亿美元。

🤯30😁18❤3👀1🤮1

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

@DNSPODT edited 8 posts 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
17 August 2026
Most recent edit
10 October 2026

Posts recorded as deleted after publishing

We recorded 9 posts on @DNSPODT as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
10 August 2026
Most recent seen missing
15 October 2026
Median time before seen missing
16 hours
Seen missing in the last 30 days
4

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 18 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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

风向旗参考快讯
@xhqcankao · 200,273
#1
在花🎗️科技圈
@zaihuapd · 289,994
#2
竹新社
@tnews365 · 167,192
#3
Yummy 😋
@GodlyNews1 · 71,143
#4
每日消费电子观察
@CE_Observe · 77,552
#5
蓝点网订阅频道
@landiansub · 47,142
#6
VPS信号旗播报
@vps_xhq · 50,835
#7
Solidot
@solidot · 48,811
#8
2.5次元日常 🍉
@acgdaily · 17,329
#9
每日沙雕墙
@woshadiao · 114,505
#10
层叠 - The Cascading
@outvivid · 9,324
#11
Newlearnerの自留地
@NewlearnerChannel · 68,274
#12
隐私中国 Dark Web Inform
@CN_Privacy · 17,115
#13
不存在的世界
@illusory_world · 11,114
#14
rvalue的生草日常
@rvalue_daily · 8,802
#15
心灵魔法站
@personal_hub · 11,582
#16
港新日美雲服務裸金屬 - 牛彼☁️
@KuaiCheDao_Info · 7,405
#17
简中互联网废物大赏
@fucku_idiot · 41,768
#18
APPDO的互联网记忆
@appdopic · 16,962
#19
橘橘橘子汁 & 🍊
@microblock_pub · 16,066
#20
cnBeta.COM中文业界资讯站 - 总频道(精选新闻)
@cnbeta_com · 27,396
#21
新·世界观察日志
@NewWorldObservationLog · 7,062
#22
今天abc看了啥🤔
@abcthoughts · 7,136
#23
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud · 101,557
#24
kMBRjund/0 🧊
@MBRjunDaily · 2,092
#25
AKILE NOTICE
@akile_notice · 19,019
#26
Global Macro View
@Marcoview666 · 5,471
#27
凯露酱的朋友圈
@HakureiKyaru · 2,461
#28
APPDO 数字生活指南
@AppDoDo · 40,980
#29
财经慢报
@Financial_Express · 36,925
#30
Sukka's Notebook
@SukkaChannel · 6,937
#31
折腾啥
@zhetengsha · 53,830
#32
少数派sspai
@sspai · 39,123
#33
学习墙国🐸
@XueXi_China · 86,381
#34
🥳靠谱VPS推荐(默认带aff) - VPS仓/古博
@vpscang · 12,082
#35
zrj766的频道
@zrj96 · 17,853
#36
不靠谱的喵(>^ω^<) #CatGPT
@MlgmXyysd_bibilailai · 22,511
#37
Project X Channel
@projectXtls · 30,549
#38
机场稽查局
@VPN_Police · 8,337
#39
希特乐乐
@NyarimeW · 6,025
#40
COALCLOUD(NEW)
@coalcloud · 5,978
#41
gledos Lia green 的微型博客
@gledos_microblogging · 6,605
#42
特价VPS分享
@Tjjcfx · 17,877
#43
LetITFly News
@LetITFlyW · 9,732
#44
Soha 的日常
@sohadays · 4,825
#45
品测
@SIM_CN · 9,993
#46
灵车漂移
@Hearse_Drifting · 10,883
#47
bupt.moe
@bupt_moe · 5,286
#48
企业级欢乐花园
@MaterialDesign3 · 9,208
#49
青鸟的频道
@bluebird_channel · 7,950
#50
 Apple Nuts
@AppleNuts · 37,705
#51
Milkice's 生而喵喵
@milkice_portal · 3,393
#52
Karen医生の日常
@KarenMoeMoe · 9,355
#53
平壤卫视
@pingrangTV · 29,366
#54
Android Weekly Update ⚡️
@update4weekly · 5,249
#55
翻翻墙 | 机场评测
@ffqchannel · 69,031
#56
Arch Linux Chinese Messages
@archlinuxcn · 11,274
#57
杰尼龟和他的订阅们
@jngchannel · 17,014
#58
Paily Connect
@nodpai · 8,462
#59

Read from Telegram’s recommendation API, most recently 20 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

风向旗参考快讯
@xhqcankao · 200,273
Telegram ranks this channel #2 of 45 here — alongside 44 others — read 12 August 2026
知乎暴论
@mightyflame · 25,397
Telegram ranks this channel #3 of 42 here — alongside 41 others — read 13 September 2026
看鉴中国 OutsightChina
@OutsightChina · 41,905
Telegram ranks this channel #3 of 58 here — alongside 57 others — read 29 August 2026
蓝点网订阅频道
@landiansub · 47,142
Telegram ranks this channel #3 of 58 here — alongside 57 others — read 28 August 2026
VPS信号旗播报
@vps_xhq · 50,835
Telegram ranks this channel #3 of 57 here — alongside 56 others — read 26 August 2026
Yummy 😋
@GodlyNews1 · 71,143
Telegram ranks this channel #3 of 55 here — alongside 54 others — read 20 August 2026
Legado|开源阅读|频道
@Legado_Channels · 93,165
Telegram ranks this channel #3 of 61 here — alongside 60 others — read 17 August 2026
Iyouport
@iyouport · 27,612
Telegram ranks this channel #4 of 55 here — alongside 54 others — read 10 September 2026
简中互联网废物大赏
@fucku_idiot · 41,768
Telegram ranks this channel #4 of 47 here — alongside 46 others — read 30 August 2026
敏感经济信息分享
@pelosi3 · 72,526
Telegram ranks this channel #4 of 51 here — alongside 50 others — read 20 August 2026
树洞🌳群友问❓有点意思🗳
@qunyouwen · 89,042
Telegram ranks this channel #4 of 67 here — alongside 66 others — read 17 August 2026
每日沙雕墙
@woshadiao · 114,505
Telegram ranks this channel #4 of 52 here — alongside 51 others — read 14 August 2026
竹新社
@tnews365 · 167,192
Telegram ranks this channel #4 of 59 here — alongside 58 others — read 12 August 2026
在花🎗️科技圈
@zaihuapd · 289,994
Telegram ranks this channel #4 of 40 here — alongside 39 others — read 12 August 2026
Ruters乳透社🐻
@Ruters0615 · 25,110
Telegram ranks this channel #5 of 40 here — alongside 39 others — read 14 September 2026
FREE 中文
@freechinese · 27,756
Telegram ranks this channel #5 of 55 here — alongside 54 others — read 10 September 2026
cnBeta.COM中文业界资讯站 - 总频道(精选新闻)
@cnbeta_com · 27,396
Telegram ranks this channel #5 of 55 here — alongside 54 others — read 10 September 2026
【李老师不是你老师】官方电报
@lilaoshibushinilaoshi · 49,209
Telegram ranks this channel #5 of 60 here — alongside 59 others — read 26 August 2026
电报时报
@times001 · 84,497
Telegram ranks this channel #5 of 66 here — alongside 65 others — read 18 August 2026
即刻精选
@jike_collection · 35,883
Telegram ranks this channel #6 of 48 here — alongside 47 others — read 2 September 2026
科技&趣闻&杂记
@kejiqu · 36,774
Telegram ranks this channel #6 of 48 here — alongside 47 others — read 1 September 2026
zaobao.sg 早报
@zaobaosg · 46,565
Telegram ranks this channel #6 of 59 here — alongside 58 others — read 1 September 2026
赛博忏悔室
@cyber_confessional · 40,961
Telegram ranks this channel #6 of 35 here — alongside 34 others — read 30 August 2026
Solidot
@solidot · 48,811
Telegram ranks this channel #6 of 59 here — alongside 58 others — read 28 August 2026

This channel appears in 104 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“LoopDNS资讯播报” (@DNSPODT), 73,241 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/DNSPODT.

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.