Telegram RegisterThe public register of Telegram
Telegram profile photo for @qq58258

Channel

@qq58258

@qq58258

On this record: Growth · Engagement · Posts · Citations · Cite this entry

1subscribers

+0 since we began measuring on 30 September 2026

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

Register entry

Telegram ID-1002677207485
TypeChannel
Username@qq58258
Created22 March 2025 — measured — dated from the channel’s first post
First recorded30 September 2026
Last confirmed live30 September 2026
Measurements held2
On Telegramt.me/qq58258

Growth

130 Sept 2026, 07:47 — 1 subscribers30 Sept 2026, 08:22 — 1 subscribers30 Sept 2026, 07:4730 Sept 2026, 08:22
2 measurements taken within a single day. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Sept 2026, 08:221no change
30 Sept 2026, 07:471first reading

Engagement

2 posts held, back to 22 March 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 2 posts for this entry, the most recent from 22 March 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

22 Mar 2025, 07:19 UTC2 viewsread 30 September 2026

【需】 料方找取现车大押车(欢迎车头或中介来谈) 资金性质:一道色刷、空降约炮料、一切色料 【随时可以查后台记录】 汇率:【按照市场汇率随时有上浮】 优势:稳定不断供 长期合作 夜车优先! 交易时间:晚七点-凌晨4点 具体要求:押金越多,放的越多,回款越快,放的更快 单笔:3000到20万(可以控) 无三黑 小贷 淘宝 发现可不回款 联系人:@qq58258 ⭐️只走汇旺担保 @kefu 其他担保勿扰⭐️

Showing the 2 most recent of 2 posts we hold for @qq58258. 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 30 September 2026 — this entry's latest reading, not the date you are reading this.

“@qq58258” (@qq58258), 1 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/qq58258.

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.