Telegram RegisterThe public register of Telegram
Telegram profile photo for 云帆雾航 | Sailoud LLC

Channel

云帆雾航 | Sailoud LLC

@Sailoud

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

183subscribers

+0 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-1001211032932
TypeChannel
Username@Sailoud
DescriptionSubculture and ACGN sharing and communication community 🔗https://sailoud.com
CreatedBetween 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/Sailoud

Growth

1837 Aug 2026, 01:37 — 183 subscribers7 Aug 2026, 08:02 — 183 subscribers7 Aug 2026, 01:377 Aug 2026, 08:02
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 182–184 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 08:02183no change
7 Aug 2026, 01:37183first reading

Engagement

20 posts held, back to 13 December 2021the 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 20 posts for this entry, the most recent from 13 July 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
13
Links
8

Lifetime counters from Telegram’s own channel header, read 7 August 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.

Reaction mix

30 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 46.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🎉1446.7%
👍620.0%
🤡413.3%
310.0%
🥰310.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 10 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 30reactions 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 13 December 2021 to 13 July 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

13 Jul 2024, 07:07 UTC≈3,460 views4 reactionsread 7 August 2026

因运营策略调整,我们将在未来几周将维咔的运营主体由Sailoud LLC切换为VikACG Pte. Ltd.,商户合作关系将继承到新的主体,原有的用户运营模式保持不变,同时我们也将引入更多其他集团业务到维咔的运营中

🤡4

14 Feb 2024, 15:45 UTC538 views3 reactionsread 7 August 2026
Forwarded from @vikacgPhoto

我们在这里很高兴地为大家宣布,#云帆小程序 将在维咔的 #鸳鸯锅架构移动端 上正式搭载,届时第三方编写的特定格式程式将可以在维咔内打开,您也可以抛弃掉某些原生App仅使用云帆小程序,有维咔就够了!

🥰3

10 Dec 2023, 05:37 UTC≈4,850 views4 reactionsread 7 August 2026

热烈庆祝云帆雾航Sailoud LLC成立五周年~

🎉4

22 Sept 2023, 11:30 UTC≈3,790 viewsread 7 August 2026
Photo

新的大型DLC要发布了,大家懂得都懂,26日全员鸽子王绝赞上线中!

27 May 2023, 11:33 UTC≈4,200 views3 reactionsread 7 August 2026

#有关云帆互联产品停止运行的公告 尊敬的云帆雾航用户,您好: 我们是云帆互联的维护和开发团队(Sailoud LLC 智慧办公组),在此向您发布重要通知。 经过仔细考虑和评估,我们决定在三个月后的2023年8月31日停止云帆互联的运营。为了确保用户数据的隐私和安全,我们将严格按照隐私政策的规定,在停止运营时对所有数据进行清空处理。 为了方便用户的过渡和使用,我们已经在维咔VikACG、联合办公Uni-Work等平台上重新开放了直接登录或注册的选项。然而,在这三个月的过渡期内,我们也将保留从云帆互联登录的选项。在此期间,我们已关闭了云帆互联的注册选项。因此,我们特别提醒那些仅通过第三方平台登录云帆互联且没有在这些平台设置密码的用户,请尽快在对应平台的用户中心的相应位置完成邮箱绑定和设置密码的操作。 绑定邮箱和设置密码是为了确保您在云帆互联停止运营后能够顺利使用对应平台,并保障您的账户安全和数据隐私。我们强烈建议您尽早完成

👍3

9 Dec 2022, 15:59 UTC≈5,240 views11 reactionsread 7 August 2026
Photo

还记得我们当年做产品时的初心吗?云帆雾航四周年快乐

🎉10👍1

6 Aug 2022, 12:58 UTC923 views0 reactionsread 7 August 2026
Forwarded from @vikacg

因我们Office域翻车,所以暂停受理新增创作者Office申请。顺带一提,我司对外工作邮箱也收不到邮箱了,望周知。

6 Jul 2022, 09:32 UTC≈4,210 viewsread 7 August 2026

云帆雾航部分业务正在执行跨地域迁移行为,可能会出现业务服务不稳定的情况

24 May 2022, 16:08 UTC≈5,430 viewsread 7 August 2026

我们注意到,Jsdelivr公共库在中国大陆的部分地区的解析已失效,我们已经向上游反馈此问题,请注意:云帆雾航无法主动控制此事件,如果确定上游无法修复此问题,我们将会彻底更换部分公共库为云帆雾航自有的PicJS公共库

16 Mar 2022, 02:22 UTC≈4,520 viewsread 7 August 2026

云帆互联中国补充协议已发布,云帆互联中国账号是云帆联合办公协同软件账号系统的升级版,是云帆雾航未来的统一账号体系的组成部分,我们将在未来某一段不确定的时间执行账号体系迁移操作 https://account.sailoud.com/legal/china

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

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

“云帆雾航 | Sailoud LLC” (@Sailoud), 183 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/Sailoud.

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.