Telegram RegisterThe public register of Telegram
Telegram profile photo for Beard_Cliff

Channel

Beard_Cliff

@beard_cliff

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

6,377subscribers

+119 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001587838653
TypeChannel
Username@beard_cliff
DescriptionТот самый Клифф Хинкальный богатырь из России🇷🇺 VK: vk.com/zurabovich RuTube: https://rutube.ru/channel/36549481/ RED CLIFF GEAR: • https://redcliffgear.ru • vk.com/redcliffgear • instagram.com/redcliffgear
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 November 2026
Measurements held27
Confirmed unchanged2 times, most recently 10 November 2026
On Telegramt.me/beard_cliff

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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.

Growth

6,2576,3776,3176 August 2026 — 6,258 subscribers6 August 2026 — 6,258 subscribers6 August 2026 — 6,257 subscribers9 August 2026 — 6,269 subscribers12 August 2026 — 6,285 subscribers16 August 2026 — 6,282 subscribers19 August 2026 — 6,283 subscribers22 August 2026 — 6,281 subscribers25 August 2026 — 6,279 subscribers28 August 2026 — 6,271 subscribers31 August 2026 — 6,283 subscribers4 September 2026 — 6,298 subscribers9 September 2026 — 6,307 subscribers13 September 2026 — 6,314 subscribers17 September 2026 — 6,335 subscribers26 September 2026 — 6,334 subscribers5 October 2026 — 6,340 subscribers11 October 2026 — 6,346 subscribers15 October 2026 — 6,347 subscribers18 October 2026 — 6,352 subscribers21 October 2026 — 6,351 subscribers24 October 2026 — 6,367 subscribers26 October 2026 — 6,373 subscribers30 October 2026 — 6,370 subscribers1 November 2026 — 6,368 subscribers4 November 2026 — 6,372 subscribers7 November 2026 — 6,377 subscribers6 August 20267 November 2026
27 measurements spanning 93 days, net +119. 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 6,239–6,395 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
7 Nov 2026, 11:516,377+5
4 Nov 2026, 14:506,372+4
1 Nov 2026, 23:546,368-2
30 Oct 2026, 01:116,370-3
26 Oct 2026, 19:406,373+6
24 Oct 2026, 05:016,367+16
21 Oct 2026, 04:316,351-1
18 Oct 2026, 02:556,352+5
15 Oct 2026, 02:116,347+1
11 Oct 2026, 14:386,346+6
5 Oct 2026, 02:366,340+6
26 Sept 2026, 12:176,334-1
17 Sept 2026, 20:366,335+21
13 Sept 2026, 16:366,314+7
9 Sept 2026, 17:586,307+9
4 Sept 2026, 11:016,298+15
31 Aug 2026, 16:056,283+12
28 Aug 2026, 17:546,271-8
25 Aug 2026, 21:346,279-2
22 Aug 2026, 21:036,281first reading

Engagement

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

ERR · 30 days
13.7%
avg views ÷ 6,377 subscribers
Avg views / post
875
20 posts measured
Reaction rate
2.75%
reactions ÷ views · ER floor
Posts in window
20
of 64 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 7 November 2026
Posts held64 (2 August 2026 – 7 November 2026)
Views total17,508
Reactions total481
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 11:52 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

Photos
≈7,350
Videos
≈1,460
Links
≈1,070

Lifetime counters from Telegram’s own channel header, read 7 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
9m 13s
Average length
26s

Measured directly from 21 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

1,257 reactions across 56 posts, in 10 distinct kinds. The most used accounts for 27.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥33927.0%
🔥33726.8%
🤣23718.9%
👍14111.2%
custom 52651949106082816251048.27%
🦄372.94%
🌭282.23%
💯282.23%
custom 530086269415117992040.318%
👎20.159%

Custom emoji. 2 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 61 of the 64 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 1,380 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 64 most recent posts we hold, published 2 August 2026 to 7 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
1
across the posts below
Posts paid on
1
of 64 we hold a reading for · 2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @beard_cliff. 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 64 most recent posts we hold for this entry, published 2 August 2026 to 7 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: 3 of 20 posts held from the last 30 days (15.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).

7 Nov 2026, 10:15 UTC207 views5 reactionsread 7 November 2026

Погода теплая, но жаль уже не в этом сезоне) Ждем лета 2027 покорять ночные просторы Канельярви 😁 Headgear: • Шлем OPS CORE Fast Carbon • FCS AMP гарнитура • Dedal DS-21 бинокуляр с маунтом Dedal • Sotac IR/VIS и какая то реплика Princeton • 3D чехол КотОК • SC ballast pouch 2nd line: • Pew 34 ALPHA сплит риг с модулем PEW LBV • 2х Pew Большие утилитарные подсумки • 2х AK PRO от FILLIN • Сброс RedCliff SDP • Armyte…

🔥5

7 Nov 2026, 09:58 UTC383 views28 reactionsread 7 November 2026
Photo

VANILLA 🏝️

👍15❤‍🔥6🦄5👎1🔥1

7 Nov 2026, 06:55 UTC427 views24 reactionsread 7 November 2026
Photo

Утро доброе 🤗

🦄20❤‍🔥4

6 Nov 2026, 11:07 UTC≈1,410 views13 reactionsread 7 November 2026
Photo

Время посмотреть демисезонные ботиночки Milgear. Ну и рубашечки мы жалуем 😏

🔥13

5 Nov 2026, 13:10 UTC861 views36 reactionsread 7 November 2026
Photo

АльфаАрмс покажи!

🤣35❤‍🔥1

5 Nov 2026, 11:17 UTC857 views21 reactionsread 7 November 2026
Photo

Если посчитать слова причетания и всевозможнные "пупупу" когда начали стрелять баррикаду с левого плеча, то можно не удивляться причине крайне потешных цифр хитфактора :) Я очень рад возможности подтянуть и порты и стрельбу со слабой руки. Не самая распространенная задача в упражнениях, однако когда выпадает случай стрелять это всегда ступор "а как вложится, а как переложиться". В общем, если имеете в доступе баррик…

🔥17👍4

5 Nov 2026, 08:06 UTC959 views26 reactionsread 7 November 2026
Video

Когда поставил новый дульник 😂

🔥19👍4🌭3

4 Nov 2026, 18:03 UTC876 views41 reactionsread 6 November 2026
Photo

Пострелял- обслужи. @fillin_pro

💯24🔥9custom 52651949106082816256👍2

4 Nov 2026, 11:55 UTC909 views12 reactionsread 6 November 2026
Photo

Никуда не поехал, зато выкроил время усесться за компутер. Денис, Беляш гиенной славной охоты 🤩

🔥8👍3🤣1

3 Nov 2026, 10:20 UTC≈1,490 views18 reactionsread 6 November 2026
Photo

Поздравляем с наступающим Днем народного единства!🇷🇺 В период с 04.11.2026 по 06.11.2026 скидка 10% на весь ассортимент по промокоду 04NOV2026 REDCLIFFGEAR.RU

🔥13👍5

2 Nov 2026, 17:55 UTC≈1,080 views35 reactionsread 6 November 2026
Video

Хороша, хороша🤗

❤‍🔥25🔥8👍1🤣1

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

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

FTF
@tactical_flava · 30,965
Telegram ranks this channel #5 of 45 here — alongside 44 others — read 16 September 2026
Рустам Ковальски и Kowalski team
@kowalski_team · 23,329
Telegram ranks this channel #31 of 53 here — alongside 52 others — read 18 September 2026
Unfair Advantage
@unfair_advantage_tg · 25,002
Telegram ranks this channel #42 of 58 here — alongside 57 others — read 16 September 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Beard_Cliff” (@beard_cliff), 6,377 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/beard_cliff.

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.