Telegram RegisterThe public register of Telegram
Telegram profile photo for Закрыты.⎯ׄ 𝖀𝐍𝕱𝐀𝟏𝐑 𝐑𝕰𝐀𝕷𝐈𝐓𝐘𓈒

Channel

Закрыты.⎯ׄ 𝖀𝐍𝕱𝐀𝟏𝐑 𝐑𝕰𝐀𝕷𝐈𝐓𝐘𓈒

@UR1NFO

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

64subscribers

+0 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1004327176250
TypeChannel
Username@UR1NFO
Created23 June 2026measured — dated from the channel’s first post
First recorded14 August 2026
Last confirmed live8 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/UR1NFO

Growth

641028314 August 2026 — 64 subscribers16 August 2026 — 77 subscribers24 August 2026 — 102 subscribers31 August 2026 — 66 subscribers8 September 2026 — 64 subscribers14 August 20268 September 2026
5 measurements spanning 25 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 58–108 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 22:0064-2
31 Aug 2026, 09:2866-36
24 Aug 2026, 00:37102+25
16 Aug 2026, 07:5777+13
14 Aug 2026, 22:3064first reading

Engagement

20 posts held, back to 23 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.

ERR · 30 days
64.8%
avg views ÷ 64 subscribers
Avg views / post
41.4
18 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
18
of 20 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 12 August 2026
Posts held20 (23 June 202612 August 2026)
Views total746
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 22:30 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.

Recent posts

12 Aug 2026, 19:21 UTC62 viewsread 14 August 2026

🌟:: 🩸𝙰𝚅𝙸𝙶𝙰𝚃𝙸𝙾𝙽 Добро пожаловать во флуд по магической битве ⎯ׄ 𝖀𝐍𝕱𝐀𝟏𝐑 𝐑𝕰𝐀𝕷𝐈𝐓𝐘𓈒 🌟🌟𝓑ажная информация:🌟 🌟𝗿𝘂𝗹𝗲𝘀🌟𝗨𝗻𝗶𝗼𝗻𝘀🌟𝗿𝗼𝗹𝗲𝘀 🌟🌟𝗮𝗱𝗺𝗶𝗻𝘀🌟🌟𝗰𝗹𝗲𝗮𝗻𝗶𝗻𝗴 🌟🌟🌟🌟🌟𝗿𝗲𝘀𝘁𝘀 ☺️ринимаем только с подпиской на инфо и лайф!! 🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩🤩 #𝖀𝐑 — 13+

12 Aug 2026, 19:10 UTC64 viewsread 14 August 2026
Photo

🎁 :: 🩸𝙽𝙸𝙾𝙽𝚂 Союз - это взаимовырочка друг друга в трудную минуту.. 🌟🌟𝕮𝐥ic𝐤 - условия.👀 🌟Союзы Мегуми и Нобары. — 𝕮𝐥ic𝐤🌟 🌟🌟🌟Союзы Юты. — 𝕮𝐥ic𝐤🌟 𝓑ремя репостов: Мэгуми - понедельник, среда, пятница, воскресенье. Нобара - среда и пятница. Юта - по четвергам с 18.00 до 23.00. 🌟 Бот для союза — @Unfairreality1782_bot

12 Aug 2026, 15:01 UTC52 viewsread 14 August 2026

⭐ ::🩸𝐋𝐄𝐀𝐍𝐈𝐍𝐆 𝐇едельная норма — 𝟏𝟎𝟎 сообщений. . . . 𝟗𝟎-𝟗𝟗 соо : вместо бана вам выдадут один варн навсегда. 🌟 чистка проводится каждую субботу в 𝟐𝟎:𝟎𝟎 по мск ִ ⃕ участники, зашедшие за 𝟑 дня до чистки не УЧАСТВУЕТ в ней. 🌟неактив более 𝟑-х дней … 🌟🌟🌟бан . — 🩸⫶𝐍𝕱𝐀𝟏𝐑. 𝐑𝕰𝐀𝕷𝐈𝐓𝐘𓈒

12 Aug 2026, 14:55 UTC40 viewsread 14 August 2026
Photo

🌟🌸⎯ׄ 🩸⫶𝐍𝕱𝐀𝟏𝐑. 𝐑𝕰𝐀𝕷𝐈𝐓𝐘𓈒 🎁 :: 🩸.𝐃𝐌𝐈𝐍 .exe 🌟🌟» мeгуми -🩸𝐖𝐍. 🤩 ⃕ отвечает за все. приём нью, следит за активом чата, проводит чистку. « инумаки :: - 🩸𝐃𝐌.(senior)🤩 отвечает за актив, выдачу наказаний, проведение интерактивов. « ??? :: - 🩸𝐃𝐌.(junior)🤩 Отвечает за список ролей и чат флуда. « ??? :: - Ꭲᕼᗴ ᴇdiᴛᴏr.🤩 Отвечает за видео для тик ток аккаунта. #𝖀𝐑. - 🎚

12 Aug 2026, 14:51 UTC31 viewsread 14 August 2026
Photo

📣 ::🩸𝐄𝐒𝐓. ⎯ׄ 🩸⫶𝐍𝕱𝐀𝟏𝐑. 𝐑𝕰𝐀𝕷𝐈𝐓𝐘𓈒 🌟Рест (от англ. rest – отдых) во флудах – это временный перерыв от активности пользователя в чате. 🌟𝐎𝟏. максимум на 2 недели. 🌟🌟𝐎𝟐. между рестами должно быть расстояние хотя бы неделю. #𝖀𝐑. - 👀 🌟взять рест можно у : @Anasia_R О1. роль и юз О2. с какого до какого числа О3. причина » список отдыхающих . . .

12 Aug 2026, 14:46 UTC31 viewsread 14 August 2026

🎁:: 🩸𝐔𝐋𝐄𝐒 .exe 🌟⎯ׄ 🩸⫶𝐍𝕱𝐀𝟏𝐑. 𝐑𝕰𝐀𝕷𝐈𝐓𝐘𓈒💋 😻𝐎знакомиться с правилами . . . :: 🌟🌟Открыть файл — 𝕮𝐥ic𝐤

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

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

“Закрыты.⎯ׄ 𝖀𝐍𝕱𝐀𝟏𝐑 𝐑𝕰𝐀𝕷𝐈𝐓𝐘𓈒” (@UR1NFO), 64 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/UR1NFO.

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.