Channel
@guabc2
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
789subscribers
+593 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002244289383 |
|---|---|
| Type | Channel |
| Username | @guabc2 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 October 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 7 |
| On Telegram | t.me/guabc2 |
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 October 2026 and assigned it the closest of 31 fixed categories, at 39% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 00:23 | 789 | no change |
| 7 Oct 2026, 21:35 | 789 | -2 |
| 26 Sept 2026, 23:39 | 791 | +603 |
| 14 Sept 2026, 11:21 | 188 | -1 |
| 7 Sept 2026, 05:54 | 189 | -6 |
| 29 Aug 2026, 13:17 | 195 | -1 |
| 7 Aug 2026, 12:16 | 196 | first reading |
10 posts held, back to 17 September 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 1 page of 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 28 September 2026 |
|---|---|
| Posts held | 10 (17 September 2026 – 28 September 2026) |
| Views total | 326 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Oct 2026, 00:23 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 9 October 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 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.
皮虾®️精选人设套图素材一直在持续更新最新人设套图 💻请大家持续关注💠频道💠以免上架错过更好的人设套图👨💻祝您天天开大单，财源广进！ 🔴亚洲『女』套图 🟢亚洲『男』套图 🔴欧美『女』套图 🟢欧美『男』套图 🛡『女证件』套图 🛡『男证件』套图 🚨私密『女』套图 🌐 代开飞机会员 📱代洗人设照片 📱各国证件定制 精选三方套图推荐专区 ⏩亚洲女套图 ⏩亚洲男套图 ⏩欧洲女套图 ⏩欧洲男套图 ⏩女证件套图 ⏩男证件套图 😘😘😘😘😘😘😘😘😘 🔹🔹🔹🔹🔹🔹🔹🔹🔹🔹 😊😊😊😊😊😊 😘@guabc 😘 点击进入➡️海外『素材』区⬅️ ➖➖➖➖➖➖➖➖➖➖ 感谢您的关注与支持 🔼请鼠标往上面😊移动，挑选您喜欢的三方套图发编号或者转发给客服😘 @guabc
【编号_ZW #EE74 】 曝光率低，法国年轻女性，职业服装设计师，部分工作和学习的环境素材。自拍视频较多，部分符合虚拟摄像头。 【370照片. 112视频】 #法国＿＿＿需要请联系客服：@guabc
编号 WN_ #VX654 #澳大利亚 #亚裔 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 生日照 宠物 情侣照 比基尼 毕业照 浴缸照 曝光度低 粉丝4000 742张照片 68个视频 (带IG）后期可更新＿＿需要请联系客服：@guabc
欧美MM（53） ZW #MM53 地区∶ #瑞典 价格∶10U 粉丝数量/曝光量∶ 1.6W/低 职业∶暂无特定职业 日常动态∶ ⭐️⭐️⭐️⭐️⭐️ 居家日常∶ ⭐️⭐️⭐️⭐️ （有较多个人自拍照，车内自拍，母亲车内合拍，居家自拍，较少冬季服装，美食照，宠物照，有较少个人自拍视频，聚会视频，看演唱会视频，个人素材丰富。曝光低。 后期根更新可查看IG ） 【照片644 视频30】#瑞典 #带IG可持续更新＿＿需要请联系客服：@guabc
编号 WN_ #25AC134 #精品 证件⭐️ 美国驾驶证 证件⭐️ 美国绿卡 自拍🌟🌟🌟🌟 #美国 黑丝 蕾丝 魅惑 宝妈 生活场景丰富 自拍多 旅游 风景 生活日常 《证件照》 照片950张 视屏58个（带IG）＿＿需要请联系客服：@guabc
编号WN_ #AC113 自拍🌟🌟🌟🌟 #捷克共和国 职业 心理学家 名媛 美女 生活场景丰富 自拍多 旅游 风景 生活日常 照片1901张 暂无视屏（带IG）＿＿需要请联系客服：@guabc
编号 WN #L33 欧洲美女 生活 旅游 605 相片视频 18 个＿＿需要请联系客服：@guabc
编号 WN #kk53 欧美女 日常 生活旅游 633 张照片视频 29 个＿＿需要请联系客服：@guabc
编号 WN_ #VX361 #美国 气质美女 生活场景丰富 自拍多 旅游 时尚会穿搭 美景 闺蜜照 美食 宠物 生日照 毕业照 1952张照片 158个视频 (带IG）后期可更新＿＿.需要请联系客服：@guabc
编号_ZW #mp63 #欧美女 欧美美女，个人自拍照片，车内自拍，敷面膜照，泳装照，朋友合拍，宠物合拍，个人自拍视频，个人素材丰富。 照片937 视频81＿＿＿需要请联系客服：@guabc
Showing the 10 most recent of 10 posts we hold for @guabc2. 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.
Named by 28 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“欧美【女】套图” (@guabc2), 789 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/guabc2.
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.