Channel
@tlywpdzy
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
229subscribers
+61 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003295516727 |
|---|---|
| Type | Channel |
| Username | @tlywpdzy |
| Created | 28 November 2025 — measured — dated from the channel’s first post |
| First recorded | 23 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/tlywpdzy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 20:38 | 229 | +16 |
| 1 Sept 2026, 11:25 | 213 | +27 |
| 24 Aug 2026, 16:44 | 186 | +18 |
| 23 Aug 2026, 01:00 | 168 | first reading |
9 posts held, back to 28 November 2025 — 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 22 August 2026 |
|---|---|
| Posts held | 9 (28 November 2025 – 22 August 2026) |
| Views total | 58 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Aug 2026, 01:00 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.
12 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 91.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 11 | 91.7% | |
| 👍 | 1 | 8.33% |
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 9 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 28 November 2025 to 22 August 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.
💌【太郎优选妹妹备忘录】 💌统计妹妹的联系方式，以防遗忘 多多： @dszjcj 小冉： @xiaoran633 小炤： 上岸了 思雨： @siyuz112 宝宝： 桩跑了 钰钰： 离郑了 金怡： 离郑了 小沫： @hxiaomo 茹茹： @ru232 饭崽： @fanf987 奶琪： 离郑了 苏韵： @xiaohushi88 媛媛： @PaoPaoI10 妙妙： @miaomiaonckkx 倩倩： 上岸了 苏篱： @suli06815 予落： @yuluo0452 豆包： @doub090 小馨： 上岸了 小艺： 上岸了 小泰雅： @xty0221 苏千月： @sqy0909 姜宝宝： @jbb235 小小柔： @xiaoxiaorou1
开盒业务小贵，咨询费100，先付口令在咨询，拒绝口嗨！
登录账号要邮箱开会员下载这个版本
主任自己在用的VPN xyz.aayi1.com
❤1
@sx2025bot 双向机器人
https://youtu.be/zedlIvabGHs 键解决客户私信限制：Telegram双向私聊机器人设置教程 担心因为私信限制而失去宝贵的客户联系？不用担心，我们提供了一种简单且高效的方法，确保你能够保持与客户的双向沟通，避免客户流失。 通过以下步骤设置一个双向私聊机器人，你可以轻松绕过私信限制，与客户保持无缝沟通。无论你是新手还是老手，这个教程都能帮助你快速上手。 步骤1：创建双向私聊机器人 打开Telegram并搜索 @BotFather 这是创建和管理Telegram机器人的官方工具。 创建一个新的机器人 输入 /start 开始与 @BotFather 的对话。 输入 /newbot 创建一个新机器人。 按提示输入机器人的名称和用户名。 获取机器人的令牌 @BotFather 会生成一个API令牌，复制这个令牌备用。 步骤2：配置回声机器人 @LivegramBot 打开Telegram并搜索 @Livegr…
❤10👍1
点击切换中文语言包 https://t.me/setlanguage/zhcncc
Channel photo updated
Channel created
Showing the 9 most recent of 9 posts we hold for @tlywpdzy. 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 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“太狼业务频道” (@tlywpdzy), 229 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/tlywpdzy.
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.