Channel
@yhapi_free
On this record: Growth · Engagement · Posts · Polls · Citations · Cite this entry
33subscribers
-4 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003736516008 |
|---|---|
| Type | Channel |
| Username | @yhapi_free |
| Created | 26 February 2026 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/yhapi_free |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 01:57 | 33 | -1 |
| 11 Sept 2026, 01:56 | 34 | -1 |
| 1 Sept 2026, 01:38 | 35 | +1 |
| 25 Aug 2026, 02:57 | 34 | -2 |
| 18 Aug 2026, 12:42 | 36 | -1 |
| 10 Aug 2026, 22:02 | 37 | no change |
| 10 Aug 2026, 10:32 | 37 | first reading |
9 posts held, back to 26 February 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 1 page of 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 14 July 2026. An engagement rate over an empty window would be a number about nothing.
公益什么API呢
The shares total 109%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
新增公益API: 📱手机号归属地查询API 提供参数：phone-手机号 返回参数〔JSON〕： ·province-省份 ·city-城市 ·sp-运营商 ·waterMark API地址： http://muying.jianglin.icu/muyin/api/gy/guishu.php?phone=手机号 特别致谢：360
Testing... 测试中... 豆包自定义详细人设API，后续可能会推出相关机器人。
Test
Test
🌐永恒API - Free 2 官方频道通知 Free API〔API所有者〕项目已正式启动，我们所公益的API不会进行包括但不限于: 查询限速/次数限制/IP限制等限制。 ❔Free API〔API所有者〕项目成立初心： ·让所有使用我们API的用户都成为API所有者。 〔中译中：让我们都拥有不受限制的API，不再有可怕的限制。〕 😊Free API〔API所有者〕项目正面向所有用户进行公开招募免费接口，提供接口可获得机器人会员/任意API免费使用12h等优惠福利。 @guhetw
稍后更新
梦开始的地方 永恒の公益API频道 by @guhetw by @newyanchannel
Channel created
Showing the 9 most recent of 9 posts we hold for @yhapi_free. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
公益什么API呢
The shares total 109%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 9 most recent posts we hold, published 26 February 2026 to 14 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“永恒API - Free 2” (@yhapi_free), 33 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/yhapi_free.
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.