Telegram RegisterThe public register of Telegram
Telegram profile photo for [RSTC'S 🍗] @ramilakimov

Channel

[RSTC'S 🍗] @ramilakimov

@ramilakimov

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

71subscribers

+11 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003533357423
TypeChannel
Username@ramilakimov
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live14 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/ramilakimov

Growth

601,25865911 August 2026 — 60 subscribers12 August 2026 — 60 subscribers19 August 2026 — 78 subscribers27 August 2026 — 1,258 subscribers30 August 2026 — 717 subscribers7 September 2026 — 76 subscribers14 September 2026 — 71 subscribers7111 August 202614 September 2026
7 measurements spanning 34 days, net +11. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 17:5871-5
7 Sept 2026, 06:5676-641
30 Aug 2026, 09:28717-541
27 Aug 2026, 00:281,258+1,180
19 Aug 2026, 09:5378+18
12 Aug 2026, 04:3860no change
11 Aug 2026, 12:4860first reading

Engagement

20 posts held, back to 27 July 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 10 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

25 reactions across 8 posts, in 8 distinct kinds. The most used accounts for 40.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54719019155141509511040.0%
custom 5472354575002376982416.0%
custom 5472292255026912314312.0%
custom 547188270412543500728.00%
custom 547197932800469308628.00%
custom 547199879279647809128.00%
custom 547196069214159625214.00%
custom 547236888583340766014.00%

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 25 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 27 July 2026 to 10 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

10 Aug 2026, 12:05 UTC29 viewsread 11 August 2026

(🇷🇺) KFC Notes: https://t.me/+pC075BdjU6NjYTli

Signed [編集済み]

10 Aug 2026, 12:04 UTC29 views3 reactionsread 11 August 2026

Since then I officially work in Rostic's (KFC)

custom 54719019155141509513

Signed [編集済み]

7 Aug 2026, 14:53 UTC42 views2 reactionsread 11 August 2026

Found a job🔴❤️🔴

custom 54719793280046930862

Signed [編集済み]

6 Aug 2026, 19:22 UTC61 views3 reactionsread 11 August 2026
Photo

cr: @Fliqpyhtf10007 🍭

custom 54719019155141509513

Signed [編集済み]

2 Aug 2026, 21:23 UTC83 views2 reactionsread 11 August 2026

Наконец-то у меня дошли руки почистить аккаунт от всякого ненужного дерьма. Простите, если кого-то игнорил в личке, я вас из-за ботов и активных каналов не видел 🪴 /// Finally I found time to clear my account from whole useless shit. Sorry, if I ignored you. I could see you because of bots and active channels 🪴

custom 54719019155141509512

Signed [編集済み]

2 Aug 2026, 17:26 UTC90 views4 reactionsread 11 August 2026

I don't wanna do anything anymore. 🌟

custom 54718827041254350072custom 54719987927964780912

Signed [編集済み]

1 Aug 2026, 12:28 UTC84 views2 reactionsread 11 August 2026
Photo

И снова Флиппи /// And Flippy again

custom 54719019155141509512

Signed /// [𝗥𝗘𝗗𝗔𝗖𝗧𝗘𝗗]

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

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

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

“[RSTC'S 🍗] @ramilakimov” (@ramilakimov), 71 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/ramilakimov.

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.