小柴

Channel
富豪评价
@szdfw3
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
5,176subscribers
+2,725 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003943230813 |
|---|---|
| Type | Channel |
| Username | @szdfw3 |
| Created | 16 August 2026 — measured — dated from the channel’s first post |
| First recorded | 26 August 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 24 October 2026 |
| On Telegram | t.me/szdfw3 |
Topic
Other / unclassifiable — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Oct 2026, 05:50 | 5,176 | -144 |
| 21 Oct 2026, 09:46 | 5,320 | -191 |
| 18 Oct 2026, 04:50 | 5,511 | -111 |
| 14 Oct 2026, 21:29 | 5,622 | -177 |
| 11 Oct 2026, 15:18 | 5,799 | -213 |
| 5 Oct 2026, 07:36 | 6,012 | +42 |
| 26 Sept 2026, 14:01 | 5,970 | +237 |
| 17 Sept 2026, 07:01 | 5,733 | +276 |
| 13 Sept 2026, 17:39 | 5,457 | +87 |
| 10 Sept 2026, 04:37 | 5,370 | +437 |
| 5 Sept 2026, 00:21 | 4,933 | +482 |
| 1 Sept 2026, 05:47 | 4,451 | +757 |
| 29 Aug 2026, 05:51 | 3,694 | +1,241 |
| 26 Aug 2026, 03:53 | 2,453 | +2 |
| 26 Aug 2026, 00:00 | 2,451 | no change |
| 25 Aug 2026, 23:45 | 2,451 | first reading |
Engagement
3 posts held, back to 16 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 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 3 posts for this entry, the most recent from 24 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
【工兵报告】 https://t.me/szdfw 【老师艺名】 【联系方式】 【所在位置】 【验证留名】 【验证时间】 【修车费用】 【颜值身材】 【服务内容】 【服务态度】 【优点缺点】 【推荐程度】 【体验细节】 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 报告提交机器人:@feichaiyabot 报告提交条件:需要提供约课记录及付款记录验证
Channel created
Showing the 3 most recent of 3 posts we hold for @szdfw3. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 59 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.
@lotterynav · 188,296166 posts坂田雨馨
@jzojebe1 · 1,1052 posts小九儿 ,后花园💋💋
@xbzn97 · 4662 posts龙华朵朵个人
@a83253255 · 2201 post南山文静个人频道
@asdp6613 · 2621 post冰🧊兒🉐三芊👨🏻宠🏠
@bingerlh452 · 5651 post可可解忧小屋🏡
@httpdkttk · 891 post坂田金莲潮喷女王深圳特服天花板
@JLszban · 2841 post1
@kekecc68 · 3781 post宝安 乐乐(大一新生兼职)
@loulou355 · 2621 post米线的日常⭕
@missfh_4679 · 1941 post矜矜的奇妙圈
@nsjinjin05 · 1951 post绮梦 情人小屋(ootd)
@ootdqi77 · 4461 post妙妙的奇妙小屋🏠
@Qmiaomiao520 · 2381 post兔熊小房子
@tuxiong5566 · 2931 post招财进宝
@tyuiendnku · 3291 post深圳骆骆公主(洛丽塔开课)
@wwwii3333 · 1,5001 post西丽小汐个人频道
@xiaoxi777888 · 841 post深圳福田月月的小破屋
@xiaoyy88 · 9781 post欣欣频道
@xinxinxfc · 2611 post小玉空间
@Xioauusl · 3571 post南山 08年嫩妹 诗诗
@yhaoyunlianlianpd · 6651 post依依宝贝后花园
@yiyibaobeb · 1,1461 post知恩的朋友圈
@zhienbao66 · 1,0631 post
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.
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 24 October 2026 — this entry's latest reading, not the date you are reading this.
“富豪评价” (@szdfw3), 5,176 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/szdfw3.
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.