Telegram RegisterThe public register of Telegram
Telegram profile photo for SAME Group

Channel

SAME Group

@samegroup

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

431subscribers

+21 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003812017016
TypeChannel
Username@samegroup
CreatedBetween 1 February 2026 and 18 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/samegroup

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

402431416.57 August 2026 — 410 subscribers7 August 2026 — 410 subscribers13 August 2026 — 402 subscribers20 August 2026 — 412 subscribers27 August 2026 — 428 subscribers4 September 2026 — 429 subscribers12 September 2026 — 431 subscribers7 August 202612 September 2026
7 measurements spanning 36 days, net +21. 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 398–435 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 02:17431+2
4 Sept 2026, 03:56429+1
27 Aug 2026, 16:44428+16
20 Aug 2026, 07:34412+10
13 Aug 2026, 13:27402-8
7 Aug 2026, 00:38410no change
7 Aug 2026, 00:03410first reading

Engagement

9 posts held, back to 18 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 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

180 reactions across 9 posts, in 9 distinct kinds. The most used accounts for 23.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54518319671316722144323.9%
custom 54519295230188328063318.3%
custom 54517525317115324332212.2%
custom 5451715204150761724179.44%
custom 5451671215095719713168.89%
custom 5452038078317237068168.89%
custom 5451681570261869769137.22%
custom 5472075634056403883126.67%
custom 545184002449031848384.44%

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

Measured over the 9 most recent posts we hold, published 18 July 2026 to 31 July 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

31 Jul 2026, 13:03 UTC289 views18 reactionsread 7 August 2026
Photo

Чем больше становится компания, тем меньше результат зависит от отдельных людей и тем больше — от процессов 🔑 Почему операционка определяет скорость роста компании, какую роль играет автоматизация, а также что отличает сильную систему управления — рассказал COO SAME Group. ◽️Читать лонгрид Также мы развиваем сильное профессиональное комьюнити вокруг индустрии и всегда рады новым знакомствам. Контакт COO: @plus_w2

custom 54516815702618697697custom 54519295230188328065custom 54518319671316722144custom 54516712150957197132

31 Jul 2026, 10:20 UTC301 views19 reactionsread 7 August 2026

🔑 SAME note «Операционное управление — это фундамент, на котором строится масштабирование». Баинг приносит результат, но именно процессы помогают повторять его снова и снова, сохраняя скорость, качество и управляемость. 🪙 Как это работает внутри медиабаинговой компании — расскажем в новом материале

custom 54520380783172370688custom 54518319671316722147custom 54517525317115324334

29 Jul 2026, 13:35 UTC327 views21 reactionsread 7 August 2026

Posted without readable text

custom 54519295230188328069custom 54517525317115324336custom 54518319671316722145custom 54516815702618697691

23 Jul 2026, 13:04 UTC405 views20 reactionsread 7 August 2026
Photo

В новом лонгриде рассказываем, как устроена роль Head of Media Buying, за что она отвечает и чем отличается от Team Lead. Разбираем: ◽️почему Head of Media Buying — это уже управленец бизнес-юнита; ◽️какие решения находятся в его зоне ответственности; ◽️ как строится работа с тимлидами, аналитикой, отделом дизайна и операционной командой; ◽️что стоит развивать Тимлиду, если следующая цель — Head of Media Buying

custom 54518319671316722148custom 54517525317115324336custom 54516712150957197135custom 54519295230188328061

22 Jul 2026, 12:05 UTC387 views23 reactionsread 7 August 2026
Photo

Собрали Starter Pack Head of Media Buying 🔑 — все то, что каждый день помогает управлять командой, принимать решения и масштабировать результат. Как думаешь, чего здесь не хватает? 🔅 пиши в комментариях ↓

custom 545192952301883280612custom 54517525317115324334custom 54516712150957197133custom 54516815702618697692custom 54517152041507617242

20 Jul 2026, 14:02 UTC388 views19 reactionsread 7 August 2026
Photo

Почему в SAME готовы растить специалистов быстрее остальных ? 🪙 Сильные специалисты появляются благодаря сильной системе. 🟠 В SAME Group развитие — это часть ежедневной работы: обмен опытом, понятные процессы, масштабные задачи и команда, которая помогает расти быстрее. Внутри карусели рассказываем, что стоит за этим подходом.

custom 54518319671316722149custom 54516712150957197135custom 54516815702618697693custom 54517525317115324332

18 Jul 2026, 15:27 UTC394 views21 reactionsread 7 August 2026
Photo

Что ограничивает потенциал этой связки? 🔘 Разбираем кейс глазами Team Lead SAME Group.

custom 545171520415076172410custom 54720756340564038836custom 54518319671316722145

18 Jul 2026, 12:55 UTC392 views19 reactionsread 7 August 2026

Posted without readable text

custom 54520380783172370688custom 54720756340564038836custom 54517152041507617245

18 Jul 2026, 12:55 UTC387 views20 reactionsread 7 August 2026
Photo

Масштабировали бы связку? 🟠 Продолжаем рубрику, в которой разбираем реальные связки и смотрим на них глазами медиабаинга. Сегодняшний кейс: ◽️ ГЕО: Аргентина ◽️ Залив: PWA-приложение ◽️ Креатив: статичное изображение Что видим: — акцент на крупном выигрыше; — упоминание известной личности; — обещание быстрого вывода средств. Вопрос: Масштабировали бы вы такую связку? 🪙 Голосуй в опросе, а сразу после поделимся …

custom 54518400244903184838custom 54519295230188328066custom 54518319671316722145custom 54516712150957197131

Showing the 9 most recent of 9 posts we hold for @samegroup. 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.

Mentions

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

“SAME Group” (@samegroup), 431 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/samegroup.

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.