Telegram RegisterThe public register of Telegram

Channel

YG每日爆奖分享每天抽奖群

@yg46com

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

542subscribers

+7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003713275073
TypeChannel
Username@yg46com
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/yg46com

Growth

535542538.57 Aug 2026, 14:30 — 535 subscribers8 Aug 2026, 03:50 — 535 subscribers8 Aug 2026, 06:46 — 542 subscribers7 Aug 2026, 14:308 Aug 2026, 06:46
3 measurements taken within a single day, net +7. 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 534–543 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 06:46542+7
8 Aug 2026, 03:50535no change
7 Aug 2026, 14:30535first reading

Engagement

6 posts held, back to 7 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
31.0%
avg views ÷ 542 subscribers
Avg views / post
168
5 posts measured
Reaction rate
5.48%
reactions ÷ views · ER floor
Posts in window
6
of 6 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. It is computed over the 4 of 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held6 (7 August 20267 August 2026)
Views total840
Reactions total35
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:50 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.

What this channel posts

Video runtime
12s
Average length
12s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

35 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 80.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2880.0%
💩617.1%
😁12.86%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 4 of the 6 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 35reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 6 most recent posts we hold, published 7 August 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 21:06 UTC122 views11 reactionsread 8 August 2026
Photo

中奖玩家代哦管理员会发信息给你们等待

💩64😁1

7 Aug 2026, 19:01 UTC146 views22 reactionsread 8 August 2026

缅甸时间3点左右抽奖金额38888元12位幸运玩家

22

7 Aug 2026, 17:42 UTC164 views1 reactionsread 8 August 2026
Photo

🔥【YG顶级娱乐城】活动火热来袭!🔥 🎁豪礼天天领不停!🎁 1️⃣ 新会员首存 ➠ 120% 专享 🧧 2️⃣ 每日首存 ➠ 10% 稳定回馈 🧧 3️⃣ 救援金 ➠ 最高 5800000 🤑 4️⃣ VIP晋级彩金 ➠ 越玩越尊贵 5️⃣ 签到彩金 ➠ 天天签到天天领 🧧

1

7 Aug 2026, 16:21 UTC207 views1 reactionsread 8 August 2026
Photo

🔥【YG顶级娱乐城】活动火热来袭!🔥 🚀超热榜单推荐,进来闭眼选,闭眼赢!🚀 WG:麻将湖2 WD:金钱兔2 PG:金钱兔 PG:宝石热气球 PP:奥林匹斯之门 PG:沙皇宝藏 PG:赏金大对决 PG:墨西哥狂欢 PG:阿努比斯 PG:鼠鼠福福 JDB:马上有钱 JDB:金刚 CP:神枪手 CP:财富熊猫 JlLl:幸运金币 JlLl:迦罗宝石 JlLl:超级王牌 JlLl:开心捕鱼 JlLl:财神彩金 YB:金钱兔 全球人气最高、最让人放心的娱乐首选,YG就是你的家!🎉🎉 天天爆大奖,实力看得见。赶紧点开图片,挑选你喜欢的上。家人们,冲冲冲!🤣🤣

1

7 Aug 2026, 14:38 UTC201 viewsread 8 August 2026
Photo

🔥【YG顶级娱乐城】活动火热来袭!🔥 PG 麻将胡了 ⚡️⚡️⚡️ 恭喜大哥!惊喜不断,天天都有好收获! 跟着 YG平台 就是稳🎉🎉🎉 超多新款热门游戏啦! 根本不用到处找,看图就可以玩到你想玩的游戏拉 🎉😉😙🙂😉 😀😀😀😀😀😀

Showing the 6 most recent of 6 posts we hold for @yg46com. 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 — 320,568 of 1,160,990entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

“YG每日爆奖分享每天抽奖群” (@yg46com), 542 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/yg46com.

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.