Telegram RegisterThe public register of Telegram
Telegram profile photo for بازرگانی وهاب (علی فراهانی)

Channel

بازرگانی وهاب (علی فراهانی)

@vahabco

On this record: Topic · Growth · Engagement · Posts · Cite this entry

383subscribers

+2 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001646863818
TypeChannel
Username@vahabco
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 19 August 2026
On Telegramt.me/vahabco

Topic

Ecommerce storefront — 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 19 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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

3813833825 August 2026 — 381 subscribers6 August 2026 — 381 subscribers19 August 2026 — 383 subscribers5 August 202619 August 2026
3 measurements spanning 14 days, net +2. 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 381–383 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Aug 2026, 20:07383+2
6 Aug 2026, 20:17381no change
5 Aug 2026, 20:06381first reading

Engagement

10 posts held, back to 2 August 2026the 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
11.8%
avg views ÷ 383 subscribers
Avg views / post
45.2
10 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
10
of 10 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 6 August 2026
Posts held10 (2 August 20266 August 2026)
Views total452
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 20:17 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.

Recent posts

6 Aug 2026, 05:40 UTC43 viewsread 6 August 2026

سرویس ۵پارچه کودک چینی پارس در ۳رنگ موجود شد

6 Aug 2026, 05:39 UTC42 viewsread 6 August 2026

⚜️سرویس ۱۲۹پارچه و ۵۲پارچه ۸۰پارچه گرد چینی پارس در طرح های مختلف موجود شد⚜️

5 Aug 2026, 04:44 UTC44 viewsread 6 August 2026

سرویس های ۱۰۰پارچه ۱۰۱پارچه و ۱۰۲پارچه چهارگوش چینی پارس در طرح های مختلف موجود شد

5 Aug 2026, 04:44 UTC38 viewsread 6 August 2026

سرویس های ۹۰پارچه چینی پارس قالب درسا موجود شد

Showing the 10 most recent of 10 posts we hold for @vahabco. 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 19 August 2026 — this entry's latest reading, not the date you are reading this.

“بازرگانی وهاب (علی فراهانی)” (@vahabco), 383 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/vahabco.

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.