2 measurements taken within a single day. 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 32–34 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 03:32
33
no change
11 Aug 2026, 06:01
33
first reading
Engagement
10 posts held, back to 13 December 2021 — 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 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 10 posts for this entry, the most recent from 14 February 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
5s
Average length
5s
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
226 reactions across 9 posts, in 16 distinct kinds. The most used accounts for 35.4% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
80
35.4%
❤
42
18.6%
😍
26
11.5%
🥰
24
10.6%
💊
11
4.87%
🙏
9
3.98%
😎
7
3.10%
💘
5
2.21%
🎉
4
1.77%
😘
4
1.77%
🦄
4
1.77%
🙈
3
1.33%
🎄
2
0.885%
💋
2
0.885%
🔥
2
0.885%
💅
1
0.442%
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 9 of the 10 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 226reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 13 December 2021 to 14 February 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.
⬆️ پروژه ربات 《 عضو سین 》به نسخه 2.0 تکمیل شد !
❤️ تشکر میکنیم از حمایت های فوق العاده شما از ربات عضو سین
😍 آپدیت فوق العاده 《 عضو سین 》 به مناسبت سال جدید میلادی آماده شد
⭐️ موارد اضافه شده در نسخه جدید ربات ربات 👇🏻
✔️ اضافه شدن بخش افزایش لایک و نظر سنجی به صورت حرفه ای (قیمت #هرعددلایک10تاتک_تومان_است)
✔️ بهبود سرعت ربات در افزایش بازدید و امکان تنظیم بازدید حتی با لینک و امکان افزایش بازدید موزیک (قیمت #هرهزاربا…
📍 وب اپلیکیشن #گوگل_پنل
✅ متصل به سایت GooglePanel.ir
✅ دسترسی آسان جهت ثبت سفارش
✅ حجم کم برای نصب
✅ عدم دسترسی به اطلاعات تلفن شما(فقط اتصال به اینترنت که برنامه کار کنه)
✅ عدم نیاز به پیدا کردن سایت از کانال تلگرام
✅ امکان استفاده برای کسانی که تلگرام ندارند
✅ بهینه سازی شده برای اندروید 4.4 به بالا
➖➖➖➖➖➖➖
📌 @GooglePanelBot
📌 GooglePanel.ir
Showing the 10 most recent of 10 posts we hold for @ozvseen. 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 — 526,468 of 1,151,006entries 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
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.
Mentions
Named by 2 registered channels — 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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@ozvseen named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@ozvseenbot named in 1 post, 12 August 2026 – 12 August 2026
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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“عضو سین ozv seen ربات عضوگیری گروه کانال لینکدونی” (@ozvseen), 33 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ozvseen.
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.
