⭐ Все работает в штатном режиме! @starbuy2bot
custom 53710275777061642844custom 53729275896335340162custom 53978830117756386182
Signed Artem

Channel
@starbuychannel
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Citations · Cite this entry
7,384subscribers
+263 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002416655964 |
|---|---|
| Type | Channel |
| Usernames | @starbuychannel @starbuyoff |
| Description | Бот для покупки звезд - @Starbuy1bot Отзывы проекта - @starsbuyreviews Реклама / Сотрудничество - Писать в директ канала |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 54 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/starbuychannel |
Giveaways & airdrops — 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 51% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 17:59 | 7,384 | -14 |
| 15 Nov 2026, 09:37 | 7,398 | -29 |
| 10 Nov 2026, 23:50 | 7,427 | -5 |
| 9 Nov 2026, 22:17 | 7,432 | +19 |
| 6 Nov 2026, 22:46 | 7,413 | -3 |
| 6 Nov 2026, 06:35 | 7,416 | -25 |
| 4 Nov 2026, 07:37 | 7,441 | +3 |
| 3 Nov 2026, 08:46 | 7,438 | +6 |
| 1 Nov 2026, 08:48 | 7,432 | +13 |
| 31 Oct 2026, 15:56 | 7,419 | +46 |
| 28 Oct 2026, 22:50 | 7,373 | +6 |
| 28 Oct 2026, 08:05 | 7,367 | -4 |
| 26 Oct 2026, 07:55 | 7,371 | +72 |
| 25 Oct 2026, 04:56 | 7,299 | -11 |
| 23 Oct 2026, 02:40 | 7,310 | +3 |
| 22 Oct 2026, 11:34 | 7,307 | -36 |
| 19 Oct 2026, 20:18 | 7,343 | no change |
| 19 Oct 2026, 12:56 | 7,343 | +19 |
| 16 Oct 2026, 23:15 | 7,324 | -2 |
| 16 Oct 2026, 19:59 | 7,326 | first reading |
114 posts held, back to 3 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 44 pages of Telegram’s post history, 20 posts per page.
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. It is computed over the 56 of 61 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 114 (3 August 2026 – 17 November 2026) |
| Views total | 51,325 |
| Reactions total | 1,419 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 20:33 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.
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
3,622 reactions across 107 posts, in 11 distinct kinds. The most used accounts for 31.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,139 | 31.4% | |
| 🔥 | 672 | 18.6% | |
| custom 5397783192440711980 | 404 | 11.2% | |
| custom 5397883011775638618 | 362 | 9.99% | |
| custom 5372927589633534016 | 206 | 5.69% | |
| custom 5373138601376783766 | 189 | 5.22% | |
| custom 5237691237124820624 | 137 | 3.78% | |
| 👎 | 135 | 3.73% | |
| custom 5404783349183063850 | 130 | 3.59% | |
| custom 5237829955978547322 | 127 | 3.51% | |
| custom 5371027577706164284 | 121 | 3.34% |
Custom emoji. 8 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 107 of the 114 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 3,622 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 114 most recent posts we hold, published 3 August 2026 to 17 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @starbuychannel. 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 114 most recent posts we hold for this entry, published 3 August 2026 to 17 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.
Telegram’s own ‘edited’ marker: 24 of 62 posts held from the last 30 days (38.7%) 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).
⭐ Все работает в штатном режиме! @starbuy2bot
custom 53710275777061642844custom 53729275896335340162custom 53978830117756386182
Signed Artem
это рофл какой то, теперь у тг баг с выдачей звезд всех кто оплатил помним, и все выдадим как тг починит баг 🙏 старбай душат как могут
custom 53977831924407119807
Signed лео
💳 Временно новый бот - @starbuy2bot
custom 53729275896335340165custom 53710275777061642843
Signed лео
‼️ Временно пришлось убрать платежи за рубли из-за обновления Телеграм ❗ В скорейшем времени включим веб версию в которой можно будет купить звезды
custom 539778319244071198015
Signed лео
⚠️ Видим неполадки в работе текстового бота, исправим в течениии 10-15 минут
Signed лео
самое залайканное нововведение в комментариях появится в старбае (и в боте и в миниаппе) (без чего либо нарушающего закон рф) (опционально) (не сделает из меня бомжа)
custom 537292758963353401612custom 53710275777061642844custom 53731386013767837664
Signed лео
❓ Испытываете проблемы с интернетом сегодня? ❤️ - да, сегодня сильнее 💔 - нет, все как обычно
custom 539788301177563861847custom 539778319244071198027custom 52376912371248206242
Signed лео
Posted without readable text
custom 53978830117756386188custom 53729275896335340162custom 53731386013767837662
Signed лео
🕺
custom 52376912371248206243custom 53977831924407119801
Signed лео
🇯🇴 🇮🇶Телеграм только что заблокировали в Иордании и Ираке 😳 Официальная причина: угроза нацбезопасности и борьба с экстремизмом 👤 бедолаги? ❤️ - добро пожаловать в клуб 💔 - ждем их версию макса
custom 539788301177563861861custom 539778319244071198015custom 52376912371248206243
Signed лео
нажмите
custom 53977831924407119809custom 53978830117756386187
Signed лео
❤️ Также выйдет уточка компаньон ❓ Ее цель пока не особо понятна ❤️ - мило, мне нравится 💔 - зачем
custom 539788301177563861856custom 539778319244071198018
Signed лео
Showing the 12 most recent of 114 posts we hold for @starbuychannel. 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.
We recorded 1 post on @starbuychannel 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.
Named by 3 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“StarBuy” (@starbuychannel), 7,384 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/starbuychannel.
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.