“景色不同路相同 I'm still going on” “我要去西藏 我要去拉萨” “撵起了理想 My life is a drama 许多人避让 因为我按响了喇叭” “那天我忽然和风玩起了追逐”

Channel
骄傲放纵小天地
@jiaoaofangzong
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,140subscribers
+146 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003945570263 |
|---|---|
| Type | Channel |
| Username | @jiaoaofangzong |
| Created | Between 1 April 2026 and 12 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/jiaoaofangzong |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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 |
|---|---|---|
| 18 Sept 2026, 03:19 | 1,140 | +31 |
| 13 Sept 2026, 11:58 | 1,109 | -4 |
| 9 Sept 2026, 06:22 | 1,113 | +11 |
| 4 Sept 2026, 06:20 | 1,102 | +13 |
| 31 Aug 2026, 23:18 | 1,089 | +1 |
| 28 Aug 2026, 13:23 | 1,088 | +10 |
| 25 Aug 2026, 02:35 | 1,078 | +26 |
| 21 Aug 2026, 14:48 | 1,052 | +19 |
| 18 Aug 2026, 21:54 | 1,033 | +32 |
| 15 Aug 2026, 17:23 | 1,001 | +7 |
| 14 Aug 2026, 19:30 | 994 | no change |
| 14 Aug 2026, 19:25 | 994 | first reading |
Engagement
8 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 8 posts for this entry, the most recent from 14 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 9s
- Average length
- 9s
Measured directly from 1 video 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.
Reaction mix
3 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 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 8 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 12 August 2026 to 14 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.
Recent posts
你就是你,我就是我,她不是她。 相逢何必曾相识...... 朋友圈导航
这个别是丽丽,不是我😅 不过欢迎i霜去冲他🤣 我再蠢也不会搞这么像的小号😎
❤1
“爱看热闹的说啥子 说爷青回咯 你们要咋子就咋子诶 都别顶嘴咯 各位懂爷 可以跪咯 但评委是林北 我明人不说暗话 更不会阳奉阴违” “新仇旧恨 了就了了 了断趁着来个彻底的 咱不是同一条船上的 但是同一条河里的” “保持独立 独特 独裁可没什么好下场”
❤1
吃瓜2:模特娜娜vs狼友 起因:狼友约上了模特娜娜的课,体验完后在给群的报告(图1)和自己频道写的报告(图2)略有不同,个人看本质无区别,属中差评,仅用词委婉程度不一(见个人看报告的习惯) 娜娜反击(图3):小人行径,有本事来群里对线!大不了鱼死网破,双方都进去! 狼友解释(图4):没瓜,只是课表没蛇这点不满意了 群主解释(图4):狼友要点老师是臆想的,其实他是优质狼友 娜娜结尾(图4):我是个温柔的宝宝,大家说对不对? 简评: 1. 第一次见老师在群里主动找狼友对线,情商堪忧 2. 好评多的老师,就不能容忍中差评?这是一个问题 3. 能想到群主做了多少扯皮与公关工作,哈哈哈你也是成长了 4. 事后狼友主动撤回了报告(图1),也清空了自己的频道,个中曲折,看官自由想象与判断 5. 写的时候笔者发现疑似被娜娜拉黑,正好出锐评 锐评: 1. 墙内转墙外的老鸡(指开得久),照搬了部分墙内养狗打法,由于墙内有联系方式,安全系数堪…
花魁娜娜,顶流之一 ,去过的都说好,大圈质量。就是约课难啊。需要提前说一声。另:团长已经问过老师 写报告可以优惠一张。兄弟们都可以,去了只要写,电报去的兄弟貌似优惠力度更大 备注:模特下海 人照对版。围子的质量 联系方式两个号 与你 cs6677 与你 cs7766 新电报号:@nncs6677
吃瓜1:团长vs东京听雪(雪王) 起因(图1):团长在某群说到雪王在一年时间里从4p7pp带房涨价到7p13pp只上门,同时服务还是老样子,觉得看不过去 雪王反击1(图2):当初挂低价是鸡头定的价,不是自己想定低价,现在定高价让“觉得值的来” 雪王反击2(图2-3):我升级服务了!不是你团长在群里说了我这事就过去了,我不开心了! 雪王反击3(图4):我要团长你给我解释!顺带一串高级的骂人招数+直接开喷 简评: 1. 一年内涨价幅度确实离谱,几乎翻倍了,甚至还从带课室到只上门,涨得实在过分了 2. 雪王在鸡头手下挂500p的时候,鸡头一单抽450,可这不是脱离鸡头后涨价的理由 3. 个人认为,带cos可成为溢价理由,但是能不能不带cos少2张呢?这样或许更加合理 4. 同理,雪王说的加服务加钱指足交+1张,舌吻+1张。既然如此,可否自由选配服务,自由选择是否加钱呢?(妈的这不是某霜打法吗😡) 又:探长图书馆评论区有其作为J…
❤1
#本大王只上门哦 📍坐标 #雨花区 #雪王 #昧雪儿 #小野猫 #东京听雪 #小叁 #兮兮 💴车费 P600 PP1100 📱联系 @mxrttkx123 ✅频道 t.me/xueernb666 🤖双向 @xuernbmmm_bot 🔂提交报告 @CSZXBG_bot ➡️长沙【小熊甄选】闲聊群 📝报告01 📝报告02 📝报告03 📝报告04 📝报告05 📝报告06
Showing the 8 most recent of 8 posts we hold for @jiaoaofangzong. 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
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.
Mentions
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“骄傲放纵小天地” (@jiaoaofangzong), 1,140 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/jiaoaofangzong.
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.