Telegram RegisterThe public register of Telegram
Telegram profile photo for Abdrahmanov's

Channel

Abdrahmanov's

@abdrahmanovs

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

1,029subscribers

-11 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003632498771
TypeChannel
Username@abdrahmanovs
Created23 January 2026measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/abdrahmanovs

Growth

1,0291,0551,0426 August 2026 — 1,040 subscribers6 August 2026 — 1,040 subscribers7 August 2026 — 1,055 subscribers10 August 2026 — 1,041 subscribers13 August 2026 — 1,029 subscribers6 August 202613 August 2026
5 measurements spanning 7 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”. The vertical axis spans 1,025–1,059 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 05:281,029-12
10 Aug 2026, 10:311,041-14
7 Aug 2026, 08:221,055+15
6 Aug 2026, 13:021,040no change
6 Aug 2026, 12:201,040first reading

Engagement

12 posts held, back to 23 January 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.

ERR · 30 days
4.32%
avg views ÷ 1,029 subscribers
Avg views / post
44.4
7 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
7
of 12 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 5 August 2026
Posts held12 (23 January 20265 August 2026)
Views total311
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 13:02 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.

Reaction mix

348 reactions across 3 posts, in 14 distinct kinds. The most used accounts for 18.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53325778880110636976418.4%
custom 52201024140398003545214.9%
custom 53323149028685608444713.5%
custom 52807545592144429324212.1%
custom 53324984955405947084111.8%
custom 53304640854965991393710.6%
custom 5219879629791188166154.31%
custom 5219680575236890719144.02%
custom 5267123428233600008133.74%
custom 522223244723567641582.30%
custom 528080992563785540861.72%
custom 538416700365108327951.44%
custom 519061361526208055130.862%
custom 538443317136434652110.287%

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

Measured over the 12 most recent posts we hold, published 23 January 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, 09:49 UTC49 viewsread 6 August 2026
Forwarded from @PJKMS

+ @abdrahmanovs

Signed Màdi-MvpMD Hìro

5 Aug 2026, 09:13 UTC47 viewsread 6 August 2026
Forwarded from @infoS1reneFile

🔤irene в поиске союзов. 🤩🤩🤩🤩🤩🤩🤩🤩 Сладящий: @bakke_r папки: рп/вз. max подписка 3:3 🌸🌸🌸🌸🌸🌸🌸🌸 правила.

Signed Màdi-MvpMD Hìro

5 Aug 2026, 09:13 UTC42 viewsread 6 August 2026
Forwarded from @infoS1reneFile

🔤irene в поиске союзов. 🤩🤩🤩🤩🤩🤩🤩🤩 Сладящий: @amdasad0r в случае бана - anon. папки: рп/вз/актив+рп. max подписка 2:2 🌸🌸🌸🌸🌸🌸🌸🌸 правила.

Signed Màdi-MvpMD Hìro

5 Aug 2026, 09:13 UTC28 viewsread 6 August 2026
Forwarded from @infoS1rene

SIRÈNE в поиске администрации. Админ по союзам (1/3) Админ по интерактивам (1/3) Всему научим, главное иметь желание. Писать: @amdasad0r #SIRÉNERP

Signed Màdi-MvpMD Hìro

5 Aug 2026, 09:12 UTC34 viewsread 6 August 2026
Forwarded from @infoS1renePhoto

– New union by Sirène. @infos1rene + @abdrahmanovs

Signed Màdi-MvpMD Hìro

5 Aug 2026, 08:32 UTC55 viewsread 6 August 2026

Дайте мне союзников

Signed Màdi-MvpMD Hìro

5 Aug 2026, 08:15 UTC56 viewsread 6 August 2026
Forwarded from @soulovskieeVideo

🌟🌟🌟🌟🌟💎🌟🌟🌟🌟🌟 @MADEXW День начинается не с кофе. Он начинается с решения, кем ты сегодня не станешь. 🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟 спасибо за участие! #𝗦𝗢𝗨𝗟_𝗥𝗘𝗔𝗩𝗘𝗥

Signed Màdi-MvpMD Hìro

28 Jun 2026, 18:56 UTC≈1,260 viewsread 6 August 2026

проголосуйте что бы у нас были шикарные обои

Signed Dexter

30 May 2026, 09:51 UTC≈8,610 views4 reactionsread 6 August 2026
File

Четких союзников нам 🔔 макс 4:4 / рп+вз - актив+вз правила для союзов Связь madi ⏰ #Abds #AbdRP

custom 52201024140398003542custom 52198796297911881661custom 53844331713643465211

Signed Dexter

30 Mar 2026, 07:24 UTC≈4,900 views164 reactionsread 6 August 2026
Photo

ABDRAHMANOV'S CRASH LIST 😇 group members: unions: Milfs / Miu Miu / Chambers hades

custom 533257788801106369742custom 533231490286856084441custom 533046408549659913932custom 522010241403980035414custom 52196805752368907197custom 52198796297911881667custom 52671234282336000086custom 52808099256378554086

Signed Dexter

26 Mar 2026, 17:59 UTC≈6,710 views180 reactionsread 6 August 2026
Photo

Thé Dexter is your göd and his chat is your têmple. (Rules)

custom 528075455921444293242custom 522010241403980035436custom 533249849554059470835custom 533257788801106369722custom 52222324472356764158custom 52196805752368907197custom 52198796297911881667custom 52671234282336000087

Showing the 12 most recent of 12 posts we hold for @abdrahmanovs. 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 — 20,654 of 1,481,217entries 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

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

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

“Abdrahmanov's” (@abdrahmanovs), 1,029 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/abdrahmanovs.

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.