Telegram RegisterThe public register of Telegram
Telegram profile photo for دفتر معماری و اجرایی ونار

Channel

دفتر معماری و اجرایی ونار

@wenar_co

On this record: Growth · Engagement · What this channel posts · Posts · Cite this entry

148subscribers

-1 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001332364284
TypeChannel
Username@wenar_co
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/wenar_co

Growth

148149148.58 August 2026 — 149 subscribers8 August 2026 — 149 subscribers22 August 2026 — 148 subscribers8 August 202622 August 2026
3 measurements spanning 15 days, net -1. 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 148–149 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 21:17148-1
8 Aug 2026, 20:16149no change
8 Aug 2026, 00:14149first reading

Engagement

20 posts held, back to 4 April 2023the 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.

ERR · 30 days
no view readings in window
Avg views / post
no view readings
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held20 (4 April 20234 August 2026)
Views total
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 20:16 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
59s
Average length
59s

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.

Recent posts

4 Aug 2026, 12:20 UTCviews —

Channel name was changed to «دفتر معماری و اجرایی ونار»

14 Apr 2023, 11:13 UTC407 viewsread 8 August 2026
Photo

▫️ صمیمیت ترکیب مصالح مختلف▫️

5 Apr 2023, 17:41 UTC341 viewsread 8 August 2026
Photo

▫️سادگی همیشە ماندگار است▫️

4 Apr 2023, 20:20 UTC317 viewsread 8 August 2026
Photo

▫️طراحی داخلی، با اشکال ساده▫️

4 Apr 2023, 20:10 UTC295 viewsread 8 August 2026
Photo

▫️طراحی پروژه های اداری،تجاری،مسکونی▫️ مجتمع پزشکی((ژیان)) کاری متفاوت از دفتر ((ونار))

4 Apr 2023, 20:07 UTC258 viewsread 8 August 2026
Photo

▫️نمای ساختمان میتواند تداعی گر احساسات مختلف باشد▫️

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

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

“دفتر معماری و اجرایی ونار” (@wenar_co), 148 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/wenar_co.

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.