Telegram RegisterThe public register of Telegram

Channel

︎ ︎︎໋ ۪✿᮫ ᪾ ︎ ︎︎ ︎ ︎︎𝚂𝙰𝙽𝙹𝙴⵿𝚃 ︎ ︎︎ ︎︎ ︎₍ᲘᲘ₎ᵗ᷒ᰰ

@sanjetcom

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

581subscribers

+8 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003603892517
TypeChannel
Username@sanjetcom
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/sanjetcom

Growth

5735815779 Aug 2026, 19:47 — 573 subscribers9 Aug 2026, 20:00 — 573 subscribers10 Aug 2026, 16:52 — 581 subscribers9 Aug 2026, 19:4710 Aug 2026, 16:52
3 measurements taken within a single day, net +8. 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 572–582 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 16:52581+8
9 Aug 2026, 20:00573no change
9 Aug 2026, 19:47573first reading

Engagement

18 posts held, back to 22 July 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
83.8%
avg views ÷ 581 subscribers
Avg views / post
487
18 posts measured
Reaction rate
13.6%
reactions ÷ views · ER floor
Posts in window
18
of 18 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. It is computed over the 15 of 18 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held18 (22 July 20269 August 2026)
Views total8,767
Reactions total1,111
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 20:00 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

1,111 reactions across 15 posts, in 21 distinct kinds. The most used accounts for 8.37% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5375269875818210383938.37%
custom 5375511957354881568847.56%
custom 5350652050990467645776.93%
custom 5433885953091480496766.84%
custom 5219745317573920876746.66%
custom 5339264696824406793746.66%
custom 5350409260784195591726.48%
custom 5350478100520013729716.39%
custom 5434009021084376728716.39%
custom 5339130994492482056706.30%
custom 5434094314839910224595.31%
custom 5339372513388436527575.13%
custom 5431718819968099424322.88%
custom 5449588353525655052322.88%
custom 5445235966811873748302.70%
custom 5429590431744701336272.43%
custom 5431767855609718266272.43%
custom 5444864203032667625221.98%
custom 5445399532051405591221.98%
custom 5449616107604320951211.89%
1 further kind201.80%

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 15 of the 18 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 1,111reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 22 July 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.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
3
of 18 we hold a reading for · 17%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @sanjetcom. 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 18 most recent posts we hold for this entry, published 22 July 2026 to 9 August 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

9 Aug 2026, 18:25 UTC29 viewsread 9 August 2026

не забываем ставить реакции ! все итоги яикто я закинула в архив. еще раз спасибо всем, было круто

8 Aug 2026, 10:25 UTC267 views73 reactions1 Starread 9 August 2026
Photo

ㅤ ㅤ۪ㅤㅤٟ₍𑊃᩹᷒ ᪽᤹ᵔ₎ㅤ ׄㅤ🤩᷼᪾‌✿ㅤㅤִㅤ ㅤ֪🤩ֵ۫ㅤ𝐈 𝐬𝐞𝐞 𝐲𝐨𝐮 𝐭𝐡𝐞𝐫𝐞 𝐫𝐞𝐣𝐞𝐜𝐭𝐢𝐧𝐠 ㅤ ۪ㅤ𝐚𝐥𝐥 𝐲𝐨𝐮𝐫ㅤ࣪ 𝐞𝐚𝐫𝐭𝐡𝐥𝐲 𝙿𝙾⵿𝚆𝙴𝚁 ࡙🤩ᰰ ㅤ ㅤㅤ ㅤ ᅠ ᷼︵ㅤ۪ ㅤ ㅤ۪ ♡ิ‌ㅤ ໋ㅤ𝐏𝐫𝐨𝐭𝐞𝐜𝐭𝐢𝐧𝐠 𝐚𝐧𝐝 𝐝𝐢𝐬𝐬𝐞𝐜𝐭𝐢𝐧𝐠 ㅤ’𝐭𝐢𝐥 𝐲𝐨𝐮’𝐯𝐞 𝐞𝐦𝐩𝐭𝐢𝐞𝐝 𝐞𝐯𝐞𝐫𝐲 𝐡𝐨𝐮𝐫 ᜔🤩۪᪾ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤㅤ ㅤ ᜔ㅤ ㅤ ︶‎‌ㅤ ໋ ㅤֵ֪۫🤩🤩 ᰰᩙㅤ𝐖𝐞 𝐣𝐮𝐦𝐩 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐩𝐨𝐧𝐝, ㅤ 𝐭𝐡𝐞𝐧 𝐰𝐞 𝐜𝐨𝐦𝐞 𝐮𝐧𝐝𝐞𝐫 ‌፝֟ ㅤ᜔ ּㅤ₍֖𐍷 ִ֕ ׄ ֥𐍷₎ ꠥ 𝐭𝐡𝐞 𝐬𝐡𝐨𝐰𝐞𝐫 ꪳ🤩ְ ֪ @sanjetcom ♡‌& @she1vyn ㅤㅤ۫ㅤ₍‌֖ᴖ ֛֭֟ׄᴖ֥₎ㅤㅤִ🤩‌𝟏֑𝟏‌ ׅ❲ㅤㅤׄㅤ ㅤ᪾ 𐦖ּ ְㅤ𝐘𝐨𝐮 𝐥𝐚𝐲 𝐮𝐩𝐨𝐧 𝐦

custom 544958835352565505232custom 544961610760432095121custom 544945601699333339720

7 Aug 2026, 11:59 UTC286 views72 reactionsread 9 August 2026

🤩𝗋𝗈𝗓𝖾𝗇 ㅤִ ( 𝗁𝖾𝖺𝗋𝗍 ) 👋 ֩᷼͝ᰰ(ㅤ ㅤ ͝ ︶ ℴ𝖿 𝗆𝗂𝓃e ੭👋👋ㅤִㅤ

custom 533926469682440679330custom 533913099449248205621custom 533937251338843652721

7 Aug 2026, 11:59 UTC299 views65 reactionsread 9 August 2026
File

File, posted without a caption

custom 533913099449248205625custom 533926469682440679322custom 533937251338843652718

7 Aug 2026, 11:59 UTC300 views64 reactionsread 9 August 2026

ㅤִ 🫰🫰🫰ㅤ᷼⏜ ᷼𝒮i𝗅𝖾n𝗍 𝗋𝗎𝓁𝖾𝗋𖫲 ⃟

custom 533913099449248205624custom 533926469682440679322custom 533937251338843652718

5 Aug 2026, 20:08 UTC349 views74 reactionsread 9 August 2026
Photo

ㅤׅ ㅤٕ₍֖Ი𑪏 ׅ Ი𑪏֥₎ㅤㅤ۫🤩🤩𓈅 ㅤㅤׅ ㅤ ܹ🤩ᩙ᜔ㅤ𝐉𝐚𝐜𝐤𝐩𝐨𝐭 𝐒𝐚𝐝 𝐆𝐢𝐫𝐥, 𝐬𝐭𝐢𝐥𝐥 ㅤ 𝐮𝐧𝐚𝐛𝐥𝐞 𝐭𝐨 𝐜𝐨𝐦𝐩𝐫𝐞𝐡𝐞𝐧𝐝 ㅤ ㅤ ㅤ 𝐞𝐚𝐜𝐡 𝐨𝐭𝐡𝐞𝐫 ㅤ ㅤㅤ ㅤ ㅤ ㅤ ᷼ ᷼ ㅤ 𔖳ㅤ ׄ ㅤٕ₍ᐢ ︧ ︨᪲ ׅᐢ₎ㅤ𝐃𝐮𝐫𝐢𝐧𝐠 𝐭𝐡𝐞𝐬𝐞 𝐝𝐚𝐲𝐬 ㅤ ㅤ𝐰𝐡𝐞𝐫𝐞 𝐰𝐞 𝐝𝐫𝐚𝐰 𝐭𝐡𝐞 '𝐞𝐧𝐝 𝐫𝐨𝐥𝐥' ㅤ ㅤ ㅤ 𝐰𝐢𝐭𝐡 𝐩𝐨𝐢𝐧𝐭𝐬 𝐚𝐧𝐝 𝐥𝐢𝐧𝐞𝐬 🤩⁠⁠⁠⁠ ㅤㅤ ㅤ ㅤ ㅤ ㅤ ‌ ‌ ㅤ𝐓𝐡𝐞 𝐭𝐡𝐨𝐮𝐠𝐡𝐭𝐬 𝐈 𝐡𝐨𝐥𝐝 𝐜𝐥𝐨𝐬𝐞 𝐭⃨𝐡𝐚𝐭 ㅤ𓉳 𝐈'𝐦 𝐮𝐧𝐚𝐛𝐥𝐞 𝐭𝐨 𝐭𝐞𝐥𝐥 𝐚 𝐬𝐨𝐮𝐥 ㅤ ㅤ𝐚𝐫𝐞 𝐰𝐡𝐚𝐭 𝐫𝐞𝐚𝐥𝐥𝐲 𝐡𝐚𝐯𝐞 𝚆𝙾𝚁𝚃𝙷 ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤ ㅤㅤ𝅄✿𝆬 ㅤ𝐓𝐡𝐞 𝐚𝐧𝐬𝐰𝐞𝐫 ㅤ ㅤ 𝐈 𝐰𝐚𝐬 𝐥𝐨𝐨𝐤𝐢𝐧𝐠 𝐟𝐨𝐫 🤩🤩

custom 544523596681187374830custom 544486420303266762522custom 544539953205140559122

1 Aug 2026, 15:12 UTC570 views71 reactionsread 9 August 2026

ּ🤩ᰰᩙ ㅤㅤ𝓶𝔂 𝓵𝓸𝓿𝓮 𝓶𝓲𝓷𝓮ㅤ 𝃣ㅤ᷒ᰰ𐇽᳝ ㅤㅤ᮫ㅤ ㅤ 𝓪𝓵𝓵 𝓶𝓲𝓷𝓮 ㅤ🤩🤩

custom 543388595309148049631custom 543400902108437672820custom 543409431483991022420

1 Aug 2026, 15:12 UTC564 views69 reactionsread 9 August 2026

ㅤּ ㅤ Იֵ۫𐑼ּ ֻㅤ 𝃣🤩🤩🤩 ࣯ㅤ ㅤ ּ‌ ‌፝֟

custom 543400902108437672830custom 543409431483991022421custom 543388595309148049618

1 Aug 2026, 15:12 UTC557 views66 reactionsread 9 August 2026

‌ㅤִ𓎩᪾᷒‌𝃣 ㅤ𝓼𝓸𝓶𝓮𝓽𝓲𝓶𝓮𝓼 🤩᷒͡ㅤۣ₍‌⁽֨ ՟ִ ⁾‌₎ ‌

custom 543388595309148049627custom 543400902108437672821custom 543409431483991022418

31 Jul 2026, 06:19 UTC625 views86 reactions2 Starsread 9 August 2026
Photo

₊ ˖ 🤩ㅤ𝐧݀𝐞𝐰 𝐞𝐦𝐨̤𝐣𝐢 𝐩͝𝐚𝐜𝐤 𝐟𝐨𝐫 𝐮ㅤ ⃘♡゙۪ ㅤ𝟅𝟈ㅤ #emoji ㅤ #loveliveㅤ #rinaㅤ ㅤㅤ ㅤ ᷼︵ㅤ ㅤ 𝓭𝓸𝔀𝓷𝓵𝓸𝓪𝓭 𓏼 ᪶

custom 543171881996809942432custom 542959043174470133627custom 543176785560971826627

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

Citation-graph rank

Citation-graph rank — 270,286 of 1,169,250entries 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 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.

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

“︎ ︎︎໋ ۪✿᮫ ᪾ ︎ ︎︎ ︎ ︎︎𝚂𝙰𝙽𝙹𝙴⵿𝚃 ︎ ︎︎ ︎︎ ︎₍ᲘᲘ₎ᵗ᷒ᰰ” (@sanjetcom), 581 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/sanjetcom.

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.