9 May 2025, 00:17 UTC34 viewsread 13 August 2026
此ID出售，关注豪华 ID @G2222
Channel
i
@renchong
On this record: Previous handles · Growth · Engagement · Posts · Citations · Cite this entry
7subscribers
+2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002424255623 |
|---|---|
| Type | Channel |
| Username | @renchong |
| Created | 14 December 2024 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/renchong |
Previous handles
@renchong was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
@renchong
held 13 August 2026 – 13 August 2026
held 13 August 2026 – 13 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 23:25 | 7 | +4 |
| 16 Aug 2026, 21:13 | 3 | -2 |
| 13 Aug 2026, 03:32 | 5 | no change |
| 8 Aug 2026, 15:46 | 5 | first reading |
Engagement
6 posts held, back to 14 December 2024 — 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 6 posts for this entry, the most recent from 9 May 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
28 Apr 2025, 12:22 UTC45 viewsread 13 August 2026
以下 id 出售中 @xintuo 信托 @xinyuge 信誉阁 @Manzu 满足 @xinyushe 信誉社 @xiaoqie 小妾 @wushen 武神 @guanxuan 官宣 @xinpin 新品 @cundai 存贷 @lujin 撸金 @shouzu 售租 @jiezu 借租 @Biiiii 哔哩哔哩 @jingzhen 经侦 @Diwang 帝王 @wanjia 玩家 @lukou 撸口 @jiama jiama @dabaoguang 曝光 @danbaoshe 担保 @iD_bot ID @Bossi bossi @asvip svip @Xinnn 信 @yinke 更多 ID 购买关注：@G2222
20 Feb 2025, 12:13 UTCviews —
Channel name was changed to «人宠»
20 Feb 2025, 12:12 UTC65 viewsread 13 August 2026
Sticker
Sticker, posted without a caption
28 Dec 2024, 07:23 UTCviews —
Channel name was changed to «renchong»
14 Dec 2024, 15:29 UTCviews —
Channel created
Showing the 6 most recent of 6 posts we hold for @renchong. 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
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“i” (@renchong), 7 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/renchong.
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.