Telegram RegisterThe public register of Telegram

Channel

Федеральная служба безопасности

@podPrikrityiem

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

8subscribers

+0 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1002552880580
TypeChannel
Username@podPrikrityiem
Created11 May 2025measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/podPrikrityiem

Growth

813 Aug 2026, 20:18 — 8 subscribers14 Aug 2026, 14:56 — 8 subscribers13 Aug 2026, 20:1814 Aug 2026, 14:56
2 measurements taken within a single day. 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 7–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 14:568no change
13 Aug 2026, 20:188first reading

Engagement

16 posts held, back to 11 May 2025the 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.

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

What this channel posts

Video runtime
18s
Average length
18s

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

132 reactions across 10 posts, in 14 distinct kinds. The most used accounts for 14.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53821472394455441081914.4%
custom 5400238977431122726129.09%
custom 5217501094082528152118.33%
custom 5350413366772910618118.33%
custom 5354896333377398855118.33%
custom 5355178066052148036107.58%
custom 524896205164828211396.82%
custom 538200169159381909696.82%
custom 544760928843021036096.82%
custom 547229586709441101296.82%
custom 535272827683605333175.30%
75.30%
custom 535030970773721676953.79%
custom 518846167343800360632.27%

Custom emoji. 13 of the rows above are 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 10 of the 16 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 132reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 11 May 2025 to 26 May 2025, 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

26 May 2025, 10:25 UTC390 views6 reactionsread 13 August 2026

"🎶" КФ закрывается. Спасибо всем, кто был с нами вы сделали этот путь особенным! 🌹 Патент всё ещё работает, так что это не прощание, а просто новая глава.

6

24 May 2025, 12:21 UTC463 views8 reactionsread 13 August 2026

Чат

custom 53821472394455441082custom 54002389774311227262custom 52175010940825281521custom 52489620516482821131custom 53820016915938190961custom 54476092884302103601

20 May 2025, 19:39 UTC509 views9 reactionsread 13 August 2026

У нас был перенабор. Если есть те, кто хочет заново войти в чат, отправьте в комментарии "+".

custom 52489620516482821132custom 53821472394455441082custom 52175010940825281521custom 53548963333773988551custom 53820016915938190961custom 54002389774311227261custom 54722958670944110121

18 May 2025, 12:39 UTC502 views15 reactionsread 13 August 2026
File

cr - Akiya

custom 53548963333773988553custom 52489620516482821132custom 53820016915938190962custom 52175010940825281521custom 53504133667729106181custom 53527282768360533311custom 53551780660521480361custom 53821472394455441081

18 May 2025, 07:42 UTC470 viewsread 13 August 2026

Нужны видео и нью-админы. Пишите в личку - @zaibalma 👋

14 May 2025, 06:13 UTC659 views12 reactionsread 13 August 2026

иниц строго в ник

custom 53548963333773988552custom 53821472394455441082custom 54476092884302103602custom 52175010940825281521custom 53527282768360533311custom 53551780660521480361custom 53820016915938190961custom 54002389774311227261

13 May 2025, 19:25 UTC635 views21 reactionsread 13 August 2026

НАБОР В АДМИНИСТРАЦИЮ ФСБ ‼️ - видео админ 0/2 - нью админ 0/2 - чат админ 2/2 - союз админ 1/1 @zaibalma 👋

custom 53527282768360533314custom 53821472394455441083custom 54722958670944110123custom 52175010940825281522custom 53551780660521480362custom 54002389774311227262custom 54476092884302103602custom 52489620516482821131

13 May 2025, 16:05 UTC593 views11 reactionsread 13 August 2026

Все материалы о нашем братстве и союзах будут выкладываться в этот канал. 🪙 @bratyafsb

custom 52175010940825281522custom 538214723944554410821custom 51884616734380036061custom 52489620516482821131custom 53504133667729106181custom 53548963333773988551custom 53820016915938190961

11 May 2025, 11:55 UTC670 views18 reactionsread 13 August 2026

🏀 инициал фсбшник - фсбшница фсб - fsb 🎶 премиум эмодзи ВНИМАНИЕ 👋 без инициала в чат не принимаем!

custom 53503097077372167693custom 53551780660521480363custom 53504133667729106182custom 53821472394455441082custom 54002389774311227262custom 52175010940825281521custom 52489620516482821131custom 53548963333773988551

Showing the 12 most recent of 16 posts we hold for @podPrikrityiem. 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 — 1,369,660 of 1,480,688entries 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.

Mentions

Named by 2 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.

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

“Федеральная служба безопасности” (@podPrikrityiem), 8 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/podPrikrityiem.

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.