Telegram RegisterThe public register of Telegram
Telegram profile photo for 高级UI/美工设计/LOGO设计【原匠客设计】【推广频道】

Channel

高级UI/美工设计/LOGO设计【原匠客设计】【推广频道】

@meigongLOGO

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

501subscribers

+0 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001235317185
TypeChannel
Username@meigongLOGO
CreatedBetween 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live28 August 2026
Measurements held2
Confirmed unchanged3 times, most recently 28 August 2026
On Telegramt.me/meigongLOGO

Growth

50113 Aug 2026, 19:38 — 501 subscribers14 Aug 2026, 15:34 — 501 subscribers13 Aug 2026, 19:3814 Aug 2026, 15:34
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 500–502 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 15:34501no change
13 Aug 2026, 19:38501first reading

Engagement

15 posts held, back to 17 August 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.79%
avg views ÷ 501 subscribers
Avg views / post
14.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 15 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 August 2026
Posts held15 (17 August 20242 August 2026)
Views total14
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 19:38 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.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 1 of the 15 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 17 August 2024 to 2 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

2 Aug 2026, 10:07 UTC14 viewsread 13 August 2026
Photo

TG必备的搜索引擎,快搜kuai帮你发现有趣群组、频道、视频、音乐、电影、新闻 | Find cool stuff all in one bot! 机器人:@kuai @kuaia @kuaiaa 👉 https://t.me/kuai?start=a_2W82XNM

18 Jun 2026, 13:32 UTC123 viewsread 13 August 2026

端午不放假哈老哥们 有图继续安排,等我把端午忙过了我再慢慢的收拾频道发作品

3 Mar 2026, 12:45 UTC≈12,200 views2 reactionsread 13 August 2026
Photo

😌😌😌😌😌😌😌😌😌 点击下方字体自动跳转案例专区 🥰🥰🥰🥰🥰🥰 🥰 UI界面/盘口设计专区 🥰 🥰 头像案例专区 🥰 视频/特效/数字人口播案例专区 🥰 🥰 海报案例专区 🥰 🥰 轮播案例专区 🥰 logo案例专区 🥰 连贯广告表情案例专区 🥰 🥰 动态GIF图,贴纸案例专区 🥰 前端开发/维护 🥰 需要定制请联系🥰 @QLpro1 @QLpro2 🥰🥰🥰🥰

2

20 Dec 2025, 08:24 UTC≈12,200 viewsread 13 August 2026

😍😍😍 😍😍😍😍😍 😍 好运支付定制2

10 Dec 2025, 08:19 UTC137 viewsread 13 August 2026

🥰🥰🥰🥰 🥰🥰🥰🥰 🥰🥰🥰🥰 🥰🥰🥰 🥰🥰🥰🥰 好运支付

6 Oct 2025, 06:52 UTC141 viewsread 13 August 2026

❤️❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️❤️ 没发作品不代表不在哈,这段时间有点忙 单子有点多,等会儿会发一些作品出来给老哥们参考的哟!~~~~ 【我们主打高端图片UI设计】海报,GIF设计,头像设计,视频设计剪辑,UI界面设计,博彩,资金盘设计。 20人UI团队,可包月,出图极快,【10年博彩UI设计经验】 #原创动画设计 #UI设计 #美工 #logo设计 #海报设计 #青龙美工 下单客服👉 @QLpro1 @QLpro2

6 Aug 2025, 08:56 UTC127 viewsread 13 August 2026
Photo

没发作品不代表不在哈,这段时间有点忙 单子有点多,等会儿会发一些作品出来给老哥们参考的哟!~~~~ 【我们主打高端图片UI设计】海报,GIF设计,头像设计,视频设计剪辑,UI界面设计,博彩,资金盘设计。 20人UI团队,可包月,出图极快,【10年博彩UI设计经验】 下单客服👉 @aodbuibot @QLpro1 @QLpro2

24 Apr 2025, 07:33 UTC133 viewsread 13 August 2026

【我们主打高端图片UI设计】海报,GIF设计,头像设计,视频设计剪辑,UI界面设计,博彩,资金盘设计。 20人UI团队,可包月,出图极快,【10年博彩UI设计经验】

22 Dec 2024, 17:34 UTCviews —

高级UI/美工设计/LOGO设计【原匠客设计】【推广频道】 pinned a photo

22 Dec 2024, 16:49 UTC157 viewsread 13 August 2026
Forwarded from @UIsheji16Photo

💀💀💀💀💀😆😆😆😆😆骗子不得好死!!!!大家都是来赚钱的 没必要这样子,请各位老哥认准我们的号,我们没有双向机器人号,只有2个号: @QLpro1 @QLpro2 千万别看错了,让骗子有可乘之机!!!!!!!!

12 Nov 2024, 15:32 UTCviews —

高级UI/美工设计/LOGO设计【原匠客设计】【推广频道】 pinned a photo

12 Nov 2024, 15:32 UTC136 viewsread 13 August 2026
Photo

😉好久没更新了,马上双12来袭,青龙特惠活动火热进行中! 😀活动时间:11月15日-12月13日 😀活动一 凡是在青龙这里消费满350U做图设计的,都可以找我充值3个月TGVIP会员。 😀活动二 凡是在青龙这里消费满300U做图设计的,可以按照3个月TGVIP价格来抵扣优惠。 😀活动三 任何找青龙的查档业务,均享受8折优惠。 (以上活动新老客户都有效) 活动最终解释权归青龙高级UI设计团队所有,赶快联系 @QLpro1 骚扰吧! 🤓🤓🤓🤓🤓 🤓🤓🤓🤓🤓😀 (平时事情多,我不会主动提及,截图的客户都有,只要消费满)

Showing the 12 most recent of 15 posts we hold for @meigongLOGO. 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.

Citation-graph rank

Citation-graph rank — 561,181 of 1,627,445entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“高级UI/美工设计/LOGO设计【原匠客设计】【推广频道】” (@meigongLOGO), 501 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/meigongLOGO.

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.