Telegram RegisterThe public register of Telegram

Channel

𝖲𝖴𝖫𝖫𝖸'𝗌 𝗋𝖾𝖼. ( 🩹 )

@jakesully_records

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

50subscribers

+0 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003752713606
TypeChannel
Username@jakesully_records
CreatedBetween 1 February 2026 and 16 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/jakesully_records

Growth

5013 Aug 2026, 04:01 — 50 subscribers14 Aug 2026, 09:46 — 50 subscribers13 Aug 2026, 04:0114 Aug 2026, 09:46
2 measurements spanning 1 day. 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 49–51 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 09:4650no change
13 Aug 2026, 04:0150first reading

Engagement

16 posts held, back to 16 March 2026the 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 · 30 days
42.0%
avg views ÷ 50 subscribers
Avg views / post
21.0
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
of 16 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held16 (16 March 20269 August 2026)
Views total84
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 04:01 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

103 reactions across 5 posts, in 12 distinct kinds. The most used accounts for 19.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54111478550605613962019.4%
custom 53100214628018061361716.5%
custom 54632574606073156311514.6%
custom 53458380884363506121312.6%
custom 524032356245099800787.77%
custom 532363860077919578587.77%
custom 532376363586711469376.80%
custom 521298507770470955165.83%
custom 542268224743201002043.88%
custom 540888736223307147521.94%
custom 545884823429634600421.94%
custom 599010970425937756210.971%

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 areTelegram’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 5 of the 16 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 103reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 16 March 2026 to 9 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

9 Aug 2026, 14:01 UTC21 viewsread 13 August 2026
File

🪷🪷🪷🎁🥹🪷#𝖺𝖾𝗌𝗍𝗁𝖾𝗍𝖾🤍🤍🤍

9 Aug 2026, 14:01 UTC21 viewsread 13 August 2026
Photo

🤍🤍 🤍🌴🥹It's been a long day without you .. 🌫️🌫️ .. my 𝔣𝔯𝔦𝔢𝔫𝔡 🤩nd I'll 𝔱𝔢𝔩𝔩 𝛾𝔬𝔲 𝔞𝔩𝔩 about it 🔭🥹when I see 🔠 again ! 🤩 🥹🌟🌟🌟🥹 we've 𝙘𝙤𝙢𝙚 𝙖 𝙡𝙤𝙣𝙜 way .. from where we began 🍼 𝔬𝔥 — i'll tell you all about (!) it when 𝗜 𝘀𝗲𝗲 𝘆𝗼𝘂 again ,, 🫐 🤩hen I see you again ¡ 🤍🤍 🤍🤍

9 May 2026, 18:42 UTC214 views20 reactionsread 13 August 2026
Video

𝗠𝗔𝗥𝗥𝗜𝗔𝗚𝗘 🥹💎 : an intense affection for another person based on personal or familial ties .. 🍼 🤩 .. 🔗 .. @jakesully_records 🥹 @Neytiritetsa 🤩 🪷🪷🪷🪷🪷🪷🪷 ( 🌟🌟 ) 09.05.26

custom 54111478550605613968custom 53100214628018061364custom 54632574606073156314custom 53458380884363506122custom 53236386007791957851custom 53237636358671146931

9 May 2026, 16:21 UTC168 views18 reactionsread 13 August 2026
Photo

✔️ i was a warrior who dreamed he could bring peace. sooner or later, though, you always wake up. 🌟 . 😀😀😀🥹NAVIgation ' #𝗛𝗘𝗔𝗗𝗖𝗔𝗡𝗢𝗡 🥹 #𝗧𝗛𝗢𝗨𝗚𝗛𝗧𝗦 🥹🎁🥹 #𝘔𝘌𝘔𝘖𝘙𝘐𝘌𝘚 nd 🥹 #𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻 🥹 #𝖺𝖾𝗌𝗍𝗁𝖾𝗍𝖾 important links MP POST . . FRIENDS 🖤 🍼 text to me ( anon )

custom 53237636358671146935custom 53100214628018061363custom 53458380884363506123custom 54111478550605613963custom 54632574606073156313custom 53236386007791957851

9 May 2026, 16:19 UTC145 views16 reactionsread 13 August 2026
Photo

🌟🥹🤩 .. my CONNECTions🤩 i see you. 🦴 ( .🔔 )) 🍼 🤩 только дв по аватару 🤩 мне неважно, единственный я или нет🍼✔️ 🪷🪷🤩 взаимная подписка'🤩 🌟 look in comments 🌟🌟🌟 )

custom 53458380884363506125custom 54632574606073156315custom 53100214628018061363custom 53236386007791957853

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

Citation-graph rank — 966,979 of 1,478,351entries 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.

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 4 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.

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

“𝖲𝖴𝖫𝖫𝖸'𝗌 𝗋𝖾𝖼. ( 🩹 )” (@jakesully_records), 50 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/jakesully_records.

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.