‼️جهت عضویت در تیم: @TITANPING_AD

Channel
𝑺𝑺 𝑶𝑵𝑬 𝑬𝑺𝑷𝑶𝑹𝑻𝑺
@SsOne_Esports
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
80subscribers
+12 since we began measuring on 30 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002747946438 |
|---|---|
| Type | Channel |
| Username | @SsOne_Esports |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 September 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 October 2026 |
| On Telegram | t.me/SsOne_Esports |
Topic
Sports — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 54% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Oct 2026, 06:56 | 80 | +12 |
| 30 Sept 2026, 01:22 | 68 | no change |
| 30 Sept 2026, 00:47 | 68 | first reading |
Engagement
14 posts held, back to 5 November 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 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 36.3%
- avg views ÷ 80 subscribers
- Avg views / post
- 29.0
- 1 post measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 1
- of 14 held
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 15 September 2026 |
|---|---|
| Posts held | 14 (5 November 2025 – 15 September 2026) |
| Views total | 29 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Sept 2026, 01:22 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.
Reaction mix
89 reactions across 12 posts, in 9 distinct kinds. The most used accounts for 20.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5963030377839727876 | 18 | 20.2% | |
| custom 5400238977431122726 | 17 | 19.1% | |
| custom 4929746480048112940 | 14 | 15.7% | |
| custom 5397699333204226798 | 14 | 15.7% | |
| custom 5465146683576822104 | 8 | 8.99% | |
| custom 5979027185397142248 | 6 | 6.74% | |
| custom 5352542184493031170 | 5 | 5.62% | |
| custom 6028419919186498613 | 4 | 4.49% | |
| custom 4999020196543857894 | 3 | 3.37% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 13 of the 14 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 89 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 5 November 2025 to 15 September 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.
Telegram Stars
- Stars received
- 1
- across the posts below
- Posts paid on
- 1
- of 13 we hold a reading for · 8%
- Most on one post
- 1
- single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @SsOne_Esports. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 14 most recent posts we hold for this entry, published 5 November 2025 to 15 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
𝑺𝑺 𝑶𝑵𝑬 𝑬𝑺𝑷𝑶𝑹𝑻𝑺 pinned a file
𝑪𝒐𝒎𝒊𝒏𝒈 𝑺𝒐𝒐𝒏‼️
custom 49297464800481129402custom 53976993332042267982custom 54002389774311227261
Update 🌿
custom 49297464800481129403custom 54002389774311227262custom 53525421844930311701custom 53976993332042267981custom 59630303778397278761custom 60284199191864986131
✅ 𝑺𝑺 𝑶𝑵𝑬 𝑬𝑺𝑷𝑶𝑹𝑻𝑺 🤩 Accepting🔹player 🔵 🔘At least 3 years of experience ✅ 🔘Free time✅ 🔘game play✅ 🔘FPS ANDROID: +90✅ 🔘FPS IOS: +60✅ 🔘Id card:✅ 🔘+AGE: +17✅ ✅Awards in the clan🔥 🌹CLAN (RANK UP . SCRIM T1)🎁 ❤️ @TITAN_PLAY_AD
custom 49297464800481129406custom 54002389774311227262custom 59790271853971422482custom 59630303778397278761
Ss¹个TEST | اکانت تست کلن ✅
custom 53976993332042267984custom 59630303778397278763custom 49297464800481129401custom 53525421844930311701
AFK
custom 53976993332042267983custom 49297464800481129401
🤩🩸🩸🩸🩸🩸 𝐑𝐎𝐒𝐓𝐄𝐑🤩 💦 𝐎𝐖𝐍𝐄𝐑 MMD.TITAN 🤩 💦 𝐌𝐀𝐍𝐀𝐆𝐄𝐑 CHAVOSHI ❤️ ✅𝐒𝐬¹个 ✅𝐒𝐬¹个 ✅𝐒𝐬¹个 ✅𝐒𝐬¹个 ✅𝐒𝐬¹个 ❤️🔥 AGENT : 𝑺𝑺 𝑶𝑵𝑬 𝑬𝑺𝑷𝑶𝑹𝑻𝑺 ✅ 🚀 CHANNEL 🚀 REC 🚀 PUBLIC
custom 54002389774311227264custom 59630303778397278763custom 49297464800481129401custom 49990201965438578941custom 53525421844930311701custom 53976993332042267981
✅🔠🔠🔠🔠 𝐑𝐎𝐒𝐓𝐄𝐑✅ 💦 𝐎𝐖𝐍𝐄𝐑 MMD.TITAN 💦 𝐌𝐀𝐍𝐀𝐆𝐄𝐑 CHAVOSHI ❤️ ➡️AFK ❤️🔥 AGENT : 𝑺𝑺 𝑶𝑵𝑬 𝑬𝑺𝑷𝑶𝑹𝑻𝑺 ✅ 🚀 CHANNEL 🚀 REC 🚀 PUBLIC
custom 54651466835768221042custom 53976993332042267981custom 59630303778397278761custom 59790271853971422481
✨Result DEATHLESS Scrim😈 🥉SS ONE TEAM #𝑹𝒆𝒔𝒖𝒍𝒕𝒔 #Event ⚜️ SS ONE ESPORT
custom 54651466835768221043custom 54002389774311227262custom 59790271853971422482custom 53525421844930311701custom 60284199191864986131
🤎 ROSE PLAY WEEKLY EVENT OVERALL STANDING RESULT❤️ 🥈 SS ONE TEAM #𝑹𝒆𝒔𝒖𝒍𝒕𝒔 #Event ⚜️ SS ONE ESPORT
custom 59630303778397278763custom 54002389774311227261custom 59790271853971422481custom 60284199191864986131
دیزاینر و استریمر های عزیز از این پی انجی برای ریزالت یا لایو پوینت استفاده کنید 😀🌺
custom 59630303778397278763custom 53525421844930311701custom 60284199191864986131
Showing the 12 most recent of 14 posts we hold for @SsOne_Esports. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Mentions
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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“𝑺𝑺 𝑶𝑵𝑬 𝑬𝑺𝑷𝑶𝑹𝑻𝑺” (@SsOne_Esports), 80 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/SsOne_Esports.
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.