у кого-то вопросы остались?
❤105custom 528730742947267627018🤣6🔥3😎2

Channel
@AuroraTeam
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry
199,310subscribers
-15,405 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001735223705 |
|---|---|
| Type | Channel |
| Username | @AuroraTeam |
| Description | профессионально нажимаем кнопки 🤙 Наш мерч: https://market.yandex.ru/cc/ABDBds Промокод AURORATG — скидка 20% КФЫ ТОП ФРИБЕТОВ ГОРЫ 1XBET — Партнёр Авроры 🤝 Лови бонус от 1X до $800 с промиком AURORACS: https://1xrora.pro/auroracstg |
| Created | 15 August 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/AuroraTeam |
Gambling & betting — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @Aurora_Dota2/611712 Aug 2026, 14:49 UTC | @AuroraTeam/7461 · this entry12 Aug 2026, 15:01 UTC | 1.00 | 13 minutes |
| @Aurora_Dota2/619815 Aug 2026, 10:45 UTC | @AuroraTeam/7487 · this entry15 Aug 2026, 12:33 UTC | 1.00 | 1.8 hours |
| @Aurora_Dota2/626914 Sept 2026, 13:00 UTC | @AuroraTeam/7616 · this entry14 Sept 2026, 13:33 UTC | 1.00 | 32 minutes |
| @Aurora_Dota2/648528 Oct 2026, 21:25 UTC | @AuroraTeam/7918 · this entry28 Oct 2026, 21:25 UTC | 1.00 | under a minute |
| @AuroraTeam/7938 · this entry1 Nov 2026, 07:20 UTC | @Aurora_Dota2/65001 Nov 2026, 08:01 UTC | 1.00 | 40 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Aurora_Dota2 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 36 minutes | @Aurora_Dota2 (3–2) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 3 of the 3 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 88 comparable posts for this entry, running 28 July 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Recorded under the key clone_mutual, last confirmed 11 November 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 14:36 | 199,310 | -287 |
| 9 Nov 2026, 01:31 | 199,597 | -355 |
| 7 Nov 2026, 17:59 | 199,952 | -466 |
| 6 Nov 2026, 14:08 | 200,418 | -409 |
| 5 Nov 2026, 12:45 | 200,827 | -541 |
| 4 Nov 2026, 13:51 | 201,368 | +1,948 |
| 3 Nov 2026, 12:38 | 199,420 | +199 |
| 2 Nov 2026, 11:49 | 199,221 | +154 |
| 1 Nov 2026, 12:41 | 199,067 | +947 |
| 31 Oct 2026, 10:31 | 198,120 | -225 |
| 30 Oct 2026, 07:55 | 198,345 | -308 |
| 29 Oct 2026, 06:56 | 198,653 | -320 |
| 28 Oct 2026, 05:00 | 198,973 | -287 |
| 27 Oct 2026, 04:15 | 199,260 | -276 |
| 26 Oct 2026, 02:16 | 199,536 | -270 |
| 25 Oct 2026, 02:44 | 199,806 | -335 |
| 24 Oct 2026, 05:20 | 200,141 | +973 |
| 23 Oct 2026, 02:20 | 199,168 | +875 |
| 21 Oct 2026, 22:16 | 198,293 | +35 |
| 20 Oct 2026, 20:47 | 198,258 | first reading |
533 posts held, back to 27 July 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 196 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.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 533 (27 July 2026 – 10 November 2026) |
| Views total | 1,326,850 |
| Reactions total | 25,117 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 02:29 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 11 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.
Measured directly from 83 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.
97,179 reactions across 530 posts, in 147 distinct kinds. The most used accounts for 33.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 32,053 | 33.0% | |
| custom 5350521806107221261 | 17,300 | 17.8% | |
| 🤣 | 12,598 | 13.0% | |
| 🔥 | 2,314 | 2.38% | |
| 😭 | 1,605 | 1.65% | |
| custom 5395759863412324818 | 1,379 | 1.42% | |
| 👍 | 1,322 | 1.36% | |
| custom 5395400305930173261 | 1,278 | 1.32% | |
| custom 5361805303669113217 | 1,218 | 1.25% | |
| custom 5287307429472676270 | 1,139 | 1.17% | |
| custom 5474457803307359926 | 913 | 0.94% | |
| 👎 | 821 | 0.845% | |
| custom 5278432678419410674 | 819 | 0.843% | |
| 🙏 | 770 | 0.792% | |
| custom 5454360762271178443 | 705 | 0.725% | |
| 🤯 | 695 | 0.715% | |
| custom 5332802330117054338 | 682 | 0.702% | |
| custom 5287449459746189063 | 587 | 0.604% | |
| custom 5197394281995742980 | 550 | 0.566% | |
| custom 5249166440551978981 | 505 | 0.52% | |
| 127 further kinds | 17,926 | 18.4% |
Custom emoji. 12 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 532 of the 533 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 97,968 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 533 most recent posts we hold, published 27 July 2026 to 10 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 @AuroraTeam. 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 533 most recent posts we hold for this entry, published 27 July 2026 to 10 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: 78 of 180 posts held from the last 30 days (43.3%) 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).
у кого-то вопросы остались?
❤105custom 528730742947267627018🤣6🔥3😎2
🤔 Ну, не просто же так они добавили питомцев 💚 Если тоже что-то подозреваешь перед выходом мажорного обновления — делай предикт на Polymarket
❤72🤣5custom 53505218061072212615custom 52832020763928274294
Posted without readable text
custom 535052180610722126166🤣21❤17🔥4🙏1custom 52873074294726762701custom 53503494834293706781
Posted without readable text
🤣83🙏20❤8😭5custom 53505218061072212614🔥3custom 53503494834293706781
💚FACEIT ВРАЛИ НАМ ВСЕ ЭТО ВРЕМЯ! Ведь кто может не знать что-либо про Хантареса в 2026?
custom 5287307429472676270201❤26🤯10🥴4🤣3💅2💔2
💚 У тебя всего 100$, чтобы победить праймовых Виталити 💚 Какую команду собираем?
❤114🤣36custom 535052180610722126112😎3custom 52873074294726762703💅1custom 53503494834293706781
💀 [ ОБНОВЛЕНИЕ COUNTER-STRIKE 2 ] - Удалён режим «Большие головы» - Был добавлен режим «Subway Surfers» 💚 А, СТОП, В КС2 ТАКОГО НЕ ВЫХОДИЛО... Зато выходило на 1xBet, где можно ставить на Subway Surfers 😏
🤣92❤23😭5custom 53505218061072212612custom 53999382610009577241
Posted without readable text
🔥79❤19🤣6custom 53505218061072212615custom 52561210663460292064
📞 Что-что? Они — кто?? Оборвалось... Давайте думать, че вы, подсказывайте 🚗 — машины ☠️ — монстры 🥰 — маси
🥰241custom 540936862190853723149custom 539993826100095772446❤7🤣2🔥1
Posted without readable text
❤210custom 535052180610722126112custom 52873074294726762709custom 52782414063458485696custom 53503494834293706783
Posted without readable text
custom 528730742947267627059❤26custom 52782414063458485698custom 53505218061072212616💔1🤣1🥰1
💔 Покидаем IEM Beijing 2026. Будем работать над ошибками, чтобы показать красивый CS уже на PGL Singapore Major. Спасибо за поддержку каждого, увидимся в декабре.
🙏128🤣45😭24❤15💔9🤬2
Showing the 12 most recent of 533 posts we hold for @AuroraTeam. 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.
@AuroraTeam edited 8 posts 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Опрос
Shares as published. No per-option vote count is published by Telegram, so none is 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 533 most recent posts we hold, published 27 July 2026 to 10 November 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 10 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 11 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 129 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“Aurora CS2” (@AuroraTeam), 199,310 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/AuroraTeam.
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.