Telegram RegisterThe public register of Telegram
Telegram profile photo for MyBB

Channel

MyBB

@mybb_ru

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

780subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001393628064
TypeChannel
Username@mybb_ru
Created29 July 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/mybb_ru

Growth

780781780.57 August 2026 — 781 subscribers8 August 2026 — 781 subscribers16 August 2026 — 780 subscribers7 August 202616 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 780–781 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 03:36780-1
8 Aug 2026, 01:47781no change
7 Aug 2026, 19:55781first reading

Engagement

18 posts held, back to 29 December 2025the 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
246.2%
avg views ÷ 780 subscribers
Avg views / post
1,920
2 posts measured
Reaction rate
0.573%
reactions ÷ views · ER floor
Posts in window
2
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 19 July 2026
Posts held18 (29 December 202519 July 2026)
Views total3,840
Reactions total22
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:47 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

594 reactions across 18 posts, in 9 distinct kinds. The most used accounts for 49.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
29649.8%
😢10918.4%
🔥7212.1%
👍6010.1%
👎244.04%
👀152.53%
😁122.02%
👏40.673%
😍20.337%

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 594reactions 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 29 December 2025 to 19 July 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

19 Jul 2026, 11:45 UTC≈1,890 views14 reactionsread 8 August 2026

🛠 Работа регистрации на форумах восстановлена. Приносим извинения за доставленные неудобства.

14

18 Jul 2026, 23:07 UTC≈1,950 views8 reactionsread 8 August 2026

⚠️ На всех форумах сервиса наблюдается проблема с регистрацией (в том числе с регистрацией через админ-панель). С наибольшей вероятностью проблема будет решена уже только днём.

👍8

30 Jun 2026, 10:25 UTC≈1,360 views23 reactionsread 8 August 2026

❗️В связи с изменениями в законодательстве, на всех форумах была убрана возможность авторизации через зарубежные сервисы. Если ваш профиль использовал такой метод авторизации, вернуть доступ к нему можно через кнопку восстановления пароля в форме входа. Другие изменения: - добавлена возможность загружать в хранилище админки файлы формата JSON

🔥12👎9😢2

27 Jun 2026, 07:37 UTC≈2,520 views33 reactionsread 8 August 2026

🛠 Работа сервиса восстановлена. Приносим извинения за доставленные неудобства.

33

26 Jun 2026, 18:25 UTC≈3,200 views53 reactionsread 8 August 2026

⚠️ Наблюдаются перебои в работе и доступности форумов. С наибольшей вероятностью проблема будет решена уже только утром.

😢2515👎8👀3😍2

6 Jun 2026, 19:06 UTC≈1,630 views30 reactionsread 8 August 2026

🛠 Работа сервиса восстановлена. Приносим извинения за доставленные неудобства.

👍1413👀3

6 Jun 2026, 17:19 UTC≈3,270 views25 reactionsread 8 August 2026

⚠️ Наблюдаются проблемы с доступом к форумам. О проблеме знаем, разбираемся.

😢136👎3🔥3

14 May 2026, 12:30 UTC≈2,000 views24 reactionsread 8 August 2026

Уважаемые пользователи! К настоящему моменту работоспособность поиска по форумам (включая поиск по каталогу webtalk.ru) должна быть восстановлена в полном объёме. Приносим извинения за возникшие неудобства.

23👀1

12 May 2026, 15:25 UTC≈1,890 views37 reactionsread 8 August 2026

К настоящему моменту проблема с SSL сертификатами, вызывавшая недоступность форумов по протоколу HTTPS, устранена. Истёкшие сертификаты перевыпущены и в дальнейшем продолжат выпускаться в автоматическом режиме. Проблема с поиском в процессе решения, но сроки устранения, к сожалению, обозначить пока нет возможности. Делаем всё возможное для скорейшего восстановления. Приносим извинения за доставленные неудобства.

33🔥4

12 May 2026, 07:33 UTC≈1,520 views31 reactionsread 8 August 2026

⚠️ По всему сервису вышел из строя внутрифорумный поиск; также вышел из строя поиск по каталогу WebTalk.ru. О проблеме известно. Поломка оказалась серьёзной, и восстановить его работу быстро не получится чисто технически. Постараемся наладить всё как можно скорее. Приносим извинения за доставленные неудобства

😢218👍1😁1

5 May 2026, 19:39 UTC≈3,790 views51 reactionsread 8 August 2026

⚠️ По техническим причинам форумы в настоящий момент недоступны. С наибольшей вероятностью работу сервиса восстановят уже к утру. Приносим извинения за доставленные неудобства. UPD. Проблемы с доступностью форумов устранены

😢368👀3👎2😁2

1 Apr 2026, 07:50 UTC≈2,130 views37 reactionsread 8 August 2026

К настоящему моменту проблема, вызвавшая недоступность форумов, устранена. Приносим извинения за доставленные неудобства.

35😁2

Showing the 12 most recent of 18 posts we hold for @mybb_ru. 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 — 311,922 of 1,481,502entries 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

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.

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

“MyBB” (@mybb_ru), 780 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/mybb_ru.

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.