Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 2 of the 13 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 16 comparable posts for this entry, running 22 July 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Across the whole group of 2, the earliest publisher we hold is @vellayat1. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
3 measurements spanning 7 days, net -5. 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 2,878–2,885 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 18:25
2,879
-5
6 Aug 2026, 05:04
2,884
no change
5 Aug 2026, 22:22
2,884
first reading
Engagement
23 posts held, back to 22 July 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 2 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
7.53%
avg views ÷ 2,879 subscribers
Avg views / post
217
22 posts measured
Reaction rate
1.21%
reactions ÷ views · ER floor
Posts in window
23
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 8 of 22 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 6 August 2026
Posts held
23 (22 July 2026 – 6 August 2026)
Views total
4,768
Reactions total
23
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 16:05 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
1m 11s
Average length
24s
Measured directly from 3 videos 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
19 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 57.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
11
57.9%
💔
8
42.1%
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 8 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 23reactions 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 22 July 2026 to 6 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.
🔸️ به اشتباه درخواست #مجوز انتخاب واحد برای نیمسال ۴۰۴۳ (ترم تابستان) ثبت کردم، چیکارکنم؟
▫️در صورتی که به اشتباه درخواست مجوز انتخاب واحد برای نیمسال ۴۰۴۳ ثبت کردهاید، به کارشناس آموزش دانشکده مراجعه کنید تا مجوز انتخاب واحد به صورت دستی حذف شود.
📕ترم تابستان ۱۴۰۵ : نیمسال ۴۰۴۳
📘ترم مهر ۱۴۰۵ : نیمسال ۴۰۵۱
⚠️ فعالیت بخش اداری دانشگاه آزاد مجددا از روز شنبه ۲۴ مرداد آغاز خواهد شد. بنابراین بعد از شروع فعالیت …
#مجوز انتخاب واحد ترم مهر هنوز فعال نشده!
▫️تا به این لحظه، مجوز انتخاب واحد نیمسال ۴۰۵۱ در سامانه آموزشیار فعال نشده و برای گرفتن مجوز و پرداخت شهریه فعلا صبر کنید.
🗓 انتخاب واحد تهران مرکز
┘ ۲۸ مرداد ۱۴۰۵
هر زمان فعال بشه داخل کانال اطلاع رسانی انجام میشه
🔶پیج اینستاگرام مجتمع دانشگاهی ولایت
instagram.com/vellayat1
🔶مجتمع دانشگاهی ولایت🔶
☑️ @vellayat1
☑️ @vellayat1
☑️ @vellayat1
🔸 نحوه مشاهده تعداد جلسات برگزار شده دروس ترم تابستان ۱۴۰۵ سامانه #وادانا
🔹سامانه وادانا:
🔗 amzy.ir/vadana
1️⃣ ابتدا وارد سامانه وادانا (نیمسال ۴۰۴۳) شوید، نام کابری و رمز ورود (شماره دانشجویی) خود را وارد کرده و سپس لاگین کنید.
2️⃣ بعد از ورود به صفحه میزکار، دروس شما نمایش داده میشود. بر روی کلاس مورد نظر خود کلیک نمایید
3️⃣ بر روی گزینه "مشاهده آرشیو جلسات" کلیک نمایید.
4️⃣ با انتخاب منوی "برنامه کلاسی" می…
🔸️ آموزش استعلام دانشنامه (اصل مدرک فارغالتحصیلی) و گواهی موقت دانشگاه آزاد
▫️دانش آموختگان با وارد کردن کد ۱۲ رقمی درج شده روی دانشنامه یا گواهی موقت در سامانه استعلام، میتوانند وضعیت مدارک خود را مشاهده و بررسی نمایند.
🔗 amzy.ir/estelam-iau
🔶پیج اینستاگرام مجتمع دانشگاهی ولایت
instagram.com/vellayat1
🔶مجتمع دانشگاهی ولایت🔶
☑️ @vellayat1
☑️ @vellayat1
☑️ @vellayat1
🔸️ آموزش ثبت درخواست #گواهی اشتغال به تحصیل در سامانه آموزشیار
▫️سامانه آموزشیار:
🔗 amzy.ir/Amozeshyar-old
1️⃣ انتخاب منوی "EER -خدمات آموزشی" و زیر منوی "ارسال/ پیگیری درخواست صدور مدرک آموزشی دانشجو"
2️⃣ طبقهبندی موضوع درخواست: عملیات آموزشی دانشجو
3️⃣ موضوع درخواست: صدور گواهی اشتغال به تحصیل - قابل ترجمه
4️⃣ انتخاب نیمسال درخواست موردنظر
5️⃣ کلیک بر روی گزینه "ثبت"
▫️بعد از ثبت درخواست، در انتهای صفحه در…
Showing the 12 most recent of 23 posts we hold for @Markaz1. 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.
Mentions
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.
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.
“🔷️تهــــــران مرکـــــز” (@Markaz1), 2,879 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Markaz1.
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.
