193.148.16.116 有坏逼

Channel
杰尼龟和他的订阅们
@jngchannel
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
16,921subscribers
-39 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001719025498 |
|---|---|
| Type | Channel |
| Username | @jngchannel |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/jngchannel |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 14:47 | 16,921 | +3 |
| 13 Aug 2026, 08:53 | 16,918 | -4 |
| 12 Aug 2026, 05:55 | 16,922 | -12 |
| 11 Aug 2026, 06:36 | 16,934 | -1 |
| 10 Aug 2026, 08:28 | 16,935 | -4 |
| 9 Aug 2026, 05:12 | 16,939 | -13 |
| 8 Aug 2026, 02:51 | 16,952 | -8 |
| 7 Aug 2026, 09:00 | 16,960 | no change |
| 7 Aug 2026, 08:51 | 16,960 | first reading |
Engagement
9 posts held, back to 24 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 22 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈202
- Videos
- ≈12
- Links
- ≈531
Lifetime counters from Telegram’s own channel header, read 14 August 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
- 57s
- Average length
- 57s
Measured directly from 1 video 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
47 reactions across 4 posts, in 6 distinct kinds. The most used accounts for 40.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 19 | 40.4% | |
| 🤣 | 18 | 38.3% | |
| 😱 | 4 | 8.51% | |
| 🥱 | 4 | 8.51% | |
| 😈 | 1 | 2.13% | |
| 🤔 | 1 | 2.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 4 of the 9 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 47reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 24 November 2025 to 22 May 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
https://t.me/harukalab/183 https://t.me/dishujichang_pd/1171 芭芭拉叭叭,漏洞又出新品啦!机场老板还不快修
关于 VLESS 协议的说明 我们长期收到用户关于支持 VLESS 代理协议的请求。鉴于围绕该协议存在较多争议,我们过去倾向于避免公开回应,以免引发不必要的讨论与争端。然而,持续的沉默本身也被部分解读为一种态度,甚至产生了一些误解与猜测。基于这一现实情况,我们决定对相关问题进行一次正式说明。 (由于 vless / vision / xtls 等名称本身缺乏统一且明确的定义,下文将以「VLESS」作为整个协议族的统称。) 加密代理协议社区始终保持着高度活跃。从早期的 Shadowsocks,到后来的 Trojan、ShadowTLS、TUIC、Hysteria、AnyTLS 等项目,不同开发者持续提出新的设计思路,并在开放讨论与相互借鉴中推动技术演进。许多项目均由开发者无偿投入时间与精力完成,对整个生态产生了积极影响。 因此,当新的项目具备成熟度与稳定性时,我们通常乐于进行支持与适配。尽管 Surge 本身并未直接参与开…
🤣18🥱4🤔1😈1
#机场主送测 #一元中转 #SS 测速带宽 #长沙电信2000M #深圳移动1000M #山东联通1000M 官网: https://yyzz.one 频道: https://t.me/yyzzvpn 群组: https://t.me/yyzzgroup 套餐截图: https://t.me/taochanyuantu/226 说实话都这个价格了(不过感觉有点灵),也没啥好奢求的了,移动和联通的效果还是不错的 入口:厦门快快网络103.219段、北上广腾讯云、中山移动36.141段 落地:如图 ☁️送测要求|🎁🎁🎁🎁🎁
😱4
新年快乐
👍12
既然气氛都到这了,那就先祝各位新年快乐,同时也祝你 祝我 祝我们在新的一年,事事顺意 、岁岁平安、阖家幸福、拥有爱与被爱的勇气、天天好心情。
Photo, posted without a caption
#机场主送测 #Dragonfly #蜻蜓 #Vless 测速带宽 #辽宁电信2000M #上海移动1000M #陕西联通1000M 官网: https://9dragonfly.com 频道: https://t.me/+KHnpa-a7S84wYmQ1 群组: https://t.me/+2J618HhhfE9lNjM1 套餐截图: https://t.me/taochanyuantu/225 又是一家直连优化的机场,域名注册是10月的,应该开了没多久,节点数量也不是很多,但是三网的速度还说得过去。据官方所说线路是CN2、CMIN2、10099 等混合,就是希望后续多加点别的地区的 入口、落地:如图 ☁️送测要求|🎁🎁🎁🎁🎁
👍7
#机场主送测 #极连云 #Trojan 测速带宽 #江苏电信2000M #辽宁联通1500M #山东移动1000M 官网: https://web01.hyperlink.mobi 频道: https://t.me/JLYjichang 群组: https://t.me/JLYNCloud 套餐截图: https://t.me/taochanyuantu/224 说实话挺一般的,单线入口就是会各种跨省跨运营商限速,还得是三线接入才行 入口:广州移动120.236段 落地:如图 🍷送测要求|🎁🎁🎁🎁🎁
Showing the 9 most recent of 9 posts we hold for @jngchannel. 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 — 518,634 of 1,345,403entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@jngchannel named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 6 posts, 8 August 2026 – 14 August 2026
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.
“杰尼龟和他的订阅们” (@jngchannel), 16,921 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/jngchannel.
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.