Telegram RegisterThe public register of Telegram
Telegram profile photo for 译牛 GPT-AI 翻译器【译牛AI】聚合聊天翻译 | 谷歌翻译 | AI智能翻译 | deepl翻译|【官方频道】yiniuai001 yiniui001

Channel

译牛 GPT-AI 翻译器【译牛AI】聚合聊天翻译 | 谷歌翻译 | AI智能翻译 | deepl翻译|【官方频道】yiniuai001 yiniui001

@yainiuai001

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

5,743subscribers

-2,207 since we began measuring on 26 September 2026

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

Register entry

Telegram ID-1003736051650
TypeChannel
Username@yainiuai001
CreatedBetween 1 February 2026 and 14 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 September 2026
Last confirmed live18 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/yainiuai001

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 12 October 2026 and assigned it the closest of 31 fixed categories, at 95% 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 the other topics.

Growth

5,7437,9506,846.526 September 2026 — 7,950 subscribers4 October 2026 — 7,921 subscribers11 October 2026 — 7,900 subscribers14 October 2026 — 7,793 subscribers17 October 2026 — 7,607 subscribers20 October 2026 — 7,312 subscribers23 October 2026 — 7,103 subscribers26 October 2026 — 6,857 subscribers29 October 2026 — 6,675 subscribers1 November 2026 — 6,467 subscribers5 November 2026 — 6,406 subscribers9 November 2026 — 6,215 subscribers13 November 2026 — 5,941 subscribers18 November 2026 — 5,743 subscribers26 September 202618 November 2026
14 measurements spanning 52 days, net -2,207. 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 5,412–8,281 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Nov 2026, 10:575,743-198
13 Nov 2026, 15:115,941-274
9 Nov 2026, 01:306,215-191
5 Nov 2026, 08:146,406-61
1 Nov 2026, 23:166,467-208
29 Oct 2026, 20:116,675-182
26 Oct 2026, 11:266,857-246
23 Oct 2026, 07:567,103-209
20 Oct 2026, 08:587,312-295
17 Oct 2026, 04:377,607-186
14 Oct 2026, 10:267,793-107
11 Oct 2026, 04:207,900-21
4 Oct 2026, 14:007,921-29
26 Sept 2026, 23:227,950first reading

Engagement

28 posts held, back to 14 May 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 6 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.721%
avg views ÷ 5,743 subscribers
Avg views / post
41.4
5 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
5
of 28 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 5 November 2026
Posts held28 (14 May 2026 – 5 November 2026)
Views total207
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 11:09 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.

Recent posts

Telegram’s own ‘edited’ marker: 2 of 5 posts held from the last 30 days (40.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

5 Nov 2026, 09:57 UTC12 viewsread 6 November 2026
File

译牛1.5.69 版本更新内容: 1. 修复翻译时提示网络异常问题 官方客服:@yiniui001

4 Nov 2026, 13:14 UTC21 viewsread 6 November 2026
File

译牛1.5.68 版本更新内容: 1. 修复gm不翻译问题; 2. 修复显隐译文无效问题 官方客服:@yiniui001

2 Nov 2026, 10:34 UTC40 viewsread 6 November 2026
File

译牛1.5.67 版本更新内容: 1. gm消息不提示问题; 2. 优化系统业务 官方客服:@yiniui001

30 Oct 2026, 17:46 UTC61 viewsread 6 November 2026
File

译牛1.5.66 版本更新内容: 1. 解决ws备注不显示问题; 2. 解决ws双输入框消息无法发送问题; 3. 解决x不翻译问题; 4. 解决tgk图文消息不翻译问题; 5. 解决tgk编辑消息发送后,译文未更新问题 官方客服:@yiniui001

28 Oct 2026, 09:15 UTC73 viewsread 6 November 2026
File

译牛1.5.65 版本更新内容: 1. 修复tgk发送不翻译问题; 2. 移除signal模式切换功能 官方客服:@yiniui001

14 Oct 2026, 13:49 UTC152 viewsread 6 November 2026
File

译牛1.5.63 版本更新内容: 1. 修复ws语音不翻译问题; 2. 修复tw不翻译问题 官方客服:@yiniui001

9 Oct 2026, 08:27 UTC171 viewsread 6 November 2026
File

译牛1.5.61 版本更新内容: 1. 修复ws官方更新导致的问题; 2. 修复fb商业版消息丢失问题 官方客服:@yiniui001

4 Oct 2026, 17:44 UTC197 viewsread 6 November 2026
File

1.ws更新导致 文本,语音,视频消息不翻译问题修复 官方客服:@yiniui001

21 Sept 2026, 05:15 UTC263 viewsread 6 November 2026
File

译牛1.5.57 版本更新内容: 1. 修复了ws视频不翻译问题 官方客服:@yiniui001

10 Sept 2026, 09:17 UTC326 viewsread 6 November 2026
File

译牛1.5.55 版本更新内容: 1. 解决teams直接显示不可用问题; 2. 解决tgk爆中文问题; 3. 解决ws切换联系人,昵称不同步问题 官方客服:@yiniui001

29 Aug 2026, 04:23 UTC377 viewsread 6 November 2026
File

译牛1.5.51 版本更新内容: 1. 解决客户端异常提示问题 官方客服:@yiniui001

27 Aug 2026, 06:44 UTC367 viewsread 6 November 2026
File

译牛1.5.50 版本更新内容: 1. 优化客户端加载业务 官方客服:@yiniui001

Showing the 12 most recent of 28 posts we hold for @yainiuai001. 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.

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

“译牛 GPT-AI 翻译器【译牛AI】聚合聊天翻译 | 谷歌翻译 | AI智能翻译 | deepl翻译|【官方频道】yiniuai001 yiniui001” (@yainiuai001), 5,743 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/yainiuai001.

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.