Telegram RegisterThe public register of Telegram
Telegram profile photo for 𓐇۪ۜܵ ۗ í᭢𝕗ᨵׁׅׅ ƙׁׅ𝓸ᡶo̶p░ᥲ𝚑ꪱׁׁׁׅׅׅ .ֵ۫ ꒱

Channel

𓐇۪ۜܵ ۗ í᭢𝕗ᨵׁׅׅ ƙׁׅ𝓸ᡶo̶p░ᥲ𝚑ꪱׁׁׁׅׅׅ .ֵ۫ ꒱

@info_kotopah1

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

145subscribers

+11 since we began measuring on 14 October 2026

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

Register entry

Telegram ID-1004371887092
TypeChannel
Username@info_kotopah1
CreatedBetween 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 October 2026
Last confirmed live14 October 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 October 2026
On Telegramt.me/info_kotopah1

Growth

134145139.514 Oct 2026, 05:47 — 134 subscribers14 Oct 2026, 06:22 — 134 subscribers14 Oct 2026, 18:20 — 145 subscribers14 Oct 2026, 05:4714 Oct 2026, 18:20
3 measurements taken within a single day, net +11. 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 132–147 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Oct 2026, 18:20145+11
14 Oct 2026, 06:22134no change
14 Oct 2026, 05:47134first reading

Engagement

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

ERR · 30 days
63.9%
avg views ÷ 145 subscribers
Avg views / post
92.6
20 posts measured
Reaction rate
2.34%
reactions ÷ views · ER floor
Posts in window
20
of 20 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 14 of 20 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 13 October 2026
Posts held20 (6 October 2026 – 13 October 2026)
Views total1,852
Reactions total29
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Oct 2026, 06: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

29 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 31.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5341501185079654476931.0%
custom 5341274604079952751724.1%
custom 5346104071466006131517.2%
custom 5341480401732907875413.8%
custom 5341763298343794558310.3%
custom 534596667116723769613.45%

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

Measured over the 20 most recent posts we hold, published 6 October 2026 to 13 October 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

13 Oct 2026, 16:57 UTC49 viewsread 14 October 2026
Photo

Привет распишитесь пожалуйста🥺 Только не расписывайтесь на всб аву и не перекрывайте полностью других.. Акт!!

13 Oct 2026, 13:44 UTC339 viewsread 14 October 2026
Photo

──РОЗЫГРЫШ НА ЗВЁЗДЫ ОТ─── 𝂅˛ֺ ꒰ۭ͡⬦͡ ꠥ ‌፝ ๋ 𑀺ְֿؗ ⷭ ƙָׂ𐐫𝕥𐐫ꪀ𝕒✗𐐫ℬִׄ 𑀺ְֿؗ ⷭ౬ 𑀹꤭𓈒‌ ┉̸ۖ ⋮ۡ́̐ ‌ྀິ ꠥ 𓏲𝄞 В ⳡ𝕖ɕ𝕥ь 𝟭00 ꪀ𐐫∂ꪀυɕⳡυƙָׂ𐐫ℬִׄ ⏤͟͟͞͞☆ ꪀ℘υʓ𐐫ℬִׄы𝕖 ຕ᳕ᥱ۫᥋ꭑ⍺ִ:: 1 ຕ᳕ᥱ۫᥋ꭑ𝑜 - 100 звезд 2 ຕ᳕ᥱ۫᥋ꭑ𝑜 - 50 звезд 3 ຕ᳕ᥱ۫᥋ꭑ𝑜 - 25 звезд ᥡɕᱤ𐐫ℬִׄυя̸ :: 01.Быть подписанным на мое инфо 02.Рт желательно не стикером в свое инфо/тгк 03.Доки, юз и порядковый номер в коммы Прошу не путаться!! …

12 Oct 2026, 22:10 UTC35 viewsread 14 October 2026
Forwarded from @sandjisinfoPhoto

🤩🤩ини конкурс! 🤩 🤩🤩🤩 🤍а авторег аккаунт!🤍 🤩🤩🤩🤩 🤩🤩🤩 🤩словия:🤩 🤩 подписка на инфо без дальнейшей отписки🤩 🤩 рт в свое активное инфо от 25+ дпд, НЕ стикером 🤩 порядковый номер 🤩 доки 🤩 🤩рошу не путаться!! 🤩езы на 70 участников 🤩

12 Oct 2026, 15:26 UTC35 views0 reactionsread 14 October 2026
Forwarded from @maowenaIPhoto

𓏏ㅤшиппɐ໌ринг 𝒴словия: пдп&𝒫т не стикером ℬ комментарии: скрин профиля & пруфы рт ℳеста: 18/20 бронь: Локи Открыто/закрыто

12 Oct 2026, 13:02 UTC49 views5 reactionsread 14 October 2026
Photo

‍‍ 𝕆ꪀ 𝚝𝕙𝙞క ძᴀᥡ ║ 𝟷𝟸.𝟷𝟶.𝟸𝟶𝟸𝟼 ──────────────────────── 𓍯 𝙵𝚎𝚖𝚒𝚡𝚡 𝚊𝚗𝚍 𝙺𝚘𝚝𝚘𝚙𝚊𝚑𝚒 𓏲 ⏤͟͟͞͞ ♡ 𝚐𝚘𝚝 𝚖𝚊𝚛𝚛𝚒𝚎𝚍 !! ➥ ᯓ 𝑐𝑜𝑛𝑔𝑟𝑎𝑡𝑢𝑙𝑎𝑡𝑒 𝑡ℎ𝑒𝑚 𝑖𝑛 𝑡ℎ𝑒 𝑐𝑜𝑚𝑚𝑒𝑛𝑡𝑠

custom 53414804017329078752custom 53461040714660061312custom 53415011850796544761

11 Oct 2026, 11:39 UTC90 views3 reactionsread 14 October 2026
Photo

𐂂​ .☲˚ ࣳ᧗ᤢִׄью̷̷ ┆ 𐐼̸ׄห᧗ᤢִׄью̷̷ ຖ𑄹ɕׁ݂ⲧ̸ּׁ͠ !! ٩ꈍᴗꈍ ─────── ᦸֺ݂ ӄִׄׄ𐐼̸ׄӄִׄׄ ࣳ᧗ᤢִׄью̷̷ :: ──────── Стараюсь участвовать во всех интерактивах, розыгрышах, яикто и тд, пишу коммы и все такое.. ຖ𐐼̸ׄຖӄִׄׄᥲ ➥ если мы мью и вас нету в папке/вы по случайности оказались там, сообщите пожалуйста...

custom 53415011850796544761custom 53417632983437945581custom 53461040714660061311

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

Polls

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

6 Oct 2026, 09:37 UTCAnonymous Poll33 voters

༅ ⏤͟͟͞͞ 𝕜τ𝗼 ϐƅɩ ⲙн͜͡𝗲ׅິ?◌▒​᭄˙

  1. 𐂂 ӡϰa⃟ᴋ𑄜⃨݁ⲙƅɩꪌ ▒​᭄୧18%
  2. 𐂂 ꪀׄթֵᦢ࣪࣪᥊ׁׅ𐒀ѫ𝐮𑪑⃪⃕ꪌ ░​᭄༅42%
  3. 𐂂 ɕ ф͜͡ꪒ𝒚ַ∂ꪖ ▒​᭄܀9%
  4. 𐂂 ꪎℴִ࣪ⲧ𝗲ׅິꪒꪊ 𐴳ƅɩ ꪀ𑄜⃨݁ვִห֞𑜅݂݁ᴋ𑄜⃨݁ⲙꪊτь𝑐ꪯִ ░​᭄᭕24%
  5. 𐂂 η𝕠მթ𝔂ɾꪋ ▒​᭄࿐6%

Shares as published, totalling 99%. 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 20 most recent posts we hold, published 6 October 2026 to 13 October 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.

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.

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

“𓐇۪ۜܵ ۗ í᭢𝕗ᨵׁׅׅ ƙׁׅ𝓸ᡶo̶p░ᥲ𝚑ꪱׁׁׁׅׅׅ .ֵ۫ ꒱” (@info_kotopah1), 145 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/info_kotopah1.

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.