Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝒏𝒆𝒍𝒍𝒚𝒅𝒐𝒓’𝒔 home¿

Channel

𝒏𝒆𝒍𝒍𝒚𝒅𝒐𝒓’𝒔 home¿

@cazadorskitten

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

34subscribers

+5 since we began measuring on 15 August 2026

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

Register entry

Telegram ID-1004442568733
TypeChannel
Username@cazadorskitten
Created1 August 2026measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live10 September 2026
Measurements held3
Confirmed unchanged3 times, most recently 10 September 2026
On Telegramt.me/cazadorskitten

Growth

293431.515 August 2026 — 29 subscribers15 August 2026 — 29 subscribers25 August 2026 — 34 subscribers15 August 202625 August 2026
3 measurements spanning 10 days, net +5. 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 28–35 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 01:3734+5
15 Aug 2026, 08:3029no change
15 Aug 2026, 08:1829first reading

Engagement

16 posts held, back to 1 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
14.7%
avg views ÷ 34 subscribers
Avg views / post
5.0
1 post measured
Reaction rate
80.0%
reactions ÷ views · ER floor
Posts in window
1
of 16 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 15 August 2026
Posts held16 (1 August 202615 August 2026)
Views total5
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 08:30 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

39 reactions across 4 posts, in 7 distinct kinds. The most used accounts for 30.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 51906672465186965251230.8%
custom 5465631933276910444923.1%
custom 5463372909328233134512.8%
custom 5283251154984144202410.3%
custom 5429309377674774470410.3%
custom 528277135559757346737.69%
🕊25.13%

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

Measured over the 16 most recent posts we hold, published 1 August 2026 to 15 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

15 Aug 2026, 08:02 UTC5 views4 reactionsread 15 August 2026
Photo

⸻⸺『⚔️🩸』 ⸺⸻ Пока пишутся хедканоны скину вам рисуночек который художница набросала вдохновившись Нелли ______________ cr: @akiaric #арт

custom 51906672465186965252custom 54293093776747744701custom 54656319332769104441

13 Aug 2026, 12:42 UTC17 viewsread 15 August 2026

⸻⸺『⚔️🩸』 ⸺⸻ Кстати,результаты готовы! {#щп}

13 Aug 2026, 12:35 UTC17 views14 reactionsread 15 August 2026
Photo

⸻⸺『⚔️🩸』 ⸺⸻ Я тоже полезла в эти дебри хпхпхп https://yumeship.app/s/aWtsWVDFie {#щп}

custom 54656319332769104446custom 51906672465186965254custom 52832511549841442024

13 Aug 2026, 12:08 UTC19 viewsread 15 August 2026
Poll

пока делается реф соны и пишется лор,что бы вы хотели?

  1. какие нибудь бинго40%
  2. хедканоны60%

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

12 Aug 2026, 14:05 UTC34 views19 reactionsread 15 August 2026
Photo

⸻⸺『⚔️🩸』 ⸺⸻ I've seen people turn their heads And quickly look away Like a newborn baby It just happens everyday I look inside myself And see my heart is black I see my red door I must have it painted black Maybe then, I'll fade away And not have to face the facts It's not easy facing up When your whole world is black No more will my green sea Go turn a deeper blue I could not foresee this thing Happening to you

custom 51906672465186965256custom 54633729093282331345custom 52827713555975734673custom 54293093776747744703custom 54656319332769104442

12 Aug 2026, 07:48 UTC35 views2 reactionsread 15 August 2026

Все работы закончены,про интерактив помню сегодня -завтра отрисую и оформлю. Скажите у кого в сапп листах переотметитсья #щп

🕊2

9 Aug 2026, 15:06 UTC47 viewsread 15 August 2026
Photo

🐰 🤩екв𝓮сты на ч𝓾биков ! . . . места : 11 / 12 🌟 от вас: 01. р𝓮пост поста в сшкн (скрин прикрепить), 02. скинуть реф𝓮ренс персонажа / ос / с𝓸ны в комм𝓮нтарии, 03. подп𝓾саться на м𝓸й сшкн 🤍 одн𝓸му человеку рисую максим𝔂м двух чиб𝓾ков (ос / сона + ф/о), в этом случае зан𝓾маются два места!

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

13 Aug 2026, 12:08 UTCAnonymous Poll10 voters

пока делается реф соны и пишется лор,что бы вы хотели?

  1. какие нибудь бинго40%
  2. хедканоны60%

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 16 most recent posts we hold, published 1 August 2026 to 15 August 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.

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.

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

“𝒏𝒆𝒍𝒍𝒚𝒅𝒐𝒓’𝒔 home¿” (@cazadorskitten), 34 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/cazadorskitten.

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.