Telegram RegisterThe public register of Telegram
Telegram profile photo for rest || frida kalt

Channel

rest || frida kalt

@fr1d2klt

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

128subscribers

-23 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-1003735290589
TypeChannel
Username@fr1d2klt
CreatedBetween 1 February 2026 and 26 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/fr1d2klt

Growth

128151139.58 August 2026 — 151 subscribers8 August 2026 — 151 subscribers17 August 2026 — 148 subscribers24 August 2026 — 138 subscribers31 August 2026 — 137 subscribers8 September 2026 — 128 subscribers8 August 20268 September 2026
6 measurements spanning 31 days, net -23. 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 125–154 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 23:35128-9
31 Aug 2026, 16:34137-1
24 Aug 2026, 23:08138-10
17 Aug 2026, 16:26148-3
8 Aug 2026, 19:32151no change
8 Aug 2026, 17:32151first reading

Engagement

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

Reaction mix

55 reactions across 8 posts, in 11 distinct kinds. The most used accounts for 20.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 51904019678636629151120.0%
custom 51908478799582700641018.2%
custom 53256873688988752211018.2%
custom 5323410254547949966814.5%
custom 532363318482544684547.27%
custom 519060596163035217435.45%
custom 529636355269987947535.45%
custom 529641551750920069223.64%
custom 540015796146302544723.64%
custom 529665179654504963711.82%
custom 540018422948300966611.82%

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 are Telegram’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 8 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 55 reactions 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 26 June 2026 to 5 August 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

5 Aug 2026, 12:34 UTC61 views3 reactionsread 8 August 2026

🤩здравствуйте, милые! меня долго не было: недавно я отдыхала на море и совсем скоро вернусь с новой работой. также мне нужно узнать, с кем из персонажей аниме я у вас ассоциируюсь. 🤩

custom 53234102545479499663

28 Jul 2026, 12:59 UTC152 views19 reactionsread 8 August 2026
Photo

💙💙 «Доктор Фушигуро забрал 💙💙 это проклятие себе — такова была цена за то, что он слишком самонадеянно тебе не поверил.» 🤩🤩😀😀😀😀😀😀😀😀 🤩🤩🤩🤩« СПАСИБО » 🤩🤩#jujutsukaisen #fridakalt

custom 532568736889887522110custom 53234102545479499665custom 53236331848254468454

19 Jul 2026, 10:11 UTC224 viewsread 8 August 2026
Photo

💙💙 «…мое имя Фрида, и с 💙💙 того дня оно навечно осталось витать над морем.» 🤩🤩🤩в тот день солнце уходило за горизонт как-то иначе — медленно, окрашивая небо в золотистый цвет, а морская вода казалась непривычно теплой, почти парной. волны тихонько лизали мои щиколотки, теплый бриз путал пряди волос, а последние лучи слепили глаза, заставляя щуриться. в моих наушниках крутилась какая-то мелодия, но я не разбирала слов

18 Jul 2026, 07:45 UTC185 viewsread 8 August 2026

🤩ассоциации готовы. можете лицезреть результат —> @frid2ass0 🤩

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 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.

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.

“rest || frida kalt” (@fr1d2klt), 128 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/fr1d2klt.

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.