Telegram RegisterThe public register of Telegram
Telegram profile photo for Scrooge Team

Channel

Scrooge Team

@scrgtm

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

1,255subscribers

+56 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002181648425
TypeChannel
Username@scrgtm
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/scrgtm

Growth

1,1921,3241,2587 August 2026 — 1,199 subscribers7 August 2026 — 1,199 subscribers8 August 2026 — 1,192 subscribers11 August 2026 — 1,324 subscribers15 August 2026 — 1,311 subscribers18 August 2026 — 1,293 subscribers21 August 2026 — 1,290 subscribers24 August 2026 — 1,267 subscribers27 August 2026 — 1,255 subscribers1,2557 August 202627 August 2026
9 measurements spanning 20 days, net +56. 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 1,172–1,344 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 09:331,255-12
24 Aug 2026, 16:141,267-23
21 Aug 2026, 08:281,290-3
18 Aug 2026, 04:421,293-18
15 Aug 2026, 08:251,311-13
11 Aug 2026, 21:321,324+132
8 Aug 2026, 13:431,192-7
7 Aug 2026, 23:181,199no change
7 Aug 2026, 16:221,199first reading

Engagement

19 posts held, back to 16 April 2026the 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
58.8%
avg views ÷ 1,255 subscribers
Avg views / post
738
1 post measured
Reaction rate
3.12%
reactions ÷ views · ER floor
Posts in window
1
of 19 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 6 August 2026
Posts held19 (16 April 20266 August 2026)
Views total738
Reactions total23
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 23:18 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

563 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 47.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 520218621136761504726947.8%
custom 52022188058744234069917.6%
custom 52016908727893651077613.5%
custom 5201858647096848699356.22%
custom 5201910014905709886346.04%
custom 5202214175899676858234.09%
custom 5199516841948514290183.20%
custom 520178487244360721191.60%

Custom emoji. Every row above is a 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 19 of the 19 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 563reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 16 April 2026 to 6 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.

Telegram Stars

Stars received
13
across the posts below
Posts paid on
3
of 19 we hold a reading for · 16%
Most on one post
7
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @scrgtm. 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 19 most recent posts we hold for this entry, published 16 April 2026 to 6 August 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.

Recent posts

6 Aug 2026, 10:22 UTC738 views23 reactionsread 7 August 2026
Photo

Почему у лучших байеров есть жизнь вне рекламных кабинетов Есть миф, что топовый результат в баинге — это когда ты живёшь в кабинетах 24/7, реагируешь на каждое движение цифр и засыпаешь на клавиатуре с открытым адсом. На практике всё наоборот: у большинства сильных байеров, которые стабильно в плюсе на длинной дистанции, есть чёткая жизнь за пределами рекламных кабинетов — и это не побочный эффект успеха, а одно из

custom 520218621136761504717custom 52016908727893651073custom 52019100149057098862custom 52018586470968486991

20 Jul 2026, 11:33 UTC806 views34 reactionsread 7 August 2026
Photo

❤️ Сейчас наша команда масштабируется и усиливается, поэтому мы в поисках Media Buyer Facebook Ожидаем от кандидата: ⚙️ От 1 года успешного опыта заливов в iGaming вертикали; ⚙️ Умеют работать с крупными рекламными бюджетами и масштабировать прибыльные связки; ⚙️ Обладают актуальными кейсами заливов за последние 3 месяца по Tier 2–3 GEO | CPA. Почему сильные баеры выбирают нас: 📌 масштабируем рабочие связки без ог

custom 519951684194851429018custom 52021862113676150476custom 52016908727893651074custom 52018586470968486994custom 52019100149057098861custom 52022141758996768581

13 Jul 2026, 11:23 UTC814 views32 reactionsread 7 August 2026
Photo

Влияние AI на структуру команд ИИ - это уже не про картинки, а про жесткое сокращение костов и рост чистой прибыли на каждого сотрудника. Главный сдвиг: масштабирование спенда больше не требует линейного раздувания штата. ⚡️ Какие линейные роли пойдут под нож Заливалы (руки): Ручной микроменеджмент, дублирование и стоп минусовых адсетов уже скоро и лучше будут делать автоправила и алгоритмы самих источников. Рути

custom 520218621136761504723custom 52016908727893651076custom 52019100149057098863

2 Jul 2026, 11:23 UTC822 views34 reactionsread 7 August 2026
Photo

Поглощение на рынке медиабаинга: Как купить чужой ROI, а не растить его с нуля ⚙️ Органический рост через обучение джунов - это долго, дорого и больно, хотя и эффективно. Пока вы с нуля выводите новичка в плюс, рынок меняется, а связки умирают. Стратегия быстрого и агрессивного масштабирования для сильного овнера сегодня - это поглощение готовых микро-команд или сильных соло-байеров вместе с их наработками. Вы поку

custom 520221880587442340624custom 52019100149057098865custom 52021862113676150473custom 52018586470968486992

23 Jun 2026, 11:11 UTC916 views26 reactionsread 7 August 2026
Photo

Иллюзия бурной деятельности: Почему околоарбитражный стафф обходится как топ-менеджмент, а работает час в день 📌 Мы привыкли считать каждый цент в CPA и молиться на высокий ROI, но часто закрываем глаза на зарплатную ведомость инфраструктуры. Рынок околоарбитражных кадров перегрет до абсурда: зарплаты обслуживающего персонала пробили потолок IT-сектора, а реальная вовлеченность часто сводится к часу работы, размазан

custom 520218621136761504719custom 52019100149057098864custom 52022141758996768583

15 Jun 2026, 11:02 UTC831 views21 reactionsread 7 August 2026
Photo

Личный бренд в Affiliate: Почему байеру не нужно светить лицом, и почему деньги любят тишину Сейчас из каждого утюга кричат, что без личного бренда ты никто. Лента забита арбитражниками, которые флексят спорткарами, пилят лайфстайл-сторис и продают наставничество. У новичков складывается иллюзия: чтобы стать топом, нужно быть публичным. Но так ли это на самом деле, если твоя реальная цель - стабильно заливать в плюс

custom 520218621136761504714custom 52016908727893651074custom 52018586470968486992custom 52022141758996768581

10 Jun 2026, 10:34 UTC727 views29 reactionsread 7 August 2026
Photo

Тимбилдинг, который работает: Как сплотить амбициозных байеров без скучных тренингов ❌ Загонять заряженных на профит арбитражников в переговорку, чтобы строить дженгу или падать друг другу в доверительные объятия - худшая идея. Амбициозные байеры терпеть не могут духоту и искусственный корпоративный позитив. Классические тренинги здесь не работают: они вызывают лишь кринж. ⚙️ В Scrooge Team мы быстро поняли, что лу

custom 520218621136761504719custom 52018586470968486997custom 52016908727893651073

1 Jun 2026, 09:24 UTC842 views27 reactionsread 7 August 2026
Photo

Выращивание джунов: слив бюджета или лучшая долгосрочная инвестиция? ❌ «Проще схантить готового топа, чем возиться с новичками» - мантра овнеров, которые устали оплачивать чужие ошибки на тестах. На первый взгляд, математика сходится: джун жжет расходники, банит кабы, отвлекает тимлида и первые месяцы гарантированно работает в минус. ✔️ Но если мы строим системный бизнес, а не стартап-однодневку, то покупка «звезд»

custom 520218621136761504719custom 52022141758996768585custom 52018586470968486993

25 May 2026, 10:19 UTC731 views25 reactionsread 7 August 2026
Photo

Из топ-баера в Тимлиды: почему это лучший сценарий для команды ⚙️ На рынке гуляет популярный миф: «Сделал из лучшего баера управленца - потерял баера». Якобы он погрязнет в табличках, выгорит, а трафик встанет. Но давайте честно: в реалиях арбитража «кабинетные менеджеры» без свежего опыта заливов не выживают. Выращивание тимлида из самого сильного и плюсового игрока - это не ловушка, это единственно верный путь ма

custom 520218621136761504719custom 52018586470968486994custom 52016908727893651072

19 May 2026, 12:39 UTC689 views43 reactionsread 7 August 2026
Photo

Скрытые ГЕО: почему стоит перестать ломиться в перегретый Tier-1 Каждый раз, когда на конфе заходит речь про масштабирование, кто-то обязательно произносит мантру: «Надо идти в Tier-1, там самые жирные выплаты». США, Канада, Великобритания, Австралия манят новичков и опытные команды цифрами по 200-300 баксов за игрока. Кажется, что именно там - настоящая элита арбитража. ⚙️ А теперь давайте снимем розовые очки и по

custom 520221880587442340636custom 52016908727893651074custom 52022141758996768583

13 May 2026, 14:19 UTC638 views26 reactionsread 7 August 2026
Photo

Ожидание vs Реальность: почему новички приходят за миллионами, а уходят с минусом Инфополе продает медиабаинг как красивую картинку: нашел связку, нажал пару кнопок в Ads Manager, поймал ROI 300% и улетел зимовать на Бали. Этот образ стабильно генерирует бесконечный поток новичков, уверенных, что арбитраж - это легальный чит-код на быстрые деньги. Реальность же встречает их ледяным душем из банов и слитых денег. Ра

custom 520218621136761504719custom 52019100149057098864custom 52016908727893651072custom 52022141758996768581

7 May 2026, 11:40 UTC635 views28 reactionsread 7 August 2026
Photo

Эра нейросетей в баинге: кто кого заменит и почему креативщики могут спать спокойно 🔗 Каждый второй паблик уже успел похоронить профессию дизайнера и копирайтера. Сценарий рисуют апокалиптичный: ChatGPT пишет идеальные тексты, Midjourney и Gemini генерирует креативы с космическим CTR, а автоправила и AI-оптимизация ФБ сами крутят кампании в плюс. Кажется, что баинг-команде скоро останется только выводить профит. Но

custom 520221880587442340619custom 52016908727893651075custom 52018586470968486993custom 52021862113676150471

Showing the 12 most recent of 19 posts we hold for @scrgtm. 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 — 557,333 of 1,620,455entries 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

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.

Mentions

Named by 1 registered channel — 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.

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

“Scrooge Team” (@scrgtm), 1,255 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/scrgtm.

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.