Telegram RegisterThe public register of Telegram

Channel

马猴的业务频道

@pc28li

3 usernames

On this record: Previous handles · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

2,405subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002213157355
TypeChannel
Usernames@aill06 @hpvvvv @ivhhhh
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/pc28li

Previous handles

@pc28li 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.

@pc28li
held 7 August 20267 August 2026

Growth

2,40512,8447,624.57 August 2026 — 2,405 subscribers7 August 2026 — 2,405 subscribers10 August 2026 — 2,407 subscribers11 August 2026 — 2,407 subscribers11 August 2026 — 2,407 subscribers12 August 2026 — 12,844 subscribers13 August 2026 — 10,537 subscribers14 August 2026 — 2,405 subscribers7 August 202614 August 2026
8 measurements spanning 6 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 839–14,410 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 01:082,405-8,132
13 Aug 2026, 18:0810,537-2,307
12 Aug 2026, 18:2312,844+10,437
11 Aug 2026, 09:262,407no change
11 Aug 2026, 08:542,407no change
10 Aug 2026, 16:382,407+2
7 Aug 2026, 20:042,405no change
7 Aug 2026, 17:322,405first reading

Engagement

20 posts held, back to 5 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
33.4%
avg views ÷ 2,405 subscribers
Avg views / post
802
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
7
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (5 May 20267 August 2026)
Views total5,616
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:32 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

7 Aug 2026, 04:04 UTC73 viewsread 7 August 2026

更新了TG代理的套餐组合 缩减了原有商品数量 增加了月付可选50G 100G等套餐 tg内置代理socks5的 速度起飞🛫 体验7天 5G流量 1u🐛 30天 50G流量 6u🐛 30天 100G流量 9u🐛 90天 300G流量 25u🐛 90天500G流量38u🐛 365天 1000G流量 68u🐛 365天3000G流量170u🐛 注意个人独享的 可以3个人使用 速度起飞 自己可以看到自己的ip 别人看不到 不要再使用免费的代理啦 让别人看到你ip 支持安卓 苹果 电脑 都可以使用 滴滴 @cunli

28 Jul 2026, 12:49 UTC702 viewsread 7 August 2026
Photo

闪连vpn 一直有货在卖,不发不代表没货 注意⚠️苹果 安卓 电脑都可以用 可以同时3个设备使用 成品号 账号密码登录 闪连vpn三月会员15uu🐛 闪连vpn年会员33uu🐛 滴滴 @cunli

26 Jul 2026, 14:40 UTC815 viewsread 7 August 2026

https://t.me/nft/LibertyFigure-45678 新出的款式顺子编号礼物 48u卖🐛 用户名都是nft的 @v9ccc 48🐛 @j3ppp 48🐛 @hpvvvv 38🐛 @ivhhhh 38🐛 @ikeeee 38🐛 @z8zzzzzzzzz 28🐛 @a8aaaaaaaaa 28🐛 @b6bbbbbbbbbb 28🐛 @zzkkkkkkkkkkkk 28🐛 联系 @cunli

23 Jul 2026, 12:58 UTC946 viewsread 7 August 2026

10U赠送tg✈️年会员(无售后),抓紧时间,一旦错过就不再来 直接用户名送 滴滴 @cunli

23 Jul 2026, 07:01 UTC939 viewsread 7 August 2026

出租几个888 60u🐛一个月 接码无费用 滴滴 @cunli

19 Jul 2026, 09:49 UTC≈1,170 viewsread 7 August 2026
Photo

闪连vpn 一直有货在卖,不发不代表没货 注意⚠️苹果 安卓 电脑都可以用 可以同时3个设备使用 成品号 账号密码登录 闪连vpn三月会员15uu🐛 闪连vpn年会员33uu🐛 滴滴 @cunli

19 Jun 2026, 16:11 UTC≈1,960 viewsread 7 August 2026
Photo

闪连vpn正常有货 不发不代表没货 3月15u🐛 年35u🐛 闪连vpn支持3个设备使用 注意都是成品号 我给你账号密码登录 滴滴 @cunli

10 Jun 2026, 15:04 UTC≈2,030 viewsread 7 August 2026

三月闪连有那么几个需要的抓紧 滴滴 @cunli

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

Citation-graph rank — 843,012 of 1,189,255entries 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.

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

“马猴的业务频道” (@pc28li), 2,405 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/pc28li.

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.