Telegram RegisterThe public register of Telegram
Telegram profile photo for 译达通【edatone】聚合聊天翻译 | 谷歌翻译 | AI智能翻译 | deepl翻译|【官方频道】

Channel

译达通【edatone】聚合聊天翻译 | 谷歌翻译 | AI智能翻译 | deepl翻译|【官方频道】

@edatone_xiaoge1

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Posts recorded as deleted · Citations · Cite this entry

8,646subscribers

-3,151 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003576244862
TypeChannel
Username@edatone_xiaoge1
Description译达通 AI智能聊天翻译软件,官网注册下载软件后即可免费体验3万字符,官网链接:https://edatone.com;下载地址:https://edatone.com/download.html
CreatedBetween 1 December 2025 and 29 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live17 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/edatone_xiaoge1

Topic

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

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@edatone_xiaoge1/33 · this entry29 Mar 2026, 12:17 UTC@edt_aii1/3329 Mar 2026, 12:18 UTC1.00under a minute
@edatone_xiaoge1/36 · this entry29 Mar 2026, 12:17 UTC@edt_aii1/3629 Mar 2026, 12:18 UTC1.00under a minute
@edt_aii1/4331 May 2026, 04:45 UTC@edatone_xiaoge1/43 · this entry31 May 2026, 04:46 UTC1.00under a minute
@edt_aii1/4512 Jun 2026, 14:12 UTC@edatone_xiaoge1/45 · this entry12 Jun 2026, 14:12 UTC1.00under a minute
@edt_aii1/4612 Jun 2026, 14:40 UTC@edatone_xiaoge1/46 · this entry12 Jun 2026, 14:40 UTC1.00under a minute
@edt_aii1/5320 Sept 2026, 06:30 UTC@edatone_xiaoge1/53 · this entry20 Sept 2026, 06:30 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@edt_aii115 (8/8 hand-verifiable sample passed)1.00under a minute@edt_aii1 (10–5)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 2 of the 10 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 15 comparable posts for this entry, running 29 March 2026 to 17 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @edatone_xiaoge1 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 18 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

8,64612,74410,69511 August 202617 November 2026
64 measurements spanning 98 days, net -3,151. 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 8,031–13,359 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
17 Nov 2026, 23:218,646-2,245
14 Nov 2026, 17:0810,891-5
11 Nov 2026, 15:4710,896-5
9 Nov 2026, 18:1910,901-13
8 Nov 2026, 10:1610,914-3
7 Nov 2026, 07:4910,917-1
6 Nov 2026, 07:3010,918-3
5 Nov 2026, 07:0110,921-7
4 Nov 2026, 05:1010,928-2
3 Nov 2026, 02:3910,930-5
2 Nov 2026, 03:4010,935-7
1 Nov 2026, 06:0110,942-9
31 Oct 2026, 05:5610,951-7
30 Oct 2026, 05:2810,958-5
29 Oct 2026, 06:5610,963-13
28 Oct 2026, 06:1910,976-2
27 Oct 2026, 03:2110,978-3
26 Oct 2026, 03:3910,981-2
25 Oct 2026, 03:0610,983-4
24 Oct 2026, 00:1810,987first reading

Engagement

21 posts held, back to 29 March 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 65 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.04%
avg views ÷ 8,646 subscribers
Avg views / post
3.5
2 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
2
of 21 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 17 November 2026
Posts held21 (29 March 2026 – 17 November 2026)
Views total7
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 01:56 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.

What this channel posts

Photos
40
Links
30

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

Recent posts

Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (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).

17 Nov 2026, 06:13 UTC3 viewsread 18 November 2026

👍👍功能优化 官网最新3.1.3版本,优化Signal窗口模式 👍24小时客服:@edatone_jiajian 👍 官网链接:https://edatone.com 👍 下载地址:https://edatone.com/download.html 👍 频道链接:https://t.me/edt_aii1

16 Nov 2026, 10:52 UTC4 viewsread 18 November 2026

Win10 版本升级重要提示 ⚠️ ⚠️ 本次下载为全新架构大版本(v3.0.0 及以上),升级前请务必知悉: 从低版本升级到 v3.0.0 及以上版本后,不支持回退到旧版本; 如需回退使用旧版本,客户端内已登录的账号需要重新扫码登录后才能继续使用。 v3.0.1 更新日志 🚀🚀功能优化 1、翻译语种列表切换为规范语种,按各应用实际支持情况显示,避免选到无法翻译的语种,并自动保持最新 2、群发更稳定:单次最多启动 2 个任务、自动分批发送,不易漏发;定时群发错过时间后自动错峰补发;暂停/恢复更灵敏 3、客户端整体性能大幅优化:开启硬件图形加速、减少界面重复计算、引入后台并行处理,运行更流畅、更省内存,多账号挂机占用明显降低 4、新增性能监测面板(首页与群发视图) 5、群发发送期间防止系统休眠,长时间任务不中断 6、翻译更快:常用内容的翻译结果缓存命中 7、图片缩略图加载更快、更省流量 8、TG-A 群发:联系人列表首屏秒…

20 Sept 2026, 06:30 UTC81 viewsread 18 November 2026
Photo

版本升级重要提示: ⚠️ 本次下载为全新架构大版本(v3.0.0 及以上),升级前请务必知悉: 从低版本升级到 v3.0.0 及以上版本后,不支持回退到旧版本; 如需回退使用旧版本,客户端内已登录的账号需要重新扫码登录后才能继续使用。 v3.0.0 👍👍 🔒 稳定性与安全日志 1、新增窃密防护引擎:自动检测恶意进程与可疑文件,及时告警响应 2、会话安全升级:展示账号已登录天数,支持快速重新登录;登录凭证 30 天自动轮换,退出登录即时失效 3、记住的密码加密保存,更好地保护账号安全 4、、密码强度要求提升:8~30 位且需同时包含字母和数字;分享密码改为安全随机生成 5、新增网络安全检测开关,可自行开启/关闭;证书被篡改时明确提示并展示错误详情 6、应用脚本和安装包增加防篡改校验,被恶意修改时会明确提示 7、应用更新流程安全性加固 8、多项稳定性改进,长时间挂机运行更稳定 唯一官网:https://edatone.co…

28 Jul 2026, 15:12 UTC≈1,130 viewsread 18 November 2026
Photo

通知:Line商业版本,Line官方已恢复正常。 👍 24小时客服:@edatone_jiajian 👍 唯一官网:https://edatone.com 👍 下载地址:https://edatone.com/download.html 👍 唯一频道: https://t.me/edt_aii1

28 Jul 2026, 10:24 UTC≈1,120 viewsread 18 November 2026
Photo

通知:Line商业版本,因官方正在维护中,暂时无法使用,待line官方恢复正常。 👍 24小时客服:@edatone_jiajian 👍 唯一官网:https://edatone.com 👍 下载地址:https://edatone.com/download.html 👍 唯一频道: https://t.me/edt_aii1

10 Jul 2026, 14:46 UTC≈1,150 viewsread 18 November 2026
Photo

重要通知: 请务必通过访问译达通官网:https://edatone.com 不要通过搜索引擎、陌生链接等不明网址登录译达通。

10 Jul 2026, 14:46 UTC≈1,150 viewsread 18 November 2026
Photo

重要通知: 尊敬的译达通用户: 近期我们发现有不法分子仿冒译达通官方网站、客服、频道,搭建钓鱼网站进行诈骗等违法活动,严重威胁您的信息安全。请您务必提高警惕,注意以下事项: 认准译达通唯一官方网址:https://edatone.com 请务必通过此访问译达通官网:https://edatone.com 不要通过搜索引擎、陌生链接等不明网址登录译达通。 译达通官方渠道如下: 唯一官网:https://edatone.com 官方客服:@edatone_jiajian 唯一频道:https://t.me/edt_aii1

12 Jun 2026, 14:40 UTC≈2,220 viewsread 18 November 2026
Photo

WhatsApp官方已恢复,请刷新界面正常使用。 👍24小时客服:@edatone_jiajian 👍 官网链接:https://edatone.com 👍 下载地址:https://edatone.com/download.html 👍 频道链接:https://t.me/edt_aii1

12 Jun 2026, 14:12 UTC≈2,190 viewsread 18 November 2026
Photo

因WhatsApp官方异常,导致网页版本页面无法加载打开,有异常的宝子,请等待官方恢复。 👍24小时客服:@edatone_jiajian 👍 官网链接:https://edatone.com 👍 下载地址:https://edatone.com/download.html 👍 频道链接:https://t.me/edt_aii1

11 Jun 2026, 14:56 UTC≈4,140 viewsread 18 November 2026
Photo

因WhatsApp官方更新,导致聊天内容不显示翻译的请更新版本,技术已优化,有异常的宝子,有问题请及时联系客服。 👍24小时客服:@edatone_jiajian 👍 官网链接:https://edatone.com 👍 下载地址:https://edatone.com/download.html 👍 频道链接:https://t.me/edt_aii1

31 May 2026, 04:46 UTC≈4,160 viewsread 18 November 2026
Photo

因WhatsApp官方更新,导致图片无法发送,技术已优化,有异常的宝子,请更新应用使用,有问题请及时联系客服。 👍24小时客服:@edatone_jiajian 👍 官网链接:https://edatone.com 👍 下载地址:https://edatone.com/download.html 👍 频道链接:https://t.me/edt_aii1

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

Posts recorded as deleted after publishing

We recorded 2 posts on @edatone_xiaoge1 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
16 November 2026
Most recent seen missing
16 November 2026
Median time before seen missing
26 days
Seen missing in the last 30 days
2

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.

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

“译达通【edatone】聚合聊天翻译 | 谷歌翻译 | AI智能翻译 | deepl翻译|【官方频道】” (@edatone_xiaoge1), 8,646 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/edatone_xiaoge1.

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.