Telegram RegisterThe public register of Telegram
Telegram profile photo for Хозяйка Джи У | Манхва

Channel

Хозяйка Джи У | Манхва

@hozyajka_dzhi_u

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

6,537subscribers

-959 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002438561518
TypeChannel
Username@hozyajka_dzhi_u
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 November 2026
Measurements held29
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/hozyajka_dzhi_u

Topic

Gambling & betting — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 72% 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.

Growth

6,5377,4967,016.57 August 2026 — 7,496 subscribers7 August 2026 — 7,496 subscribers7 August 2026 — 7,494 subscribers10 August 2026 — 7,458 subscribers14 August 2026 — 7,419 subscribers17 August 2026 — 7,379 subscribers20 August 2026 — 7,336 subscribers24 August 2026 — 7,305 subscribers26 August 2026 — 7,277 subscribers30 August 2026 — 7,245 subscribers1 September 2026 — 7,210 subscribers6 September 2026 — 7,155 subscribers11 September 2026 — 7,123 subscribers14 September 2026 — 7,099 subscribers19 September 2026 — 7,072 subscribers28 September 2026 — 7,005 subscribers5 October 2026 — 6,962 subscribers12 October 2026 — 6,915 subscribers15 October 2026 — 6,884 subscribers18 October 2026 — 6,848 subscribers20 October 2026 — 6,820 subscribers24 October 2026 — 6,783 subscribers27 October 2026 — 6,757 subscribers30 October 2026 — 6,716 subscribers2 November 2026 — 6,683 subscribers5 November 2026 — 6,660 subscribers8 November 2026 — 6,640 subscribers12 November 2026 — 6,594 subscribers17 November 2026 — 6,537 subscribers7 August 202617 November 2026
29 measurements spanning 102 days, net -959. 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 6,393–7,640 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
17 Nov 2026, 08:526,537-57
12 Nov 2026, 09:046,594-46
8 Nov 2026, 12:066,640-20
5 Nov 2026, 01:006,660-23
2 Nov 2026, 00:066,683-33
30 Oct 2026, 06:216,716-41
27 Oct 2026, 02:486,757-26
24 Oct 2026, 01:506,783-37
20 Oct 2026, 21:056,820-28
18 Oct 2026, 05:576,848-36
15 Oct 2026, 12:376,884-31
12 Oct 2026, 16:446,915-47
5 Oct 2026, 23:196,962-43
28 Sept 2026, 13:567,005-67
19 Sept 2026, 05:547,072-27
14 Sept 2026, 22:597,099-24
11 Sept 2026, 16:397,123-32
6 Sept 2026, 17:007,155-55
1 Sept 2026, 21:337,210-35
30 Aug 2026, 03:377,245first reading

Engagement

23 posts held, back to 9 February 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 28 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.67%
avg views ÷ 6,537 subscribers
Avg views / post
370
6 posts measured
Reaction rate
0.292%
reactions ÷ views · ER floor
Posts in window
6
of 23 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. It is computed over the 1 of 6 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 November 2026
Posts held23 (9 February 2026 – 15 November 2026)
Views total2,222
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 15:12 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
44s
Average length
44s

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

1,339 reactions across 18 posts, in 21 distinct kinds. The most used accounts for 49.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤65949.2%
❤‍🔥15611.7%
🥰1128.36%
💘947.02%
🍓745.53%
🤯443.29%
💔382.84%
🔥382.84%
💋312.32%
😡251.87%
🤬181.34%
🌚110.822%
🤔110.822%
🗿100.747%
👍50.373%
🍾40.299%
👻20.149%
😁20.149%
😢20.149%
🥱20.149%
1 further kind10.075%

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

Measured over the 23 most recent posts we hold, published 9 February 2026 to 15 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 6 posts held from the last 30 days (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).

15 Nov 2026, 16:00 UTC201 viewsread 16 November 2026
Video

1️⃣2️⃣3️⃣4️⃣5️⃣6️⃣7️⃣ 🤣 🪙 В Telegram появилось лицензионное казино Счастливый код: LKB052 ✈️ Пробуйте: Luckybear 👈 🌐 Сайт: Luckybear 👈

14 Nov 2026, 15:55 UTC13 viewsread 14 November 2026

✨Крути Ducky Wheel и получай до $777 на баланс!

14 Nov 2026, 15:25 UTC309 viewsread 16 November 2026
Photo

😎 Утиная охота: ищем тех, кто ещё не забрал бонус! До 425% к депозиту➕200 фриспинов только за вход Все в лицензионном казино — TonPlay 👇

28 Oct 2026, 13:16 UTC≈1,370 views4 reactionsread 16 November 2026
Forwarded from @rhymestgPhoto

🎁 РОЗЫГРЫШ СКЛАДНОГО IPHONE И ЕЩЕ 6 НОВЫХ ДЕВАЙСОВ ОТ APPLE Пока все смотрели стрим — мы готовили подарки. 7 УСТРОЙСТВ, которые Apple только что показала миру, уже ищут своих владельцев Среди призов: 🍏 Складной iPhone DUO — впервые в истории Apple; 🍏 iPhone 18 Pro и Pro Max; 🍏 AirPods 5 и AirPods Pro 4; 🍏 Apple Watch Series 12 и Ultra 4. Условия розыгрыша: 🤍 Подписаться на «Рифмы и Панчи»; 🤍 Подписаться на «Рифмы …

😡3❤1

21 Jun 2026, 09:21 UTC≈14,500 views154 reactionsread 16 November 2026
Forwarded from @telemanga_glaviPhoto

Хозяйка Джи У — Глава 36 Читать — https://telemanga.me/manga/jiwoos-master/glava-36/ Основной канал — @telemanga1

❤106🔥25🥰13❤‍🔥5👻2👾1💋1🥱1

26 May 2026, 18:40 UTC≈12,100 views47 reactionsread 16 November 2026
Photo

Делаете эдиты по манхвам? Накидайте видосики в коменты 🥰 Так же можете заработать на эдитах в тт/инст, пишите: @krepostnoi_boss

❤29🤔11🍓6💘1

23 May 2026, 15:54 UTC≈8,160 views50 reactionsread 16 November 2026
Forwarded from @telemanga_glaviPhoto

Цветы лишь приманка — Глава 48 Читать — https://telemanga.me/manga/flowers-of-allure/glava-48/ Основной канал — @telemanga1

❤‍🔥28🤬15🔥4❤1😁1😢1

18 May 2026, 09:40 UTC≈6,850 views14 reactionsread 16 November 2026
Photo

🤩 СОВЕТУЮ ПРОЧЕСТЬ! "Опрометчивый флирт" Маньхуа с САМОЙ качественной рисовкой, интересным сюжетом и привлекательными персонажами ❤️ Описание: Сногсшибательная финансовая журналистка Чжэн Шуйи встречается с двуличным мерзавцем? Как она могла остаться в стороне и ничего не делать с этими влюбленными птицами: ублюдком-изменником и его белым лотосом любовницей. Увидев номерной знак "Роллс-Ройса" дяди любовницы, состо…

❤6👍5❤‍🔥1🥱1😢1

4 May 2026, 15:36 UTC≈8,390 views158 reactionsread 16 November 2026
Forwarded from @telemanga_glaviPhoto

33 глава 🐰 https://telemanga.me/manga/jiwoos-master/glava-33/

❤86💔38😡13🗿10❤‍🔥8🤬3

18 Apr 2026, 14:31 UTC≈8,340 views35 reactionsread 16 November 2026
Forwarded from @telemanga_glaviPhoto

Цветы лишь приманка — Глава 44 Читать — https://telemanga.me/manga/flowers-of-allure/glava-44/ Основной канал — @telemanga1

❤34😁1

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

Posts recorded as deleted after publishing

We recorded 4 posts on @hozyajka_dzhi_u as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
12 August 2026
Most recent seen missing
3 November 2026
Median time before seen missing
43 days
Seen missing in the last 30 days
2

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

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

“Хозяйка Джи У | Манхва” (@hozyajka_dzhi_u), 6,537 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/hozyajka_dzhi_u.

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.