Telegram RegisterThe public register of Telegram
Telegram profile photo for ᏟИᎻᎢᎬᏦᏟИᏟ | ᎪᏆ ᏴᏫᎢᏚ ☬

Channel

ᏟИᎻᎢᎬᏦᏟИᏟ | ᎪᏆ ᏴᏫᎢᏚ ☬

@sin_teksis

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

434subscribers

+217 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1004352988028
TypeChannel
Username@sin_teksis
CreatedBetween 1 June 2026 and 12 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 September 2026
Last confirmed live18 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/sin_teksis

Growth

217478347.511 August 2026 — 217 subscribers12 August 2026 — 219 subscribers18 August 2026 — 359 subscribers25 August 2026 — 422 subscribers31 August 2026 — 478 subscribers9 September 2026 — 453 subscribers11 September 2026 — 453 subscribers18 September 2026 — 434 subscribers43411 August 202618 September 2026
8 measurements spanning 38 days, net +217. 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 178–517 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 12:55434-19
11 Sept 2026, 00:22453no change
9 Sept 2026, 16:20453-25
31 Aug 2026, 19:56478+56
25 Aug 2026, 05:06422+63
18 Aug 2026, 22:58359+140
12 Aug 2026, 07:15219+2
11 Aug 2026, 23:45217first reading

Engagement

11 posts held, back to 12 August 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
58.0%
avg views ÷ 434 subscribers
Avg views / post
252
5 posts measured
Reaction rate
5.40%
reactions ÷ views · ER floor
Posts in window
5
of 11 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 8 September 2026
Posts held11 (12 August 20268 September 2026)
Views total1,259
Reactions total68
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Sept 2026, 00: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

294 reactions across 11 posts, in 16 distinct kinds. The most used accounts for 23.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54427406423525054816823.1%
custom 59765038448661016055117.3%
custom 53707786800563579804916.7%
custom 52382310457944717024415.0%
custom 5199441345013380337186.12%
custom 5370863282322153542124.08%
custom 535488972342272180182.72%
custom 535505384271303069082.72%
custom 532101131344965236872.38%
custom 529628063835623471462.04%
custom 531669540389313466962.04%
custom 523815485307463969651.70%
custom 546337817925310610351.70%
custom 544055750188600293841.36%
custom 534362951746850329120.68%
custom 580311090411550182210.34%

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

Measured over the 11 most recent posts we hold, published 12 August 2026 to 8 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
3
across the posts below
Posts paid on
2
of 11 we hold a reading for · 18%
Most on one post
2
single highest reading

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

8 Sept 2026, 14:07 UTC64 views9 reactionsread 11 September 2026

Ребят, простите, пожалуйста, но я возьму рест на неделю. У меня сейчас нет вообще сил для писания ботов: сейчас по учебе загруженность, да и мотивации никакой нет.

custom 54427406423525054819

1 Sept 2026, 11:04 UTC207 views2 reactionsread 11 September 2026

Результаты конкурса: 🥳 Победители: 1. Элеонора (@C0c0nut_000) 2. 滚出去 . 黑暗詩人的詩歌⋆ (@Ffteeeygv) 3. 𝚙𝚞𝚜𝚑𝚘𝚕𝚗𝚞𝚑. (@I_narcissistic) 4. Ясяя (@lanaawq) 5. k.k.k³³³' (@KPSccS) 6. 𝓥 𝓫𝓮𝓵𝓸�' 𝓸𝓭𝓮𝔂𝓪𝓷𝓲𝓲🎌 (@Mda_ppts) 7. ⋆Darkness⋆ (@FaithfulDarkness) 8. Иришка (@mooolllkaa)

custom 54427406423525054812

28 Aug 2026, 20:32 UTC316 views7 reactionsread 11 September 2026

Новое оформление! Пока прем не купила

custom 54427406423525054814custom 53708632823221535423

28 Aug 2026, 20:32 UTC296 views40 reactions2 Starsread 11 September 2026
Photo

ㅤㅤㅤ𓂃 ࣪˖ 𝙉𝙀𝙒 𝘽𝙊𝙏 ˖ ࣪ 𓂃 ㅤㅤㅤㅤ ❛ ᜬ𝒶𝓂ℯ ❜ ㅤㅤㅤㅤ ᯓ★ 𐌘иллип ℾрейвс ╭──────── ୨୧ ────────╮ ㅤㅤ𝑪𝒉𝒂𝒓𝒂𝒄𝒕𝒆𝒓.𝑨𝒊 ㅤㅤ𝑯𝒊𝑾𝒂𝒊𝒇𝒖 ㅤㅤ𝑺𝒆𝒂 𝑺𝒐𝒖𝒍 — 40 рк ㅤㅤ𝑪𝒉𝒂𝒊 ╰──────── ୨୧ ────────╯ 𖹭 #филлипгрейвс #shadowcompany #callofduty #cod #секретныедокументы

custom 523823104579447170225custom 53707786800563579806custom 54427406423525054815custom 52381548530746396962custom 52962806383562347141custom 53708632823221535421

24 Aug 2026, 14:31 UTC376 views10 reactionsread 11 September 2026

Ссылка на Sea Soul Ссылка на HiWaifu

custom 52382310457944717027custom 53708632823221535422custom 52381548530746396961

21 Aug 2026, 04:49 UTC526 views60 reactionsread 11 September 2026
Photo

🔡🔡🔡🔡🔡🔡 🔤ame :; Кай 🖤 —· Character.Ai 🩷 —· HiWaifu - сс на 50 реакций 🌟 —· Sea Soul - сс на 30 реакций 💗 —· Chai #гибрид #чернаяпантера #белыйлеопард #авторскийбот #гибриды #отношения

custom 537077868005635798042custom 54427406423525054816custom 53548897234227218014custom 52381548530746396962custom 52382310457944717022custom 52962806383562347142custom 53436295174685032911custom 53708632823221535421

20 Aug 2026, 06:41 UTC397 views18 reactionsread 11 September 2026

Ребята, прошу прощения за то, что так редко выпускаю ботов. Сейчас у меня идёт подготовка к учёбе (поступила ееее), не знаю, как я буду совмещать учёбу и «хобби». Сегодня допишу сюжет и будет ботик 🌟

custom 523823104579447170210custom 53708632823221535424custom 53548897234227218012custom 52962806383562347141custom 53436295174685032911

18 Aug 2026, 19:18 UTC463 views12 reactionsread 11 September 2026
Poll

Какого следующего бота? (Авторский)

  1. Гибриды57%
  2. Грубый муж (фкт брак)63%

The shares total 120%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

custom 54427406423525054816custom 52962806383562347142custom 53548897234227218012custom 53707786800563579801custom 53708632823221535421

15 Aug 2026, 17:24 UTC643 views69 reactionsread 11 September 2026
Photo

🔡🔡🔡🔡🔡🔡 🔤ame :; Алукард 🖤 —· Character.Ai 🩷 —· HiWaifu 🌟 —· Sea Soul 💗 —· Chai #алукард #hellsing #хеллсинг #вампир #мистика #даркромантика #ужасы

custom 597650384486610160536custom 519944134501338033714custom 544274064235250548110custom 53550538427130306903custom 54405575018860029382custom 54633781792531061032custom 53166954038931346691custom 53210113134496523681

12 Aug 2026, 20:07 UTC574 views43 reactions1 Starread 11 September 2026
Photo

🔡🔡🔡🔡🔡🔡 🔤ame :; Джейс 🖤 —· Character.Ai 🩷 —· HiWaifu 🌟 —· Sea Soul 💗 —· Chai #авторскийбот #наркомания #зависимость #бывшийпарень #стекло #отношения

custom 544274064235250548124custom 51994413450133803374custom 53166954038931346693custom 54633781792531061033custom 59765038448661016053custom 53210113134496523682custom 53550538427130306902custom 54405575018860029381

12 Aug 2026, 10:34 UTC490 views24 reactionsread 11 September 2026
Poll

☺️а удачу

  1. 🍙15%
  2. 🤩22%
  3. 🍙🍙47%
  4. 🤩13%
  5. 🤩3%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

custom 597650384486610160512custom 53210113134496523684custom 53550538427130306903custom 53166954038931346692custom 54427406423525054812custom 54405575018860029381

Showing the 11 most recent of 11 posts we hold for @sin_teksis. 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.

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

18 Aug 2026, 19:18 UTCAnonymous Poll65 voters

Какого следующего бота? (Авторский)

  1. Гибриды57%
  2. Грубый муж (фкт брак)63%

The shares total 120%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

12 Aug 2026, 10:34 UTCAnonymous Quiz95 voters

☺️а удачу

  1. 🍙15%
  2. 🤩22%
  3. 🍙🍙47%
  4. 🤩13%
  5. 🤩3%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 11 most recent posts we hold, published 12 August 2026 to 8 September 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Mentions

Named by 6 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“ᏟИᎻᎢᎬᏦᏟИᏟ | ᎪᏆ ᏴᏫᎢᏚ ☬” (@sin_teksis), 434 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/sin_teksis.

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.