Telegram RegisterThe public register of Telegram

Channel

SaveMod New

@modsaver

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

146,112subscribers

+3,573 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001504736125
TypeChannel
Username@modsaver
Description📰 Новостной канал бота @ModSaverRobot 🗣 Вступить в чат - @savemod_chat 🧑‍💻Тех.Поддержка - @HelpModSaverBot
Created26 August 2021measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/modsaver

Topic

Technology — 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 9 August 2026 and assigned it the closest of 31 fixed categories, at 74% 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.

Observations

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.

Content that also appears on other registered channels

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.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@modsaver/146 · this entry10 Jul 2026, 12:55 UTC@savemod1/53510 Jul 2026, 17:02 UTC1.004.1 hours
@savemod1/5551 Aug 2026, 04:00 UTC@modsaver/153 · this entry1 Aug 2026, 04:03 UTC1.003 minutes
@savemod1/5643 Aug 2026, 04:27 UTC@modsaver/159 · this entry3 Aug 2026, 05:13 UTC1.0046 minutes
@savemod1/5675 Aug 2026, 20:00 UTC@modsaver/163 · this entry5 Aug 2026, 20:33 UTC1.0033 minutes
@savemod1/5717 Aug 2026, 10:28 UTC@modsaver/166 · this entry7 Aug 2026, 10:28 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@savemod16 (6/6 hand-verifiable sample passed)1.0019 minutes@savemod1 (51)

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. 1 of the 4 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 11 comparable posts for this entry, running 3 April 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @modsaver — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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.

Also posting the same content

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.

Growth

142,539147,427144,9837 August 2026 — 142,539 subscribers7 August 2026 — 142,539 subscribers8 August 2026 — 144,258 subscribers9 August 2026 — 147,427 subscribers10 August 2026 — 146,985 subscribers11 August 2026 — 146,489 subscribers12 August 2026 — 146,112 subscribers146,1127 August 202612 August 2026
7 measurements spanning 5 days, net +3,573. 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 141,806–148,160 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 12:43146,112-377
11 Aug 2026, 16:12146,489-496
10 Aug 2026, 12:55146,985-442
9 Aug 2026, 10:11147,427+3,169
8 Aug 2026, 11:13144,258+1,719
7 Aug 2026, 19:30142,539no change
7 Aug 2026, 19:18142,539first reading

Engagement

14 posts held, back to 26 August 2021the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 15 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
41.0%
avg views ÷ 146,112 subscribers
Avg views / post
59,900
7 posts measured
Reaction rate
0.508%
reactions ÷ views · ER floor
Posts in window
7
of 14 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 9 August 2026
Posts held14 (26 August 20219 August 2026)
Views total419,000
Reactions total2,128
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 18:13 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.

What this channel posts

Photos
15
Videos
1
Links
8

Lifetime counters from Telegram’s own channel header, read 12 August 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.

Video runtime
12s
Average length
12s

Measured directly from 1 video 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.

Reaction mix

2,603 reactions across 13 posts, in 13 distinct kinds. The most used accounts for 61.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,59561.3%
👍26810.3%
❤‍🔥1686.45%
👏1565.99%
😁1505.76%
🥰913.50%
🔥863.30%
🤔522.00%
🌚140.538%
😱110.423%
💯90.346%
👀20.077%
10.038%

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

Measured over the 14 most recent posts we hold, published 26 August 2021 to 9 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
102
across the posts below
Posts paid on
13
of 13 we hold a reading for · 100%
Most on one post
62
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @modsaver. 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 14 most recent posts we hold for this entry, published 26 August 2021 to 9 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

9 Aug 2026, 12:41 UTC≈31,200 views276 reactions1 Starread 12 August 2026
Photo

Если вам кто-то пишет в лс и предлагает купить ваш подарок, а потом кидает говнобота(они все приблизительно одинаково бездарно сделанные куски говна с одной страницей функционала) похожего на один из этих - это 100% скам. Передайте мудиле привет от savemod ❤️ и в черный список. Не ведитесь на гарантов, даже если в них большая цифра участников - они накручены. Из маркетов знаю Портал - там и советую продавать свои под

196🥰46👏29😁5

7 Aug 2026, 10:28 UTC≈48,500 views288 reactions6 Starsread 12 August 2026

От моего имени всякие чепухи могут пытаться втереть вам верификации, услуги и прочее. От своего имени я говорю сам. Если вам что-то предлагают купить - лучше уточняйте в @SaveMod_Chat И напоминаю: лучшее средство если вам угрожают - черный список. Не общайтесь - сразу блокируйте, от вас отвалят. Бот для подключения: @SaveMod Бот для скачивания видео: @SaveModGameBot

189❤‍🔥55🥰29👏15

5 Aug 2026, 20:33 UTC≈70,500 views384 reactions62 Starsread 12 August 2026
Photo

Передаю 42 бригаде имени 47 хромосомы пламенный привет и пожелание начать разбираться в технических вопросах перед тем, как строить из себя человека, имеющего право их обсуждать. Суть этого проекта в отображении удаленных и отредактированных сообщений. А для этого их надо сохранить. Сэйв Мод. Сохранение. Хватит обвинять/спрашивать, сохраняет ли бот сообщения? Да! В этом суть его работы. Сохраняет и следит за списком

261👍60🔥51😁12

5 Aug 2026, 12:16 UTC≈51,300 views168 reactions5 Starsread 12 August 2026
Forwarded from @GladOS_Blog

Вчерашнее удаление телеграм из эпстора связано с тем, о чем я писал еще давно. Есть кучка вымогателей, которые шантажируют владельцев групп, угрожая удалением. Методом, который я описывал ранее, они размещают запрещенный контент в группах, редактируя старые сообщения и жалуются в эпл. Вчера у них это получилось слишком эффективно. А если бы в вашей группе стоял @NoEdits_Bot - такие угрозы вам были бы не страшны. Нап

111👍28🤔21❤‍🔥8

3 Aug 2026, 05:13 UTC≈67,400 views141 reactions2 Starsread 12 August 2026
Photo

Звёзды для пользователей @SaveMod доступны по самой низкой цене. Активные пользователи @SaveMod с подпиской могут покупать каждый день пакет из 100 звезд по 118 рублей! Либо без ограничений по 124 рубля за 100 звезд! Перейдите сюда и бот вам выдаст актуальную ссылку на бота @SaveMod

❤‍🔥7142👍19💯9

1 Aug 2026, 09:04 UTC≈67,600 views130 reactions5 Starsread 12 August 2026
Forwarded from @savemod1Photo

Объединение подписок SaveMod и UserBot: покупка одной даёт бесплатный доступ ко второй. Работает с этого момента. Зачем использовать оба? @SaveMod через автоматизацию выполняет задачи, для которых задумывался: мониторинг удалённых и отредактированных сообщений. Подключите по ссылке tg://settings/edit, выберите "Автоматизацию" и введите @SaveMod. Если не работает - отключите и подключите снова. Сильная сторона @Save

83😁17👍15🔥15

1 Aug 2026, 04:03 UTC≈82,500 views741 reactions3 Starsread 12 August 2026
Photo

Вчера пнули одного петушка из чата. Он пошел к своему педодружку из Hikka UserBot жаловаться. Долбоеб по классике высрал статью якобы я что-то ворую у пользователей. На вопрос у кого и что - ничего он ответить не смог(первые два скрина). А теперь десерт. Кто на самом деле опасен - Hikka UserBot. Судя по третьему скрину они имеют полный доступ к вашим данным, анализируют написанное и кого хотят - сдают ментам. Не хоти

521😁116👍82👏22

10 Jul 2026, 12:55 UTC≈137,000 views217 reactions4 Starsread 12 August 2026
Photo

@SaveModUserBot - тестим, сэйвмод 2.0 Работает в том числе и в группах. О багах сообщаем сюда. Да, создается отдельная сессия и да, бот получает доступ. Не надо этого бояться - это необходимо для работы.

👏9073🤔31❤‍🔥23

26 Jun 2026, 00:57 UTC≈81,900 views23 reactions5 Starsread 12 August 2026

Теперь можно красиво оформить свой профиль через нарезку сторисов. Выдайте тут боту разрешение публиковать сторисы. Кидаете в чат с другом любое фото. И отвечаете на фото командой .story Пример профиля: @mostecloud

18❤‍🔥31🔥1

21 Jun 2026, 11:00 UTC≈49,800 views33 reactions2 Starsread 12 August 2026

Акция Savemod: для клиентов доступна покупка 🌟 по 1₽ ⁠

🔥19😱112🌚1

14 Jun 2026, 17:24 UTC≈41,700 views50 reactions1 Starread 12 August 2026

Два дефолтных бота. Первый скачивает видео с YouTube. Без обязательной подписки на кучу говна. @SaveModGameBot - качать можно через ЛС бота или в инлайн-режиме (поиск по YouTube и скачивание по ссылкам). Второй - исчезающие записки. Если нужно отправить в группу видео, которое нельзя кидать напрямую: отправьте видео боту @SaveModNotesBot, а в группу — ссылку на бота, который выдаст видео. Доступны записки в инлайн

29👍13❤‍🔥8

7 May 2026, 00:40 UTC≈26,400 views83 reactions2 Starsread 12 August 2026
Forwarded from @savemod1Photo

Теперь подключать ботов для управления профилем и сообщениями можно без подписки Telegram Premium. Не забудьте перед этим обновить клиент! Ловите подарок для теста нашего нового бомбезного функционала. Теперь вас обмануть будет ещё сложнее. Когда вам в лс напишет незнакомый пользователь - бот выдаст о нем полный отчёт.

👍3730🥰16

Showing the 12 most recent of 14 posts we hold for @modsaver. 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.

Forward network

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.

Mentions

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

“SaveMod New” (@modsaver), 146,112 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/modsaver.

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.