1
Signed 𝙈𝙖𝙭

Channel
@meigong818
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
37subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002044696608 |
|---|---|
| Type | Channel |
| Username | @meigong818 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/meigong818 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 09:40 | 37 | -1 |
| 29 Aug 2026, 08:05 | 38 | -1 |
| 21 Aug 2026, 08:43 | 39 | -3 |
| 13 Aug 2026, 23:37 | 42 | -1 |
| 10 Aug 2026, 16:31 | 43 | no change |
| 7 Aug 2026, 12:16 | 43 | first reading |
17 posts held, back to 17 August 2024 — 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 17 posts for this entry, the most recent from 6 March 2026. An engagement rate over an empty window would be a number about nothing.
1
Signed 𝙈𝙖𝙭
Channel name was changed to «青龙高级UI美工【头像案例】»
祝老哥们,祝2026马到成功,一切顺利,在外面多注意身体,多多赚金! 开年我们会改变模式,更多分类频道制作中,还有免费的头像设计,vip标志设计,到时候我会一一发到频道。谢谢各位老哥的关照了!
Signed 青龙pro(没有双向机器人小心被骗(高级UI/美工)
😍😍😍 😍😍😍😍😍 😍 好运支付定制2
Signed 青龙pro(没有双向机器人小心被骗(高级UI/美工)
https://t.me/addemoji/QLUI1
Signed 青龙pro(没有双向机器人小心被骗(高级UI/美工)
🥰🥰🥰🥰 🥰🥰🥰🥰 🥰🥰🥰🥰 🥰🥰🥰 🥰🥰🥰🥰 好运支付
Signed 𝙈𝙖𝙭
❤️❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️ 没发作品不代表不在哈,这段时间有点忙 单子有点多,等会儿会发一些作品出来给老哥们参考的哟!~~~~ 【我们主打高端图片UI设计】海报,GIF设计,头像设计,视频设计剪辑,UI界面设计,博彩,资金盘设计。 20人UI团队,可包月,出图极快,【10年博彩UI设计经验】 #原创动画设计 #UI设计 #美工 #logo设计 #海报设计 #青龙美工 下单客服👉 @QLpro1 @QLpro2
Signed 青龙pro(没有双向机器人小心被骗(高级UI/美工)
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 28 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
没发作品不代表不在哈,这段时间有点忙 单子有点多,等会儿会发一些作品出来给老哥们参考的哟!~~~~ 【我们主打高端图片UI设计】海报,GIF设计,头像设计,视频设计剪辑,UI界面设计,博彩,资金盘设计。 20人UI团队,可包月,出图极快,【10年博彩UI设计经验】 下单客服👉 @aodbuibot @QLpro1 @QLpro2
Signed 𝙈𝙖𝙭
【我们主打高端图片UI设计】海报,GIF设计,头像设计,视频设计剪辑,UI界面设计,博彩,资金盘设计。 20人UI团队,可包月,出图极快,【10年博彩UI设计经验】
Signed 青龙pro(没有双向机器人小心被骗(高级UI/美工)
青龙高级UI美工【头像案例】 pinned a photo
💀💀💀💀💀😆😆😆😆😆骗子不得好死!!!!大家都是来赚钱的 没必要这样子,请各位老哥认准我们的号,我们没有双向机器人号,只有2个号: @QLpro1 @QLpro2 千万别看错了,让骗子有可乘之机!!!!!!!!
Signed 青龙pro(高级UI/美工)
Showing the 12 most recent of 17 posts we hold for @meigong818. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@meigong818 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“青龙高级UI美工【头像案例】” (@meigong818), 37 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/meigong818.
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.