Channel
@blackcatcom13
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
383subscribers
-5 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002558153369 |
|---|---|
| Type | Channel |
| Username | @blackcatcom13 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/blackcatcom13 |
Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 77% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 15:40 | 383 | -2 |
| 6 Sept 2026, 21:01 | 385 | -3 |
| 28 Aug 2026, 21:58 | 388 | no change |
| 28 Aug 2026, 18:16 | 388 | first reading |
18 posts held, back to 12 August 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 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.
| Window | Rolling 30 days · latest post in window 27 August 2026 |
|---|---|
| Posts held | 18 (12 August 2026 – 27 August 2026) |
| Views total | 1,171 |
| Reactions total | 202 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 18:16 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.
726 reactions across 18 posts, in 3 distinct kinds. The most used accounts for 39.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5366414976103773767 | 285 | 39.3% | |
| custom 5366206210628412475 | 261 | 36.0% | |
| custom 5368519793546647059 | 180 | 24.8% |
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 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 726 reactions 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 12 August 2026 to 27 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.
тот кто поставил мою любовь на верхнюю полку гори в аду Я НЕ ДОТЯГИВАЮСЬ. поэтому пришлось взять сок💔
custom 536620621062841247526custom 53685197935466470599custom 53664149761037737678
госпаде из за пмс я щас плачу просто из за грустного сна это уже какой то новый уровень
custom 536641497610377376722custom 53685197935466470598custom 53662062106284124757
я ржу
custom 536620621062841247528
Photo, posted without a caption
custom 536641497610377376722custom 536620621062841247510custom 536851979354664705910
у меня короче температура сутками держится и каждый раз как я сплю мне снится такая хуйня…. я уже устала ! щас вот такой бред снился что даже не объяснить. единственное, что я могу хоть как-то объяснить словами, это то что ко мне катил какой-то косплеер тартальи из геншина и звал на гиккон фестиваль и сказал что хочет одевать на меня штаны сам???😕
custom 536641497610377376734custom 53662062106284124759custom 53685197935466470599
мне сегодня приснилось что за мной следил мужик, и он отправил ко мне на пульте управления трех кукол барби с крыльями типо они феи, и они залетели ко мне в комнату через окно, я думала это настоящие феи прилетели и мне чето было так радостно, а потом я увидела что это куклы и все поняла и мне стало страшно🏔 очень классно спать с температурой
custom 536620621062841247526custom 536851979354664705913custom 536641497610377376712
пов я и все мое окружение
custom 536851979354664705924custom 536641497610377376711custom 536620621062841247510
я себя ощущаю щас как мэны когда у них температура 37 и они уже себя хоронят
custom 536641497610377376718custom 53685197935466470597custom 53662062106284124754
только заболела, но уже жалею что не ценила время, когда была здорова
custom 536620621062841247517custom 53664149761037737673custom 53685197935466470593
они в районе 10 тыщ стоят 🫥 ну ладно с моей работой она у меня подохнет
custom 536620621062841247516custom 53685197935466470599custom 53664149761037737672
я хочу завести себе змею
custom 536641497610377376718custom 53662062106284124758custom 53685197935466470598
я ржу в голос уже
custom 536851979354664705937custom 536641497610377376716custom 536620621062841247515
Showing the 12 most recent of 18 posts we hold for @blackcatcom13. 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.
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.
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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“blackcat.com” (@blackcatcom13), 383 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/blackcatcom13.
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.