Telegram RegisterThe public register of Telegram

Channel

стртгм

@strtgmof

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

161subscribers

+0 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001689414209
TypeChannel
Username@strtgmof
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/strtgmof

Growth

1618 Aug 2026, 20:31 — 161 subscribers9 Aug 2026, 07:54 — 161 subscribers8 Aug 2026, 20:319 Aug 2026, 07:54
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 160–162 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 07:54161no change
8 Aug 2026, 20:31161first reading

Engagement

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

What this channel posts

Video runtime
5m 14s
Average length
5m 14s

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

220 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 40.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54337198881809623978940.5%
custom 54472288359321649415525.0%
custom 53525911900698824284018.2%
custom 53707786800563579803616.4%

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

Measured over the 19 most recent posts we hold, published 14 April 2026 to 8 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

8 Jul 2026, 17:02 UTC265 views12 reactionsread 8 August 2026
Photo

чо как чувачоксы? чем в субботу заняты, планы мб были? неважно. пригоняйте на SWAP.EXE там будет и музон и консось старых пакаленя я отыграю свой последний гиг с Vintage Green, буду рад видеть вас вся инфа о дате деньгах и месте в ссылке где текст синий вон там сверху 👆 p.s. давайте добъем 150 подписоты до конца недели, а то по отпискам чето как то не серьезно все ребят - надо жогнуть

custom 53707786800563579808custom 53525911900698824284

Signed Илья Кабатов

4 Jul 2026, 16:49 UTC243 views9 reactionsread 8 August 2026
Video

заглохли на восточке freestyle royalty free 2026

custom 53707786800563579808custom 54472288359321649411

Signed Илья Кабатов

4 Jul 2026, 10:29 UTC219 views8 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 54472288359321649417custom 54337198881809623971

Signed Илья Кабатов

27 Jun 2026, 14:29 UTC261 views18 reactionsread 8 August 2026
Photo

увидимся через месяц 🤩 ну по лп вот такой расклад, работаем все будет анонсы хуенсы синглы даблы как все более менее устаканится 🌟

custom 54472288359321649419custom 53525911900698824285custom 54337198881809623973custom 53707786800563579801

Signed Илья Кабатов

27 Jun 2026, 14:14 UTC208 views8 reactionsread 8 August 2026
File

File, posted without a caption

custom 54337198881809623978

Signed Илья Кабатов

27 Jun 2026, 14:14 UTC189 viewsread 8 August 2026
Video message

Video message, posted without a caption

Signed Илья Кабатов

22 May 2026, 18:34 UTC324 views22 reactionsread 8 August 2026
Photo

йоооооооооооооо! немного просели по информации о том как мы мы мозгуем материал на новый LP, в этот раз точно что-то будет к сожалению, творчество не равно время/силы => результат но мы делаем все что можем имаджинируются гитарные партии у нас с владосом, Павел генерирует еБейший бас, родян отсекает партии разной степени fabrics and details ну и Тоха рвет связки в связке (ахахаххаха лооооол) с определенной свагой ско

custom 544722883593216494113custom 54337198881809623976custom 53707786800563579803

Signed Илья Кабатов

28 Apr 2026, 14:20 UTC343 views18 reactionsread 8 August 2026
Photo

доби магуаир

custom 544722883593216494110custom 54337198881809623974custom 53525911900698824283custom 53707786800563579801

Signed Илья Кабатов

25 Apr 2026, 19:05 UTC361 views5 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 54337198881809623975

Signed Илья Кабатов

25 Apr 2026, 18:38 UTC327 views3 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 54337198881809623973

Signed Илья Кабатов

25 Apr 2026, 17:32 UTC307 views8 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 53707786800563579808

Signed Илья Кабатов

25 Apr 2026, 13:22 UTC292 views11 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 535259119006988242811

Signed Илья Кабатов

Showing the 12 most recent of 19 posts we hold for @strtgmof. 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 — 640,041 of 1,160,990entries 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 3 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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“стртгм” (@strtgmof), 161 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/strtgmof.

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.