Telegram RegisterThe public register of Telegram
Telegram profile photo for Rahimov's blog

Channel

Rahimov's blog

@rahimovs_blog

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

3,448subscribers

+329 since we began measuring on 3 November 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003753779306
TypeChannel
Username@rahimovs_blog
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 November 2026
Last confirmed live4 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/rahimovs_blog

Topic

Personal blog — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 5 November 2026 and assigned it the closest of 31 fixed categories, at 75% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

6,930 average views per post against 3,448 subscribers — an engagement rate of 201.1%. Across the 356 registered channels in the same cohort — 3,448–9,967 subscribers, posting mainly in Belarusian — the middle half sit between 11.7% and 41.0%, with a median of 23.4%.

What this was computed from
Window30 days (6 October 2026 – 5 November 2026)
Posts measured20 of 20 published in the window (1 exact, 19 rounded by Telegram)
Views totalled138,674
Mature posts only213.3% over 18 posts read at least 24h after publication
Subscribers3,448 measured 4 November 2026
Cohortb3162:bel · 356 channels · p10 4.88% · p25 11.7% · p50 23.4% · p75 41.0% · p90 58.7%
Position in cohort99.718th percentile · 8.6× the cohort median
Uncertainty±0.084% of the figure, from Telegram’s rounding
Post languageBelarusian · 66.7% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 5 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

3,1193,4483,283.53 Nov 2026, 20:22 — 3,119 subscribers4 Nov 2026, 19:31 — 3,448 subscribers3 Nov 2026, 20:224 Nov 2026, 19:31
2 measurements taken within a single day, net +329. 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 3,070–3,497 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Nov 2026, 19:313,448+329
3 Nov 2026, 20:223,119first reading

Engagement

20 posts held, back to 9 October 2026 — the 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.

ERR · 30 days
201.1%
avg views ÷ 3,448 subscribers
Avg views / post
6,930
20 posts measured
Reaction rate
2.33%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 November 2026
Posts held20 (9 October 2026 – 3 November 2026)
Views total138,674
Reactions total3,233
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Nov 2026, 20:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
1m 22s
Average length
1m 22s

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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54069056170780424322,16767.0%
❤‍🔥68121.1%
custom 543407850936024992638511.9%

Custom emoji. 2 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 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 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 3,233 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 9 October 2026 to 3 November 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.

Telegram Stars

Stars received
85
across the posts below
Posts paid on
14
of 20 we hold a reading for · 70%
Most on one post
44
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @rahimovs_blog. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 9 October 2026 to 3 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 3 of 20 posts held from the last 30 days (15.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

3 Nov 2026, 16:29 UTC594 views117 reactionsread 3 November 2026

Bunday aktivni korib marafon boshlavorishni o‘ylab qoldim 😅 Qatnashamiz - ❤️‍🔥

❤‍🔥96custom 540690561707804243221

3 Nov 2026, 02:40 UTC≈5,700 views241 reactions6 Starsread 3 November 2026

Yangi kitob hidini sezmaydiganlar bizga mutolaa haqida gapirmasin!

custom 5406905617078042432241

2 Nov 2026, 13:59 UTC≈7,060 views208 reactions3 Starsread 3 November 2026

oy toʻldi, lekin koʻngillarchi..

custom 5406905617078042432203❤‍🔥5

2 Nov 2026, 03:46 UTC≈7,580 views217 reactions6 Starsread 3 November 2026

ayt yomgʻir ostida birga yurmasak, arzirmi umrimiz goʻzal deyishga?

custom 5406905617078042432217

1 Nov 2026, 17:24 UTC≈7,380 views207 reactions6 Starsread 3 November 2026

Men ayolim bilan turmush qurgan kunim butun ayollarga janoza o'qidim...

custom 5406905617078042432207

1 Nov 2026, 11:04 UTC≈7,480 views167 reactions3 Starsread 3 November 2026

Uxlab yurganlar tushdan boshqasi nasiyb qilmaydi... Uyg'onganlar esa taqdirni o'zi yozadi..

custom 5406905617078042432167

31 Oct 2026, 01:14 UTC≈7,380 views162 reactionsread 3 November 2026

kitob sotib olish ham qalb kasalligi, faqat yaxshi kasallik..

custom 5406905617078042432162

Signed рахимов

30 Oct 2026, 00:43 UTC≈7,270 views151 reactions4 Starsread 3 November 2026

Masofalarni qo'y, bir osmon ostida ekanimiz yetarli emasmi?

custom 5406905617078042432151

Signed рахимов

29 Oct 2026, 15:01 UTC≈7,130 views163 reactionsread 3 November 2026

Kulma, tabassum qil. Dugonalaringga xolos, erkak zotiga emas. Chunki har kulgining bahosi bor. Ba’zilar uni ilinj bilan termuladi, ba’zilar esa yo‘qotgandek his qiladi. Va kimdir uni xato tushunadi. Keyin esa ayblash ham sendan boshlanadi. Chunki ba’zi ko‘zlar sening baxtingni ko‘rishni istamaydi, ba’zilari esa uni o‘ziniki deb bilishni boshlaydi.

custom 5406905617078042432163

Signed рахимов

28 Oct 2026, 02:15 UTC≈6,040 views123 reactions2 Starsread 3 November 2026

Ahlingiz o'qiydigan ilmning ajru savobi sizga ham bo'lishi uchun u oladigan ilmlarning manbai siz bo'ling..

❤‍🔥104custom 540690561707804243219

Signed рахимов

24 Oct 2026, 09:43 UTC≈5,820 views139 reactionsread 3 November 2026

iymonlarini qutqarmaguncha o'lmasinlar

❤‍🔥114custom 540690561707804243225

Signed рахимов

22 Oct 2026, 02:05 UTC≈6,340 views136 reactionsread 3 November 2026

Oldingi o'zingni qaytarish emas, yangi o'zingni qurish harakatida bo'l.

❤‍🔥111custom 540690561707804243225

Signed Рахимов

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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.

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

“Rahimov's blog” (@rahimovs_blog), 3,448 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/rahimovs_blog.

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.