Telegram RegisterThe public register of Telegram

Channel

胡歌🐠出货频道

@v_huge

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

3,234subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1001705819152
TypeChannel
Username@v_huge
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/v_huge

Growth

3,23413 Aug 2026, 07:01 — 3,234 subscribers13 Aug 2026, 15:06 — 3,234 subscribers13 Aug 2026, 07:0113 Aug 2026, 15:06
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”. The vertical axis spans 3,231–3,237 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 15:063,234no change
13 Aug 2026, 07:013,234first reading

Engagement

16 posts held, back to 11 August 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
0.674%
avg views ÷ 3,234 subscribers
Avg views / post
21.8
16 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
16
of 16 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 13 August 2026
Posts held16 (11 August 202613 August 2026)
Views total349
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 07:01 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

13 Aug 2026, 02:20 UTC8 viewsread 13 August 2026

💋 H5小程序/公众号/服务号/teams/云客服/腾讯企点/企业微信 @i_huge

13 Aug 2026, 02:02 UTC9 viewsread 13 August 2026

😅企业绿标 出货 微希旭贸易有限公司。 三亚 逡兮贸易有限公司。 江西 服励商贸有限公司。 广州 挥堪贸易有限公司。 三亚 泽正贸易有限公司。 云南 获客已经通过 可绑定知客和芝麻账号直接上号‼️

13 Aug 2026, 01:46 UTC11 viewsread 13 August 2026

😀😀微博全系列 私人十年老号阳光信用420-450 私人十年老号阳光信用450-570 私人十年老号阳光信用570-599 私人十年老号阳光信用600-619 私人十年老号阳光信用620-650 私人十年老号阳光信用650-690 私人十年老号阳光信用690-900 私人十年 财经黄V 信用450-570 私人 足球赛事黄V 信用450-570 绝版微博达人老号 绝版微博兔女郎老号 微博黄V认证老号【认证随机 】 微博蓝V认证老号【认证随机 】 卡密+飞机机器人自助登录。 所有号都是冷了一年以上的 会员可代开 ‼️

13 Aug 2026, 01:30 UTC13 viewsread 13 August 2026

😏😏 钉钉地推私人老号,私人高级认证老号,需要的来,质量硬,直接转移vm云机,川川云,一手批发,来跑量代理,大量接预订。售后:包7天找回 钉钉地推3月 半年 扫码真机登陆 报客户ip扫码上号 https://shouji.vmos.cn/

12 Aug 2026, 14:35 UTC21 viewsread 13 August 2026

😏钉钉地推私人老号年号现货30+,需要的来,质量硬,直接转移vmos云机 扫码和谐上不去了

12 Aug 2026, 10:13 UTC21 viewsread 13 August 2026

😀缅甸私人微信 满月 25u 三月 35u 半年 47u 一年 65u 两年 70u 扫码登陆 包秒

12 Aug 2026, 08:55 UTC25 viewsread 13 August 2026
Photo

😀 红薯 私人国卡新老号随机 7天内包核对 😀 代sm 7天内包核对 免费升级专业号 秒开不挤号 😀 私人🐟号开工,每天100+ 纯私人 学生号 近期使用的号,带使用痕迹,发作品自热 截流 耐用 😀小红书实卡链接接码 @i_huge

12 Aug 2026, 06:19 UTC27 viewsread 13 August 2026

⚠️机房通知: 😀所有黑龙江103链接涉炸要下卡! 给一天时间换绑! 要用的号尽快换绑! 这个链接 http://103.80.27.8:2025/dxdx/dxyonghudx.php?p

12 Aug 2026, 06:11 UTC25 viewsread 13 August 2026

皓娴霁贸易公司。 文昌 深愿伴贸易公司。 海口 获客已经通过

12 Aug 2026, 03:33 UTC27 viewsread 13 August 2026

😍注册接码 小红书实卡接码带链接 余卡 300+ 陌陌实卡接码带链接 余卡500+ 企业微信首次 200+ 其它APP 带链接都有欢迎咨询,量大优惠 @i_huge

Showing the 12 most recent of 16 posts we hold for @v_huge. 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 — 996,969 of 1,345,403entries 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 4 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.

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

“胡歌🐠出货频道” (@v_huge), 3,234 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/v_huge.

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.