Telegram RegisterThe public register of Telegram
Telegram profile photo for 金盾免费代理·ProxyMTProto

Channel

金盾免费代理·ProxyMTProto

@jindun

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

7,612subscribers

-161 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-1001909371923
TypeChannel
Username@jindun
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/jindun

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 81% 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.

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 word for word on 1 other registered channel. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@wd000/1773 Jul 2026, 05:46 UTC@jindun/42599 · this entry3 Jul 2026, 05:46 UTC1.00under a minute
@wd000/1784 Jul 2026, 12:45 UTC@jindun/42600 · this entry4 Jul 2026, 12:46 UTC1.00under a minute
@wd000/18617 Jul 2026, 15:19 UTC@jindun/42607 · this entry17 Jul 2026, 15:20 UTC1.00under a minute
@wd000/18721 Jul 2026, 15:57 UTC@jindun/42608 · this entry21 Jul 2026, 15:57 UTC1.00under a minute
@wd000/1977 Aug 2026, 14:41 UTC@jindun/42618 · this entry7 Aug 2026, 14:41 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@wd0005 (5/5 hand-verifiable sample passed)1.00under a minute@wd000 (50)

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. 1 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 12 comparable posts for this entry, running 3 July 2026 to 7 August 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).

Across the whole group of 2, the earliest publisher we hold is @wd000. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

7,6127,7737,692.57 August 2026 — 7,773 subscribers7 August 2026 — 7,773 subscribers8 August 2026 — 7,767 subscribers11 August 2026 — 7,746 subscribers15 August 2026 — 7,710 subscribers17 August 2026 — 7,668 subscribers21 August 2026 — 7,661 subscribers24 August 2026 — 7,643 subscribers27 August 2026 — 7,629 subscribers30 August 2026 — 7,612 subscribers7 August 202630 August 2026
10 measurements spanning 23 days, net -161. 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 7,588–7,797 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 09:367,612-17
27 Aug 2026, 17:027,629-14
24 Aug 2026, 11:177,643-18
21 Aug 2026, 01:577,661-7
17 Aug 2026, 22:137,668-42
15 Aug 2026, 00:177,710-36
11 Aug 2026, 09:587,746-21
8 Aug 2026, 04:087,767-6
7 Aug 2026, 12:327,773no change
7 Aug 2026, 12:217,773first reading

Engagement

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

ERR · 30 days
4.50%
avg views ÷ 7,612 subscribers
Avg views / post
342
11 posts measured
Reaction rate
0.223%
reactions ÷ views · ER floor
Posts in window
11
of 27 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 7 of 11 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 27 August 2026
Posts held27 (29 June 202627 August 2026)
Views total3,765
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 21:27 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

32 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 84.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2784.4%
👍412.5%
🤔13.13%

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

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

27 Aug 2026, 17:34 UTC89 viewsread 28 August 2026

🔤🔤🔤🔣🔣🔣 🇸🇬 新加坡(Singapore) IPV6内置代理分部 🧩https://t.me/proxy?server=2407:d140:1:100:9000:9000:20db:c9d7&port=11854&secret=dd621418961f9f616470fdff00dd1e1f73 🧩https://t.me/proxy?server=2407:d140:1:100:9000:9000:20db:c9d7&port=11854&secret=dd621418961f9f616470fdff00dd1e1f73 🧩https://t.me/proxy?server=2407:d140:1:100:9000:9000:20db:c9d7&port=11854&secret=dd621418961f9f616470fdff00dd1e1f73 近期网络通报严重,请使用ipv6线路来保障连接 更多线路 包含了世界各地

21 Aug 2026, 01:29 UTC313 viewsread 28 August 2026

🔤🔤🔤🔣🔣🔣 🇺🇸 美国亚特兰大 IPV4内置代理分布 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 IPV6内置代理分部 🧩https://t.me/proxy?server=2602:fa4f:802:485c:a4a4:44ed:446c:1401&port=27865&secret=dd0e3cc675ef8829d36c5

15 Aug 2026, 18:24 UTC369 views1 reactionsread 28 August 2026

针对部分群友反映的流量被重置及大量消耗问题,现作出如下说明:系统会记录用户过往使用本代理服务所产生的数据消耗。经核查,凡服务有效期未届满且流量未超限的用户,均不予恢复流量;仅针对已超使用量但服务期限仍在有效期内的用户,系统将执行重置并补足流量。需要强调的是,本免费代理服务旨在解决用户的紧急需求,无法提供与付费代理同等水平的维护与售后服务。作为公益项目,我们已多次重申此原则。

1

15 Aug 2026, 13:42 UTC352 views0 reactionsread 28 August 2026

在巡查过程中,发现个别用户利用节点服务器进行倒卖活动,其在线设备数量高达64台,此举严重损害了其他用户的利益。我们致力于为用户提供优质的互联网服务,为此现做出以下调整: 第一,将在线设备数量上限调整为2台。 第二,重置所有用户的套餐流量,恢复至初始状态(对于剩余有效期的用户,已使用的流量将被清零)。 第三,如有其他问题,请通过设立的问题反馈组进行反馈,工作人员将在空闲时间查看并予以说明。 问题反馈群🔣🔣🔣https://t.me/+wahWfIOa3sdhOTRk 🔡🔡🔡

13 Aug 2026, 14:41 UTC371 views1 reactionsread 28 August 2026

🔤🔤🔤🔣🔣🔣 🇳🇱 荷兰阿姆斯特丹 IPV4内置代理分布 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b IPV6内置代理分部 🧩https://t.me/proxy?server=2a06:f901:1:100::261&port=26464&secret=dd91c7fecdf5805a482ea70043dede1e

1

8 Aug 2026, 05:16 UTC404 views1 reactionsread 28 August 2026

🔤🔤🔤🔣🔣🔣 🇳🇱 荷兰阿姆斯特丹 IPV4内置代理分布 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b 🧩https://t.me/proxy?server=tw01.mioc.top&port=13376&secret=dd91c7fecdf5805a482ea70043dede1e5b IPV6内置代理分部 🧩https://t.me/proxy?server=2a06:f901:1:100::261&port=26464&secret=dd91c7fecdf5805a482ea70043dede1e

1

7 Aug 2026, 14:41 UTC324 views0 reactionsread 28 August 2026

🔤🔤🔤🔣🔣🔣 🇺🇸 美国亚特兰大 IPV4内置代理分布 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 IPV6内置代理分部 🧩https://t.me/proxy?server=2602:fa4f:802:485c:a4a4:44ed:446c:1401&port=27865&secret=dd0e3cc675ef8829d36c5

7 Aug 2026, 04:55 UTC314 viewsread 28 August 2026

🔤🔤🔤🔣🔣🔣 🇯🇵 日本东京(Japan Tokyo) IPV4内置代理分布 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 IPV6内置代理分部 🧩https://t.me/proxy?server=2602:f3f2:c4:cf66:b936:b592:6d99:d33d&port=55995&secret=fbab1231e1f

4 Aug 2026, 14:56 UTC357 viewsread 28 August 2026

机器人的流量不会用的可以通过机器人【查看教程】,该教程频道有相关问题介绍,若有其他问题可以通过交流群反馈问题需求。 流量机器人 @AH66Bot 流量签到群 @nwsss 内部交流群 @内部群 教程频道 @E1666

2 Aug 2026, 16:13 UTC501 views2 reactionsread 28 August 2026

🔤🔤🔤🔣🔣🔣 🇯🇵 日本东京(Japan Tokyo) IPV4内置代理分布 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 🧩https://t.me/proxy?server=84.75.203.234&port=47649&secret=fbab1231e1f4969f7ae184c4337ce8e0 IPV6内置代理分部 🧩https://t.me/proxy?server=2602:f3f2:c4:cf66:b936:b592:6d99:d33d&port=55995&secret=fbab1231e1f

2

29 Jul 2026, 15:09 UTC773 views2 reactionsread 28 August 2026

🔤🔤🔤🔣🔣🔣 🇸🇬 新加坡(Singapore) IPV4内置代理分布 🧩https://t.me/proxy?server=84.75.203.234&port=31665&secret=dd5948fed33ebccf03a1b274e01938d325 🧩https://t.me/proxy?server=84.75.203.234&port=31665&secret=dd5948fed33ebccf03a1b274e01938d325 🧩https://t.me/proxy?server=84.75.203.234&port=31665&secret=dd5948fed33ebccf03a1b274e01938d325 IPV6内置代理分部 🧩https://t.me/proxy?server=2605:e440:b::22f&port=19985&secret=dd5948fed33ebccf03a1b274e0193

2

Showing the 12 most recent of 27 posts we hold for @jindun. 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 — 818,271 of 1,626,935entries 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 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“金盾免费代理·ProxyMTProto” (@jindun), 7,612 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/jindun.

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.