🎁 LinuxDO 专属套餐领取通知 如需领取 LinuxDO 专属套餐,请私聊: 👉 @ZeroCatTGBot ⚠️ 请注意:是 @ZeroCatTGBot,不是群里的验证机器人!

Channel
ZeroCat
@ZeroCatAI
On this record: Growth · Engagement · Posts · Citations · Cite this entry
4,833subscribers
+314 since we began measuring on 2 September 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1004306902203 |
|---|---|
| Type | Channel |
| Username | @ZeroCatAI |
| Created | 17 July 2026 — measured — dated from the channel’s first post |
| First recorded | 2 September 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/ZeroCatAI |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 06:21 | 4,833 | +165 |
| 2 Sept 2026, 17:16 | 4,668 | +149 |
| 2 Sept 2026, 11:15 | 4,519 | no change |
| 2 Sept 2026, 11:00 | 4,519 | first reading |
Engagement
6 posts held, back to 17 July 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.
- ERR · 30 days
- 16.0%
- avg views ÷ 4,833 subscribers
- Avg views / post
- 774
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 6 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.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 6 (17 July 2026 – 2 September 2026) |
| Views total | 1,548 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 11:15 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
Posted without readable text
ZeroCat 线上服务说明 原站点以及迁移至 ZeroCat 余额已经同步 常规入口:https://zero.cat 直连 API:https://api.zero.cat 亚洲入口:https://asia.zerocat.cc 模型、分组和价格会持续调整,请以模型广场实时页面为准。遇到调用问题时,请提供模型名、分组、请求时间和 request id,不要公开 API Key。 后续模型更新、线路维护和活动信息,通过官网公告发布。 TG 群 :https://t.me/+e9Q7SAUrGjhlOTE5
服务器将迁移
kiro 分组已经恢复
Channel created
Showing the 6 most recent of 6 posts we hold for @ZeroCatAI. 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 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“ZeroCat” (@ZeroCatAI), 4,833 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/ZeroCatAI.
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.