Channel
@PersianPBIUG
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,252subscribers
+11 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001798296631 |
|---|---|
| Type | Channel |
| Username | @PersianPBIUG |
| Created | Between 1 January 2022 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 29 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 29 August 2026 |
| On Telegram | t.me/PersianPBIUG |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 07:43 | 3,252 | +2 |
| 26 Aug 2026, 02:27 | 3,250 | -2 |
| 19 Aug 2026, 09:09 | 3,252 | +1 |
| 16 Aug 2026, 04:54 | 3,251 | +5 |
| 12 Aug 2026, 09:16 | 3,246 | +5 |
| 9 Aug 2026, 08:41 | 3,241 | +1 |
| 6 Aug 2026, 11:05 | 3,240 | -1 |
| 6 Aug 2026, 04:48 | 3,241 | no change |
| 6 Aug 2026, 02:19 | 3,241 | first reading |
20 posts held, back to 4 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof 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 20 March 2026. An engagement rate over an empty window would be a number about nothing.
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.
263 reactions across 15 posts, in 8 distinct kinds. The most used accounts for 81.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 213 | 81.0% | |
| 👍 | 25 | 9.51% | |
| 👏 | 12 | 4.56% | |
| 🔥 | 5 | 1.90% | |
| 🤩 | 3 | 1.14% | |
| ❤🔥 | 2 | 0.76% | |
| 🎉 | 2 | 0.76% | |
| 😍 | 1 | 0.38% |
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 15 of the 20 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 263reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 4 September 2025 to 20 March 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.
نوروز امسال در حالی از راه رسیده که دلهایمان سبک نیست. قبل از رسیدن بهار، داغهای زیادی بر دل این سرزمین نشست. جوانهایی که باید امروز کنار سفره هفتسین مینشستند، حالا فقط جای خالیشان را حس میکنیم. ایران روزهای سختی را میگذراند. روزهایی که خبرها سنگین است، دلها نگران است، و لبخندها گاهی با بغض همراه میشود. اما نوروز همیشه فقط شروع یک سال جدید نبوده، پیامش این بوده که حتی بعد از سردترین زمستان، باز هم بهار را…
❤25
#MIGA امید به خدا به زودی جلسات حضوری در وطن برگزار میکنیم ✌🏻✌🏻✌🏻
❤79👍8
تا 20 دقیقه دیگر جلسه شروع میشود. لینک: https://www.linkedin.com/events/7396148326120869888/
👏8❤1👍1
Persian Power BI User Group pinned a photo
🎞جلسه هفته آینده: مقایسههای هوشمند در Power Query در این جلسه درباره مشکلی صحبت میکنیم که همه با آن روبهرو میشوند؛ وقتی Power Query بیش از حد سختگیر است و دو مقدار تقریبا مشابه را «یکسان» تشخیص نمیدهد. دادههای واقعی همیشه تمیز و مرتب نیستند و همین موضوع منطق ما را خراب میکند. در این جلسه یاد میگیرید که: ✅ Power Query را وادار کنید از قواعد شما پیروی کند ✅ مقادیر متنی را به شکل طبیعیتری مقایسه کنید ✅ اولی…
👍5❤2😍1
🥇سلام دوستان ممنون از همه عزیزانى که در کنفرانس دیروز شرکت کردند. اگر نتوانستید به صورت آنلاین حضور داشته باشید، تمام جلسات ضبط شده و از طریق یوتیوب قابل مشاهده است. 📹لینک ویدیو: https://www.youtube.com/watch?v=14dXXNaakXo
❤25👏2
Live stream started
دوستان متاسفانه پخش زنده در لینکدین به دلایل خارج از کنترل ما قطع شده، لطفا یوتیوب را دنبال کنید: پخش زنده: • یوتیوب: https://www.youtube.com/watch?v=14dXXNaakXo
❤5
با سلام فردا کنفرانس Persian Power BI and Fabric Conference 2025 نسخه فارسی برگزار میشود. شروع: جمعه 16 آبان، ساعت 2 بعدازظهر سیدنی مدت: 8 ساعت پخش زنده: • یوتیوب: https://www.youtube.com/watch?v=14dXXNaakXo اطلاعات تکمیلی در وبسایت کنفرانس موجود است: https://www.fabricevents.net/
❤11👏2👍1
🎞 برنامه کامل کنفرانس پاور بیآی و فبریک فارسی منتشر شد! 🗓 تاریخ برگزاری: ۷ نوامبر ۲۰۲۵ 📌 رویدادی آنلاین با حضور سخنرانان برجسته از سراسر جهان 🎙 موضوعاتی از تازهترین قابلیتهای پاور بیآی و فبریک تا تجربههای واقعی متخصصان در پروژههای دادهمحور. ✔️ همراه شوید و از جدیدترین ایدهها و تجربهها الهام بگیرید 🔗جزییات کامل و ثبتنام رایگان Www.fabricevents.net
❤9👍6🔥1
🎤معرفی جلسات کنفرانس پاور بیآی و مایکروسافت فبریک – نسخه فارسی | ۷ نوامبر ۲۰۲۵ سهیل بخشی موضوع: Beyond the Star Schema ✔️کنفرانس فارسی پاور بیآی و فبریک فرصتی است برای یادگیری عمیق، تبادل تجربه و ارتباط مستقیم با جامعه حرفهای فارسیزبان در حوزه داده، تحلیل و فناوریهای مایکروسافت. 🔗جزییات کامل و ثبتنام رایگان Www.fabricevents.net
❤10
Persian Power BI User Group pinned a video
Showing the 12 most recent of 20 posts we hold for @PersianPBIUG. 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 — 359,149 of 1,626,935entries 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“Persian Power BI User Group” (@PersianPBIUG), 3,252 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/PersianPBIUG.
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.