Channel
@www350525
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,156subscribers
-29 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002926863786 |
|---|---|
| Type | Channel |
| Username | @www350525 |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/www350525 |
Giveaways & airdrops — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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 |
|---|---|---|
| 18 Sept 2026, 03:55 | 1,156 | -12 |
| 13 Sept 2026, 21:00 | 1,168 | -7 |
| 10 Sept 2026, 09:57 | 1,175 | -9 |
| 4 Sept 2026, 22:58 | 1,184 | -20 |
| 1 Sept 2026, 07:05 | 1,204 | -17 |
| 29 Aug 2026, 03:57 | 1,221 | -14 |
| 26 Aug 2026, 08:02 | 1,235 | -13 |
| 23 Aug 2026, 09:36 | 1,248 | -28 |
| 19 Aug 2026, 10:18 | 1,276 | -8 |
| 16 Aug 2026, 06:13 | 1,284 | -4 |
| 12 Aug 2026, 20:48 | 1,288 | +50 |
| 9 Aug 2026, 19:21 | 1,238 | +53 |
| 9 Aug 2026, 13:15 | 1,185 | no change |
| 9 Aug 2026, 13:03 | 1,185 | first reading |
20 posts held, back to 25 July 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 3 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 1 reactions 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 25 July 2026 to 9 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.
🎉 联邦～禅城然然💃🏻福利抽奖🎰 🎁 奖品清单 • 1p半价券 × 1 • 通用券100 × 5 📢 参与条件 • 加入 广州佛山联邦出击群（重生版） • 加入 广州佛山联邦老师榜 • 加入 广州佛山邦女郎动态榜 • 加入 广州佛山联邦老师打卡群 • 加入 广州佛山联邦抽奖榜 • 加入 然然的后宫 ⌛ 开奖时间 • 2026-08-11 20:00:00 📜 抽奖说明 然然：https://t.me/Gzffol/40889 1，本活动由然然老师赞助,私聊 @jxj8288 兑奖。 2，开奖后请老师七天内兑券，转让需老师同意。 3，中半价券先拉黑抽奖30天，出击交报告即解。 ✨ 愿好运常伴大家，祝大家好运！点击下方按钮参与抽奖。
只有两个名额
今天给宝宝们放波福利噢 先来心得
群内有免费白嫖劵，五折工兵劵，更有聊天挖宝活动，各种现金口令红包 广佛高质量狼友交流群组：https://t.me/+d2VfZXpstac2OGE1 广州佛山公开榜群组：https://t.me/GuangzhouCBy 广州佛山报告群组：https://t.me/guangzhou1728 投诉建议上榜联系：@bbca12
#联邦报告 <https://telegram.me/gzafua> 【出击留名】：ppss 【出击时间】：2026年8月9日 【老师艺名】：#然然 【联系方式】：@jxj8288 【开课位置】：#禅城 【上课费用】：700 【颜值身材】：身材苗条 【身高体重】：163 48gk 【胸杯紧度】：b+ 【老师类型】：#嫩妹 【服务种类】：舌吻、69、洗吹做 【情绪态度】：热情 【优点缺点】： ①缺点：没有缺点 ②优点：嫩、三点粉 【自由描述】：看频道老师今天开课就约了，老师的安全意识还是很强，一步步按老师指引到课室，老师是嫩妹型，身材高，气质佳，老师胸也挺大，老师洗澡都挺认真的，下面已是顶天柱，床上舌吻，漫游，口一套下来，带套直入，正面传教式，后入，斜入，老师已经满面红光，老师说太猛了，最后拥抱传教式，一会吸着奶头，一会蛇到窒息，在我不断进攻下出货，全身放松，很满意 自由发挥，尽量写得客观点，可详细点，太短无法给人参考。 如不知道…
头课哟、有没有宝宝过来头炮的呀🥰
开课啦
下课了，宝宝们下午两点见哟
还有空位噢
开课了宝宝们🈳🈳
下课啦宝宝们
广州佛山报告： https://t.me/+d2VfZXpstac2OGE1 【妹子花名】：然然 【验证留名】：匿名 【验证时间】：8.7 【所在位置】：禅城 【颜值评分】：8 【身材评分】：9 【服务评分】：9 【优点缺点】：真嫩妹，三点粉，缺点广州过去距离有点远 【推荐程度】：9 【个人发挥】：安排好时间到达战场！课室选在附近地铁口，步行1分钟，酒店公寓，位置挺隐秘的，隔音一般，然然本地陀地，酮体很白，奶头粉嫩，奶奶比较软.乳摇的厉害！身上无赘肉，颜值中上，身体有一层少女绒毛，一股荷尔蒙的味道！BB好看，一看最近没咋做爱. 优点：前后陪洗，可以一直口，不催，姿势配合度较高，我换了六七个姿势都没有不难烦！酮体干净整洁，毛毛不是很多，挺能聊的！又紧又嫩，还挺敏感～吃下面，能蛇，耐桩度一般，课表上有的都能做自聊！ 正片开始： 上楼开门，人照八分，胸部隆起，小腹平坦，面带微笑！有种莫名的熟悉感感觉，闲聊几句，得知是本地陀地，宽…
❤1
Showing the 12 most recent of 20 posts we hold for @www350525. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 2 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“萧萧” (@www350525), 1,156 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/www350525.
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.