恢复注册 不用强制邀请了 群组也已经开放

Channel
MaikCloud
@maikcloud
On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
122subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001913759719 |
|---|---|
| Type | Channel |
| Username | @maikcloud |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 10 October 2026 |
| On Telegram | t.me/maikcloud |
Topic
Other / unclassifiable — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 |
|---|---|---|
| 16 Sept 2026, 13:15 | 122 | +2 |
| 16 Aug 2026, 17:16 | 120 | -3 |
| 9 Aug 2026, 03:16 | 123 | no change |
| 7 Aug 2026, 11:12 | 123 | first reading |
Engagement
20 posts held, back to 21 January 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 20 posts for this entry, the most recent from 16 February 2024. An engagement rate over an empty window would be a number about nothing.
Reaction mix
6 reactions across 2 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 33.3% | |
| 🔥 | 2 | 33.3% | |
| 👏 | 1 | 16.7% | |
| 😁 | 1 | 16.7% |
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 3 of the 20 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 21 January 2024 to 16 February 2024, 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
官方邀请码:点击注册
最近会清理进一个月未上线的成员,如有误清请及时联系 @XC2820
新年快乐,bangbang~
🎆
所有活动取消,所有不限时套餐下架。不限时套餐修改退款的私聊 @xc2820
我是垃圾机场 不认识的就别来了谢谢
老用户想用的你就好好用 瞎jb逼逼的 直接滚 我尼玛一个个小姑娘 天天熬夜修机场 我特码乐意啊 再说了这个破机场 开业到现在一直赔钱 什么配置你们自己心里清楚 。我用心服务的是相信我的用户,你感觉不好用你就去各大测频频道去喷别在我群里喷。我看见就烦。没骂你是给你们面子。以后全邀请制。
🔥2😁1
已恢复 请及时更新订阅 最新域名访问 maikuaiyun.com
本次攻击造成的损失 将补偿所有付费用户 时常3天
服务器正在被攻击
临时维护
Showing the 12 most recent of 20 posts we hold for @maikcloud. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@maikcloud 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 10 August 2026 – 10 August 2026
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“MaikCloud” (@maikcloud), 122 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/maikcloud.
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.