Channel
@tazan
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
144subscribers
+2 since we began measuring on 14 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003731584514 |
|---|---|
| Type | Channel |
| Username | @tazan |
| Created | 28 April 2026 — measured — dated from the channel’s first post |
| First recorded | 14 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/tazan |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 23:20 | 144 | +2 |
| 14 Sept 2026, 18:22 | 142 | no change |
| 14 Sept 2026, 17:47 | 142 | first reading |
14 posts held, back to 28 April 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 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 1 September 2026 |
|---|---|
| Posts held | 14 (28 April 2026 – 1 September 2026) |
| Views total | 527 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Sept 2026, 18:22 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.
Measured directly from 2 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.
6 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 83.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 83.3% | |
| 👏 | 1 | 16.7% |
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 3 of the 14 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 28 April 2026 to 1 September 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.
塔赞科技 专注 Telegram 机器人开发与自动化服务，产品稳定、操作简单，持续更新升级。 核心产品 1️⃣ ID 查询机器人 一键查询用户、群组及频道 ID。 ✨ 信息识别更快，机器人开发必备工具。 2️⃣ TG 代理机器人 快速获取 Telegram 专用代理。 ✨ 一键连接，使用简单，让 Telegram 连接更顺畅。 3️⃣ USDT 监控机器人 实时监控 TRON 地址的 USDT 收支变化。 ✨ 转账秒级提醒，收款、对账、盯盘更省心。 4️⃣ 多客服双向机器人 支持多客服协作、消息双向转发及群组客服。 ✨ 一个机器人连接用户与客服，告别漏回、重复回复。 🎬 基础模式演示视频 🎬 群组模式演示视频 5️⃣ TRON 能量租赁机器人 自助租赁 TRON 能量，降低 USDT 转账成本。 ✨ 自动下发、快速到账，无需私钥，高频转账更划算。 6️⃣ 工资记账机器人 支持群组工资记账、账本管理、…
❤4👏1
💬新一代多客服双向机器人 - 群组模式 - 每位客户都会拥有一个独立话题。 - 客户发来的消息会进入对应话题。 - 客服直接在话题中发送消息即可回复客户。 - 支持添加多位客服成员协作回复 - 客服成员只能回复客户，不能删除或管理客户话题。
❤1
💬 新一代多客服双向机器人 - 基础模式 适合个人客服或咨询量较少的场景，无需创建群组。 使用方法： 1. 用户向客服机器人发送消息。 2. 消息会转发到机器人所有者的私聊窗口。 3. 客服找到对应消息，点击“回复”后输入内容。 4. 机器人会将回复发送给对应用户。 特点： - 无需创建和配置群组。 - 部署简单，创建机器人后即可使用。 - 所有客户消息集中在一个私聊窗口。 - 必须回复对应消息，才能准确回复客户。 - 适合单人管理。
10
9
8
7
6
5
4
3
2
Showing the 12 most recent of 14 posts we hold for @tazan. 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 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.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“塔赞科技” (@tazan), 144 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/tazan.
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.