Telegram RegisterThe public register of Telegram

Channel

— бредни рыбки.

@koi_kerr

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

201subscribers

-1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001981790184
TypeChannel
Username@koi_kerr
Created5 April 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/koi_kerr

Growth

201202201.56 August 2026 — 202 subscribers7 August 2026 — 202 subscribers14 August 2026 — 201 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net -1. 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 201–202 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 20:45201-1
7 Aug 2026, 04:01202no change
6 Aug 2026, 21:01202first reading

Engagement

8 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
72.2%
avg views ÷ 201 subscribers
Avg views / post
145
8 posts measured
Reaction rate
14.6%
reactions ÷ views · ER floor
Posts in window
8
of 8 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 5 August 2026
Posts held8 (22 July 20265 August 2026)
Views total1,161
Reactions total170
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 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

170 reactions across 8 posts, in 14 distinct kinds. The most used accounts for 25.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
4425.9%
🎉2011.8%
custom 5305401680014115120158.82%
custom 5312227830451424098148.24%
custom 5305534068086046854137.65%
custom 5314385269833627000137.65%
❤‍🔥137.65%
custom 5451802391986855290127.06%
custom 5249096759002546240105.88%
custom 541792605218802598363.53%
🙏42.35%
🕊31.76%
🍾21.18%
🔥10.588%

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

Measured over the 8 most recent posts we hold, published 22 July 2026 to 5 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

5 Aug 2026, 17:45 UTC527 views41 reactionsread 7 August 2026
Photo

🅰️🅰️🅰️🅰️🅰️💙🅰️🅰️🅰️ 💙💙🅰️🅰️🅰️💙🅰️🅰️🅰️🅰️🅰️🅰️ 🤩 — Wow, we actually pulled it off. That’s incredible. 🌸— If the chance arises... I’d love for everyone at the Victoria Agency to experience this, too. 🌸— Von Lycaon. 🌸— Ellen Joe. 🌸- Photo.

custom 530540168001411512015custom 530553406808604685413custom 531438526983362700013

Signed — kerrigan.

4 Aug 2026, 15:59 UTC24 views6 reactionsread 7 August 2026
Forwarded from @lunamoonshade

👽🧦™️🦄🛼🥑🐈™️🪀🍷 Представь, что мы делаем с тобой парный косплей. Кого будем делать и почему? 👁 Или кем ты меня видишь в пару к уже своему сделанному образу? 😇

4custom 53122278304514240982

Signed — kerrigan.

4 Aug 2026, 10:25 UTC28 views3 reactionsread 7 August 2026
Forwarded from @karasik_cosPhoto

🤩╰ ׅ ᅠ࣪ ⁠⁠⁠᷼ ︵ ꯭ 🤩🤩 ꯭ ︵ ⁠⁠⁠᷼ 🤩ятичасовая репетиция в воскресенье была!! Жесть как устали все, но результат того стоил🍼 ╰┈➤ А тут у нас: Герта, Аглая, Мидей, Гисиленса, Фаенон, Стелла, Босс Фаенон, мини Кирена, Кирена, Ривер, Кастория, Керидра, Темень, Дань Хэн, Март 7, Анакса, Цифер, Гиацина и Трибби

3

Signed — kerrigan.

27 Jul 2026, 13:26 UTC161 views52 reactionsread 7 August 2026
Photo

— в последнее время я от себя пишу мало, больше репощу, но всё-таки... сегодня немного праздник, на канале стукнуло 200 подписчиков, чему я несказанно рада и безумно благодарна всех хвостиков в моем канале я безумно благодарю за поддержку, спасибо что следите за моей деятельностью, спасибо что остаётесь здесь❤️

🎉2018❤‍🔥12🍾1🔥1

Signed — kerrigan.

25 Jul 2026, 13:51 UTC128 views31 reactionsread 7 August 2026
Forwarded from @mad_maskmakerPhoto

🩷🩷🖤🩷🩷🩷🩷🩷🖤 Уже завтра 26.07 Дуэт Оверлордов будет выступать на сцене фестиваля АнимэДзин. Наше выступление будет в начале второго блока 💫 ______ Да, мы снова без Валентино, он плохо переносят общественные места потравленные от насекомых Вельветт 💅 Вокс 📺

custom 531222783045142409812custom 524909675900254624010custom 54518023919868552909

Signed — kerrigan.

24 Jul 2026, 08:24 UTC125 views18 reactionsread 7 August 2026
Forwarded from @ven_viiiiPhoto

🔤🔤🔤🔤🔤 В воскресенье, на А-Дзине, будем выступать вместе с Эллен в конце 1 блока 🤍 Будем рады вас видеть) 🤍

8custom 54179260521880259836custom 54518023919868552903🍾1

Signed — kerrigan.

23 Jul 2026, 07:22 UTC86 views8 reactionsread 7 August 2026
Forwarded from @fatui_samaraPhoto

🔠🔠⏺🔠🔠🔠🔠🔠🔠🔠🔠🔠 В прошлую субботу состоялась наша ориджинал-фотосессия проекта. Для этого мы примерили новые амплуа для своих персонажей, при этом не забывая держать их в характере, получая по итогу невероятный результат и сочные кадры! Большое спасибо Пейн и её помощнице Харуки за всю проделанную работу! Каждая совместная съемка приносит потрясающий для всех экспириенс. 🖤 Так же благодарим всю супер команду помощник

6❤‍🔥1🙏1

Signed — kerrigan.

22 Jul 2026, 21:23 UTC82 views11 reactionsread 7 August 2026
Forwarded from @taky_yonPhoto

🔠🔠🔠🔠🔠🔠 🔠🔠🔠🔠🔠🔠🔠🔠 🤩 Royal mage and Sentinel knight 🤩 ✦ PH | RT ✦

5🕊3🙏3

Signed — kerrigan.

Showing the 8 most recent of 8 posts we hold for @koi_kerr. 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 — 61,813 of 1,480,688entries 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

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

“— бредни рыбки.” (@koi_kerr), 201 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/koi_kerr.

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.