Telegram RegisterThe public register of Telegram
Telegram profile photo for HUVAYDO RESIDENCE

Channel

HUVAYDO RESIDENCE

@huvaydo_residence

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

24subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001988423163
TypeChannel
Username@huvaydo_residence
Created8 June 2023measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/huvaydo_residence

Growth

247 August 2026 — 24 subscribers11 August 2026 — 24 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 23–25 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 10:3124no change
7 Aug 2026, 03:4824first reading

Engagement

11 posts held, back to 8 June 2023the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 31 July 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3
Videos
1
Links
5

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
3m 36s
Average length
3m 36s

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

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍150.0%
🙏150.0%

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

Measured over the 11 most recent posts we hold, published 8 June 2023 to 31 July 2023, 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

31 Jul 2023, 16:48 UTC189 viewsread 11 August 2026
Forwarded from @uzmdkPhoto

В Ташкенте оштрафовали мужчину на 1,65 млн суммов за мойку автомобиля водой из под шланга Инцидент произошел на массиве Ахмада Дониша в Юнусабадском районе. В министерстве юстиции напомнили о том, что за неразумное использование питьевой воды (мытье машины, полив огорода, полив двора) сейчас строго следят и штрафуют до 3 млн. сумов. Подпишитесь и следите за актуальными новостями на нашем канале👇 https://telegram.m

10 Jul 2023, 12:18 UTC191 viewsread 11 August 2026
Forwarded from @hetmuloqotVideo

O'zbekiston Jinoyat kodeksiga kiritilgan oʼzgartishlarga koʼra, elektr, gaz va suvdan qonunga hilof ravishda foydalanish holatlari oʼgʼirlik jinoyatiga tenglashtirilgan. Taassufki, hozirgi kunda shunday holatlar ko'plab uchramoqda. Xususan, Qiziltepa tumanida oʼtkazilgan tezkor tadbirda noqonuniy mayning ferma faoliyatiga chek qoʼyildi. Bu haqda “Sevimli” telekanalining “Zamon” informatsion dasturida namoyish etilga

20 Jun 2023, 06:37 UTC190 viewsread 11 August 2026
Forwarded from @uzmdkPhoto

Сегодня 20 июня в 7 районах Ташкента ожидается отключение электроэнергии в связи с работами по модернизации и реконструкции сети Отключается электроснабжение по следующим адресам: Чиланзарский район: в махаллях «Козиробод» и «Куркам» с 09:00 до 16:00; Яшнабадский район: в махалле «Миришкор» с 09:00 до 16:00; Янгихаетский район: в махаллях «Ходжаучкун» и «Викор» с 09:00 до 16:00; Шайхонтохурский район: в махаллях »

14 Jun 2023, 09:19 UTC198 viewsread 11 August 2026
Forwarded from @uzmdkPhoto

Предупредите водителей: за мойку машины из крана с питьевой водой можно получить штраф В министерстве юстиции напомнили о том, что за неразумное использование питьевой воды (мытье машины, полив огорода, полив двора) положен штраф до 3 млн. сумов. Подпишитесь и следите за актуальными новостями на нашем канале👇 https://telegram.me/joinchat/AAAAAEEdc-qam7052mnXKA

10 Jun 2023, 09:42 UTC191 viewsread 11 August 2026
Forwarded from @liderlar1

"АХЛАТОЛОГИЯ" ЁҲУД ЯПОНЧА ФАРЗАНД ТАРБИЯСИ • Бугун сизларга айтиб бeрмоқчи бўлган воқeам aхлат ташлаш одоби ҳақида. Японияга кeлган кўпчиликни биринчи бўлиб дуч кeладиган ҳодисаларидан биттаси ахлат ташлаш маданияти бўлса ажабмас. Ҳаттоки, ҳорижлик талабаларга дастлабки дарсларда қандай қилиб ахлат тўкиш, ҳафтани қайси кунлари қандай турдаги ахлатни тўкиш, ахлатларни турларга ажратиб тўкиш, умуман ахлат ҳақида тушу

9 Jun 2023, 11:31 UTC168 views1 reactionsread 11 August 2026
Forwarded from @potrebitel_uz

8 хокимиятов Ташкента опубликовали в своих каналах дополнительные номера, по которым жители могут звонить по проблемам с электроэнергией В среднем все дали по 3-4 номера. Больше всех выделил Сергелийский хокимият - 8 номеров Переходите по ссылкам, заскриньте номера на всякий случай: Сергелийский https://t.me/Sergelihokimiyati/33274 Чиланзарский https://t.me/chilonzor_tuman_hokimligi/36440 Мирабадский https://t.me/m

👍1

Showing the 11 most recent of 11 posts we hold for @huvaydo_residence. 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 — 655,452 of 1,549,376entries 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 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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“HUVAYDO RESIDENCE” (@huvaydo_residence), 24 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/huvaydo_residence.

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.