Channel
@saseul_notice
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
671subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001787819504 |
|---|---|
| Type | Channel |
| Username | @saseul_notice |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/saseul_notice |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 04:03 | 671 | +1 |
| 7 Aug 2026, 19:53 | 670 | no change |
| 7 Aug 2026, 00:16 | 670 | first reading |
20 posts held, back to 12 March 2025 — 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.
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.
| Window | Rolling 30 days · latest post in window 28 July 2026 |
|---|---|
| Posts held | 20 (12 March 2025 – 28 July 2026) |
| Views total | 208 |
| Reactions total | 10 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 00:16 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.
305 reactions across 20 posts, in 12 distinct kinds. The most used accounts for 41.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 125 | 41.0% | |
| 👍 | 120 | 39.3% | |
| 👎 | 30 | 9.84% | |
| 👏 | 10 | 3.28% | |
| 🔥 | 9 | 2.95% | |
| 😁 | 3 | 0.984% | |
| 🎉 | 2 | 0.656% | |
| 💩 | 2 | 0.656% | |
| 😭 | 1 | 0.328% | |
| 🤔 | 1 | 0.328% | |
| 🥰 | 1 | 0.328% | |
| 🫡 | 1 | 0.328% |
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 20 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 305reactions 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 12 March 2025 to 28 July 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.
Hello, this is the SASEUL Development Team. Version 2.2.0.5 is now available. https://hub.docker.com/r/artifriends/saseul-network This is a stability patch. It improves how quickly a node recovers when it enters a branch other than the network's best branch. If you are participating in mining, we recommend updating your node. Update instructions are available on the Docker Hub page above. This is expected to be …
👍4❤3👏2🥰1
Hello, this is the SASEUL Team. The Guardee overhaul update has been completed. You will be able to download the updated version as soon as the app review process has been completed. Since launching the SASEUL mainnet, we have talked about the true value and potential of blockchain technology, as well as the many things blockchain can make possible. However, technologies and features that cannot be directly seen a…
❤3👍1🤔1
10. Miscellaneous / Changes Compatibility patches for the latest operating systems have been applied. This resolves biometric authentication issues that affected some newer OS versions. BTC and ETH support has been discontinued. Private keys and address information from legacy wallets can still be viewed and migrated through the Settings tab. In addition, we will soon unveil the new capabilities of Guardee and sho…
❤11👍7👏1
Hello, this is the SASEUL Development Team. We are continuing work to restore normal operation following the main block generation delay reported earlier. Additional mining nodes are currently being deployed to generate main blocks, and full normalization is expected to take some time. To address this issue, we have prepared version 2.2.0.4, which brings forward part of the content planned for the upcoming hardfork…
❤4👍4
Hello, this is the SASEUL Team. Since approximately 7:32 PM (KST) on June 14, 2026, some nodes that successfully mine blocks have been failing to generate main blocks. We became aware of the issue about one hour after it began and have been urgently deploying additional mining nodes to resolve the problem. We expect the current block generation issue to be resolved once the newly deployed mining nodes successfully …
👍4❤1
Hello, this is the SASEUL team. Four years have passed since May 17, 2022. During that time, many things have happened and many changes have taken place. Some of these changes may not have felt significant to everyone. However, we believe that for others, this has been a truly meaningful period of time. We sincerely thank everyone who has continued to support and stand by SASEUL over the past four years. Moving for…
❤6👍4🎉2🔥2
Hello, this is the SASEUL Team. The documentation required for SASEUL development has been updated. Please check the details at the site below. http://docs.saseul.com Thank you.
❤12👎1
Hello, this is the SASEUL development team. The v2.2.0.3 Docker image has been released. Unnecessary traffic between nodes has been reduced, convenience features such as query APIs have been added, and several bugs have been fixed. Detailed documentation will be updated soon. Please refer to the link below for update instructions: https://hub.docker.com/r/artifriends/saseul-network Thank you.
👍11❤5👎2
Hello, this is the SASEUL team. We have deployed a new version to Docker Hub that fixes minor bugs found in the first update. In addition, improvements have been applied to Guardee following the first update. You should notice overall speed improvements in SL transfers, NFT lookup, NFT ticket purchases, and related functions. A patch that reflects results without needing to press the refresh button during SL trans…
❤11👏4👎2
Hello. This is the SASEUL team. We would like to inform you about the hard fork update. This update required significantly more time and effort than originally expected during the initial planning stage. For over two years, the entire team worked without pause, fully immersed in the process, reviewing and incorporating every factor that could be considered. The first update file will be distributed via Docker Hub …
❤11👎2🔥2
Hello. This is the SASEUL team. We would like to share a few points regarding the update. First, we sincerely apologize for the disappointment caused by several delays to the schedule. We spent a great deal of time considering whether we should provide guidance about the future timeline or present a new exact date. We concluded that, in a situation already filled with disappointment, stating a specific date might no…
❤9👍5👎4🔥2
Hello, this is the SASEUL Team. First, we ask for your understanding from everyone who has been waiting for the update that was scheduled to be released on January 19, 2026. As previously announced on January 14, we explained the reasons for the update delay at that time. We stated that securing the stability of the SASEUL network is our top priority, that a sufficient number of test samples was required, and that t…
👍7👎3😭1
Showing the 12 most recent of 20 posts we hold for @saseul_notice. 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.
Citation-graph rank — 1,299,641 of 1,548,671entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“SASEUL (Official)” (@saseul_notice), 671 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/saseul_notice.
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.