Posted without readable text
Signed Zž

Channel
@zo_z_s
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
304subscribers
+71 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003890979017 |
|---|---|
| Type | Channel |
| Username | @zo_z_s |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/zo_z_s |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 22:58 | 304 | -6 |
| 7 Nov 2026, 12:48 | 310 | -11 |
| 30 Oct 2026, 15:58 | 321 | +8 |
| 22 Oct 2026, 16:59 | 313 | +69 |
| 15 Oct 2026, 22:46 | 244 | +17 |
| 7 Oct 2026, 23:02 | 227 | +9 |
| 26 Sept 2026, 09:37 | 218 | -18 |
| 10 Sept 2026, 18:55 | 236 | +2 |
| 1 Sept 2026, 10:14 | 234 | -2 |
| 24 Aug 2026, 13:28 | 236 | +3 |
| 23 Aug 2026, 12:15 | 233 | first reading |
17 posts held, back to 17 August 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 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 17 posts for this entry, the most recent from 23 August 2026. An engagement rate over an empty window would be a number about nothing.
75 reactions across 14 posts, in 14 distinct kinds. The most used accounts for 21.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6026047194568596059 | 16 | 21.3% | |
| custom 5963155812359606966 | 10 | 13.3% | |
| custom 5254002290259423382 | 9 | 12.0% | |
| custom 5963119060324455918 | 9 | 12.0% | |
| custom 5965405043782849904 | 7 | 9.33% | |
| custom 5773842531649331742 | 6 | 8.00% | |
| custom 5963189437658567369 | 6 | 8.00% | |
| custom 5962800416700765716 | 3 | 4.00% | |
| custom 5962850397235189899 | 3 | 4.00% | |
| custom 5125417347443589781 | 2 | 2.67% | |
| custom 5253580915312980238 | 1 | 1.33% | |
| custom 5323598687648107382 | 1 | 1.33% | |
| custom 5963290536893747934 | 1 | 1.33% | |
| custom 6030569421469129706 | 1 | 1.33% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 14 of the 17 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 75 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 17 August 2026 to 23 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.
Posted without readable text
Signed Zž
🎶︙@KXl_3bot .
custom 57738425316493317421
Signed Zž
مين ابن المتناكه الي بيحاول يجمدني دا تع شاتي ي دمج قول ف وشي @zo_z_x
custom 57738425316493317421custom 59628004167007657161custom 59631558123596069661
Signed Zž
و ف نفس اليوم فكيت اك ليا مصري 015 @Q_A_D_E_M_A_H_K_A_M_A يوزر. الاك
custom 59654050437828499042custom 59631190603244559181
Signed Zž
تم رجوع اك سيكا @si_ka7_x
custom 59631190603244559181custom 59631894376585673691
Signed Zž
وهنا كان معنا جرو مسمي نفسو فليكس ك الشياطين دلوقت ظبط نفسو و شال الاسم اول م سال بس عن التيم
Signed Zž
يتكرم يولاد المره طالع من الاول هما مشغلين اغاني دينيه وانا مشغل السيد حسن ف الايربوتز😂
custom 52540022902594233821custom 59631190603244559181custom 59631558123596069661
Signed Zž
اوصفني ب كلمه @zo_z_x
custom 52540022902594233823custom 59628004167007657161custom 59631190603244559181custom 59631558123596069661custom 59632905368937479341
Signed Zž
سمحني مش ب ايدي ي قلبي والله
custom 60260471945685960593custom 59631894376585673692custom 53235986876481073821custom 59631558123596069661
Signed Zž
و ابقي افتكرني ب كلمه حلوه
custom 60260471945685960596custom 59631558123596069662custom 59631190603244559181
Signed Zž
خليني ذكري جميله عندك و اوعي تنسي زمان
custom 60260471945685960597custom 59631558123596069662custom 57738425316493317421
Signed Zž
• uploader @Moscow_xbot
Signed Zž
Showing the 12 most recent of 17 posts we hold for @zo_z_s. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“انا الزوز تسمع عني” (@zo_z_s), 304 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/zo_z_s.
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.