Channel
@sucaiv88
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
41,983subscribers
-373 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1003587285436 |
|---|---|
| Type | Channel |
| Username | @sucaiv88 |
| Description | 素材包装p图绘画套图 |
| Created | Between 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/sucaiv88 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 16:34 | 41,983 | -10 |
| 11 Aug 2026, 15:03 | 41,993 | -2 |
| 10 Aug 2026, 17:44 | 41,995 | -233 |
| 9 Aug 2026, 19:03 | 42,228 | -72 |
| 8 Aug 2026, 19:23 | 42,300 | -45 |
| 7 Aug 2026, 16:26 | 42,345 | -11 |
| 6 Aug 2026, 19:46 | 42,356 | first reading |
13 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 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 | 13 (5 August 2026 – 11 August 2026) |
| Views total | 630 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 20:20 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.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 6 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.
😉疯狗人设套图素材业务如下：点击下面蓝色字体跳转 🤩{新}亚洲女性套图 🤩{新}亚洲男性套图 🤩{新}欧洲女性套图 🤩{新}欧洲男性套图 🤩{新}私密女性套图 🤩【代写】人设资料 😝疯狗工作室：点击下面蓝色字体跳转 😝【疯狗】午夜福利群 😝 【AI】智能问答 😛【代洗】人物照片 😛【商务】广告推广 😛【 P图 】做图软件 😛【能 量】TRX兑换 金主广告位展示🚩点击下面蓝色字体跳转 🚩绘画素描 🤭 专属打造新型吸金模式 🚩证件p图 🤭 美工设计 实物证件可邮寄 🚩AI建模 🤭 AI建模变声 实时变脸 🚩海外账号 🤭 大黄蜂 苹果ID 有缘 巴豆等 关注东南亚实时新闻 @dongnanyaxinwen88 😛客服：@UXXOL 😌双向客服 ：@fenggou1_bot 支付方式：😞😆🤯😫😆😢😗🙂↕️😘 😌关注东
藏在山林里的小院🏡 脚下溪水潺潺流淌 柴火土灶慢炖一锅土鸡汤 吃的就是原生态的本味 远离喧嚣，感受山野烟火✨ #山间小院 #柴火炖土鸡 #林下散养土鸡 #农家烟火气 #山野打卡地
Posted without readable text
很舒服 太安逸了，在峡湾这里看看山，看看水 今晚住在沃斯，在湖边走走吹吹风，感觉人都升华了 #挪威#峡湾 #北欧 #旅行 #享受舒适生活@liaoku
Photo, posted without a caption
人类何德何能，竟获大自然如此眷顾？赐予我们蔚蓝天空、浩瀚海洋、金黄麦田，以及蝉鸣与微风。#京都 #被好风景收买的一天 #永远喜欢大自然的生命力 #海边
😉疯狗人设套图素材业务如下：点击下面蓝色字体跳转 🤩{新}亚洲女性套图 🤩{新}亚洲男性套图 🤩{新}欧洲女性套图 🤩{新}欧洲男性套图 🤩{新}私密女性套图 🤩【代写】人设资料 😝疯狗工作室：点击下面蓝色字体跳转 😝【疯狗】午夜福利群 😝 【AI】智能问答 😛【代洗】人物照片 😛【商务】广告推广 😛【 P图 】做图软件 😛【能 量】TRX兑换 金主广告位展示🚩点击下面蓝色字体跳转 🚩绘画素描 🤭 专属打造新型吸金模式 🚩证件p图 🤭 美工设计 实物证件可邮寄 🚩AI建模 🤭 AI建模变声 实时变脸 🚩海外账号 🤭 大黄蜂 苹果ID 有缘 巴豆等 关注东南亚实时新闻 @dongnanyaxinwen88 😛客服：@UXXOL 😌双向客服 ：@fenggou1_bot 支付方式：😞😆🤯😫😆😢😗🙂↕️😘 😌关注东
#宅家 #做饭
#宅家 #做饭 啤酒鸭，肉末茄子，红薯叶。
#宅家 #做饭 蒸鸡腿，豆芽炒鸡蛋，青菜，煎鱼，家庭版咕噜肉，水蒸蛋，清炒西兰花。
#宅家 #做饭
#家常菜 #宅家 #做饭
Showing the 12 most recent of 13 posts we hold for @sucaiv88. 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 — 287,738 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.
Named by 15 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“素材包装p图绘画套图” (@sucaiv88), 41,983 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/sucaiv88.
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.