Telegram RegisterThe public register of Telegram
Telegram profile photo for 天鹅业务

Channel

天鹅业务

@Tianeliwu

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

11,433subscribers

+898 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003367379678
TypeChannel
Username@Tianeliwu
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 November 2026
Measurements held48
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/Tianeliwu

Topic

Ecommerce storefront — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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 the other topics.

Growth

1,70712,2096,9587 August 2026 — 10,535 subscribers8 August 2026 — 10,536 subscribers9 August 2026 — 10,537 subscribers10 August 2026 — 10,505 subscribers11 August 2026 — 10,433 subscribers12 August 2026 — 10,319 subscribers13 August 2026 — 10,246 subscribers14 August 2026 — 9,410 subscribers17 August 2026 — 9,233 subscribers20 August 2026 — 10,021 subscribers21 August 2026 — 10,467 subscribers23 August 2026 — 10,205 subscribers24 August 2026 — 9,835 subscribers27 August 2026 — 12,209 subscribers28 August 2026 — 12,172 subscribers29 August 2026 — 12,169 subscribers30 August 2026 — 12,163 subscribers31 August 2026 — 12,098 subscribers1 September 2026 — 12,051 subscribers2 September 2026 — 12,047 subscribers3 September 2026 — 12,030 subscribers5 September 2026 — 11,830 subscribers8 September 2026 — 11,062 subscribers11 September 2026 — 10,659 subscribers13 September 2026 — 10,165 subscribers14 September 2026 — 9,617 subscribers18 September 2026 — 9,590 subscribers28 September 2026 — 5,516 subscribers5 October 2026 — 2,951 subscribers12 October 2026 — 2,641 subscribers15 October 2026 — 1,707 subscribers18 October 2026 — 8,438 subscribers21 October 2026 — 11,673 subscribers22 October 2026 — 11,651 subscribers23 October 2026 — 11,606 subscribers24 October 2026 — 11,590 subscribers25 October 2026 — 11,587 subscribers26 October 2026 — 11,576 subscribers27 October 2026 — 11,564 subscribers28 October 2026 — 11,537 subscribers29 October 2026 — 11,532 subscribers30 October 2026 — 11,500 subscribers31 October 2026 — 11,463 subscribers1 November 2026 — 11,447 subscribers2 November 2026 — 11,440 subscribers3 November 2026 — 11,464 subscribers5 November 2026 — 11,441 subscribers6 November 2026 — 11,433 subscribers11,4337 August 20266 November 2026
48 measurements spanning 90 days, net +898. 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 132–13,784 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 48
Measured (UTC)SubscribersChange
6 Nov 2026, 00:0111,433-8
5 Nov 2026, 00:4511,441-23
3 Nov 2026, 21:5711,464+24
2 Nov 2026, 19:2711,440-7
1 Nov 2026, 19:3711,447-16
31 Oct 2026, 20:5511,463-37
30 Oct 2026, 18:0911,500-32
29 Oct 2026, 15:2911,532-5
28 Oct 2026, 17:2811,537-27
27 Oct 2026, 14:2811,564-12
26 Oct 2026, 16:1811,576-11
25 Oct 2026, 14:3711,587-3
24 Oct 2026, 11:4111,590-16
23 Oct 2026, 12:2511,606-45
22 Oct 2026, 10:0611,651-22
21 Oct 2026, 00:2711,673+3,235
18 Oct 2026, 08:318,438+6,731
15 Oct 2026, 09:491,707-934
12 Oct 2026, 12:152,641-310
5 Oct 2026, 21:412,951first reading

Engagement

13 posts held, back to 15 June 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 51 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.813%
avg views ÷ 11,433 subscribers
Avg views / post
93.0
2 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
2
of 13 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 4 November 2026
Posts held13 (15 June 2026 – 4 November 2026)
Views total186
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 19:52 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

Video runtime
7s
Average length
7s

Measured directly from 1 video 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.

Reaction mix

6 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🎉350.0%
❤116.7%
😁116.7%
🥰116.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 6 of the 13 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 13 most recent posts we hold, published 15 June 2026 to 4 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

4 Nov 2026, 14:06 UTC37 viewsread 5 November 2026
Photo

这位客户看到信息回复一下 定金压半年了 一点消息没有 地址留的还是交易所公链没法退 看到后回复下地址退定金给你 事情也不处理了 定金压了半年也不回消息

4 Aug 2026, 05:27 UTC768 views1 reactionsread 5 November 2026

🛡【精养老号·防封之王】🛡 🌩一个月耐用号 【2U】 🌩三个月耐用号 【3U】 🌩六个月耐用号 【4U】 🌩一年的耐用号 【5U】 🌩两年起耐用号 【6U】 三年-五年的耐用号【7U】 Api接码登陆 🎁 精品会员成品号: 新推出周会员新号 3.5U 送新号 新推出周会员老号 4.5U 送年号 1️⃣一个月会员号 【 6U 】送月老号 2️⃣三个月会员号 【16U】送1年老号 3️⃣六个月会员号 【21U】送2年老号 4️⃣十二月会员号 【36U】送5年老号 Api接码登陆 ✨【TG 会员专区】✨ 1️⃣一个月会员 【 5U 】需登陆账号 2️⃣三个月会员 【12U】 3️⃣六个月会员 【17U】 4️⃣十二月会员 【30U】 Tg内置代理(无需任何vpn直接使用) 7天5g 3u 30天20g 7u 30天40g 10u 30天60g12u 90天50g13u 90天100g20…

❤1

20 Jul 2026, 15:42 UTC789 viewsread 5 November 2026
Photo

4万8司法冻结 6月23日我们介入历经1个月成功解冻! 专业解冻司法冻结各类资金,战绩可查!

7 Jul 2026, 09:12 UTC941 viewsread 5 November 2026
Photo

【天鹅】自助刷粉机器人 顶级供应商 ,全球粉丝关注点赞。同质量产品全网最低价! 例如:每1000僵尸粉🟰1u 天鹅24小时自助刷粉机器人入口: @tianeSFbot 提交订单 秒级处理 无需等待! 充值ok 福利来 人民币充值

2 Jul 2026, 05:38 UTC966 viewsread 5 November 2026

开通A+认证后 不要更改认证的频道/群组链接 会掉认证

30 Jun 2026, 09:21 UTC985 viewsread 5 November 2026

群组或频道僵尸粉 机器人邀请点击 频道帖子浏览量 炸群 以上所有价格2u=1000个 老客户1u=1000个 天鹅24小时自助刷粉 @tianeSFbot 提交订单秒级处理 无需等待

30 Jun 2026, 05:59 UTC861 viewsread 5 November 2026
Photo

👑官方背书 ⭐️权威象征 👑老板专属 ⭐️稳定可靠 👑一个成功人士的门面 🅰️官方认证代开 需要同款认证的可以私信我 永久有效 可用于:频道/群组 认准 @Tianeyw ✨ Hold 验证服务 💬 定价 个人:2,500 $ 一年 频道/群:1,500 $ 一年 机器人:4,000 $ 一年

22 Jun 2026, 20:42 UTC890 views1 reactionsread 5 November 2026
Photo

依旧最真实反馈!6月8日银行卡司法冻结并且提交资料给我,6月18日两张卡成功解冻并且取现。靠谱就完事 解冻热线 @tianeyw

🥰1

20 Jun 2026, 04:32 UTC822 views1 reactionsread 5 November 2026
Photo

@ekpay 出售 易卡支付 易卡钱包 ek支付 ek钱包

🎉1

18 Jun 2026, 15:24 UTC733 views1 reactionsread 4 November 2026
Photo

解除双向无法跳转人机验证的完美解决。 @tianeyw

🎉1

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

Posts edited after publishing

@Tianeliwu edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
25 August 2026
Most recent edit
2 September 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @Tianeliwu as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
1 September 2026
Most recent seen missing
3 November 2026
Median time before seen missing
38 days
Seen missing in the last 30 days
1

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

“天鹅业务” (@Tianeliwu), 11,433 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/Tianeliwu.

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.