Telegram RegisterThe public register of Telegram
Telegram profile photo for SealSend Community

Channel

SealSend Community

@sealsend

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Domains linked from posts · Cite this entry

353,077subscribers

-16,656 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 316,228–1,000,000.

Register entry

Telegram ID-1002099868722
TypeChannel
Username@sealsend
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live8 September 2026
Measurements held30
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/sealsend

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 84% 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

353,077369,733361,4056 August 2026 — 369,733 subscribers6 August 2026 — 369,733 subscribers7 August 2026 — 369,257 subscribers8 August 2026 — 368,630 subscribers9 August 2026 — 368,192 subscribers10 August 2026 — 367,664 subscribers11 August 2026 — 367,168 subscribers12 August 2026 — 366,618 subscribers13 August 2026 — 366,060 subscribers14 August 2026 — 365,532 subscribers15 August 2026 — 365,028 subscribers17 August 2026 — 364,125 subscribers18 August 2026 — 363,588 subscribers19 August 2026 — 363,067 subscribers20 August 2026 — 362,794 subscribers21 August 2026 — 362,281 subscribers22 August 2026 — 361,493 subscribers24 August 2026 — 360,553 subscribers25 August 2026 — 360,026 subscribers26 August 2026 — 359,617 subscribers27 August 2026 — 359,108 subscribers28 August 2026 — 358,735 subscribers29 August 2026 — 358,192 subscribers30 August 2026 — 357,878 subscribers31 August 2026 — 357,314 subscribers1 September 2026 — 356,735 subscribers2 September 2026 — 356,272 subscribers3 September 2026 — 355,598 subscribers5 September 2026 — 354,638 subscribers8 September 2026 — 353,077 subscribers6 August 20268 September 2026
30 measurements spanning 34 days, net -16,656. 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 350,579–372,231 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)SubscribersChange
8 Sept 2026, 20:02353,077-1,561
5 Sept 2026, 10:38354,638-960
3 Sept 2026, 10:22355,598-674
2 Sept 2026, 07:33356,272-463
1 Sept 2026, 05:28356,735-579
31 Aug 2026, 06:04357,314-564
30 Aug 2026, 04:28357,878-314
29 Aug 2026, 06:11358,192-543
28 Aug 2026, 05:37358,735-373
27 Aug 2026, 05:25359,108-509
26 Aug 2026, 02:32359,617-409
25 Aug 2026, 05:46360,026-527
24 Aug 2026, 05:37360,553-940
22 Aug 2026, 12:55361,493-788
21 Aug 2026, 03:07362,281-513
20 Aug 2026, 06:03362,794-273
19 Aug 2026, 08:48363,067-521
18 Aug 2026, 08:52363,588-537
17 Aug 2026, 10:04364,125-903
15 Aug 2026, 19:48365,028first reading

Engagement

20 posts held, back to 19 January 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 70 pages 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 4 October 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 16s
Average length
1m 16s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

18,352 reactions across 18 posts, in 25 distinct kinds. The most used accounts for 39.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍7,18339.1%
6,70736.5%
🔥2,01811.0%
👎6193.37%
🥰3561.94%
🖕2991.63%
👏2341.28%
😁2271.24%
🍌1220.665%
🤡730.398%
💩620.338%
🍓610.332%
🤬610.332%
🙏470.256%
🕊410.223%
👀390.213%
❤‍🔥360.196%
💋350.191%
😱340.185%
🎉310.169%
5 further kinds670.365%

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 18 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 18,352 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 19 January 2025 to 4 October 2025, 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

4 Oct 2025, 13:37 UTC≈48,900 views1,824 reactionsread 8 September 2026

📢 Hello Online+ 👋 We’re excited to officially join the social platform of the ICE Open Network, the blockchain where SealSend was built. 🔐 The wait is almost over: We’re getting closer to the $SEAL distribution. Until then, don’t forget about our SealSend Chrome extension: 👉 https://shorturl.at/1lUHD SealSend is the only solution that truly encrypts your emails, and works seamlessly with Gmail, Yahoo, and Outloo

794👍547🔥147👎92🖕62👏50🍓45🍌36

26 Jun 2025, 07:46 UTC≈84,400 views1,802 reactionsread 8 September 2026

Outlook is now supported in the SealSend extension! 🔐 We’ve just submitted the update to the Chrome Web Store, it will be live in a few hours. Gmail, Yahoo, and now Outlook, privacy sealed across the board. #SealSend #EncryptedEmail #OutlookSupport Post : https://x.com/SealSendEmail/status/1938141076490989579

755👍516🔥230👏121👎36💋35🤡35🍌29

25 Jun 2025, 15:05 UTC≈85,200 views697 reactionsread 8 September 2026

🚨 SealSend Progress Update 🚨 We built the SealSend email encryption extension for Chrome — now supporting Gmail, Yahoo, and (soon) Outlook. Together, these cover over 90% of global email users. We've helped thousands activate their wallets by sending ION tokens — community support, sealed and delivered. ✅ The SealSend mobile app is in development, bringing encrypted email & chat on the go — fully compatible with o

425🔥143👍44🥰44💩27🕊75👎2

16 Jun 2025, 06:51 UTC≈66,500 views704 reactionsread 8 September 2026

Yahoo Mail is now supported in SealSend! We’ve just added full integration for Yahoo - making encrypted email possible beyond Gmail. The extension update is rolling out today. Make sure you're using the latest version. #SealSend #EncryptedEmail #PrivacyMatters https://x.com/SealSendEmail/status/1934502325671911448

322👍215🔥64🙏47🖕17🍓16🥰14🤔5

19 May 2025, 06:30 UTCviews —

SealSend Community pinned «🔐 Start an encrypted email conversation in seconds with #SealSend! Enter the recipient’s email in the “Invite & Share” tab Hit “Send” – a draft email with your wallet address is auto-filled The recipient replies with a click, encrypted & secure. Read more…»

19 May 2025, 06:26 UTC≈83,400 views1,027 reactionsread 8 September 2026

We just published a new update for the Sealsend extension. Ensure you have the latest version, 2.3.5.

👍514330🖕78🥰66😁17🤬11🔥5👎4

19 May 2025, 06:26 UTC≈76,200 views471 reactionsread 8 September 2026

https://x.com/SealSendEmail/status/1924101893753602522

👍243145🔥38🥰25🥴20

13 May 2025, 12:26 UTC≈89,800 views836 reactionsread 8 September 2026

🔐 Start an encrypted email conversation in seconds with #SealSend! Enter the recipient’s email in the “Invite & Share” tab Hit “Send” – a draft email with your wallet address is auto-filled The recipient replies with a click, encrypted & secure. Read more : https://x.com/SealSendEmail/status/1922266065867878884 Privacy made effortless. #EncryptedEmail #ION #Gmail

👍426248🔥94🎉31🖕19🥰9🤬6🕊3

9 May 2025, 09:11 UTC≈88,900 views1,612 reactionsread 8 September 2026

Get Ready: $SEAL Token Distribution Is Around the Corner! We’re thrilled to announce that the KYC process is now live—this is your final step before the highly anticipated $SEAL token distribution kicks off! KYC is mandatory for all participants to be eligible. Make sure to complete it ASAP so you don’t miss out. The countdown has begun… are you ready to secure your spot? #SealSend #SEALtoken #Crypto #KYC #Airdro

701👍556🔥196😁63👎36👏22🍌19🍾19

7 May 2025, 14:49 UTC≈78,600 views432 reactionsread 8 September 2026

https://x.com/SealSendEmail/status/1919720738493169845

227👍169🖕19🔥11🤬6

5 May 2025, 15:08 UTC≈85,200 views500 reactionsread 8 September 2026

https://x.com/SealSendEmail/status/1918577198727877038?t=MzrHMXqVj3bYzEQWi_yM5w&s=19

218👍184🔥60🖕30💩8

2 May 2025, 12:18 UTC≈80,800 views852 reactionsread 8 September 2026
Video

🚨 Big news: SealSend is going mobile. We’re excited to share that the SealSend mobile app is in development, bringing encrypted communication to your pocket. Here’s what’s coming: - Private chat & group messaging - Encrypted email (compatible with our Chrome extension) - Built-in blockchain wallet for seamless integration One app. Full privacy. Total control. More details coming soon. Stay tuned. #SealSend #E

👍321🔥244206❤‍🔥36😁22🥰15💩8

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

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

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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.

Domains linked from posts

2 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

app.online.ioregistrable domain: online.io1 post · 4 October 2025 – 4 October 2025 · example post
shorturl.at1 post · 4 October 2025 – 4 October 2025 · example post

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

“SealSend Community” (@sealsend), 353,077 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/sealsend.

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.