Channel
@zaiaSAS
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
44,464subscribers
+9,046 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001198265203 |
|---|---|
| Type | Channel |
| Username | @zaiaSAS |
| Description | 辽宁，吉林，黑龙江 管理员 @DaxiongoBot 交流群组 https://t.me/zhaiSAA |
| Created | 14 July 2022 — measured — dated from the channel’s first post |
| First recorded | 20 August 2026 |
| Last confirmed live | 25 October 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 25 October 2026 |
| On Telegram | t.me/zaiaSAS |
Other / unclassifiable — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Oct 2026, 10:56 | 44,464 | +190 |
| 24 Oct 2026, 11:16 | 44,274 | +52 |
| 23 Oct 2026, 13:49 | 44,222 | +115 |
| 22 Oct 2026, 13:39 | 44,107 | +57 |
| 21 Oct 2026, 07:39 | 44,050 | +131 |
| 20 Oct 2026, 03:09 | 43,919 | +115 |
| 19 Oct 2026, 04:18 | 43,804 | +96 |
| 18 Oct 2026, 07:46 | 43,708 | +215 |
| 17 Oct 2026, 08:59 | 43,493 | +111 |
| 16 Oct 2026, 12:19 | 43,382 | +229 |
| 15 Oct 2026, 11:47 | 43,153 | +86 |
| 14 Oct 2026, 13:18 | 43,067 | +231 |
| 12 Oct 2026, 23:21 | 42,836 | +805 |
| 8 Oct 2026, 12:41 | 42,031 | +655 |
| 4 Oct 2026, 01:55 | 41,376 | +1,063 |
| 25 Sept 2026, 04:17 | 40,313 | +772 |
| 17 Sept 2026, 04:59 | 39,541 | +319 |
| 15 Sept 2026, 09:01 | 39,222 | +174 |
| 13 Sept 2026, 18:58 | 39,048 | +111 |
| 12 Sept 2026, 02:15 | 38,937 | first reading |
93 posts held, back to 14 July 2022 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 122 pages of Telegram’s post history, 20 posts per page.
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. It is computed over the 7 of 39 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 25 October 2026 |
|---|---|
| Posts held | 93 (14 July 2022 – 25 October 2026) |
| Views total | 34,481 |
| Reactions total | 8 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 25 Oct 2026, 18:20 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.
Lifetime counters from Telegram’s own channel header, read 25 October 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.
Measured directly from 7 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
98 reactions across 21 posts, in 4 distinct kinds. The most used accounts for 85.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 84 | 85.7% | |
| 👍 | 11 | 11.2% | |
| 🎉 | 2 | 2.04% | |
| 🥰 | 1 | 1.02% |
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 24 of the 93 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 98 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 93 most recent posts we hold, published 14 July 2022 to 25 October 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.
沈阳 全裸4推 94号 本店技师18-22之间 绝对精品服务 没有一个娘们技师挺放心 裸浴 柔式spa 精油开背 果冻系列 全身ab面 毒龙 滑龙勾 海底捞月 指滑 配合69造型 可吃咪咪 可吃鲍鱼 等等 享受过程 注重结果满钟75分钟 弱水三千，只求一嫖 板电话18540273385 聊天群组 https://t.me/hyjzltqspa 选妃频道 https://t.me/hyjzspapd 私信 @hyjz69
✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅海南资源 ✅山东资源 ✅天津资源 👨👩👧👦东北群组 🛜其它地区
✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅海南资源 ✅山东资源 ✅天津资源 👨👩👧👦东北群组 🛜其它地区
✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅海南资源 ✅山东资源 ✅天津资源 👨👩👧👦东北群组 🛜其它地区
✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅海南资源 ✅山东资源 ✅天津资源 👨👩👧👦东北群组 🛜其它地区
✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅海南资源 ✅山东资源 ✅天津资源 👨👩👧👦东北群组 🛜其它地区
✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅海南资源 ✅山东资源 ✅天津资源 👨👩👧👦东北群组 🛜其它地区
✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅海南资源 ✅山东资源 ✅天津资源 👨👩👧👦东北群组 🛜其它地区
1️⃣ 1️⃣ 1️⃣ 1️⃣ 1️⃣ 1️⃣ ❤️❤️大连高端海选94SPA会所 ❤️❤️ 全程⚡⚡后 😘推出❤️春日限定 ❤️ 活动原价599元😘⚡分钟不限次 ➕200双飞不一样体验 现在预约只需要499😘⚡元项目正常进行 😀 积分优惠券 正常兑换使用出💦 方式：🍑推 🐻推 🦵夹 🦶推 👋推 🍒🇧🇫 🇧🇫 🇧🇫： 12:00-2:00 😂出勤1️⃣0️⃣➕位佳丽 各种款式我们都有 🥹不定时➕新💃，😀 😃哥哥们前来，给你不一样的极致体验 🤨🤨🤨🤨🤨🤨服务如下👇 性感熊滑💝嫦娥之吻🫦波涛汹涌🎭 蚂蚁上树💋水晶之恋🤗可毒🐉🥰 日式调情🍑🍑双飞姐妹💃🍑猴子偷桃🍑可亲可摸❤️上下可摸❤️ 水漫深幽🐳帘下勾情🐟 尊享奢宠🤜飞上云霄🐷 温阳泄潮🤪魔指仙境😻 更有cosplay换装情趣体验： 空姐 护士 JK 情趣 小野猫 秘书 学妹 女仆 御姐 更多惊喜等待哥哥…
❤1
✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅海南资源 ✅山东资源 ✅天津资源 👨👩👧👦东北群组 🛜其它地区
✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅海南资源 ✅山东资源 ✅天津资源 👨👩👧👦东北群组 🛜其它地区
✅西安资源 ✅昆明资源 ✅南昌资源 ✅惠州资源 ✅义乌资源 ✅武汉资源 ✅海南资源 ✅山东资源 ✅天津资源 👨👩👧👦东北群组 🛜其它地区
Showing the 12 most recent of 93 posts we hold for @zaiaSAS. 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.
Named by 3 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.
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.
@zaiaSAS named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 25 October 2026 — this entry's latest reading, not the date you are reading this.
“东北认证资源🥇沈阳大连长春哈尔滨” (@zaiaSAS), 44,464 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/zaiaSAS.
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.