蓝莓官方通知: 这次上量希望各位推手 代理尽职尽责、如果再次停线的永不续用、 且行且珍惜!

Channel
玫瑰 青橙直播
@meigui_qingcheng
On this record: Growth · Engagement · Posts · Citations · Cite this entry
34subscribers
-1 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001634152446 |
|---|---|
| Type | Channel |
| Username | @meigui_qingcheng |
| Created | Between 1 December 2021 and 4 April 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 3 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 3 September 2026 |
| On Telegram | t.me/meigui_qingcheng |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Aug 2026, 09:04 | 34 | -1 |
| 12 Aug 2026, 00:53 | 35 | no change |
| 11 Aug 2026, 04:16 | 35 | first reading |
Engagement
14 posts held, back to 4 April 2022 — 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 14 posts for this entry, the most recent from 17 October 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
蓝莓官方通知: 所有代理 推手蓝莓直播凌晨所有线路停止上量、我司内部调整。感谢大家这些天的推广支持.新台子会陆续上线、敬请等待通知!
玫瑰 青橙直播 pinned «蓝莓官方通知: 一切通知停掉的线路不许再上量.以通知时间点为节点.各位代理 推手以身作则免得扯皮!»
蓝莓官方通知: 一切通知停掉的线路不许再上量.以通知时间点为节点.各位代理 推手以身作则免得扯皮!
玫瑰 青橙直播 pinned a photo
冒充我司工作人员行骗 大家注意
玫瑰 青橙直播 pinned a photo
大家注意 骗子账号 自己给自己发送u当做结算图到处冒充我司行骗
玫瑰官方通报: 蓝莓直播火速上量.后期我司要调整棋牌娱乐!
玫瑰 青橙直播 pinned «玫瑰青橙官方通知: 第一直播早已结算完毕 不要再来问 拿谁的线的直接找你上家 谢谢»
玫瑰青橙官方通知: 第一直播早已结算完毕 不要再来问 拿谁的线的直接找你上家 谢谢
玫瑰 青橙直播 pinned «玫瑰青橙官方通知: 第一官方 影视站 小说站 优质色站 下载站 联盟优先欢迎合作»
Showing the 12 most recent of 14 posts we hold for @meigui_qingcheng. 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.
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.
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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“玫瑰 青橙直播” (@meigui_qingcheng), 34 subscribers as measured 26 August 2026. Telegram Register, tgregister.com/channel/meigui_qingcheng.
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.