Telegram RegisterThe public register of Telegram
Telegram profile photo for VIP工作室

Channel

VIP工作室

@VIPgongzuoshi

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

290subscribers

-1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002041309416
TypeChannel
Username@VIPgongzuoshi
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/VIPgongzuoshi

Growth

290291290.56 August 2026 — 291 subscribers6 August 2026 — 291 subscribers14 August 2026 — 290 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net -1. 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 290–291 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 14:37290-1
6 Aug 2026, 23:02291no change
6 Aug 2026, 16:04291first reading

Engagement

13 posts held, back to 9 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
28.2%
avg views ÷ 290 subscribers
Avg views / post
81.7
6 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
6
of 13 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 5 August 2026
Posts held13 (9 June 20265 August 2026)
Views total490
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 23:02 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

5 Aug 2026, 08:37 UTC35 viewsread 6 August 2026
Photo

一手加工📱私人港全✔️纯地推号,留卡25天,可续费 😀无视全球ip,一码直登,丝滑登录 一手加工📱私人美全✔️纯地推号,留卡25天,可续费 😀无视全球ip,一码直登,丝滑登录

Signed viρ(号商)

3 Aug 2026, 05:51 UTC55 viewsread 6 August 2026

美国🇺🇸2-4月(已过验证) 美国🇺🇸半年(已过验证) 售后是:登陆支持马上加5个好友或5个以内 如果聊天做业务死的就没售后当天加五个好友以内死了免费换‼️ 香港流量卡国外网络无视

Signed viρ(号商)

3 Aug 2026, 03:18 UTC58 viewsread 6 August 2026

国卡当天实名白,无限出货中,压多天业务,不是隔天死的那种。包登录。包20分钟爬虫。 留卡3-5天,无视一切一码直登。

Signed viρ(号商)

3 Aug 2026, 03:17 UTC60 viewsread 6 August 2026

非回流 , 纯私人换绑没做过项目的,现在市面90%都是回流数据在便宜卖,大家上号的时候记得问清楚!! 私人地推换绑 1-6个月全实名老号,纯私人地推,不是市面数据回流号,不是私人地推号假一罚十!!! 留卡20-30天 ‼️ 无视ip,无视设备,无视一切,嘎嘎稳定,全网最稳定的号,

Signed viρ(号商)

25 Jul 2026, 17:34 UTC134 viewsread 6 August 2026
Photo

出国卡万粉,全实名,0违规 留卡20-30天,包留卡内找回 可自行换绑 可续费

Signed viρ(号商)

22 Jul 2026, 18:32 UTC148 viewsread 6 August 2026
Photo

抖音千粉万粉十万粉(有货)

Signed viρ(号商)

2 Jul 2026, 16:48 UTC248 views0 reactionsread 6 August 2026
Video

抖音投屏我电脑有货,每天大量无视IP

Signed viρ(号商)

28 Jun 2026, 05:56 UTC244 viewsread 6 August 2026
Photo

土耳其微信有货 已过验证 可以直接加人 包当天加五个人以内死 扫码上号

Signed viρ(号商)

28 Jun 2026, 05:33 UTC208 viewsread 6 August 2026

私人地推换绑 1-6个月全实名老号,纯私人地推,不是市面数据回流号,不是私人地推号假一罚十!!! 重点,绑的是1号1链接的卡,不放其他业务(=最耐用的号+最稳定的卡) 嘎嘎就是干 留卡20-30天 无视ip,无视设备,无视活体,

Signed viρ(号商)

25 Jun 2026, 06:19 UTC209 views0 reactionsread 6 August 2026

私人qq 单太 双太 三太 皇冠 不弹窗不爆红 大量有货

Signed viρ(号商)

17 Jun 2026, 13:40 UTC253 viewsread 6 August 2026
Photo

私人抖音 一码直登 大量有货

Signed viρ(号商)

Showing the 12 most recent of 13 posts we hold for @VIPgongzuoshi. 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 — 796,745 of 1,481,306entries 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

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

“VIP工作室” (@VIPgongzuoshi), 290 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/VIPgongzuoshi.

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.