Telegram RegisterThe public register of Telegram
Telegram profile photo for ‏ ‏‎﮼غند┊𓅃

Channel

‏ ‏‎﮼غند┊𓅃

@hazin2828

On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry

5,535subscribers

-114 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001163615682
TypeChannel
Username@hazin2828
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live18 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/hazin2828

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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

5,5355,6495,59212 August 2026 — 5,649 subscribers12 August 2026 — 5,649 subscribers16 August 2026 — 5,632 subscribers19 August 2026 — 5,626 subscribers22 August 2026 — 5,611 subscribers26 August 2026 — 5,598 subscribers29 August 2026 — 5,595 subscribers1 September 2026 — 5,586 subscribers4 September 2026 — 5,576 subscribers10 September 2026 — 5,560 subscribers13 September 2026 — 5,548 subscribers18 September 2026 — 5,535 subscribers12 August 202618 September 2026
12 measurements spanning 36 days, net -114. 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 5,518–5,666 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 01:375,535-13
13 Sept 2026, 19:405,548-12
10 Sept 2026, 00:175,560-16
4 Sept 2026, 14:555,576-10
1 Sept 2026, 00:175,586-9
29 Aug 2026, 05:525,595-3
26 Aug 2026, 04:085,598-13
22 Aug 2026, 17:545,611-15
19 Aug 2026, 13:125,626-6
16 Aug 2026, 16:075,632-17
12 Aug 2026, 17:455,649no change
12 Aug 2026, 16:345,649first reading

Engagement

6 posts held, back to 30 July 2025the 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.

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

Recent posts

28 Nov 2025, 02:06 UTC≈3,440 viewsread 12 August 2026

من يستكثر أن يرضيك عند الخلاف، خسارته مكسب. من لا يمنحك الحنان الذي تستحقه، خسارته مكسب. من يستخدم الصمت العقابي لإيذائك، خسارته مكسب. ن يعاملك وفق مزاجه المتقلب، خسارته مكسب ن يعاندك وهو يعلم أنه مخطئ، خسارته مكسد * في النهاية صحتك النفسية لا تحتاج أشخاصاً يرهقونك، بل من يطمئنك بأفعاله قبل كلماته

Signed .

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

شَغف♫
@Hillli86 · 56,690
Telegram ranks this channel #14 of 86 here — alongside 85 others — read 23 August 2026
إقتباسات خَوْد
@e_ccccc · 133,782
Telegram ranks this channel #14 of 72 here — alongside 71 others — read 13 August 2026
مواساة لقلبك | ☁️❤️
@heart_a0 · 55,541
Telegram ranks this channel #38 of 91 here — alongside 90 others — read 24 August 2026
دواهي
@daoihe · 23,509
Telegram ranks this channel #68 of 78 here — alongside 77 others — read 18 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“‏ ‏‎﮼غند┊𓅃” (@hazin2828), 5,535 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/hazin2828.

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.