https://t.me/+xFQj2rnbuTE2MDVk

Channel
守护我方阿橙🍊
@acheng_7777
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
366subscribers
+210 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003295343240 |
|---|---|
| Type | Channel |
| Username | @acheng_7777 |
| Created | 4 November 2025 — measured — dated from the channel’s first post |
| First recorded | 15 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/acheng_7777 |
Topic
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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:36 | 366 | +18 |
| 9 Sept 2026, 05:16 | 348 | +24 |
| 30 Aug 2026, 20:25 | 324 | +26 |
| 24 Aug 2026, 19:57 | 298 | +122 |
| 16 Aug 2026, 07:07 | 176 | +20 |
| 15 Aug 2026, 13:30 | 156 | no change |
| 15 Aug 2026, 13:15 | 156 | first reading |
Engagement
8 posts held, back to 4 November 2025 — 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 15 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 4s
- Average length
- 4s
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.
Recent posts
【时间】:2026-08-14 【老师】:啊橙 【留名】:港岛哥哥 【费用】:工兵P 【评价】:👍 好评 【人照】:9 【颜值】:9 【身材】:9 【服务】:8 【态度】:10 【环境】:9 【综合】:9 【过程】:看到妹妹的照片资料,感觉很心动,跟妹妹约了课,下面重点说一下大家关心的点吧。 1,妹妹在一个标准居民小区开课,第一次听说,感觉安全性不错。 2,人照没啥差别,五官精致耐看,好像是新疆的妹妹,果然大新疆出美女。 3,妹妹性格很好,也很会聊天,全程沟通都很舒服,态度和情绪价值都很好。 4,女上起手,紧度正常偏紧,阻尼感很好,很敏感,很容易就能感觉到妹妹一夹一夹的收缩,很真实,感觉好像自己很厉害一样,表情声音反馈也都很真实。 颜值很高性格很好的妹妹,态度和情绪价值都很好,很放松,全程都很自然,满意的一次cj之旅。
宝宝们之前的号限制了,联系认准这个新号哦 评价暂无 有最新验证视频!
守护我方阿橙🍊 pinned a photo
我在杭州御女阁免费上榜啦,群内氛围轻松,不强制做活动,永久上榜! 👑👑认准Telegram官方认证防伪标志 👑 超多好看的小姐姐都在这里上榜!💖💖💖 https://t.me/hangzhou_777
艺名:阿橙🍊 坐标:上城 年龄:06年 🐻:天然C 身高168 体重48 大学生兼职0整清纯类型 白幼瘦的冰山雪莲 卡布奇洛的邻家女友 🛀鸳鸯浴、👅下面、💋kiss(口臭异味不接),69,戴t👄,制服诱惑、花式调情、🐻推臀推、丝袜高跟、互亲咪咪、啪啪啪 高情商 给你拉满情绪价值 高颜值,给你找你初恋女友的感觉 定金预约课程,见面抵扣课费 课费P 1200 45分钟 PP 2300 90分钟 熟客可约以下(提前一天定金预约) 包时: 3H 4000 (限三次) 包天:(非全天,因为不能过夜) 中午12点-晚上0点 6688 (限四次) 联系: @acheng_777 双向:@acheng777_bot 频道:https://t.me/acheng_7777 🈲 中途拔套 拒绝 粗大 桩机 口臭 皮肤病 无套 液体套 嗑药抹药 不接喝酒 不包夜中途出算1,服务开始不退,宝宝们尽量现金 ‼️有固定居所 ‼️也…
Channel name was changed to «守护我方阿橙🍊»
Channel created
Showing the 8 most recent of 8 posts we hold for @acheng_7777. 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.
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.
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.
“守护我方阿橙🍊” (@acheng_7777), 366 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/acheng_7777.
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.