Channel
@daixie5
On this record: Growth · Engagement · Posts · Citations · Cite this entry
44subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003167070609 |
|---|---|
| Type | Channel |
| Username | @daixie5 |
| Created | 16 October 2025 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/daixie5 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 16:47 | 44 | -3 |
| 10 Aug 2026, 13:18 | 47 | no change |
| 7 Aug 2026, 06:02 | 47 | first reading |
5 posts held, back to 16 October 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 pageof 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 23 July 2026 |
|---|---|
| Posts held | 5 (16 October 2025 – 23 July 2026) |
| Views total | 8 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 13:18 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.
😊😊😊😊 😀😀😀😀😀😀😀😀 😀 ：迪安工作室：人设套图证件绘画：点击文字跳转 😃 ： 亚洲女套图 😄 ：亚洲男套图 😄 ： 欧美女套图 😄 ：欧洲男套图 😄： 女私密套图 😀 ：迪安工作室： 😃😃😃😃😃😃😃😃 😃 ：翻译软件 😃 ：智能翻译 😃 ： 彩绘素描 😃 ：证件P图 😃 ： 批发飞机 😃 ：代写人设 😃 ： 代开会员 😃 ：海外素材 😃 ： 迪安工作室： 😄😃😄😃 : 💸 😃 ： 😀😀😃 …
人设代写，专业定制，全球任意国家，任意位置，各种职业，根据您的要求为您打造属于您独一无二的专业人设。【包含人物基本信息 家庭住址 人物生活经历 感情经历 创业经历 感情经历等等】 😃😀😃😀😃😀😃： 😀 ： 客服：@dian696
专业定制人设.包您满意。😀 ： 客服：@dian696
😃😀😃😀😃😀😃： 😀 ： 客服：@dian696
Channel created
Showing the 5 most recent of 5 posts we hold for @daixie5. 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 — 695,810 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.
Named by 5 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“人设代写 人设简历 资料代写人设资料” (@daixie5), 44 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/daixie5.
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.