Telegram RegisterThe public register of Telegram
Telegram profile photo for Maksibey

Channel

Maksibey

@maksibeyqq

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

11,215subscribers

+1,779 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003534008692
TypeChannel
Username@maksibeyqq
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held22
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/maksibeyqq

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

Growth

9,32111,53910,4307 August 2026 — 9,436 subscribers8 August 2026 — 9,407 subscribers11 August 2026 — 10,250 subscribers12 August 2026 — 10,212 subscribers13 August 2026 — 10,101 subscribers14 August 2026 — 10,107 subscribers16 August 2026 — 10,035 subscribers17 August 2026 — 10,188 subscribers18 August 2026 — 10,246 subscribers19 August 2026 — 10,170 subscribers20 August 2026 — 10,061 subscribers21 August 2026 — 9,953 subscribers25 August 2026 — 9,681 subscribers27 August 2026 — 9,946 subscribers30 August 2026 — 9,502 subscribers3 September 2026 — 9,321 subscribers8 September 2026 — 11,539 subscribers11 September 2026 — 11,263 subscribers13 September 2026 — 11,131 subscribers14 September 2026 — 11,142 subscribers16 September 2026 — 11,324 subscribers18 September 2026 — 11,215 subscribers11,2157 August 202618 September 2026
22 measurements spanning 43 days, net +1,779. 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 8,988–11,872 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
18 Sept 2026, 23:2011,215-109
16 Sept 2026, 16:0111,324+182
14 Sept 2026, 16:5911,142+11
13 Sept 2026, 06:0111,131-132
11 Sept 2026, 05:5911,263-276
8 Sept 2026, 08:3711,539+2,218
3 Sept 2026, 00:589,321-181
30 Aug 2026, 16:189,502-444
27 Aug 2026, 21:469,946+265
25 Aug 2026, 02:479,681-272
21 Aug 2026, 12:179,953-108
20 Aug 2026, 11:4210,061-109
19 Aug 2026, 10:3810,170-76
18 Aug 2026, 10:2210,246+58
17 Aug 2026, 11:4710,188+153
16 Aug 2026, 02:1510,035-72
14 Aug 2026, 08:4610,107+6
13 Aug 2026, 03:2410,101-111
12 Aug 2026, 04:0210,212-38
11 Aug 2026, 07:2110,250first reading

Engagement

76 posts held, back to 29 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 44 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.48%
avg views ÷ 11,215 subscribers
Avg views / post
1,060
12 posts measured
Reaction rate
2.95%
reactions ÷ views · ER floor
Posts in window
12
of 76 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 28 August 2026
Posts held76 (29 July 202628 August 2026)
Views total12,757
Reactions total376
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 04:32 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
50s
Average length
17s

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

2,774 reactions across 75 posts, in 45 distinct kinds. The most used accounts for 47.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,31147.3%
🔥2559.19%
😡1354.87%
❤‍🔥1204.33%
😭1204.33%
😁832.99%
🥰802.88%
👏792.85%
👍742.67%
🤔732.63%
🤣642.31%
💘622.24%
😢521.87%
🍌491.77%
💔270.973%
😱250.901%
🆒200.721%
🌭200.721%
🐳170.613%
🎃90.324%
25 further kinds993.57%

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 75 of the 76 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 2,774 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

Recent posts

28 Aug 2026, 22:00 UTC280 views15 reactionsread 29 August 2026

Пошла очисткой ботов с канала,а то некоторое время у меня оказывается сидели боты вместо людей,а я платил за норм рекламу😥

🍌103❤‍🔥2

28 Aug 2026, 11:25 UTC667 views6 reactionsread 29 August 2026
Photo

#не воздух,мишки отдал,мб еще сделаю попозже такую же тему с мишками🙂

💘5👍1

27 Aug 2026, 21:29 UTC≈1,000 views22 reactionsread 29 August 2026
Photo

Доброй ночи,друны предстоит тяжелая неделя😰

😭147🥰1

27 Aug 2026, 14:50 UTC≈1,020 views24 reactionsread 29 August 2026
Photo

Недельный отдых закончен,пора наводить суету в лиге😄

18🍓4🥰2

27 Aug 2026, 12:55 UTC≈1,020 views24 reactionsread 29 August 2026

Начал ходить на пробежечки,спортивность💪

15🤔5🤣3🥰1

26 Aug 2026, 16:21 UTC≈1,230 views97 reactionsread 29 August 2026
Photo

🍔 - с жирных

🔥82🥰7🥱2🆒2🌚1🎃1😇1😘1

25 Aug 2026, 18:40 UTC≈1,300 views4 reactionsread 29 August 2026

В комменты напишите вашу цену за нее

4

25 Aug 2026, 18:37 UTC≈1,270 views16 reactionsread 29 August 2026
Photo

Формально если бы вы покупали,то за сколько купили бы эту сумму с доставкой от меня ну или с моих рук?

9🤯4🔥2❤‍🔥1

25 Aug 2026, 14:44 UTC≈1,220 views5 reactionsread 29 August 2026

По моим подсчетам я чутка сделал неприятный подсчет по средствам,поэтому готов принять заказы мастеров на процентов 20-25% дешевле чем обычно и добавить бонусом в друзья,за бустом писать в лс @Maksibey_boost Такую акцию делаю ровно на сутки и в ближайшем сезоне больше делать не буду,поэтому успейте закупиться!

5

25 Aug 2026, 12:19 UTC≈1,230 views5 reactionsread 29 August 2026

Участвуем братва в сочном конкурсе,после этого конкурса сделаю свой конкурс на 1500-2000⭐️

🍌5

25 Aug 2026, 12:19 UTC≈1,240 views60 reactionsread 29 August 2026
Photo

🥁МЕГА РОЗЫГРЫШ💎 🔠🔠🔠 🔠🔠🔠🔠🔠🔠 🏆 Призы : 1–6 место — Brawl Pass 🎫 7–46 место — 40 пинов Дже-Ёна 😀 47–135 место — 89 спреев Nano 5 🤩 136–158 место — Мишка 🧸 159–167 место — 9 скинов Архибеа 🤩 168–169 место — 2 скина Мармеладная Нита 🤩 170–171 место — 2 скина Тёмная Печь Перл 🤩 172–174 место — 3 спрея Willow Wasteland 🤩 175–176 место — 2 спрея Hole 🤩 177–179 место — 3 пина ЛНГ 🟨 180–189 место — 10

😡28🔥12🥰8👍4🤔32👏2❤‍🔥1

25 Aug 2026, 09:30 UTC≈1,280 views98 reactionsread 29 August 2026
Photo

Почему не фиксят ебаную дизбаланс венди, которую буквально овер тяжело контрить? И играть ладдер, казалось бы, как? Закрывать заказы 3🤩, когда в игре присутствует такая дизбаланс херня? 😡- если тоже ждешь фикс этой херни

😡7615🤷‍♂5💯2

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

@maksibeyqq 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
26 August 2026
Most recent edit
26 August 2026

Polls

The 5 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.

19 Aug 2026, 15:03 UTCAnonymous Poll334 voters

Друзья сильно не тильтуйте,в этом месяце сделаю конкурс на звезды,на 10 мест, в сумме на 1500⭐️

  1. Ждем родной🥳60%
  2. Го конкурс на 10 чекушек😰66%

The shares total 126%, 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.

16 Aug 2026, 09:32 UTCAnonymous Poll331 voters

Хотите конкурс на ⭐️ в течении часа?

  1. Гоу85%
  2. Не стоит15%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

15 Aug 2026, 15:09 UTCAnonymous Poll299 voters

Выкладывать проду с Аланом?

  1. Делай😂64%
  2. Поверь алану на слово,что он даст тебе 5к за мастера49%

The shares total 113%, 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.

12 Aug 2026, 05:42 UTCAnonymous Poll395 voters

Чем вы себя мотивируете по утрам🥰

  1. Спорт26%
  2. Работа13%
  3. Игра66%
  4. Свой вариант в комменты14%

The shares total 119%, 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.

5 Aug 2026, 18:54 UTCAnonymous Poll350 voters

Хотите конкурс завтра?

  1. Делай братка🥳not shown

Results were not being shown when we read this poll, so no share was published for any option. That is not zero — it is an absence, and we record it as one.

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 76 most recent posts we hold, published 29 July 2026 to 28 August 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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“Maksibey” (@maksibeyqq), 11,215 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/maksibeyqq.

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.