Channel
@axxoxoco
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
5,598subscribers
-59 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001446425703 |
|---|---|
| Type | Channel |
| Username | @axxoxoco |
| Created | Between 1 April 2019 and 31 October 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/axxoxoco |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 14:13 | 5,598 | -11 |
| 24 Aug 2026, 14:53 | 5,609 | -2 |
| 20 Aug 2026, 15:55 | 5,611 | -6 |
| 17 Aug 2026, 14:54 | 5,617 | -15 |
| 14 Aug 2026, 15:45 | 5,632 | -9 |
| 10 Aug 2026, 20:47 | 5,641 | -14 |
| 8 Aug 2026, 04:38 | 5,655 | -2 |
| 7 Aug 2026, 17:16 | 5,657 | first reading |
12 posts held, back to 12 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 12 (12 September 2025 – 11 August 2026) |
| Views total | 51 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 05:10 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.
☢️☣️📴📳🈶🈚️🈸🈺🈷️✴️🆚💮 好博体育超多游戏，给玩家带来更全面的游戏体验 😳😳😳😳😳😳😳😳😳😳 1️⃣、天选之子单笔出款210W，查看战绩 2️⃣、麻将两千倍爆奖，查看战绩 3️⃣、返水8块爆3600元，查看战绩 4️⃣、西港盘总来收割麻将胡了两天57万U恭喜大哥，查看战绩 😛😜🤪🤨😒🤓 🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰 #雪中送炭不如锦上添花 🤢 首存200送58 🤢 首存500送108 🤢 首存1000送158+88 🤢 首存3000送388+88 🤢 首存5000送528+158 🤢 首存10000送888+125 🤢 首存20000送1188+888 🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰 😄😄😄😄😄😄😃😀😀😀😀😀😀😀😀 🇩🇪 体育推单: @lanhuo98 😳 赌王之王: @PGlllllllll 🇫🇷 电竞推单…
*FIFA世界杯2026(在加拿大&墨西哥&美国) 墨西哥 vs 南非 (12/06 03:00) 小(2/2.5) @ 1.98 *FIFA世界杯2026(在加拿大&墨西哥&美国) 韩国 vs 捷克 (12/06 10:00) 韩国(0) @ 1.92❤️ 📱📱📱📱📱📱📱📱📱 📱📱📱📱📱📱 注册链接：http://www.xk4430.com 🐭注册下载App即送特邀1⃣9⃣0⃣彩金！ 彩金申请：@feihg
https://t.me/xoxoxocn
每日自拍【 反差曝光】 pinned Deleted message
#母狗 #反差 #推特 推特母狗福利姬【夏美酱】多人群P 满身淫文 极致的骚逼 好像没有见过鸡巴一样#母狗 #反差 #推特 #评论区查看
#少女 #学生 #黑丝 #白虎 #自慰 烏黑秀發甜美小姐姐,誘惑高透視黑絲大長腿,沐洱大開,粉肉芽探出洞口 #评论区查看
#母狗 #反差 #曝光 吉林网友投稿前女友小个子契约兽【WL妍】分手后不让操了 原因是找到了新男友 据网友说找到新欢之前还能操 现在大门不再向他敞开 要让现任看看她以前的模样 非常反差 骚的不行 #评论区查看
#母狗 #反差 #淫妻 广东反差骚逼淫妻【ViViqinglv】穿着职业装黑丝被带出去3P 前后夹击 老公在旁边更兴奋了 #评论区查看
#少妇 #女神 #国产 #大奶 短發氣質女神,身材很好,該有肉的有肉,該瘦的瘦,車燈亮,水箱足 #评论区查看
#母狗 #反差 #纹身 Onlyfans驴脸纹身骚母狗【路奈】 发骚自拍视图 #评论区查看
#母狗 #反差 #颜值 舞蹈系反差高颜值母狗大学生【刘子群】 被短鸡巴男友调教成骚母畜 往头上撒尿 深喉 舔脚 舔屁眼 肛交 #评论区查看看
#母狗 #反差 #穿刺 推特高颜值重度SM博主【是丫头呀】 青春的外表下深藏着一颗狂躁的心 乳头穿刺疯狂开发 #评论区查看
Showing the 12 most recent of 12 posts we hold for @axxoxoco. 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 — 736,164 of 1,624,174entries 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@axxoxoco named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“每日自拍【 反差曝光】” (@axxoxoco), 5,598 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/axxoxoco.
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.