Channel
@Official_Saturn
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
207subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004327575619 |
|---|---|
| Type | Channel |
| Username | @Official_Saturn |
| Created | 23 July 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/Official_Saturn |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 23:35 | 207 | -1 |
| 7 Aug 2026, 03:47 | 208 | no change |
| 7 Aug 2026, 00:48 | 208 | first reading |
7 posts held, back to 23 July 2026 — 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 5 August 2026 |
|---|---|
| Posts held | 7 (23 July 2026 – 5 August 2026) |
| Views total | 1,682 |
| Reactions total | 57 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 03:47 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.
57 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 70.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 40 | 70.2% | |
| 👍 | 10 | 17.5% | |
| 🔥 | 7 | 12.3% |
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 6 of the 7 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 57reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 23 July 2026 to 5 August 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.
📢 Surf × Saturn 리서치 이벤트 당첨자 발표 Surf × Saturn 리서치 이벤트에 참여해주신 모든 분들께 진심으로 감사드립니다! 많은 분들께서 Surf를 활용해 Saturn을 직접 리서치하고 다양한 인사이트를 공유해주셨습니다. ✅ Surf 1년 구독권 당첨자 (10명/트위터명) Surf 1년 구독권 당첨자는 Saturn 팀에서 직접 선정하였습니다. 선정 기준은 다음과 같습니다. - Saturn 예치 참여자 기준 5명 - 리서치 콘텐츠 퀄리티 기준 5명 당첨자 @Node_Park @NOSTAGIA99 @lmslms1004 @songsong6059 @nunssup77 @cryptoyong727 @gridonbtc @EJseong95 @truly_punch @sacyuko ✅신세계상품권 각 10만원 (예치 금액 대상) @nunss…
❤5👍1🔥1
📢 Saturn Into Orbit Korea Meetup 후기 이벤트 당첨자 발표 안녕하세요, 먼저 Saturn Into Orbit Korea Meetup에 참석해주시고, 소중한 후기까지 남겨주신 모든 분들께 진심으로 감사드립니다. 여러분 덕분에 즐겁고 뜻깊은 밋업을 성공적으로 마무리할 수 있었습니다. 현장 이벤트 및 후기 이벤트 당첨자를 발표합니다! ✔️스타벅스 아이스 아메리카노 후기 제출 폼을 작성해주신 모든 분들 ✔️신세계 상품권 5만원권 당첨자 (8명) - Truly 진심펀치 - Ho_it - jjwandrew.apt - Johnny Jung's Web4 - Hyun - Grid - sunney4557 | 쑤니 - 하얀대장 다시 한번 Saturn Into Orbit Korea Meetup에 함께해주신 모든 분들께 감사드립니다.…
❤17👍4🔥3
📢 [행사 일정 변경 안내] Saturn Into Orbit Korea Meetup 안녕하세요, 여러분. 금일 진행 예정이었던 Saturn Into Orbit Korea Meetup과 관련하여 안내드립니다. Saturn팀의 항공편이 예기치 않게 지연됨에 따라, 부득이하게 행사 시작 시간을 기존 오후 7시에서 오후 8시로 변경하게 되었습니다. 현재 새턴 팀은 이동 중이며, 현장에는 오후 9시경 도착할 예정입니다. (교통 상황에 따라 변동될 수 있습니다.) 행사 시작 전까지는 참가자분들을 위해 준비한 피자, 맥주, 음료 및 간식과 함께 자유롭게 네트워킹을 즐기실 수 있도록 준비되어 있습니다. 따라서 오후 8시에 꼭 맞춰 오실 필요는 없으며, 퇴근 후 편하신 시간에 부담 없이 방문해 주시면 됩니다. 행사 운영에는 차질이 없도록 준비하고 있으니…
❤6👍1🔥1
✔️Saturn 예치관련 가이드 Saturn 예치 참여를 위한 가이드를 안내드립니다. 가이드에는 예치 진행 방법과 참여 전 확인해야 할 주요 내용이 정리되어 있으니, 참여를 원하시는 분들은 반드시 전체 내용을 충분히 확인한 뒤 진행해 주세요. 진행 과정에서 혼동이 없도록 단계별 안내와 유의사항까지 꼼꼼하게 확인해 주시기 바랍니다. 👉 가이드 확인하기
❤2🔥2👍1
📢 Surf × Saturn 리서치 이벤트 커피 100명 · 상품권 100만원 · Surf 1년권 10명 Surf를 활용해 Saturn에 대한 정보를 직접 리서치하고, 여러분의 X 계정에 관련 인사이트를 공유해 주세요. ✅이벤트 보상 - 커피 쿠폰 100명 네이버폼 제출 기준 선착순 100명 - 신세계상품권 총 100만원 우수 참여자 10명에게 각 10만원 - Surf 1년 구독권 10명 Saturn 예치 참여자 중 추첨 ✅ 참여 방법 1. Saturn 한국 텔레그램에 참여하고 인사하기 • 공지방 • 커뮤니티 2. Surf를 활용해 Saturn 관련 리서치 작성 후 X에 게시하기 ※ @saturn_credit 태그 필수 3. 작성한 게시물 링크와 X 아이디를 네이버폼에 제출하기 • 네이버 폼 ✅ Surf 1년 구독권 추가 참여 조건 •…
❤10
Digital Dollars on Digital Credit. Powered by Bitcoin. Saturn은 비트코인 기반의 디지털 크레딧 위에서 움직이는 '디지털 달러'를 만들고 있어요. 국채로 뒷받침되는 스테이블코인 USDat, 그리고 예치하면 수익이 붙는 sUSDat까지, 전통 금융의 안정적인 수익 구조를 온체인으로 그대로 옮겨온 셈이죠. Spartan Group이 리드하고 Anchorage와 Susquehanna Crypto가 함께한 시드 투자로 막 출발한 프로젝트입니다. Into Orbit은 이 여정을 함께할 사람들을 직접 만나려고 마련한 Saturn의 첫 오프라인 모임이에요. 무대에서 발표만 듣는 자리가 아니라, Saturn 팀이 직접 여러분 테이블에 앉아 이야기 나누는 저녁. 자료엔 없는 솔직한 뒷이야기와, 옆자리 사람…
👍3
Channel created
Showing the 7 most recent of 7 posts we hold for @Official_Saturn. 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 — 238,030 of 1,345,403entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@Official_Saturn 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.
References a handle that is not a live channel — we have no record it ever was one.
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.
“Saturn 한국 공지방” (@Official_Saturn), 207 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/Official_Saturn.
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.