- со кьют.☺️ #sinzi
❤6custom 52402793844173910121custom 54002866215033605571

Channel
@sinzi_oske
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
122subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004453864490 |
|---|---|
| Type | Channel |
| Username | @sinzi_oske |
| Created | 26 July 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/sinzi_oske |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 06:33 | 122 | no change |
| 11 Aug 2026, 04:16 | 122 | first reading |
15 posts held, back to 26 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 9 August 2026 |
|---|---|
| Posts held | 15 (26 July 2026 – 9 August 2026) |
| Views total | 2,003 |
| Reactions total | 318 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 04:16 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.
318 reactions across 14 posts, in 12 distinct kinds. The most used accounts for 39.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 124 | 39.0% | |
| custom 5400286621503360557 | 83 | 26.1% | |
| 🍓 | 24 | 7.55% | |
| custom 5240279384417391012 | 23 | 7.23% | |
| ❤🔥 | 19 | 5.97% | |
| custom 5382268576566635117 | 14 | 4.40% | |
| 🍌 | 12 | 3.77% | |
| custom 5402352324679064423 | 8 | 2.52% | |
| custom 5399848685163025302 | 7 | 2.20% | |
| custom 5469681864098728530 | 2 | 0.629% | |
| 🌭 | 1 | 0.314% | |
| 💔 | 1 | 0.314% |
Custom emoji. 6 of the rows above are 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 14 of the 15 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 318reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 26 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.
- со кьют.☺️ #sinzi
❤6custom 52402793844173910121custom 54002866215033605571
➖🤩втор :: Ода. Решил сделать не со всеми, а более комфортными для меня. 🐺 #Plama_51. #Интерактив
❤7custom 52402793844173910122custom 54002866215033605572
- я оч постараюсь вернуть актив честна..просто блин взрослая жизнь и все такое.😳 главное тоже меня активом радуйтесь, я все таки стараюсь. #sinzi
❤7custom 54002866215033605574custom 52402793844173910121
- по поводу заказов. список людей в очереди на ос : 1. @Bloxastaaa 2. @llwleksk 3. @Catho_lic 4. @Gggoicyu если хотите чет купить пишите (приму и другую валюту) @sinz235 #sinzi
❤9custom 54002866215033605573custom 52402793844173910121
- я доделал две обры, скора будет видео. #sinzi
❤7custom 54002866215033605572❤🔥1
🥹𝔭𝔬𝔰𝔱 :; 𝔰𝔨𝔢𝔱𝔠𝔥 - все что у меня есть на сегодня. сор гайс, от скуки я рисовал только эти скетчи.. со мной и моим другом лешей, ну и еще с моей беби герл😘😘😘😏😉 ночью тоже буду работать.😞😞 - давайте немножечка реакций что бы автор не умер. #sinz #щп (?)
❤13custom 54002866215033605576❤🔥4custom 52402793844173910121custom 53822685765666351171
- мне теперь надо из джейка бутчера сделать.😳 слава богу у него костюм не такой сложный как хоума.
❤7custom 54002866215033605575custom 53998486851630253022custom 54696818640987285302🍌1💔1custom 54023523246790644231
🖤𝔭𝔬𝔰𝔱 : 𝔰𝔭𝔬𝔦𝔩𝔢𝔯. - боже как это плохо. я честно пытался..очень. а еще я рад что нас уже 100, спасибо всем большое. ❤️ - как вам костюмчик? давайте много-много реакций и будет видео. #sinzi
❤17custom 540028662150336055713custom 53822685765666351177🍓2custom 54023523246790644232🍌1custom 53998486851630253021
🖤🔤𝔫𝔣𝔬𝔯𝔪𝔞𝔱𝔦𝔬𝔫𝔞𝔩 𝔭𝔬𝔰𝔱 . 🌟 🌟🌟🤩🤩🤩🤩🌟🌟 🥹хэштеги к постам. :; #sinzi , #jake , #osiris , #stone , #story #au (основаная ау), #au2 (другая версия ау) , #oc , #auction , #заказ , #video #interactive 🥹другие мои соцсети. :; тт акк , акк в пинтерест 🥹аноним для общения. :; http://t.me/anonaskbot?start=hwqbz 🎀🎀🎀🎀🎀🎀🎀🎀 🖤🔤𝔯𝔦𝔠𝔢 𝔩𝔦𝔰𝔱 . 🌟 чиби скетч :; 25-30 зв. чиби полноценн :; 60 зв. ос на заказ :; 50-75 зв. особенности :; 30 зв.…
🍓9❤🔥5custom 52402793844173910124❤3custom 54002866215033605572🍌1custom 53822685765666351171custom 53998486851630253021
🖤𝔭𝔬𝔰𝔱 : 𝔭𝔦𝔨𝔠𝔥𝔞 𝔤𝔞𝔠𝔥𝔞 (недавняя.) - что б не скучали. пикчуха осам с аукциона. когда лучше будет сделать следующий аук? - реакции если нравитца. #sinzi #pic
❤13custom 524027938441739101210custom 53822685765666351175custom 54002866215033605573🍌1custom 53998486851630253021custom 54023523246790644231
- я сегодня наконец то начну видео. а позже выложу и прайс. только не забывайте пожалуйста активничать.❤️🩹 #sinzi
❤10custom 54002866215033605577🍌4
🖤𝔭𝔬𝔰𝔱 : 𝔭𝔦𝔨𝔠𝔥𝔞 𝔤𝔞𝔠𝔥𝔞 - окак умею.☝️ пикча с челом из прошлой игры. осталось еще две пикчи, но сегодня я делаю видео. давайте актив.. - как вам? реакции? #sinzi #pic
custom 540028662150336055717❤5custom 54023523246790644234🍓2🍌1custom 53998486851630253021
Showing the 12 most recent of 15 posts we hold for @sinzi_oske. 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 — 1,161,465 of 1,336,469entries 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.
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.
@sinzi_oske named 1 handle 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“𝔰𝔦𝔫𝔷𝔦.𝔬𝔣𝔣 #sinzi [+18]” (@sinzi_oske), 122 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/sinzi_oske.
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.