الزام ثبت شماره تلفن همراه در سامانه راهداری ،جهت صدور بارنامه

Channel
My Ubaar
@MyUbaar
On this record: Growth · Engagement · Posts · Citations · Cite this entry
869subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001085195529 |
|---|---|
| Type | Channel |
| Username | @MyUbaar |
| Created | Between 1 September 2016 and 30 September 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/MyUbaar |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 00:34 | 869 | -1 |
| 6 Aug 2026, 14:34 | 870 | no change |
| 6 Aug 2026, 01:10 | 870 | first reading |
Engagement
20 posts held, back to 10 January 2023 — 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 20 posts for this entry, the most recent from 1 June 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
آقای قلاوند عزیز ازلطف و محبت شما بسیار خرسندیم خانواده بزرگ اوبار به شما افتخار میکنه
کانال روبیکا https://rubika.ir/ubaar54536300 با سرچ کردن در روبیکا وارد کانال رانندگان اوبار شوید
اعلامبار خاور مسقف 🚚 🚚 🚚 🚚 🔴 از تهران (استان تهران) 🔴 به دلگان (استان سیستان وبلوچستان) 11,000,000 تومان 2 تن _ میز و صندلی و اقلام اداری تعداد ۲ عدد خاور مسقف نیاز است ،هرماشین ۱۱ میلیون تومان صافی پرداخت میشود 👇 👇 👇 👇 👇 👇 👇 👇 👇 📞 هماهنگی 09361667062
اعلامبار تریلی بغلدار 🚚 🚚 🚚 🚚 🔴 از قم (استان قم) 🔴 به بابل (استان مازندران) 9,500,000 تومان صافی 18 تن _ وسایل مخابراتی بارگیری و تخلیه سریع تسویه آنی 👇 👇 👇 👇 👇 👇 👇 👇 👇 📞 هماهنگی 09361667062
اعلامبار تریلی بغلدار 🚚 🚚 🚚 🚚 🔴 از قم (استان قم) 🔴 به بندرعباس (استان هرمزگان) 12,500,000 تومان صافی 18 تن _ وسایل مخابراتی بارگیری و تخلیه سریع ،تسویه آنی 👇 👇 👇 👇 👇 👇 👇 👇 👇 📞 هماهنگی 09361667062
Live stream finished (4 minutes)
Live stream started
مبدا :قم مقصد: کیش تریلی ترانزیت وزن بار :14 تن 20 میلون صافی 02154536300
نحوه ارسال رسید جهت تسویه حساب پس از رسیدن به مقصد را در ویدیوی زیر مشاهده نمایید. https://www.aparat.com/dashboard/videostat/JgEx2
مبدا هشتگرد مقصد اهواز ماشین خاور نوع بار : تجهیزات مخابراتی وزن : 3 ارسال موفق یار با کرایه 4.994.000 تومان #بار_تضمینی #بارنامه_الکترونیک #بارنامه #اوبار
مبدا هشتگرد مقصد اهواز ماشین خاور نوع بار : تجهیزات مخابراتی وزن : 3 تن کرایه توافقی جهت کسب اطلاعات بیشتر ۰۲۱۵۴۵۳۶۳۰۰ ۰۹۰۲۲۰۱۳۷۷۴ #بار_تضمینی #بارنامه_الکترونیک #بارنامه #اوبار
Showing the 12 most recent of 20 posts we hold for @MyUbaar. 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 — 464,893 of 1,604,161entries 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 1 registered channel — 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.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“My Ubaar” (@MyUbaar), 869 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/MyUbaar.
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.