Posted without readable text
😍4

Channel
@svoy_v_alfe_official
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
45,207subscribers
-108 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001967059434 |
|---|---|
| Type | Channel |
| Username | @svoy_v_alfe_official |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/svoy_v_alfe_official |
Marketing & affiliate — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
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 word for word 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 |
|---|---|---|---|
| @svoy_v_alfe_official/2242 · this entry2 Aug 2026, 07:15 UTC | @svoyvalfe_nizhnvolga/65092 Aug 2026, 08:03 UTC | 1.00 | 49 minutes |
| @svoy_v_alfe_official/2239 · this entry1 Aug 2026, 07:03 UTC | @svoyvalfe_nizhnvolga/65102 Aug 2026, 17:34 UTC | 1.00 | 35 hours |
| @svoy_v_alfe_official/2245 · this entry3 Aug 2026, 09:27 UTC | @svoyvalfe_nizhnvolga/65153 Aug 2026, 13:01 UTC | 1.00 | 3.6 hours |
| @svoy_v_alfe_official/2246 · this entry4 Aug 2026, 11:45 UTC | @svoyvalfe_nizhnvolga/65184 Aug 2026, 11:48 UTC | 1.00 | 2 minutes |
| @svoy_v_alfe_official/2247 · this entry4 Aug 2026, 13:27 UTC | @svoyvalfe_nizhnvolga/65194 Aug 2026, 13:31 UTC | 1.00 | 4 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @svoyvalfe_nizhnvolga | 5 (5/5 hand-verifiable sample passed) | 1.00 | 26 minutes | this entry (5–0) |
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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 14 comparable posts for this entry, running 29 July 2026 to 7 August 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.
Across the whole group of 2, the earliest publisher we hold is @svoy_v_alfe_official — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 22:03 | 45,207 | -17 |
| 11 Aug 2026, 20:48 | 45,224 | -17 |
| 10 Aug 2026, 17:46 | 45,241 | -23 |
| 9 Aug 2026, 19:31 | 45,264 | -41 |
| 8 Aug 2026, 18:02 | 45,305 | -8 |
| 7 Aug 2026, 14:48 | 45,313 | -2 |
| 7 Aug 2026, 12:30 | 45,315 | no change |
| 7 Aug 2026, 12:18 | 45,315 | first reading |
28 posts held, back to 29 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 16 pagesof 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 12 August 2026 |
|---|---|
| Posts held | 28 (29 July 2026 – 12 August 2026) |
| Views total | 43,215 |
| Reactions total | 273 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 20:04 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.
273 reactions across 23 posts, in 9 distinct kinds. The most used accounts for 51.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 140 | 51.3% | |
| 🔥 | 69 | 25.3% | |
| 👍 | 28 | 10.3% | |
| custom 5431766202047299172 | 14 | 5.13% | |
| ❤🔥 | 6 | 2.20% | |
| 👏 | 5 | 1.83% | |
| custom 5420377348937641459 | 4 | 1.47% | |
| 😍 | 4 | 1.47% | |
| 🏆 | 3 | 1.10% |
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 areTelegram’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 23 of the 28 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 273reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 28 most recent posts we hold, published 29 July 2026 to 12 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.
Posted without readable text
😍4
ГОТОВИМ КОЕ-ЧТО СЕКРЕТНОЕ И ИНТЕРЕСНОЕ 🤫 На следующей неделе вас будет ждать особый эфир. Подробности совсем скоро, следите за новостями в канале ✨
❤8❤🔥6🔥4
КАК УВИДЕТЬ ВСЮ КОМАНДУ ЗА 5 МИНУТ ❔ Теперь у наставников появилась возможность всегда быть в курсе того, как идут дела у команды. В Личном кабинете заработал новый функционал управления командой — по сути, ваш личный навигатор по структуре. ➡️ На эфире мы разберём как он устроен и как им пользоваться, чтобы тратить минимум времени и получать максимум пользы. ➡️ Покажем, как фильтры помогают распределять партнёров…
🔥3
НОВАЯ КРЕДИТНАЯ КАРТА: 150 ДНЕЙ БЕЗ % 🔥 С 10 августа запустили обновлённую линейку кредитных карт. Главное изменение — льготный период можно продлить до 150 дней 🤩 Нужно только подключить автопродления один раз, и каждый новый период автоматически продлевается до 150 дней. Первое продление бесплатное. При следующих — первые 60 дней без комиссии, с 61-го по 150-й день комиссия 1,9% от суммы долга за покупки. Что е…
❤8🔥3
Свой в Альфе pinned a photo
❤️РАСПИСАНИЕ ЭФИРОВ 10-15 августа Фокус месяца: поиск и запуск партнеров 🔥10.08 (пн) в 11:00 по мск Сила системы: как помочь новичкам получить первый результат за 1 неделю 👤 Для кого: все активные партнеры Спикеры:Ткачук Екатерина- региональный куратор, Слепокурова Наталья- топ-партнер проекта Зап…
❤2
Вступайте в канал своего региона ✅ Свои в Альфе есть по всей стране. Чтобы каждый мог найти своих, мы объединили города в 12 регионах. У каждого региона есть куратор, который помогает расти партнёрам: ведёт мероприятия, обучающие эфиры и телеграм-канал⚡ Если вы ещё не вступили в канал своего региона: 1️⃣ Перейдите по ссылке 2️⃣ Проверьте какие города и области входят в регион. 3️⃣ Присоединяйтесь к каналу и приглаш…
👍3
СИЛА СИСТЕМЫ 💪 Как помочь новичкам получить первый результат за 1 неделю Знакомая ситуация? Новичок пропадает, молчит, обещает начать с понедельника. И вы понимаете, что без системы он просто сольётся, а вы потратите время и энергию, так и не дождавшись результата. На эфире мы разберём готовую систему наставника, которая работает: — Как провести первую встречу, чтобы зажечь сделать первые шаги, а не напугать слож…
👍5❤1
Свой в Альфе pinned a photo
ВСТУПАЙ В КАНАЛЫ ПРОЕКТА ❤️ Хочешь досконально разбираться в продуктах банка и быть в курсе последних новостей проекта? Вступайте в каналы❤️ О проекте 🔥 Свой в Альфе ТГ: ссылка …
🔥7
ЗАБЕРИТЕ НОВУЮ ССЫЛКУ НА ОФОРМЛЕНИЕ ДЕБЕТОВОЙ КАРТЫ ❤️ Мы обновили ссылку, чтобы всем было удобнее. ✨😉Клиент больше не увидит пугающее сообщение про «Небезопасное соединение». Ссылка открывается корректно в любом браузере и не требует установки сертификатов — никаких лишних предупреждений и потери доверия на старте. Важно: Все прежние ссылки продолжают работать, и все продажи по ним будут учтены в полном объёме. …
❤12
НАБРАТЬ ЗА 60 МИНУТ — РЕАЛЬНО 🚀 Ждёте пока партнёры найдутся сами? Пора действовать. На эфире получите три компонента скорости: проверенные скрипты, контроль над диалогом и решимость действовать. План действий: Мы даём готовые скрипты 🔥 вы применяете их сразу на эфире-практикуме, отправляя сообщения знакомым 🔥 получаете быстрые ответы и в моменте разбираем возражения 🔥 знакомые просят ссылку для участия в проекте.…
🔥8❤5
Showing the 12 most recent of 28 posts we hold for @svoy_v_alfe_official. 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.
@svoy_v_alfe_official 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.
Citation-graph rank — 6,130 of 1,151,006entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Свой в Альфе” (@svoy_v_alfe_official), 45,207 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/svoy_v_alfe_official.
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.