Telegram RegisterThe public register of Telegram
Telegram profile photo for 只做优势

Channel

只做优势

@Ruan0003

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

25subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003441745321
TypeChannel
Username@Ruan0003
CreatedBetween 1 November 2025 and 15 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/Ruan0003

Topic

Other / unclassifiable — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 why it has no browse page of its own yet.

Growth

252625.57 August 2026 — 25 subscribers11 August 2026 — 25 subscribers31 August 2026 — 26 subscribers11 October 2026 — 25 subscribers7 August 202611 October 2026
4 measurements spanning 65 days. 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 25–26 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 18:1925-1
31 Aug 2026, 10:3626+1
11 Aug 2026, 09:3325no change
7 Aug 2026, 10:5025first reading

Engagement

20 posts held, back to 15 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 page of 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 20 posts for this entry, the most recent from 13 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
11s
Average length
11s

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

7 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 57.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🥰457.1%
❤228.6%
😍114.3%

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 20 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 15 January 2026 to 13 April 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

12 Mar 2026, 01:19 UTC454 viewsread 11 August 2026

美团 最新一条 已经测试 价格😀😀😀 最新三条😀😀😀😀 默认三个月最新内容 @Ruan233 文字回单 带订单号 下单时间 商品详情 三个月内最新,过半年不出单

13 Feb 2026, 10:54 UTC354 viewsread 11 August 2026

以后结账只认ok 还有我自己的代收 死都不先单 口水三无一律不搭理 要做单看好频道再来 不要再掰扯7788的

5 Feb 2026, 21:51 UTC536 views0 reactionsread 11 August 2026

地区房产可出地区 没有备注的 就是可出全省房产 按套收费 可排除 12天津13河北14山西(太原大同) 15内蒙古 21辽宁22吉林(带大头)23黑龙江(大头有效期) 32江苏(大头)33浙江34安徽35福建(大头+有效期)36江西(大部分地区)37山东(济南 青岛) 41河南(郑州南阳信阳)43湖南44广东(大头)45广西(带大头)46海南 50重庆(大头+有效期)51四川(大头+有效期)52贵州(头)53云南(大头)54西藏 61陕西(大头)62甘肃(大头)63青海64宁夏65新疆(大头) 今日报价 首套😀😀😀第二套😀😀😀 目前只有这些地区了 其余地区查不了 当天即可极速回单 我在大部分即可秒 @Ruan233

3 Feb 2026, 08:58 UTC454 viewsread 11 August 2026

全天单户籍地址😀😀 量大代理 来找我拿优势 联系:@Ruan233

24 Jan 2026, 07:30 UTC809 views0 reactionsread 11 August 2026

q反😀😃😀 小红书反😃😃😀 快反😀😀😀 微码反😀😃😀 三网名下号😀😀 车小档😃😀😀 名下车😃😃😀 寻量大盘口 律所 催收前来对接 @Ruan233

22 Jan 2026, 07:54 UTC574 viewsread 11 August 2026

全国文全 😀😃😀 独集可不要保真不保漏 ‼️ 公网补齐 😃😀 无视17位 脱裤可来‼️ 公网猎魔 😃😀 可排除 空无需收费‼️ 寻有量代理 你有量我有价 @Ruan233

21 Jan 2026, 12:59 UTC519 viewsread 11 August 2026
Photo

😂 三网手机实时定位😂 📱用过的都说准,懂得都懂 😀😀😀😀 误差范围200米左右,30分钟左右回单 抓人捉奸不耽误!!! @Ruan233

21 Jan 2026, 12:35 UTC478 viewsread 11 August 2026

邮政地址源头 带单号 合作共赢 源头收单 邮政单地址 😛👌 多地址 😱👌(默认两张) 一年邮政地址(默认5张)👌😉👌 律所和催收请看频道上方批量模板 凌晨1点一车 回单时间:中午3点 中午2点一车 回单时间:晚上7点 下午7点一车 回单时间:晚上10点 当天10点我还没给你默认空单! @Ruan233 独家代理: 加急单全天在秒,3分钟内回单适用于急需客户。受理时间,中午2点-晚上10点。

21 Jan 2026, 12:23 UTC643 viewsread 11 August 2026

❤️联通机主带地址 😀😀 😀😀 工号出单 @Ruan233

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

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

“只做优势” (@Ruan0003), 25 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/Ruan0003.

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.