Telegram RegisterThe public register of Telegram
Telegram profile photo for Qulay Banklar

Channel

Qulay Banklar

@qulaybanklar_new

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

1,147subscribers

-245 since we began measuring on 25 August 2026

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

Register entry

Telegram ID-1004404612910
TypeChannel
Username@qulaybanklar_new
Created25 August 2026measured — dated from the channel’s first post
First recorded25 August 2026
Last confirmed live16 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/qulaybanklar_new

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 18 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 why it has no browse page of its own yet.

Growth

1,1471,7081,427.525 August 2026 — 1,392 subscribers25 August 2026 — 1,708 subscribers28 August 2026 — 1,249 subscribers31 August 2026 — 1,215 subscribers4 September 2026 — 1,196 subscribers9 September 2026 — 1,177 subscribers13 September 2026 — 1,158 subscribers16 September 2026 — 1,147 subscribers25 August 202616 September 2026
8 measurements spanning 22 days, net -245. 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,063–1,792 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 15:551,147-11
13 Sept 2026, 06:011,158-19
9 Sept 2026, 00:211,177-19
4 Sept 2026, 01:191,196-19
31 Aug 2026, 15:351,215-34
28 Aug 2026, 04:431,249-459
25 Aug 2026, 07:521,708+316
25 Aug 2026, 06:301,392first reading

Engagement

9 posts held, back to 25 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
143.0%
avg views ÷ 1,147 subscribers
Avg views / post
1,640
7 posts measured
Reaction rate
0.435%
reactions ÷ views · ER floor
Posts in window
9
of 9 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 25 August 2026
Posts held9 (25 August 202625 August 2026)
Views total11,482
Reactions total50
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken25 Aug 2026, 06:30 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

50 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 64.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3264.0%
👎816.0%
😢510.0%
36.00%
🔥12.00%
😁12.00%

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

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

25 Aug 2026, 05:30 UTC≈1,980 views34 reactionsread 25 August 2026

💸 Эртага доллар курси тушиши кутилмоқда Тахминан ⤵️ - 35,66 сўмга Долларнинг тахминий курси: 11 782 сўм бўлиши мумкин 👉 @qulaybanklar_new

👍21👎8😢5

25 Aug 2026, 04:55 UTC≈2,770 views11 reactionsread 25 August 2026
Photo

#dollar_kursi 25-август 9:30 💸 📊 30 та банк курслари — ягона жадвалда, осон солиштиринг! Ушбу маълумотдан хар куни хабардор бўлиш учун ушбу каналга қўшилинг ❗️Балки, яқинларингизга ҳам ушбу маълумот керакдир? 👉 @qulaybanklar_new

👍63🔥1😁1

25 Aug 2026, 04:54 UTC≈1,440 views1 reactionsread 25 August 2026

❗️ КОНТРАКТ УЧУН ТЎЛАГАН ПУЛИНГИЗДАН 12% СОЛИҚНИ ҚАЙТАРИБ ОЛИШИНГИЗ МУМКИН Ўқиш учун контракт тўлаган бўлсангиз, даромад солиғи бўйича имтиёздан фойдаланиш ҳуқуқингиз бор. Ушбу имтиёздан қуйидаги ҳолатларда фойдаланиш мумкин: ▪️ ўзингизнинг ўқишингиз учун; ▪️ фарзандингизнинг таълими учун; ▪️ 26 ёшга тўлмаган турмуш ўртоғингизнинг ўқиши учун. Агар контракт маблағи иш жойи орқали иш ҳақидан тўғридан-тўғри таълим т

👍1

25 Aug 2026, 04:54 UTC≈1,770 views1 reactionsread 25 August 2026

❗️ Юридик шахслар ва ЯТТлар диққатига! 24 август. Юридик шахс ва ЯТТ ларнинг электрон тўлов ҳужжатларини қабул қилиш вақти 🔴 узайтирилмади 👉 @qulay_banklar

👍1

25 Aug 2026, 04:54 UTC≈2,310 views1 reactionsread 25 August 2026
Photo

Доллар курси тушди 25 август куни амал қиладиган АҚШ долларининг расмий курси қуйидагича ҳисобланади: 11 818,07 сўм (-35,48 сўм) 👉 @qulay_banklar

👍1

25 Aug 2026, 04:54 UTC511 views1 reactionsread 25 August 2026
Photo

#dollar_kursi 24-август 15:30 💸 📊 30 та банк курслари — ягона жадвалда, осон солиштиринг! Ушбу маълумотдан хар куни хабардор бўлиш учун ушбу каналга қўшилинг ❗️Балки, яқинларингизга ҳам ушбу маълумот керакдир? 👉 @qulay_banklar

👍1

25 Aug 2026, 04:54 UTC701 views1 reactionsread 25 August 2026
Photo

💸 Эртага доллар курси тушиши кутилмоқда Тахминан ⤵️ - 29,26 сўмга Долларнинг тахминий курси: 11 824 сўм бўлиши мумкин 👉 @qulay_banklar

👍1

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

Mentions

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

“Qulay Banklar” (@qulaybanklar_new), 1,147 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/qulaybanklar_new.

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.