Telegram RegisterThe public register of Telegram
Telegram profile photo for 永恒 API

Channel

永恒 API

@newyanchannel

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

2,898subscribers

-94 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003424743943
TypeChannel
Username@newyanchannel
CreatedBetween 1 November 2025 and 11 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live16 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/newyanchannel

Growth

2,8982,9922,94510 August 2026 — 2,992 subscribers10 August 2026 — 2,992 subscribers13 August 2026 — 2,919 subscribers16 August 2026 — 2,898 subscribers10 August 202616 August 2026
4 measurements spanning 6 days, net -94. 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 2,884–3,006 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 20:532,898-21
13 Aug 2026, 08:482,919-73
10 Aug 2026, 13:172,992no change
10 Aug 2026, 10:312,992first reading

Engagement

20 posts held, back to 11 January 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
2.31%
avg views ÷ 2,898 subscribers
Avg views / post
67.0
1 post measured
Reaction rate
19.4%
reactions ÷ views · ER floor
Posts in window
1
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 August 2026
Posts held20 (11 January 20263 August 2026)
Views total67
Reactions total13
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 10:31 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

64 reactions across 15 posts, in 8 distinct kinds. The most used accounts for 39.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2539.1%
💩914.1%
👎812.5%
🤣812.5%
🤮812.5%
👍23.13%
🔥23.13%
🥰23.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 16 of the 20 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 64reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 11 January 2026 to 3 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

3 Aug 2026, 10:03 UTC67 views13 reactionsread 10 August 2026

新增API: 😆 独家综合Pro 😊 独家库补Pro ☺️ 独家猎魔Pro PS: 此Pro版意为增强版,数据更多,查询更精准,同时增加AI 辅助查询,使查询结果无限关联(关联技术超越 liemo)

🤣4🤮4👎31👍1

15 Jul 2026, 00:01 UTC202 viewsread 10 August 2026

新增API: 🤩 人物解析API 😨 超级 高概户籍地址API PS: 此API为史上最高概(90%),全网独家 PS: 同时优惠了数十个API价格及增加质保时间

14 Jul 2026, 22:34 UTC189 views0 reactionsread 10 August 2026

我们于今日决定承接Telegram社工库机器人搭建项目: - 框架使用我们使用了一年的稳定框架(此框架前前后后维护加固了十几次保证稳定) - 机器人界面可定制 - 机器人功能可定制 我们对比别人的优势: - 全天候在线,可随时接单高效编写 - 技术专业,非垃圾 AI 编写拼凑 - 承接过数个业内顶尖机器人搭建 - 经验丰富,价格便宜,性价比高 - 实时查看 Telegram Bot API 最新文档,掌握最新前沿技术与实践,可开发出精美UI,完善功能的机器人  一分钱一分货 我们目前承接: 社工库机器人搭建 个人使用的机器人搭建 AI 机器人搭建 后台检测倒卖机器人搭建(API商首选)

4 Jul 2026, 15:57 UTC219 views1 reactionsread 10 August 2026

@yhapi_new 永恒此号被 Telegram 官方踢出设备,原session无效无法登入,API购买/售后联系 @guhetw 所有API稳定运营。

1

16 May 2026, 15:09 UTC465 views1 reactionsread 10 August 2026

@yonghengapi 此号暂时登不上,售后/购买API暂时联系 @yhapi_new

1

24 Mar 2026, 04:39 UTC942 viewsread 10 August 2026

新增API: 😘 司法综合数据查询API〔比小孩哥强,100%出〕

13 Mar 2026, 06:54 UTC≈1,070 views1 reactionsread 10 August 2026

新增了API: - AI猎魔 API(自然语言猎魔API) PS:同时增加微信二要素核验API的质保时长。

1

11 Mar 2026, 09:43 UTC≈1,480 views1 reactionsread 10 August 2026

API 导航页 〔最近更新与 2026.8.3〕 ·X-ray 类型(社工类) X-ray同款综合查询API(超级稳定) X-ray同款微信查询API X-ray同款身份证补齐(库补)API X-ray同款姓名+地区+性别猎魔API X-ray同款地址猎魔API X-ray同款地址猎魔2.0API X-ray同款条件猎魔API X-ray全功能API X-ray同款手机号补齐API X-ray同款三要素补齐API(机主首选) X-ray同款拼音名字模糊身份证补齐(库补Pro)API ·假单类 假户籍地API 假手机定位API 假手机定位2.0API 假开房记录API 假婚姻史API 假有效期API 假机主API 假全家户籍API 假快递地址API 假银行流水记录API 假征信记录API 假地址假头API 假通话记录API 假个人名下卡API 假五年飞火记录API ·政务类 五年医疗记录文字版API 医疗记录(票据版)API

🥰1

11 Mar 2026, 03:16 UTC657 views2 reactionsread 10 August 2026

永恒API官方频道通知 我们的 X-ray API仍然是全网最便宜的价格,并且,同时我们引入了自己的独家数据: - 千万条国政三要素 - 数亿条支付宝四要素(姓名 手机号 身份证 地址) - 数亿条vivo三要素 - 数亿条快递地址数据 - 千万条贷款借款数据 ...... 这些数据中大部分都是原X-ray乃至全网综合没有的数据,加上之后使X-ray API的数据更加多,更加丰富,查询效果提升。 同时,我们推出了按月购买机制,按月买更便宜,按3月买更有性价比!

2

7 Mar 2026, 12:30 UTC628 views5 reactionsread 10 August 2026

X-ray 全功能API已降价 X-ray 综合查询API已降价 还是那句话: ·我们拥有三线路的轮询查询,不用担心查询拥挤。 ·我们拥有最完美的缓存机制,能在流量大时自动缓存,节省其他友商不必要的排队时间或查询错乱。 ·我们拥有极致的查询体验,拥有双服务器,当服务器CPU占满或被攻击时极速响应,更换服务器。 ·我们拥有最完美的售后体验,从未跑路,所有售后从未停止,耐心听从客户建议/问题。

3🔥1🥰1

26 Feb 2026, 11:26 UTC760 viewsread 10 August 2026

永恒API 官方频道通知 为打造良好生态,创建用户基础,永恒API推出公益API频道,内置多种公益免费的实用/娱乐API,同时,我们也支持推荐用户自助投稿,我们将会在打包后进行公益。 公益API频道 :@yhapi_free / / / / / / 同时为进行推广,我们将进行拉新活动,将广告消息推广至活人频道可联系永恒领取对应奖励 我们同时也在寻找代理,代理拿货价可是正常价的七折(如果量大可5折),但是每周需有业绩要求(不会很多,不强制要求太多),如有意者可联系永恒。 @guhetw

25 Feb 2026, 03:40 UTC741 views3 reactionsread 10 August 2026

事件通知 昨天晚上,我们和海湾,小无等多家API服务商的服务器遭到攻击(目前看来攻击者是有目的性的友商?),持续性发起DDoS攻击,虽然攻击量仅为每秒2G,且我们的服务器是无限流量,但是由于长期持续性的攻击,服务器还是进行了1分钟的瘫痪,不过我们在收到通知的第一刻已经更换了服务器,截止至昨日晚上十点,3台服务器(两台备用,一台主用)均已全面恢复正常。 此次攻击未造成任何用户的直接和间接损失,永恒API永远可以是您信任的API服务商。 同时,我们的网站cdn由于被他人恶意举报,目前已经暂时停止使用,我们将在稍后进行更换cdn服务商,不影响用户使用。

3

Showing the 12 most recent of 20 posts we hold for @newyanchannel. 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 — 540,443 of 1,549,704entries 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.

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

“永恒 API” (@newyanchannel), 2,898 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/newyanchannel.

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.