Channel
@rafz_01
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
22subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003531686234 |
|---|---|
| Type | Channel |
| Username | @rafz_01 |
| Created | 12 January 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/rafz_01 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 22:45 | 22 | no change |
| 12 Aug 2026, 22:32 | 22 | first reading |
2 posts held, back to 12 January 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 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 2 posts for this entry, the most recent from 13 January 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
4 reactions across 1 post, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 2 | 50.0% | |
| 💩 | 1 | 25.0% | |
| 🤣 | 1 | 25.0% |
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 1 of the 2 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 2 most recent posts we hold, published 12 January 2026 to 13 January 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.
❗️❗️新增一枚骗子 昵称：好运来天眼查（任何业务先款后单） 用户名：@gaofushuai 被骗金额：170U 其他联系方式: 无 群组/频道链接：无 安卓进入主页 tg://openmessage?user_id=5422606594 苹果进入主页 tg://user?id=5422606594 被骗过程: 车轨回单不认账 说假 包售后 可以复查 找喜力复查 结果一致 依旧不认 让结账喊进群扯 双押1700 假的吃我的 真的吃他的 开始立人设 说自己不差钱 扯遗漏 说单子出少了 又说外面现在没渠道 让找果盘复查 又说同一个渠道复查结果肯定还是一致 既然一致真单 我收单也说有记录出单即收费 不结账 你家死人了？u换冥币烧给家里人？同行谁不知道车轨系统有多少给多少 出单即收费 接受不了规则你下你MLGB单子 公示人:@ddtycd
🤡2💩1🤣1
Channel created
Showing the 2 most recent of 2 posts we hold for @rafz_01. 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 — 415,441 of 1,481,217entries 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“瑞安反诈” (@rafz_01), 22 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/rafz_01.
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.