Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝐑𝐮𝐥𝐞𝐬.

Channel

𝐑𝐮𝐥𝐞𝐬.

@seravionrules

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

2subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003660703701
TypeChannel
Username@seravionrules
Created5 June 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live31 August 2026
Measurements held2
On Telegramt.me/seravionrules

Growth

210 August 2026 — 2 subscribers13 August 2026 — 2 subscribers10 August 202613 August 2026
2 measurements spanning 3 days. 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–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 20:492no change
10 Aug 2026, 14:312first reading

Engagement

7 posts held, back to 5 June 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 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 7 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
1

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

Recent posts

31 Jul 2026, 09:56 UTC8 viewsread 13 August 2026

𝐁𝐎𝐓 𝐅𝐎𝐑 𝐂𝐎𝐌𝐏𝐋𝐀𝐈𝐍𝐓𝐒: @seravionbot

31 Jul 2026, 09:55 UTC19 viewsread 13 August 2026

13. Правила использования бота для жалоб О1. Используйте бота исключительно для отправки жалоб. Сообщения, не относящиеся к жалобам (флуд, шутки, спам и т.п.), запрещены. Наказание: бессрочная блокировка в боте. О2. Жалобу можно подать только в том случае, если участник действительно нарушил правила или мешает комфортному общению в чате. О3. К каждой жалобе обязательно прикладывайте доказательства (скриншоты

6 Jul 2026, 19:36 UTC31 viewsread 13 August 2026

12. Правила по взаимному пиару О1. можем не озвучивать причину отказа. О2. делаем вп со всеми, кроме тех, что находятся в базовом дни, щп, а также с каналами, содержащими шок-контент. O3. мы не поддерживаем каналы, с которыми делаем вп. О4. промежутка между вп нет. О5. повторную заявку принимаем только на следующий день после удаления рт. О6. по поводу вп писать @yournamelie О7. делаем вп от +0 пд

25 Jun 2026, 14:36 UTC56 viewsread 13 August 2026

10. Добровольный выход Если участник принимает решение покинуть чат, рекомендуется заранее уведомить администрацию. При наличии роли или занимаемой позиции необходимо указать её и отметить владельца либо совладельца сообщества для дальнейшего распределения обязанностей. 11. Выход из флуда. Когда вы выходите из флуда, держите у себя в голове, что обратного пути у вас нет. Вы не можете покинуть флуд просто потому ч

5 Jun 2026, 20:30 UTC108 viewsread 13 August 2026

Устав сообщество. Добро пожаловать в чат. Его главная цель, создать комфортную среду для общения, где каждый участник может чувствовать себя спокойно и безопасно. Вступая в сообщество, вы автоматически соглашаетесь соблюдать приведённые ниже правила. I. Общение 1. Поддержание порядка в чате Чат предназначен для общения между участниками. Намеренное засорение переписки запрещено. К нарушениям относятся: • многок

5 Jun 2026, 19:50 UTC92 viewsread 13 August 2026

Необычные правила появляются не без причины. Не знание правил, не освобождает вас от ответственности.

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

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

“𝐑𝐮𝐥𝐞𝐬.” (@seravionrules), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/seravionrules.

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.