Telegram RegisterThe public register of Telegram
Telegram profile photo for Hijobligim.🌼🌸Xijobli RASMLAR Profilga 🌸Profil Uchun RASMLAR❤️ XIJOBLI RASM HIJOBLIGIM HIJOBLi Qizlar ❤️‍🩹SHERLAR хижоблигим

Channel

Hijobligim.🌼🌸Xijobli RASMLAR Profilga 🌸Profil Uchun RASMLAR❤️ XIJOBLI RASM HIJOBLIGIM HIJOBLi Qizlar ❤️‍🩹SHERLAR хижоблигим

@Xijobligim6

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

786subscribers

-134 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1001407962628
TypeChannel
Username@Xijobligim6
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live29 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/Xijobligim6

Growth

78692085313 August 2026 — 920 subscribers14 August 2026 — 888 subscribers22 August 2026 — 819 subscribers29 August 2026 — 786 subscribers13 August 202629 August 2026
4 measurements spanning 16 days, net -134. 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 766–940 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 14:19786-33
22 Aug 2026, 08:05819-69
14 Aug 2026, 20:43888-32
13 Aug 2026, 23:17920first reading

Engagement

4 posts held, back to 4 August 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.

ERR · 30 days
2.16%
avg views ÷ 786 subscribers
Avg views / post
17.0
1 post measured
Reaction rate
194.1%
reactions ÷ views · ER floor
Posts in window
1
of 4 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 13 August 2026
Posts held4 (4 August 202613 August 2026)
Views total17
Reactions total33
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 23:17 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

160 reactions across 4 posts, in 11 distinct kinds. The most used accounts for 35.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5735.6%
159.38%
❤‍🔥148.75%
😘148.75%
💘116.88%
😇106.25%
😍106.25%
🤗106.25%
95.63%
🕊95.63%
💔10.625%

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

Measured over the 4 most recent posts we hold, published 4 August 2026 to 13 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

13 Aug 2026, 20:35 UTC17 views33 reactionsread 13 August 2026
Photo

Gunoh qildingmi darhol tavba qil. Inson suvga tushgani tufayli emas, balki suvdan chiqa olmagani uchun g'arq bo'ladi. @shakh_01_70 admin

👍13❤‍🔥3😘322💘2🕊2🤗2

Signed 🌒

6 Aug 2026, 18:30 UTC329 views39 reactionsread 13 August 2026
Photo

XIJOBLIGIM 🌸🧕 Yuraging tubidan joy olgan boʻlsam.☘ Lanatlab haydagin quvilib ketay🪵. Sen sevib yashagan gunoh boʻlsam gar.❤️ Shunday tavba qilki yuvilib ketay..🥀 Mensizlik baxt boʻlsa baxtli yashab koʻr🕊 Baxtsizlik azobin chekkandan ko'ra.😍 Uxlasang, uygʻonsang duo qilib yur.🦋 Qayta uchramayin xudodan soʻra..🍂 **-%——-"" " @Muhammed_Ahiy

👍16❤‍🔥3💘3🤗3😇3😘322

Signed 𝐊 𝐇 𝐀 𝐋 𝐈 𝐅

4 Aug 2026, 12:29 UTC430 views46 reactionsread 13 August 2026
Photo

Kun sayin oʻzgarib borar odamlar Men esa hali ham oʻsha oʻshaman Men bilan rasmga tushmas sanamlar Chunki rasmga ham xunik tushaman Konglimda borini yozaverdimu Sargardon yurishdan bulmadim halos Men konglim dunyosi ichra mashhurman meni oʻz sherlarm taniydi halos Men konglim dunyosi ichra mashhurman Sen uchun yuqdayman guyo Bir kuni men sendan ketib qolaman men bilan rasmga tushib qol dunyo 😊 Admin..@shakh_01_70 Par

👍146❤‍🔥4😍4😘43💘3🕊3

Signed 🌒

4 Aug 2026, 12:14 UTC385 views42 reactionsread 13 August 2026
Photo

Yurakni ozorlab to'ymaydi firoq❤️ Manzillar yaqinu ko'ngillar yiroq🍂 Men neni istasam erishdim biroq🥀 Meniki bo'lmagan faqat sen qolding😔 Ko'nglimga havaslar to'ldirdi dunyo🍃 Gullati gohida so'ldirdi dunyo🥀 Bo'lmagan ishimni bo'ldirdi dunyo🍂 Meniki bo'lmagan faqat sen qolding😔 Ishqimni soylarga so'zlab ketyamman🍂 Visoling hayolda ko'zlab ketyamman🍃 Yillarki tunlari bo'zlab o'tyamman🥀 Meniki bo'lmagan faqat sen qoldin

👍145❤‍🔥4😘4💘3🤗32🕊2

Signed ZiraPcha

Showing the 4 most recent of 4 posts we hold for @Xijobligim6. 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

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

“Hijobligim.🌼🌸Xijobli RASMLAR Profilga 🌸Profil Uchun RASMLAR❤️ XIJOBLI RASM HIJOBLIGIM HIJOBLi Qizlar ❤️‍🩹SHERLAR хижоблигим” (@Xijobligim6), 786 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/Xijobligim6.

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.