Telegram RegisterThe public register of Telegram
Telegram profile photo for брухич

Channel

брухич

@bruhych_nft

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

15,092subscribers

-1,596 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003671597766
TypeChannel
Username@bruhych_nft
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/bruhych_nft

Topic

Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 43% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@pepenskyy/12274 Aug 2026, 18:42 UTC@bruhych_nft/2663 · this entry4 Aug 2026, 18:57 UTC1.0015 minutes
@bruhych_nft/2681 · this entry6 Aug 2026, 19:11 UTC@pepenskyy/12486 Aug 2026, 19:12 UTC1.0072 seconds
@pepenskyy/127511 Aug 2026, 14:46 UTC@bruhych_nft/2710 · this entry11 Aug 2026, 14:47 UTC1.0072 seconds
@pepenskyy/143031 Aug 2026, 19:28 UTC@bruhych_nft/2818 · this entry31 Aug 2026, 19:28 UTC1.00under a minute
@pepenskyy/164020 Oct 2026, 14:49 UTC@bruhych_nft/2965 · this entry21 Oct 2026, 16:23 UTC1.0026 hours
@pepenskyy/133818 Aug 2026, 21:56 UTC@bruhych_nft/2750 · this entry18 Aug 2026, 21:56 UTC0.95under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@pepenskyy6 (6/6 hand-verifiable sample passed)0.9972 seconds@pepenskyy (4–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 3 of the 4 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 50 comparable posts for this entry, running 29 July 2026 to 11 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Recorded under the key clone_copy, last confirmed 15 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

15,09216,95116,021.56 August 202615 November 2026
66 measurements spanning 102 days, net -1,596. 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 14,813–17,230 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
15 Nov 2026, 22:0115,092-148
12 Nov 2026, 14:4815,240-71
10 Nov 2026, 09:4615,311-129
8 Nov 2026, 20:2715,440-839
7 Nov 2026, 12:5916,279-11
6 Nov 2026, 13:3616,290-53
5 Nov 2026, 12:4616,343-78
4 Nov 2026, 10:5116,421+164
3 Nov 2026, 08:3716,257-87
2 Nov 2026, 09:4416,344-24
1 Nov 2026, 08:1616,368+116
31 Oct 2026, 10:1616,252+9
30 Oct 2026, 06:5616,243-6
29 Oct 2026, 06:2116,249-23
28 Oct 2026, 07:3916,272-69
27 Oct 2026, 05:2716,341-53
26 Oct 2026, 08:4416,394-57
25 Oct 2026, 08:3016,451+224
24 Oct 2026, 11:5916,227-65
23 Oct 2026, 09:0916,292first reading

Engagement

117 posts held, back to 29 July 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 94 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.6%
avg views ÷ 15,092 subscribers
Avg views / post
2,050
30 posts measured
Reaction rate
6.95%
reactions ÷ views · ER floor
Posts in window
30
of 117 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 November 2026
Posts held117 (29 July 2026 – 15 November 2026)
Views total61,392
Reactions total4,267
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 21:28 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.

What this channel posts

Video runtime
33s
Average length
17s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

17,524 reactions across 114 posts, in 5 distinct kinds. The most used accounts for 38.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6,65438.0%
custom 54584616485850000464,99128.5%
👍2,69515.4%
custom 63322656969148349051,7249.84%
custom 54519199151769743151,4608.33%

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

Measured over the 117 most recent posts we hold, published 29 July 2026 to 15 November 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.

Telegram Stars

Stars received
120
across the posts below
Posts paid on
65
of 117 we hold a reading for · 56%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @bruhych_nft. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 117 most recent posts we hold for this entry, published 29 July 2026 to 15 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 21 of 30 posts held from the last 30 days (70.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Nov 2026, 19:30 UTC612 views108 reactions3 Starsread 15 November 2026
Photo

🎁 НФТ БЕЗ УСЛОВИЙ 🎁 🐸 НА НОЧЬ итоги в 14:00 по мск 🎁

❤54custom 545846164858500004633👍21

Signed Random Beast 🏆

13 Nov 2026, 14:46 UTC≈1,530 views53 reactions1 Starread 15 November 2026
Photo

Сверху фейковый Дуров, настоящий снизу 😏

custom 545846164858500004622👍15custom 633226569691483490511❤5

Signed Yarken

12 Nov 2026, 18:14 UTC≈1,710 views203 reactions1 Starread 15 November 2026
Photo

📍 НФТ – НА 10 МИНУТ 📍 Без условий! реакций пж 🎁 ИТОГИ

custom 545846164858500004699❤61👍38custom 63322656969148349055

Signed RandomGodBot⚡️ [Рандомайзер]

10 Nov 2026, 13:06 UTC≈1,880 views123 reactions1 Starread 15 November 2026
Photo

🎁ФЛАМИНГО НА 15 МИНУТ » подписка @ » подписка @ Репост другу увеличивает шансы на победу ❤️ РЕЗУЛЬТАТЫ

👍51❤41custom 545846164858500004628custom 63322656969148349053

Signed RandomGodBot⚡️ [Рандомайзер]

9 Nov 2026, 16:45 UTC≈1,750 views31 reactionsread 15 November 2026
Photo

❗️ Срочно! Забираем халявные кейсы за подписку! CrazyGift — первый Telegram-проект на подарки с проверкой честности. Не повезло или подкрутили? В играх без проверки этого не узнать. 🛡 Проверка честности ⚡ Моментальные выводы 🎁 Ежедневный кейс бесплатно 💵 СБП без комиссии 💸 Кешбэк до 10%, рейкбек до 1% 🏆 Турнир на 1 000 000 ₽ 💯 13 режимов с RTP до 98% 🎮 Играть: @crazygiftgame

custom 545846164858500004612custom 633226569691483490511👍6❤2

Signed Yarken

9 Nov 2026, 13:17 UTC≈1,670 views152 reactionsread 15 November 2026
Photo

🎁 НФТ ЛАМПА : 15 МИНУТ Нужно зайти в @GiftBoost (проверю) РЕЗУЛЬТАТЫ

❤68👍48custom 545846164858500004633custom 63322656969148349053

Signed RandomGodBot⚡️ [Рандомайзер]

6 Nov 2026, 20:33 UTC≈2,150 views236 reactions3 Starsread 15 November 2026
Photo

🎁 SWAG BAG НА НОЧЬ 🎁 БЕЗ УСЛОВИЙ ❤️ реакция + буст дают больше шансов 🎉 UPD: Розыгрыш завершен! 🏆 Победители: 1. @Bbezzoox 🔍 Проверить результаты

custom 5458461648585000046131👍63❤36custom 63322656969148349056

Signed Random Beast 🏆

5 Nov 2026, 17:39 UTC≈2,250 views182 reactions4 Starsread 15 November 2026
Photo

🎁 Нфт на 7 минут без условий! ИТОГИ

❤95custom 545846164858500004661custom 633226569691483490522👍4

Signed RandomGodBot⚡️ [Рандомайзер]

4 Nov 2026, 18:10 UTC≈2,230 views48 reactions2 Starsread 15 November 2026
Photo

Паша Дуров с чиксами 🔞

custom 545846164858500004626👍13❤7custom 63322656969148349052

Signed Yarken

3 Nov 2026, 20:47 UTC≈2,100 views140 reactions3 Starsread 15 November 2026
Photo

🎁 НФТ МЕЧ для своих! 🎁 » подписка @bruhych_nft Итоги в 14:00 по мск 🧸 🎉 UPD: Розыгрыш завершен! 🏆 Победители: 1. @thenurmat 🔍 Проверить результаты

❤68👍47custom 545846164858500004625

Signed Random Beast 🏆

2 Nov 2026, 19:46 UTC≈1,960 views140 reactions2 Starsread 15 November 2026
Photo

🧸7 ЗОМБИ МИШЕК — НА 5 МИНУТ🧸 условие: включить уведомления РЕЗУЛЬТАТЫ

custom 545846164858500004674👍33❤30custom 63322656969148349053

Signed RandomGodBot⚡️ [Рандомайзер]

2 Nov 2026, 13:53 UTC≈2,050 views200 reactions2 Starsread 15 November 2026
Photo

ЧТО-ТО ТУТ НЕЛАДНОЕ 😒 🧸Кому тоже подарить мишку? А то скоро исчезнут 😱

❤160custom 545846164858500004619👍16custom 63322656969148349055

Signed Yarken

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@bruhych_nft edited 17 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
8 August 2026
Most recent edit
14 November 2026

Posts recorded as deleted after publishing

We recorded 20 posts on @bruhych_nft as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
7 August 2026
Most recent seen missing
15 November 2026
Median time before seen missing
31 hours
Seen missing in the last 30 days
4

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

“брухич” (@bruhych_nft), 15,092 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/bruhych_nft.

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.