Telegram RegisterThe public register of Telegram

Channel

打住,我想说一些非常酷的话

@jinxadchannel

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

82subscribers

+0 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-1002491975192
TypeChannel
Username@jinxadchannel
Descriptionjinx.ad 公告版 官网:https://jinx.ad/ 面板:https://dash.jinx.ad/
Created19 February 2025measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live14 August 2026
Measurements held2
On Telegramt.me/jinxadchannel

Growth

826 August 2026 — 82 subscribers9 August 2026 — 82 subscribers6 August 20269 August 2026
2 measurements spanning 3 days. 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 81–83 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 18:1682no change
6 Aug 2026, 23:4682first reading

Engagement

18 posts held, back to 19 February 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 27 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
2
Links
3

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

4 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
250.0%
🥰250.0%

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 3 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 4reactions 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 19 February 2025 to 27 November 2025, 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 Nov 2025, 11:57 UTC453 views0 reactionsread 9 August 2026

公告: 由于更换了线路,导致成本较高,为了维持jinX的正常运行,我们不得不提高部分套餐的价格。老用户不受影响,可以原价正常续购。感谢您一直以来支持jinX!

13 Aug 2025, 15:49 UTC767 viewsread 9 August 2026

老用户可以凭七八折优惠券【jinxlove】续订套餐,不限套餐种类、不限数量,优惠券有效时长为两周~

13 Aug 2025, 15:47 UTC759 viewsread 9 August 2026

公告: 最近几天jinX频繁遭受有组织的DDOS攻击,导致我们不得不暂时断开部分海外节点的连接。目前问题已经基本解决,很抱歉影响大家的使用体验。我们考虑近期更换线路,扩容并升级服务器,避免此类问题再发生。

16 Jun 2025, 11:25 UTC862 viewsread 9 August 2026

公告: 由于Club Sim近期修补了可以免流的漏洞,我们没有办法继续提供Club Sim服务,敬请谅解。 jinX将原Club Sim免流套餐更换为CTHK/MO(中國電信香港/澳门)的免流服务,目前还处于测试阶段(建议暂时先不要购买,等正式版稳定运行),已经订阅Club Sim服务的可自行更换为CTHK/MO sim卡继续使用服务(作为补偿,您可以提交工单,我们会免费赠送一个月使用时长);或者您可以提交工单,我们将为您更换为等价的其他套餐

21 May 2025, 16:19 UTC894 views2 reactionsread 9 August 2026
Photo

官网更新了界面:信息更直观,内容更丰富,欢迎大家体验!https://board.jinx.ad/

2

12 May 2025, 14:34 UTC752 viewsread 9 August 2026

给大家争取了100个为期一周的优惠券: 新用户可凭优惠码 「lover」 获得88折优惠 续费订阅用户可凭优惠码「love story」 获得79折优惠 再次感谢大家选择jinX!

12 May 2025, 14:25 UTC691 viewsread 9 August 2026

公告:近期我们的入口网络在晚高峰时段表现不是很理想,jinX团队会尽快更换更加优质的入口线路,保证jinX网络稳定流畅运行,带来的不便我们深表歉意,感谢大家一直以来对jinX的喜爱与支持!

26 Mar 2025, 04:28 UTC914 viewsread 9 August 2026

群公告里的优惠券还有一天就失效啦,需要的同学们抓紧时间哟😉

24 Mar 2025, 10:23 UTC875 viewsread 9 August 2026

☺️jinX一口气上新了10个国家和地区的节点,包含东南亚和欧洲的部分地区,更新以后就可以使用啦! 🥳今天送出 10 个七九折通用优惠券和 10 个八八折 Club Sim 专用优惠券! 🍀通用优惠券: 星河欲转 🌷专用优惠券: 云影天光 记得及时领取哦~ Ps:通用优惠券仅可用于年付及以下套餐;专用优惠券仅可用于 Club Sim 专用套餐

18 Mar 2025, 17:12 UTC≈1,010 viewsread 9 August 2026

我们最近推出了 Club Sim 的套餐,为了满足大家了解能跑多少速率,欢迎大家使用我们的搭建的测速服务。 speed.jinx.ad

18 Mar 2025, 15:43 UTC875 viewsread 9 August 2026

声明我们和知名 IDC jinx 不是同一家,近期好像有人误解了,在传我们是 IDC jinx 开的。 我们的正式名称是 JinX.ad

Showing the 12 most recent of 18 posts we hold for @jinxadchannel. 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 — 1,226,035 of 1,480,688entries 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 1 registered channel — 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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“打住,我想说一些非常酷的话” (@jinxadchannel), 82 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/jinxadchannel.

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.