Telegram RegisterThe public register of Telegram

Channel

Carnivore Colds

@carnivorecolds

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

175subscribers

-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-1003953664220
TypeChannel
Username@carnivorecolds
CreatedBetween 1 April 2026 and 10 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/carnivorecolds

Growth

175176175.56 August 2026 — 176 subscribers8 August 2026 — 176 subscribers14 August 2026 — 175 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 175–176 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 19:57175-1
8 Aug 2026, 13:46176no change
6 Aug 2026, 13:08176first reading

Engagement

18 posts held, back to 10 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
208.6%
avg views ÷ 175 subscribers
Avg views / post
365
16 posts measured
Reaction rate
9.20%
reactions ÷ views · ER floor
Posts in window
16
of 18 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 August 2026
Posts held18 (10 July 20268 August 2026)
Views total5,840
Reactions total537
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 13:46 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

649 reactions across 18 posts, in 8 distinct kinds. The most used accounts for 25.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 521999260890591191316225.0%
custom 518833068123044168711818.2%
custom 52178775823257717419514.6%
custom 52201658335268948039214.2%
custom 54541838697481098698012.3%
custom 5192672734252925459456.93%
custom 5453909614611425176365.55%
custom 5192920665535054929213.24%

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

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

8 Aug 2026, 10:15 UTC66 views33 reactionsread 8 August 2026
Photo

Чортищо 💀 #СХ

custom 518833068123044168715custom 54539096146114251764custom 54541838697481098694custom 51926727342529254593custom 52199926089059119133custom 52178775823257717412custom 51929206655350549291custom 52201658335268948031

5 Aug 2026, 14:12 UTC141 views37 reactionsread 8 August 2026
Photo

💀💀💀

custom 522016583352689480320custom 52199926089059119136custom 51929206655350549295custom 52178775823257717412custom 51883306812304416871custom 51926727342529254591custom 54539096146114251761custom 54541838697481098691

4 Aug 2026, 07:40 UTC145 views30 reactionsread 8 August 2026
Photo

Трейд

custom 545390961461142517616custom 52199926089059119136custom 54541838697481098693custom 51883306812304416871custom 51926727342529254591custom 51929206655350549291custom 52178775823257717411custom 52201658335268948031

3 Aug 2026, 08:41 UTC147 views34 reactionsread 8 August 2026
Photo

🔐 #СХ

custom 518833068123044168720custom 52178775823257717415custom 52199926089059119134custom 51926727342529254591custom 51929206655350549291custom 52201658335268948031custom 54539096146114251761custom 54541838697481098691

30 Jul 2026, 14:47 UTC213 views38 reactionsread 8 August 2026
Photo

24

custom 522016583352689480318custom 54541838697481098697custom 52178775823257717414custom 52199926089059119134custom 51883306812304416872custom 51926727342529254591custom 51929206655350549291custom 54539096146114251761

29 Jul 2026, 14:11 UTC185 views35 reactionsread 8 August 2026
Photo

#СХ

custom 521999260890591191318custom 51926727342529254596custom 52201658335268948036custom 51883306812304416871custom 51929206655350549291custom 52178775823257717411custom 54539096146114251761custom 54541838697481098691

26 Jul 2026, 11:59 UTC285 views41 reactionsread 8 August 2026
Photo

23(?)

custom 545418386974810986922custom 51883306812304416877custom 51926727342529254595custom 54539096146114251763custom 51929206655350549291custom 52178775823257717411custom 52199926089059119131custom 52201658335268948031

26 Jul 2026, 11:58 UTC194 views22 reactionsread 8 August 2026
Forwarded from @dverivpodvalbeloPhoto

Мстя @carnivorecolds 🔈

custom 51883306812304416879custom 52178775823257717416custom 51926727342529254594custom 52199926089059119131custom 52201658335268948031custom 54541838697481098691

25 Jul 2026, 18:20 UTC230 views20 reactionsread 8 August 2026
Forwarded from @woodeliriumPhoto

Да сколько можно рисовать для этой ужасной девочки ⭐️⭐️

custom 521999260890591191313custom 51926727342529254594custom 52178775823257717412custom 52201658335268948031

24 Jul 2026, 12:05 UTC255 views42 reactionsread 8 August 2026
Photo

Х

custom 545418386974810986923custom 52199926089059119136custom 51883306812304416875custom 51926727342529254592custom 52178775823257717412custom 54539096146114251762custom 51929206655350549291custom 52201658335268948031

22 Jul 2026, 17:07 UTC650 views30 reactionsread 8 August 2026
Photo

22

custom 521787758232577174113custom 52201658335268948037custom 52199926089059119135custom 51883306812304416871custom 51926727342529254591custom 51929206655350549291custom 54539096146114251761custom 54541838697481098691

21 Jul 2026, 09:26 UTC320 views38 reactionsread 8 August 2026
Photo

21

custom 521999260890591191321custom 51883306812304416878custom 54541838697481098694custom 51926727342529254591custom 51929206655350549291custom 52178775823257717411custom 52201658335268948031custom 54539096146114251761

Showing the 12 most recent of 18 posts we hold for @carnivorecolds. 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 — 128,076 of 1,345,403entries 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

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

“Carnivore Colds” (@carnivorecolds), 175 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/carnivorecolds.

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.