Telegram RegisterThe public register of Telegram
Telegram profile photo for 21frms

Channel

21frms

@frms_21

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

63subscribers

+1 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002121263907
TypeChannel
Username@frms_21
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live24 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/frms_21

Growth

626362.59 August 2026 — 62 subscribers10 August 2026 — 62 subscribers24 August 2026 — 63 subscribers9 August 202624 August 2026
3 measurements spanning 15 days, net +1. 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 62–63 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 06:5663+1
10 Aug 2026, 04:1662no change
9 Aug 2026, 18:1762first reading

Engagement

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

What this channel posts

Video runtime
57s
Average length
29s

Measured directly from 2 videos 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

233 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 27.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6327.0%
❤‍🔥4017.2%
🔥3213.7%
custom 53550760777587275922611.2%
custom 53619786013045029512510.7%
custom 5357382629815502838135.58%
🎉125.15%
🥰93.86%
💔83.43%
custom 536188821371776021252.15%

Custom emoji. 4 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 20 of the 20 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 233reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 14 November 2025 to 11 June 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

11 Jun 2026, 21:00 UTC150 views12 reactionsread 10 August 2026
Photo

21frms - И ПОХ4Й🤟 Слушать🤟 Prod. by 21frms

7custom 53550760777587275923❤‍🔥1🎉1

10 Jun 2026, 14:13 UTC116 views5 reactionsread 10 August 2026
Video message

Video message, posted without a caption

3custom 53573826298155028382

10 Jun 2026, 14:12 UTC102 views5 reactionsread 10 August 2026
Video message

Video message, posted without a caption

3❤‍🔥2

10 Jun 2026, 14:10 UTC99 views5 reactionsread 10 August 2026
Video message

Video message, posted without a caption

3🥰2

10 Jun 2026, 14:09 UTC97 views5 reactionsread 10 August 2026
Video message

Video message, posted without a caption

3💔2

23 Mar 2026, 21:00 UTC227 views11 reactionsread 10 August 2026
File

🤐📵 *Meta - Признаны экстремистскими организациями и запрещены на территории РФ.

custom 53550760777587275926❤‍🔥2🔥2custom 53618882137177602121

20 Mar 2026, 20:59 UTC230 views19 reactionsread 10 August 2026
File

"Порой Белый Хочет и в Такой Рэп"💔

5💔5🔥4🎉2🥰2❤‍🔥1

7 Mar 2026, 21:15 UTC273 views18 reactionsread 10 August 2026

Дамы, с Праздником! Вы Муза, Вы Ангел, если бы о-о..., пффф, а-аа... Люблю❤️‍🔥

6❤‍🔥5🥰4🔥2custom 53619786013045029511

4 Mar 2026, 23:28 UTC265 views9 reactionsread 10 August 2026
File

Первое марта - все поменяло. Много, чего хочется сказать, много, чего нельзя сказать. Хочется сказать просто "Увы"... Но трек не связан с этим, а вот следующий...) Сорян за поздний дроп, надеюсь никого не разбудил... Решил писаться под бесплатные биты, просто тренить скилл, а то на одном треке за длинный период далеко не уйдешь.

custom 53573826298155028385custom 53550760777587275923🔥1

18 Feb 2026, 09:55 UTC270 views13 reactionsread 10 August 2026
File

Опять в разъездах... Братик просил записаться сто раз, послушать себя, попробовали, и я решил пофристайлить на фит. Ах да, ну и бит не мой, не хотел переводить проект лишний раз. Чисто на оценочку. Я без оборудования, поэтому записано на старый микро без аудиокарты.

5custom 53550760777587275923🔥2❤‍🔥1💔1custom 53619786013045029511

14 Feb 2026, 19:52 UTC262 views11 reactionsread 10 August 2026
File

Год ТГК, собственно Самое время постить то, что я собираю на альбом. Уже готово порядка 7 битов. Мало контента постится, просто молча сижу, делаю, пишусь... Постараюсь почаще щас кидать кусочки битов, как и хотел, можно будет сравнить, что делал в начале, что делаю сейчас🍷 Два тайпа в одном бите и небольшой бридж.

custom 535507607775872759271❤‍🔥1🎉1custom 53619786013045029511

Showing the 12 most recent of 20 posts we hold for @frms_21. 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 — 913,365 of 1,604,598entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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.

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

“21frms” (@frms_21), 63 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/frms_21.

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.