Telegram RegisterThe public register of Telegram
Telegram profile photo for 收U。买u卖u

Channel

收U。买u卖u

@usd55667

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

204subscribers

-113 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-1001812392340
TypeChannel
Username@usd55667
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live3 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/usd55667

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 24 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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

204317260.57 August 2026 — 317 subscribers8 August 2026 — 315 subscribers8 August 2026 — 315 subscribers15 August 2026 — 280 subscribers23 August 2026 — 254 subscribers31 August 2026 — 232 subscribers9 September 2026 — 217 subscribers18 September 2026 — 208 subscribers3 October 2026 — 204 subscribers7 August 20263 October 2026
9 measurements spanning 57 days, net -113. 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 187–334 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 04:41204-4
18 Sept 2026, 15:01208-9
9 Sept 2026, 18:19217-15
31 Aug 2026, 10:25232-22
23 Aug 2026, 14:04254-26
15 Aug 2026, 11:43280-35
8 Aug 2026, 07:34315no change
8 Aug 2026, 06:33315-2
7 Aug 2026, 14:38317first reading

Engagement

17 posts held, back to 1 January 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 21 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
52s
Average length
9s

Measured directly from 6 videos 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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤150.0%
👍150.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 2 of the 17 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 1 January 2025 to 21 May 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

21 May 2026, 05:36 UTC132 viewsread 8 August 2026

👋 您好,我是 全网高价..⭐️ @uuu590 ID:6861241645 🔍使用SOSO机器人可以搜索Telegram群组、频道、甚至视频、音乐等任何您想要的资源。 — 🔍 搜搜更懂你! 👇点击下方按钮试试吧

15 May 2026, 02:11 UTC175 viewsread 8 August 2026
Photo

高价收u/买u卖u/纯白资现存/线上收u/换汇/现金收泰达币/承兑出u,官方客服:@uuu590 高价收u/买u卖u/u换现金/现金收u/线下收u/白资收u/换汇/现金收泰达币/承兑/

8 May 2026, 16:02 UTC166 viewsread 8 August 2026
Video

高价收u/买u卖u/u换现金/现金收u/线下收u/白资收u/换汇/现金收泰达币/承兑/ 客服:@uuu590 双向联系:@uuu599bot

7 May 2026, 08:03 UTC156 viewsread 8 August 2026
Video

全国送现。 高价收u。买u。上浮收u。u换现金。承兑 ,汇率全网最高,白资 先款后u。客服:@uuu590

7 May 2026, 08:00 UTC131 viewsread 8 August 2026

@CSZWBOT已被升级为管理员,开启搜索请点击下面按钮,普通收录默认即可,关闭垃圾删除功能,否则会误删您的信息!

7 May 2026, 07:56 UTC118 viewsread 8 August 2026

内容索引成功,等待系统更新权重。 点击下方【⚡️助力】按钮获得助力权重

7 May 2026, 07:56 UTC125 viewsread 8 August 2026

@CJYQ1BOT 已设置为管理员,链接收录中! 请等待审核,非搜索群请勿打开搜索功能,会降权!

7 May 2026, 07:53 UTC116 viewsread 8 August 2026

高价收u/买u卖u/纯白资现存/线上收u/换汇/现金收泰达币/承兑出u,官方客服:@uuu590 高价收u/买u卖u/u换现金/现金收u/线下收u/白资收u/换汇/现金收泰达币/承兑/

9 Mar 2025, 00:07 UTC655 viewsread 8 August 2026
Video

USDT全球 兑换外汇 美元 港币 欧元 韩币等其他国家外汇 小额线上交易 先款后回U 大额线下同台交易 客服✈️:@usd11668

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

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

“收U。买u卖u” (@usd55667), 204 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/usd55667.

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.