Telegram RegisterThe public register of Telegram

Channel

evA 业务通知

@evAcdstzz

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

60subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003831419582
TypeChannel
Username@evAcdstzz
DescriptionThis channel is for lawful updates only. All content is monitored to comply with Telegram's rules and local laws. Illegal activity will result in removal and reporting.
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/evAcdstzz

Growth

607 August 2026 — 60 subscribers10 August 2026 — 60 subscribers7 August 202610 August 2026
2 measurements spanning 2 days. 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 59–61 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 05:1660no change
7 Aug 2026, 18:4660first reading

Engagement

20 posts held, back to 18 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
239.9%
avg views ÷ 60 subscribers
Avg views / post
144
19 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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 9 August 2026
Posts held20 (18 July 20269 August 2026)
Views total2,735
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 05:16 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
14
Links
17

Lifetime counters from Telegram’s own channel header, read 10 August 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

9 Aug 2026, 04:10 UTC45 viewsread 10 August 2026

假地址降价 ✅✅ 假地址降价 ✅✅ 假地址降价 ✅✅ 假地址降价 ✅✅ @evAcds

6 Aug 2026, 06:54 UTC65 viewsread 10 August 2026

税务局全业务 ✅✅✅ 公司对公名下卡 遗漏小全出 公司发票 一年记录 无遗漏全出 公司财务报表 无遗漏全出 公司股东 无遗漏全出 公司员工 无遗漏全出 公司房产 无遗漏全出 公司车船 无遗漏全出 报单提供: 公司名 税号代码+法人大头+法人sfz号 暂时不做上市.国企.央企 (敏感要提前说.敏感加价) @evAcds

6 Aug 2026, 03:58 UTC193 viewsread 10 August 2026

文字全户 😀😃😀 当天回 文字补齐 😀😃😀 无视脱裤 任意17位 文字猎魔 😀😃😀 无视脱裤 可带排除 单头全户 😀😀😀 当天回 公网实时户籍地 😃😀 文全地址 😃😀 有量的代理来拿优势价 😀😀😀😀😀😀😀😀 🤩🤩🤩🤩🤩🤩 @evAcds

5 Aug 2026, 02:05 UTC411 viewsread 10 August 2026

蓝色字体查看详情和注意事项 公网实时户籍地 ✅✅ 全国文全 ✅✅✅ 公网补齐/猎魔 ✅✅✅ 全国婚姻 ✅✅ 拼接个户 ✅✅ 微信收款码反手机号 ✅✅✅ 出入境+护照 ✅✅ 各种无盲机主 ✅✅✅--✅✅✅ 全天高强度在线 @evAcds 打u报单 公群上押不先单

3 Aug 2026, 12:17 UTC150 viewsread 10 August 2026

微信码反手机号(概率身份证) ✅✅✅ 报单格式: 微信收款码 地区 带地区出单率更高 当天报当天回 ≥ 10单 ✅✅✅/单 ≥ 25单 ✅✅✅/单 不收臭烂剩菜 回单记录点我 单子多的老板,报单加随机字母,以防找不到人回单 @evAcds

3 Aug 2026, 03:18 UTC51 viewsread 10 August 2026

拼接个户 ✅✅ 文全地址+公网大头 读就秒 @evAcds

2 Aug 2026, 03:01 UTC50 viewsread 10 August 2026

破解法人/股东 ✅✅/✅✅ 工商法人/股东 ✅✅/✅✅ 历史法人/股东 ✅✅--✅✅✅

23 Jul 2026, 12:20 UTC173 viewsread 10 August 2026

公网单户籍地 ✅✅ 公网单户籍地 ✅✅ 公网单户籍地 ✅✅ 实时更新户籍地址起诉专用‼️ 一天一车17:30点前报,当天回完 后边的等隔天回 批量更优势 @evAcds

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

Citation-graph rank

Citation-graph rank — 410,490 of 1,183,361entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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.

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

“evA 业务通知” (@evAcdstzz), 60 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/evAcdstzz.

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.