Channel
@sngsbi_PADIDHE
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
1,095subscribers
-1,636 since we began measuring on 9 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004320014836 |
|---|---|
| Type | Channel |
| Username | @sngsbi_PADIDHE |
| Created | Between 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/sngsbi_PADIDHE |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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.
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.
2,600 average views per post against 1,095 subscribers — an engagement rate of 237.1%. Across the 1,252 registered channels in the same cohort — 1,000–3,153 subscribers, posting mainly in Persian — the middle half sit between 7.37% and 30.3%, with a median of 15.9%.
| Window | 30 days (29 August 2026 – 28 September 2026) |
|---|---|
| Posts measured | 18 of 18 published in the window (5 exact, 13 rounded by Telegram) |
| Views totalled | 46,735 |
| Mature posts only | 251.0% over 17 posts read at least 24h after publication |
| Subscribers | 1,095 measured 26 September 2026 |
| Cohort | b1000:fas · 1,252 channels · p10 3.61% · p25 7.37% · p50 15.9% · p75 30.3% · p90 51.3% |
| Position in cohort | 99.520th percentile · 14.9× the cohort median |
| Uncertainty | ±0.265% of the figure, from Telegram’s rounding |
| Post language | Persian · 100.0% of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 28 September 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 06:01 | 1,095 | -1,001 |
| 15 Sept 2026, 11:38 | 2,096 | -486 |
| 11 Sept 2026, 16:18 | 2,582 | -149 |
| 10 Sept 2026, 00:22 | 2,731 | no change |
| 9 Sept 2026, 23:47 | 2,731 | first reading |
18 posts held, back to 31 August 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 1 page of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 9 September 2026 |
|---|---|
| Posts held | 18 (31 August 2026 – 9 September 2026) |
| Views total | 46,735 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Sept 2026, 00:22 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.
Measured directly from 4 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.
کفسابی واحد های نوساز و قدیمی در تهران شهرستان ها تمیز کردن سنگ طبیعی با کف سابی کف سنگ های طبیعی با پاک کردن منظم کاملاً تمیز نمی شوند. دلیل آن این است که سنگ طبیعی و کاشی های سنگی به طور باورنکردنی متخلخل هستند ، به این معنی که سطح سنگ می تواند لکه ها و نشت ها را جذب کند. برای تمیز کردن لکه ها از سنگ ، ما یک کفشویی حرفه ای از سنگ را با بهترین مواد تمیز کننده کف سابی پیشنهاد می کنیم. برای پاک سازی سنگ طبیعی یک رو…
کفسابی و سنگسابی (مرمر، موزائیک، سرامیک ،گرانیت، تراورتن بتون وغیره...) > 💎 پولیش حرفهای و از بین بردن خط و خش > 💎 رفع سیاهی، لکهها و آلودگیهای سطحی > 💎 رفع ناهمواری و صاف کردن سطح سنگ > ✅ بدون تخریب | ✅ با دستگاههای مدرن | ✅ با قیمت مناسب > 📞 تماس و مشاوره: ۰۹۱۹۴۹۴۹۶۹۳ کفسابی پدیده https://t.me/sngsbi_PADIDHE @Sngsbi_Padideh
@KAFSABI12 لینک کانال مون تو روبیکا
لینک کانال مون تو بله
@KAFSABI12
سلام به همه همراهان عزیز! خوش آمدید. ✨ اگر به دنبال بازگرداندن شکوه و درخشش به سنگهای خانه، ویلا یا محل کار خود هستید، جای درستی آمدهاید. 🛠 خدمات تخصصی ما: ✅ کفسابی و سنگسابی انواع سنگ (مرمر، گرانیت، تراورتن، سنگهای مصنوعی و...) ✅ پولیش حرفهای و از بین بردن خط و خش ✅ رفع سیاهی، لکهها و آلودگیهای لایهای سنگ ✅ بازگرداندن شفافیت و براقیت به سنگهای قدیمی و کدر ✅ رفع چاله و ناهمواری سطح سنگ 💎 چرا ما را انتخا…
اگر سنگهای کف یا پلههای شما کدر شده یا لکههای سیاه روی آنها نشسته، ما راه حل قطعی را داریم! ✅ کفسابی و پولیش انواع سنگ با دستگاههای مدرن ✅ رفع سیاهی، تیرگی و آلودگیهای لایه سطحی ✅ بازگرداندن شفافیت و براقیت به سنگهای قدیمی ✅ کار با دقت بالا و بدون ایجاد گرد و غبار زیاد ✅ قیمت رقابتی و اجرای سریع تماس با ما: ۰۹۱۹۴۹۴۹۶۹۳ @Sngsbi_Padideh
با کفسابی حرفهای، منزل خود را لوکس کنید «کیفیت عالی، قیمت مناسب، درخشش بینظیر.» 💥مشاوره رایگان 💥 همین حالا تماس بگیرید +989194949693
@Sngsbi_Padideh
آیا میدانستید سنگ کف ساختمان تنها یک مصالح ساختمانی نیست؟ سنگ، روحِ خانه شماست. وقتی سنگ کدر، لکهدار یا مات میشود، کل فضای خانه بیروح به نظر میرسد، حتی اگر گرانترین مبلمان را داشته باشید. کفسابی فقط برای برق انداختن نیست؛ این کار باعث میشود: ۱. منافذ سنگ بسته شود و عمر مفید آن تا چند برابر افزایش پیدا کند. ۲. نظافت منزل بسیار سریعتر و آسانتر شود. ۳. ارزش ملک شما به طرز چشمگیری بالا برود. اگر سنگهایتان د…
کفسابی چیست؟ اجرای کف سابی سنگ ساختمان کفسابی خدمتی است که کفپوش سنگ ، گرانیت ، بتن ، موزائیک و تقریبا اکثر سطوح را می توانیم احیا، براق و شفاف کنیم.ممکن است هدف شما از کف سابی برداشتن ناخنک سنگ ، لکه برداری سطوح و همرنگ سازی بند سنگ باشد. همه این ها و صدها خدمات دیگر در دسته بندی خدمات کفسابی قرار میگیرد. این کار به کمک دستگاه سه کله ساب و سنباده های مخصوص سنگ انجام می شود و از این رو براقیت و تمیزی به دست آمده ، م…
کفسابی برای ضدعفونی کردن کف کفسابی برای میکروب زدایی و استرلیزه کردن سطوح مختلف کفسابی سطوح علاوه بر تمامی مزایای ذکر شده دارای یک مزیت فوق العاده مهم نیز می باشد که آن تمیزی فوق العاده ای است که به سسطوح مختلف می دهد .
Showing the 12 most recent of 18 posts we hold for @sngsbi_PADIDHE. 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.
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.
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.
@sngsbi_PADIDHE named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“کفسابی وسنگ سابی پدیده” (@sngsbi_PADIDHE), 1,095 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/sngsbi_PADIDHE.
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.