Telegram RegisterThe public register of Telegram
Telegram profile photo for business club

Channel

business club

@hvhclub2020

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Polls · Citations · Cite this entry

17,019subscribers

-2,591 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001857069700
TypeChannel
Username@hvhclub2020
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/hvhclub2020

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 18 August 2026 and assigned it the closest of 31 fixed categories, at 73% 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.

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.

Views per post sit far below this size band

36.9 average views per post against 17,019 subscribers — an engagement rate of 0.217%. Across the 15,742 registered channels in the same cohort — 10,000–31,614 subscribers, posting mainly in Russian — the middle half sit between 4.62% and 17.7%, with a median of 9.03%.

What this was computed from
Window30 days (25 August 2026 – 24 September 2026)
Posts measured187 of 187 published in the window (187 exact, 0 rounded by Telegram)
Views totalled6,902
Mature posts only0.306% over 31 posts read at least 24h after publication
Subscribers17,019 measured 17 September 2026
Cohortb10000:rus · 15,742 channels · p10 2.35% · p25 4.62% · p50 9.03% · p75 17.7% · p90 30.3%
Position in cohort0.534th percentile · 1/42 the cohort median
Uncertainty±0.17% of the figure, from Telegram’s rounding
Post languageRussian · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_low, last confirmed 24 September 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

17,01919,61018,314.58 August 2026 — 19,610 subscribers9 August 2026 — 19,610 subscribers10 August 2026 — 19,488 subscribers11 August 2026 — 19,432 subscribers12 August 2026 — 19,366 subscribers13 August 2026 — 19,319 subscribers14 August 2026 — 19,223 subscribers16 August 2026 — 19,142 subscribers17 August 2026 — 18,929 subscribers18 August 2026 — 18,825 subscribers19 August 2026 — 18,778 subscribers20 August 2026 — 18,747 subscribers22 August 2026 — 18,681 subscribers23 August 2026 — 18,556 subscribers25 August 2026 — 18,479 subscribers25 August 2026 — 18,436 subscribers26 August 2026 — 18,370 subscribers27 August 2026 — 18,348 subscribers28 August 2026 — 18,321 subscribers29 August 2026 — 18,291 subscribers30 August 2026 — 18,214 subscribers31 August 2026 — 18,189 subscribers1 September 2026 — 18,139 subscribers2 September 2026 — 17,982 subscribers4 September 2026 — 17,826 subscribers6 September 2026 — 17,757 subscribers10 September 2026 — 17,614 subscribers12 September 2026 — 17,377 subscribers13 September 2026 — 17,267 subscribers15 September 2026 — 17,196 subscribers17 September 2026 — 17,019 subscribers8 August 202617 September 2026
31 measurements spanning 40 days, net -2,591. 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 16,630–19,999 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
17 Sept 2026, 14:4117,019-177
15 Sept 2026, 12:0017,196-71
13 Sept 2026, 22:5717,267-110
12 Sept 2026, 04:3617,377-237
10 Sept 2026, 01:2017,614-143
6 Sept 2026, 20:2217,757-69
4 Sept 2026, 05:3817,826-156
2 Sept 2026, 19:1317,982-157
1 Sept 2026, 20:1418,139-50
31 Aug 2026, 17:5918,189-25
30 Aug 2026, 21:1718,214-77
29 Aug 2026, 20:1118,291-30
28 Aug 2026, 22:3418,321-27
27 Aug 2026, 20:4718,348-22
26 Aug 2026, 20:4218,370-66
25 Aug 2026, 23:1318,436-43
25 Aug 2026, 01:0418,479-77
23 Aug 2026, 16:1918,556-125
22 Aug 2026, 01:2718,681-66
20 Aug 2026, 16:2618,747first reading

Engagement

563 posts held, back to 8 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 49 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.217%
avg views ÷ 17,019 subscribers
Avg views / post
36.9
187 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
187
of 563 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 3 September 2026
Posts held563 (8 August 2026 – 3 September 2026)
Views total6,902
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 08:58 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
4m 18s
Average length
23s

Measured directly from 11 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.

Recent posts

2 Sept 2026, 23:38 UTC32 viewsread 3 September 2026
Voice message

Voice message, posted without a caption

Signed XVII

2 Sept 2026, 12:27 UTC47 viewsread 3 September 2026

го добьем 60

Signed @𝗧𝗿𝗮𝗻𝗾𝘂𝗶𝗹𝗶𝘁𝘆𝗕𝗼𝘆𝘇'.

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

Posts edited after publishing

@hvhclub2020 edited 1 post 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
9 August 2026
Most recent edit
9 August 2026

Polls

The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

18 Aug 2026, 11:10 UTCAnonymous Poll39 voters

какая лучше на облогу

  1. 159%
  2. 246%

The shares total 105%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

17 Aug 2026, 22:47 UTCAnonymous Poll21 voters

какая лучше на облогу

  1. 157%
  2. 248%

The shares total 105%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 563 most recent posts we hold, published 8 August 2026 to 3 September 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

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

“business club” (@hvhclub2020), 17,019 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/hvhclub2020.

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.