有人在攻击服务器,有点卡,不急; 已经恢复 😁
👍5

Channel
@tg5288_cc
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
6,151subscribers
+304 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001439358108 |
|---|---|
| Type | Channel |
| Username | @tg5288_cc |
| Description | 官网地址: https://tg5288.cc/ 联系客服: @tg_daili_bot 本频道为通知频道,任何维护更新会提前通知,为了你的使用体验,所以请注意频道通知。 |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/tg5288_cc |
Ecommerce storefront — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 46% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 04:29 | 6,151 | +6 |
| 2 Nov 2026, 07:16 | 6,145 | +22 |
| 30 Oct 2026, 04:40 | 6,123 | +11 |
| 26 Oct 2026, 20:54 | 6,112 | +12 |
| 21 Oct 2026, 06:34 | 6,100 | +5 |
| 17 Oct 2026, 22:50 | 6,095 | +8 |
| 14 Oct 2026, 19:21 | 6,087 | +8 |
| 5 Oct 2026, 00:01 | 6,079 | +38 |
| 25 Sept 2026, 12:19 | 6,041 | +22 |
| 17 Sept 2026, 01:19 | 6,019 | +5 |
| 13 Sept 2026, 03:37 | 6,014 | +14 |
| 8 Sept 2026, 20:00 | 6,000 | +23 |
| 3 Sept 2026, 09:56 | 5,977 | +20 |
| 31 Aug 2026, 09:16 | 5,957 | +11 |
| 28 Aug 2026, 05:54 | 5,946 | +6 |
| 25 Aug 2026, 15:05 | 5,940 | +3 |
| 22 Aug 2026, 21:35 | 5,937 | +10 |
| 19 Aug 2026, 14:25 | 5,927 | +8 |
| 16 Aug 2026, 16:47 | 5,919 | +36 |
| 13 Aug 2026, 00:38 | 5,883 | first reading |
42 posts held, back to 1 July 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 14 pages of Telegram’s post history, 20 posts per page.
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. It is computed over the 8 of 11 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 42 (1 July 2026 – 6 November 2026) |
| Views total | 22,253 |
| Reactions total | 25 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 16:53 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.
Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
116 reactions across 29 posts, in 10 distinct kinds. The most used accounts for 44.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 51 | 44.0% | |
| 👍 | 39 | 33.6% | |
| 🤡 | 11 | 9.48% | |
| 🤣 | 4 | 3.45% | |
| 🤬 | 4 | 3.45% | |
| 👏 | 3 | 2.59% | |
| 🔥 | 1 | 0.862% | |
| 🤪 | 1 | 0.862% | |
| 🤯 | 1 | 0.862% | |
| 🥴 | 1 | 0.862% |
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 33 of the 42 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 116 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 42 most recent posts we hold, published 1 July 2026 to 6 November 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.
Telegram’s own ‘edited’ marker: 4 of 11 posts held from the last 30 days (36.4%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
有人在攻击服务器,有点卡,不急; 已经恢复 😁
👍5
优化了一下我们的代理的启动页面,目前看起来更加直观,加了引导动画。
👍5
坏消息,Telegram 网络 叕叕 炸了
我们在TG成品号接码页面增加了注册日期显示,年份基本都是正确的,月和日可能存在些许误差。 —— 近期我们发现一些超大群有些TG号无法发言,后来查明貌似新号会被限制,像5年老号就一切正常;如果你遇到类似问题,可以考虑我们店里的五年美国成品号。 ——
❤1
小火箭降价
关于小火箭账号,最近苹果有了一些新的风控策略;部分客户拿到独享号新环境马上修改密保很大概率触发风控锁定。 解决办法: 第一步:这里先解除账号锁定(密保验证) 第二步:这里登录并开启双重验证 再次提醒:该商品售后规则是“质保首登”,完成登录那一刻意味着账号正常即交易完成,后期由于共享/修改资料/等等其它行为导致的问题不在售后范围。
❤1
Telegram 数据中心(DC)科普 — 一般来讲,亚洲国家账号DC都是DC5;综合体验来讲,如果生活在亚洲 使用DC5的账号基本能得到最好的延迟体验; 那是否意味着DC5账号访问其它DC资源就慢呢? ❌ 如果你使用我们的代理线路,不存在这种情况,因为我们内部会根据实际情况自适应DC,不会让你绕路获取资源;每个DC边缘都有核心路由服务器,流量全程直连送达。
👍3❤1
据最新用户反馈,Telegram DC1【美国】炸了,上次是DC5 新加坡;就是可能看到代理有延迟 但消息刷不出来; 该问题属TG官方服务器问题,和代理线路无关,只能静候官方修复。
❤2👍2
听说外面小火箭账号都缺货了,我们这儿还有很多哈,只是没上架; 批发最低30个起,单价14元/个;数量更多还可再砍;感兴趣欢迎客服来谈。
网站服务器在维护所以有点卡,不急的单子都等明天吧 维护结束,已全部恢复。
❤1👍1
#通知 近期有用户反馈无法查询购买记录,该问题已确认是系统问题且已修复,目前已经全部正常。 特别注意,关于历史订单保留问题,除非特殊订单一律保留一个月,超过期限之后系统会自动清理且无法找回。 所以,下单之后的卡密请及时下载保存。 ——
❤3
#通知 目前我们的 SG Lite 线路宽带资源非常冗余,特此将倍率调至 x0.1,意味着20G流量实际按200G计算; 总的来讲,尽量使用随便跑; __
Showing the 12 most recent of 42 posts we hold for @tg5288_cc. 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.
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.
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.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“若楠小店|频道通知” (@tg5288_cc), 6,151 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/tg5288_cc.
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.