Telegram RegisterThe public register of Telegram

Channel

Max·冲冲冲

@Max899912

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

833subscribers

+1 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003494110130
TypeChannel
Username@Max899912
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/Max899912

Growth

832833832.58 Aug 2026, 14:45 — 832 subscribers9 Aug 2026, 10:32 — 833 subscribers8 Aug 2026, 14:459 Aug 2026, 10:32
2 measurements taken within a single day, 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 832–833 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 10:32833+1
8 Aug 2026, 14:45832first reading

Engagement

20 posts held, back to 10 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
17.3%
avg views ÷ 833 subscribers
Avg views / post
144
13 posts measured
Reaction rate
0.54%
reactions ÷ views · ER floor
Posts in window
15
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. It is computed over the 5 of 13 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 6 August 2026
Posts held20 (10 July 20266 August 2026)
Views total1,878
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 14:45 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.

Reaction mix

4 reactions across 4 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4100.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 5 of the 20 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 10 July 2026 to 6 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

6 Aug 2026, 01:27 UTC46 viewsread 8 August 2026

😂😂☹️☹️☹️☹️ 😃😃😃😄😃 ➡️高价大量收全渠道高产值色粉 ➡️抖音自热V转 ➡️抖音自热浏览器 ➡️抖音同城热评V ➡️抖音同城热评浏览器 ➡️抖音协议点赞公众号 ➡️抖音热评公众号 ➡️抖音热评浏览器 ➡️快手同城自热V转 ➡️抖音全姿势 ➡️小红书系列 ➡️陌陌全姿势 ➡️探探全姿势 ➡️灵魂全姿势 ➡️色播 楼凤 游戏 ➡️各种小平台 ➡️❗️❗️假粉勿扰❗️❗️ 欢迎各粉商,工作室以及手子跳槽合作,单价+1+2,长期稳定,大力扶持,产值3倍以上单价+3,实力承接,稳定上量,欢迎对接。

6 Aug 2026, 01:07 UTC29 viewsread 8 August 2026

拉稀仔和打假粉鹿羊毛的 不要来了 假粉在我这过不了! 那些拉稀的你们打不了的单子就不要就不要报确定能打的 再来找我开 拿了单子不打有什么意义!

2 Aug 2026, 13:23 UTC128 views1 reactionsread 8 August 2026

高价包养以下姿势 色站浏览器(好站点) 快手定位同城微转 Q附近人 抖音粉丝群系列 快手真人直播 探探附近人头像转 抖音AB转 闲鱼 抖音自热 快手采集 Q站街 灵魂Q码 劫持技术粉 快手语音厅 抖音点赞 V站 抖音截流粉丝群 色播V扫 小红书自热微转 抖音热评美女素材 陌陌动态V转 qq附近人 口信附近人 美团系列 Steam游戏粉 百度关键词贴吧 长期收以上渠道

1

1 Aug 2026, 09:13 UTCviews —

Max·冲冲冲 pinned «😀(包养一手工作室) 抖音自热 抖音橱窗 抖音直播 抖音点赞 抖音粉丝群 😀😀😀😀😀😀😀😀😀😀😀 陌陌拉群 陌陌聊天室 陌陌站街 陌陌纯动态 😀😀😀😀😀😀😀😀😀😀😀 色播浏览器/V转 Q验证 Q站街 😀😀😀😀😀😀😀😀😀😀😀 快手采集 快手语音厅 快手真人直播 😀😀😀😀😀😀😀😀😀😀😀 小红书全系列 积木 探探 灵魂 凤楼 B站自热 百度爬虫 地推 😀😀😀😀😀😀😀😀😀😀😀 游戏粉无限吃 三国杀 无尽冬日 金铲铲 王者营地 😀😀😀😀😀😀😀😀😀😀😀 联系✈️ @Max0881»

1 Aug 2026, 09:09 UTC70 viewsread 8 August 2026

每天晚上八点前截止报单子 临时报不加 除非你的粉非常棒我随时能给你开

1 Aug 2026, 02:47 UTC102 views1 reactionsread 8 August 2026

😀(包养一手工作室) 抖音自热 抖音橱窗 抖音直播 抖音点赞 抖音粉丝群 😀😀😀😀😀😀😀😀😀😀😀 陌陌拉群 陌陌聊天室 陌陌站街 陌陌纯动态 😀😀😀😀😀😀😀😀😀😀😀 色播浏览器/V转 Q验证 Q站街 😀😀😀😀😀😀😀😀😀😀😀 快手采集 快手语音厅 快手真人直播 😀😀😀😀😀😀😀😀😀😀😀 小红书全系列 积木 探探 灵魂 凤楼 B站自热 百度爬虫 地推 😀😀😀😀😀😀😀😀😀😀😀 游戏粉无限吃 三国杀 无尽冬日 金铲铲 王者营地 😀😀😀😀😀😀😀😀😀😀😀 联系✈️ @Max0881

1

25 Jul 2026, 08:57 UTC203 viewsread 8 August 2026

抖音自热V头转 公众号转💗 抖音热评V转,抖音协议点赞,抖音橱窗💗 抖音粉丝群,自热,点赞,热评,直播💗 陌陌拉群,陌陌语音厅,陌陌动态💗 地推浏览器 厕所盖章贴纸 欢迎来咨询

24 Jul 2026, 10:16 UTCviews —

Max·冲冲冲 pinned «长期收购 抖音自热V转 抖音热评V转 抖音点赞V转 抖音粉丝群V转 快手采集V转 快手自热闪V 金铲铲V转 王者荣耀 灵魂系列V转 探探系列V转 小红书自热V转 陌陌动态V转 陌陌动态浏览器 微信站街V转 付费小平台V转 哔哩哔哩V转 @Max0881»

24 Jul 2026, 10:16 UTC231 viewsread 8 August 2026

长期收购 抖音自热V转 抖音热评V转 抖音点赞V转 抖音粉丝群V转 快手采集V转 快手自热闪V 金铲铲V转 王者荣耀 灵魂系列V转 探探系列V转 小红书自热V转 陌陌动态V转 陌陌动态浏览器 微信站街V转 付费小平台V转 哔哩哔哩V转 @Max0881

Showing the 12 most recent of 20 posts we hold for @Max899912. 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 — 877,310 of 1,350,102entries 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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“Max·冲冲冲” (@Max899912), 833 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Max899912.

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.