Channel
@Fanhua333
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,701subscribers
-63 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004410354796 |
|---|---|
| Type | Channel |
| Username | @Fanhua333 |
| Created | Between 1 June 2026 and 12 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/Fanhua333 |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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 |
|---|---|---|
| 16 Sept 2026, 06:41 | 1,701 | +6 |
| 12 Sept 2026, 20:19 | 1,695 | +5 |
| 9 Sept 2026, 03:54 | 1,690 | -9 |
| 4 Sept 2026, 03:21 | 1,699 | -17 |
| 1 Sept 2026, 02:15 | 1,716 | -22 |
| 29 Aug 2026, 07:16 | 1,738 | -39 |
| 26 Aug 2026, 09:03 | 1,777 | +1 |
| 23 Aug 2026, 05:03 | 1,776 | +1 |
| 19 Aug 2026, 16:36 | 1,775 | +2 |
| 16 Aug 2026, 08:56 | 1,773 | +9 |
| 13 Aug 2026, 03:04 | 1,764 | no change |
| 12 Aug 2026, 23:17 | 1,764 | first reading |
5 posts held, back to 12 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 5 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
🪽 点击查询视频 昵称：桃子BB147 省份：广东 城市：广州 年龄︃：23͏ 身︄高︁：164 体︆重：93͏ 罩︈杯：B 职业︂：学生︀͏ 雷︍点（不能︎接受︊）:无︀ 是︄否︍chu女︂：否︄͏ 例假日期：月︀底︄͏ 体检︋后︂是否接︀受︉🈚️tao：否 可否︃kou：可︊͏ 可︍否过夜：可͏ 可︌否︎同️居：可︉͏ 可︁否︆异︉地︅：可 可︎否飞外︊省︊：可️ 能︌否︌接受sm: 否 每月︁可︂陪伴︌天数：3͏ 宝︆宝️期望︌生︊活︌费：1w͏ 生︍活︋费︅可︂否︃粉︁2-3次︆支付：2次︋͏ 如果️匹︂配上︃最︌快出︈发时️间︁：当︎天︎ 见︆面︄双方满︅意︌后︅可︃否开f：可︉ 短︁期️三︋天费︋用：1w 可︅否接受︉港︋澳︃伴游︉：否︋͏ 自︈我加︂分︎项️【越︊详…
🪽 点击查询视频 省份： 山东 城市： 廊坊 年龄：23 身高: 166 体重: 108 罩杯: B 职业：餐饮 是否chu: 否 能否口：可 能否SM:可 能否无套:可 能否内射：否 能否过夜：可 能否同居：可 有没有纹身：无 可否飞外省：近一点城市可 大姨妈日期：13号左右 每月陪伴天数：一千五陪一天，两千三白天➕过夜的 分几次支付零花钱：1-2 找金主的原因：缺米 最早出发时间：提前一天通知 加分项：活好，下面水多，主要卫生，情绪价值高 介绍费：7888 七七2 编号: 2026081203245 🌸包养联络专员：@huaer530 🌸私信双向限制：@Huaer028_bot 👉外围合作单位 🛎〖繁花🌸〗交流群 认准〖繁花🌸〗所有交易走担保，交易无忧，售后无忧（看清私聊 注意甄别骗子）
🪽 点击查询视频 昵称：lyq524 省份：江苏 城市：苏州 职业: 上班 年龄：25 身高：155 体重：94 罩杯：b 是否Chu女: 否 是否接受SM: 否 金主体检后是否接受无t: 否 是否接受内: 否 是否接受口: 是 是否接受同居: 否 是否接受过夜: 是 是否接受外地: 是 每月姨妈时间及天数: 月中下旬 绝对禁忌的事项: 不讲卫生 对金主的要求: 不用太胖，人好就行 找金主的原因: 缺钱 对恋爱费用的预期: 3天4000 / 5天5500 恋爱费分次支付能否接受: 接受 每个月可陪伴的天数: 3-5天 自我评价: 有谈吐端庄得体 细心 温柔 贤惠 私生活健康 靠谱 介绍费: 7888 lyq as 编号: 2026081203244 🌸包养联络专员：@huaer530 🌸私信双向限制：@Huaer028_bot 👉外围合作单位 🛎〖繁花🌸〗交流群 认准〖繁花🌸〗所有交易走担保，交易无忧，售后…
🪽 点击查询视频 省份： 长沙 城市： 长沙 年龄：18 身高: 166 体重: 94 罩杯: b 职业：无 是否chu: 否 能否口：可 能否SM:可 能否无套:可 能否内射：可 能否过夜：可 能否同居：可 有没有纹身：无 可否飞外省：否 大姨妈日期：不固定 每月陪伴天数：五天/8k，满月/2w 分几次支付零花钱：1-2 找金主的原因：缺钱，提高生活水平 最早出发时间：提前一天通知 加分项：懂事，配合度高，情绪价值高 介绍费：7888 满月：12888 七七2 编号: 2026081203243 🌸包养联络专员：@huaer530 🌸私信双向限制：@Huaer028_bot 👉外围合作单位 🛎〖繁花🌸〗交流群 认准〖繁花🌸〗所有交易走担保，交易无忧，售后无忧（看清私聊 注意甄别骗子）
🪽 点击查询视频 昵称：YC142 省份:广东 城市:深圳 年︉龄︉:23 身︊高︎:165͏ 体︁重:100 罩︊杯︉:36D 职业: 是否︂chu女︍：否 可︉不可以︀口:可以︄͏͏ 能不︇能内︄S:不︈͏ 能︌不能︊无T:不 能否接受︂SM：͏ 有︄没︋有纹︁身:没︁有︉͏ 是否可︇外省:可以 是︆否️可︂过夜:可以 可︋不️可以︇同居:可以︍ 月︃可︆陪伴天️数︈:3͏͏ 大概︈姨︎妈︎日期︈:͏ 月︍生️活费多少︇:1.8 分几次给︀生活︌费:2次︀͏ 自我介︅绍加分项: 对︋老︄板️雷点︌(不接受)：͏͏ 介绍费：7888yc 编号: 2026081203242 🌸包养联络专员：@huaer530 🌸私信双向限制：@Huaer028_bot 👉外围合作单位 🛎〖繁花🌸〗交流群 认准…
Showing the 5 most recent of 5 posts we hold for @Fanhua333. 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 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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“〖繁花🌸〗全国包养” (@Fanhua333), 1,701 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Fanhua333.
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.