1. 恢复Misaka机场与Whale Cloud机场套餐的请与 @nyanya2233 联系 2. 后期我们考虑上一些 IPLC游戏节点与流媒体解锁节点 3.(该咕咕咕的咕完了(一个月了

Channel
Misaka Airport Channel
@misakameng1
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
60subscribers
-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 | -1001595278751 |
|---|---|
| Type | Channel |
| Username | @misakameng1 |
| Created | Between 1 August 2021 and 15 February 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/misakameng1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 16:08 | 60 | -1 |
| 10 Aug 2026, 04:30 | 61 | no change |
| 7 Aug 2026, 09:19 | 61 | first reading |
Engagement
16 posts held, back to 15 February 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 pageof 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 16 posts for this entry, the most recent from 19 August 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
Sticker, posted without a caption
本站原场主跑路,不过运维找到了跑路前天的备份 并与某小场合并为 @ShizukuClub_Channel 特此公告 PS:由于导出的急,可能出现丢失购买数据等,请与 @shizukuclub_2233 联系恢复套餐。
知乎@知一声(知乎官方账号): 近期,我们注意到,在国内外热点事件的讨论中,出现个别用户冒充当地网友,发布、传播不实信息,干扰正常讨论秩序的情况。与此同时,众多热心知友也积极向我们反映,建议知乎公开展示用户 IP 属地信息。 为了更好地维护社区生态氛围,打击造谣传谣行为,社区拟逐步开放「用户 IP 属地」的公开显示。届时,问答页面将显示用户发布内容时的 IP 属地。 接下来,相关测试将逐步展开,大家会感受到如下变化: 部分问题下将展示回答的评论 IP 属地; 目前采用的 IP 对应属地,境内互联网用户账号 IP 地址属地信息标注到省(区、市),境外账号 IP 地址属地信息标注到国家(地区)( IP 属地以运营商提供信息为准),用户暂时无法主动开启或关闭相关展示。 https://zhuanlan.zhihu.com/p/499224411
Gitee 似乎屏蔽了非白名单的Refer请求,直接访问不影响 可能会被跳转到 https://assets.gitee.com/favicon.ico 看了下是3月底的事情,害,今天才发现
Photo, posted without a caption
我们团队正在寻找目前可用国际支付渠道 Our team is searching about international payment platforms
Channel name was changed to «Misaka Airport Channel»
Sticker, posted without a caption
由于PH屏蔽俄罗斯,我们打算开展国际业务
我们恢复了JP #2节点的同时还增加了RU #2节点
Sticker, posted without a caption
Showing the 12 most recent of 16 posts we hold for @misakameng1. 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.
Forward network
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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 2
- 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
- 2
- vacant every time we have ever looked
@misakameng1 named 2 handles 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, 11 August 2026 – 12 August 2026
named in 1 post, 11 August 2026 – 11 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Misaka Airport Channel” (@misakameng1), 60 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/misakameng1.
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.