8 Aug 2026, 10:21 UTCviews —
Posted without readable text
Channel
₊ ׁ 𝗉𝖺𝗒ment @saheex ˳ ֹ 𖦹︎
@jsuccess
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 17 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002767290370 |
|---|---|
| Type | Channel |
| Username | @jsuccess |
| Description | belongs @saheex |
| Created | 28 June 2025 — measured — dated from the channel’s first post |
| First recorded | 17 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/jsuccess |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 04:22 | 4 | no change |
| 17 Sept 2026, 03:47 | 4 | first reading |
Engagement
13 posts held, back to 28 June 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 13 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 5
Lifetime counters from Telegram’s own channel header, read 17 September 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
246 reactions across 3 posts, in 10 distinct kinds. The most used accounts for 13.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6233116806383408454 | 32 | 13.0% | |
| custom 6179382620867008257 | 30 | 12.2% | |
| custom 5064758381860881566 | 29 | 11.8% | |
| custom 5053225793375700275 | 24 | 9.76% | |
| custom 4940480187436369099 | 23 | 9.35% | |
| custom 5382044658446653078 | 23 | 9.35% | |
| custom 6111689929077559148 | 22 | 8.94% | |
| custom 6179170127360037329 | 22 | 8.94% | |
| custom 5287454910059654880 | 21 | 8.54% | |
| custom 5845952043251929742 | 20 | 8.13% |
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 4 of the 13 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 246 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 28 June 2025 to 8 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.
Recent posts
8 Aug 2026, 10:20 UTCviews —
Channel photo updated
8 Aug 2026, 10:09 UTC≈1,340 viewsread 17 September 2026
ch pay sebelumnya @cibuh JANGAN SAMPE SALAH TF, SALAH TF? HANGUS.
8 Aug 2026, 09:36 UTC≈1,370 views94 reactionsread 17 September 2026
Sticker
Sticker, posted without a caption
custom 617938262086700825715custom 506475838186088156612custom 505322579337570027511custom 61791701273600373299custom 49404801874363690998custom 52874549100596548808custom 53820446584466530788custom 61116899290775591488
8 Aug 2026, 09:35 UTC≈1,310 views0 reactionsread 17 September 2026
Posted without readable text
8 Aug 2026, 09:23 UTCviews —
Channel photo updated
8 Aug 2026, 04:52 UTCviews —
Channel photo removed
28 Jun 2025, 10:22 UTC≈1,390 viewsread 17 September 2026
😂😂😂😂😂😂😂😂
28 Jun 2025, 10:11 UTC≈1,410 views76 reactionsread 17 September 2026
Photo
’QRIS | SCAN LUAR DANA ONLY’ ﹙.. 🤩﹚this payment 🤑. ⠟ 🤩 a.n : tincshop ⠟ 🤩fee : no fee Ash falls gently upon cobblestone catching on collarbones like forgotten vows. SHADOWS—WRITE EPILOGUES NO (..) ONE “READS ALOUD..
custom 506475838186088156611custom 62331168063834084549custom 53820446584466530788custom 49404801874363690997custom 50532257933757002757custom 52874549100596548807custom 61116899290775591487custom 61791701273600373297
28 Jun 2025, 09:49 UTC≈1,410 viewsread 17 September 2026
😂😂😂😂😂😂😂😂😂😂😂😂😂
28 Jun 2025, 09:49 UTC≈1,390 views76 reactionsread 17 September 2026
Photo
’QRIS | SCAN DANA ONLY’ ﹙.. 🤩﹚this payment 🤑. ⠟ 🤩 a.n : toko scathie ⠟ 🤩fee : no fee Ash falls gently upon cobblestone catching on collarbones like forgotten vows. SHADOWS—WRITE EPILOGUES NO (..) ONE “READS ALOUD..
custom 623311680638340845415custom 49404801874363690998custom 61793826208670082578custom 53820446584466530787custom 58459520432519297427custom 61116899290775591487custom 50532257933757002756custom 50647583818608815666
28 Jun 2025, 08:32 UTCviews —
Channel name was changed to «that flirtatious face overflows, showing an adorable pose like a sweet, seductive strawberry with ease.»
Showing the 12 most recent of 13 posts we hold for @jsuccess. 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.
Mentions
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“₊ ׁ 𝗉𝖺𝗒ment @saheex ˳ ֹ 𖦹︎” (@jsuccess), 4 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/jsuccess.
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.