Telegram RegisterThe public register of Telegram

Channel

国内洋酒之杭城

@ymBOSS22

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

554subscribers

+36 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-1001952335098
TypeChannel
Username@ymBOSS22
Description洋酒日本,英国,俄罗斯,新疆,法国
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
On Telegramt.me/ymBOSS22

Growth

5185545367 Aug 2026, 18:51 — 518 subscribers8 Aug 2026, 02:50 — 554 subscribers8 Aug 2026, 03:36 — 554 subscribers7 Aug 2026, 18:518 Aug 2026, 03:36
3 measurements taken within a single day, net +36. 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 513–559 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 03:36554no change
8 Aug 2026, 02:50554+36
7 Aug 2026, 18:51518first reading

Engagement

6 posts held, back to 31 July 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
59.9%
avg views ÷ 554 subscribers
Avg views / post
332
5 posts measured
Reaction rate
0.404%
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 2 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 (31 July 20267 August 2026)
Views total1,659
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:36 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

Photos
581
Videos
160
Links
10

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
32s
Average length
11s

Measured directly from 3 videos 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

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.0%

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 2 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 2reactions 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 31 July 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, 15:18 UTC239 views1 reactionsread 8 August 2026
Photo

来自新加坡🇸🇬 身高163👆🏻体重47💃 38真E🐻 22岁💯 全程英文沟通👍 特殊服務:🈚️T做+2张、🉑双🐉‼️ 可配合项目:🐍💋、🈚️T口、6️⃣9️⃣、🐻🏊、鸳鸯浴🛀 已健检完成 保证健康✅ 💥💥💥今日特价-1800/p 💥💥💥今日特价-3ooo/pp 💎杭州上城三新家园 😃😃😃😃😃😃😃😃😃😃 咨询联系安排🌸电报 @sz007xx

1

7 Aug 2026, 15:18 UTC235 viewsread 8 August 2026
Photo

韩国🇰🇷 身高1米75👆🏻体重48💃30D🐻22岁💯🉑全程韩文,英文沟通✅ 可配合项目:💋吻、🈚️T口、6️⃣9️⃣、🐻🏊、鸳鸯浴🛀 🉑🈚套 ➕200 已健检完成 保证健康✅ 💥💥💥今日特价-1800/p 💥💥💥今日特价-3ooo/pp 💎杭州上城三新家园 😃😃😃😃😃😃😃😃😃😃 咨询联系安排🌸电报 @sz007xx

7 Aug 2026, 13:28 UTC256 views1 reactionsread 8 August 2026
Photo

🎰 香奈儿洋酒 @xnr8888 优惠福利抽奖 📮 抽奖条件: 🎫 加入-杭州Alex的大奶认证榜单 🎫 加入-杭州Alex教你123 🎫 加入-杭州Alex的小视频 🎫 加入-杭州Alex的大奶新人榜单 🎫 加入-国内洋酒之杭城 🎁 奖品内容: 洋酒200抵扣卷 × 20 大圈500抵扣卷 × 30 💡 活动说明: 5天内兑奖,炸号超时名额作废 📅 开奖日期:(UTC+8) 2026年08月10日 05时45分21秒

1

6 Aug 2026, 17:52 UTC282 viewsread 8 August 2026

😃😃😃😃😃😃😃 📴🉐㊗️📳杭州大圈单独相册 👉点进去http://www.quvn9.shop/ 密码:222666 ㊙️㊙️🆘🆑上海大圈单独相册 👉点进去https://sw69wt.cc 密码:202608 薇薇✈️: @sz007xx 在线😀:2231469223 😀所有妹子教室位置已标明 各区,空姐,网红,老师,学生妹小萝莉看好截图发我安排或者找客服推荐 【全国一二线部分三线城市,私信要资源】 👍目前开通,北京 上海 广州 深圳 杭州 苏州 南京 成都 重庆 长沙 台州 温州 嘉兴 西安 乌鲁木齐 青岛 大连

31 Jul 2026, 18:32 UTC647 viewsread 8 August 2026
Photo

🇯🇵若月凉子 本人照片 年龄22岁 身高 167 体重45,纯日本人性价比高 胸围 B+(无科技)皮肤冷白皮 💥💥💥💥今日特价-2.1k/1p 💥💥💥💥今日特价-4k/2p 💥💥今日特价-8k/叶随便玩 不限次数 💎 #杭州市拱墅区🉑️上门有地方 ➖➖➖➖➖➖➖➖➖➖➖ 👍电报: @sz007xx 🛍做我的客户❤️余生我宠你

Showing the 6 most recent of 6 posts we hold for @ymBOSS22. 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 — 293,329 of 1,151,006entries 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 3 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.

“国内洋酒之杭城” (@ymBOSS22), 554 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ymBOSS22.

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.