Channel
@Asamrockwool
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
254subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001092661450 |
|---|---|
| Type | Channel |
| Username | @Asamrockwool |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 3 times, most recently 7 November 2026 |
| On Telegram | t.me/Asamrockwool |
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 11 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @Asamrockwool/707 · this entry15 May 2020, 18:22 UTC | @ayeg_nano/34415 May 2020, 18:22 UTC | 1.00 | under a minute |
| @Asamrockwool/713 · this entry29 Aug 2020, 14:14 UTC | @ayeg_nano/34829 Aug 2020, 14:16 UTC | 0.98 | 2 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @ayeg_nano | 5 (5/5 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (4–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 16 comparable posts for this entry, running 15 January 2020 to 21 February 2023. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @Asamrockwool — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 11 November 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.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Oct 2026, 20:07 | 254 | +1 |
| 16 Oct 2026, 13:16 | 253 | -1 |
| 9 Oct 2026, 11:14 | 254 | -1 |
| 29 Sept 2026, 02:59 | 255 | +1 |
| 7 Aug 2026, 02:03 | 254 | no change |
| 6 Aug 2026, 00:23 | 254 | first reading |
20 posts held, back to 15 January 2020 — 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.
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 21 February 2023. An engagement rate over an empty window would be a number about nothing.
مزایای عایق حرارتی پشم سنگ لوله ای: پشم سنگ جلوگیری کننده از دست دادن حرارت در سیستم های گرمایشی و تامین آب گرم می شود و اساسا یک ساختار عایق حرارتی برای لوله کشی شامل یک ماده عایق مناسب است که معمولا با روکشی پوشش داده می شود. و این عمل لوله و عایق را از تاثیرات خارجی مانند تاثیر پذیری هوا محافظت می کند. لذا آب گرم و گرما نیز در آخرین نقطه دور از منبع تامین می شود. استفاده از پشم سنگ لوله ای دارای مزایای زیادی است…
🔥پشم سنگ عایق صدا چطور مشکل ما رو حل میکنه؟ پشم سنگی که برای عایق کاری صدای دیوار همجوار استفاده میشه از نوع عایق تخته ای هست. اطلاعات بیشتر رو اینجا بخونید؟ https://asamrockwool.com/news/tabid/149/vw/1/itemid/274/
روش باور نکردنی ساده موثر قطع صدای کوبه ای سقف همسایه طبقه بالا سوال: همسایه طبقه بالایی ما کودکی داره صدای دویدن و جیغ اذیت میکنه برای عایق سقف منزل خود چکار باید بکنم. برای پوشش صداهای کوبه ای مثل دویدن و کشیدن و همچنین پوشش سر و صداها پیشنهاد می شود: ۱ - عایق پشم سنگ تخته ای ضخامت ۵ سانت دانسیته ۱۴۰ استفاده شود. ۲ - اگر از پشم سنگ تخته ای ضخامت ۱۰ سانت دانسیته ۱۲۰ یا ۱۴۰ استفاده شود خیلی عالی می شود. اطلاعت بیش…
https://www.instagram.com/asemani.jafar
سلام یه پستی در مورد نحوه ساخت استودیو خانگی بی صدا با عایق پشم سنگ تخته ای در اینستاگرام گذاشتم اگر ممکنه آنرا ببینید نظرتون رو بگید. آدرس پیجم👇👇 asemani.jafar ممنونم https://www.instagram.com/p/Cd28GJ7jUD5/?igshid=YmMyMTA2M2Y=
روش باور نکردنی ساده موثر قطع صدای کوبه ای سقف همسایه طبقه بالا سوال: همسایه طبقه بالایی ما کودکی داره صدای دویدن و جیغ اذیت میکنه برای عایق سقف منزل خود چکار باید بکنم. برای پوشش صداهای کوبه ای مثل دویدن و کشیدن و همچنین پوشش سر و صداها پیشنهاد می شود: ۱ - عایق پشم سنگ تخته ای ضخامت ۵ سانت دانسیته ۱۴۰ استفاده شود. ۲ - اگر از پشم سنگ تخته ای ضخامت ۱۰ سانت دانسیته ۱۲۰ یا ۱۴۰ استفاده شود خیلی عالی می شود. اطلاعت بیش…
تشخیص بهترین چسب کاشی: 1 - مقاوم در برابر مواد شوینده، اسیدها، بازها و شوینده های خانگی 2 - چسب سرامیک ضد اسید هست که اسید نمی تواند خراب کند 3 - اهش وزن ساختمان وكاربرد آسان افزايش سرعت اجرا 4 - عمر طولانی نسبت به مصالح بندکشی معمولی 5 - مقاوم دربرابر تغییرات دما پس ا ز خشک شدن 6 - چسب کاشی ضد حرارت در حد ۲۰ تا ۳۰ درصد 7 - کاهش هزینه های دوغاب ریزی پشت کاشی 8 - چسب کاشی ضد آب و عایق رطوبتی است. 9 - قابل اجرا در کلیه…
https://asamrockwool.com/news/tabid/149/vw/1/itemid/522/
https://www.instagram.com/p/CN7kPqwjyTs/?igshid=1k21qrcj8pzfb
اگر سرمای سوزناک زمستان و گرمای تخم مرغ پز تابستان از دیوار شما نفوذ می کند به استخوانتان می رسد عایق حرارتی نانو سفید می تواند شما را با کشیدن عایق سفید حرارتی نانو به ضخامت یک سانتی متر به دیوارتان از سرما و گرما حفظ کند. برای اطلاعات بیشتر مطلب زیرا بخوانید: فروش عایق نانو حرارتی سفید دیوار با تحمل ۱۰۰۰ درجه سانتیگراد دما
نانو بند کشی جهت عایق کاری، آب بندی و ترمیم بندکشی های قدیمی، بندکشی و رفع نم بدون تخریب و خرابی سنگ، موزاییک یا سرامیک پشت بام ها ، تراس ها و نماها، سرویس های بهداشتی، آشپزخانه و دیگر سطوح ساختمانی بسیار مناسب است. آموزش مراحل هفتگانه نحوه بندکشی با نانو بندکشی کالیمورا در لینک زیر: https://bit.ly/31GMlVR
شما صدای گوش خراش پمپ آب را شنیده ای. توی این مواقع فکر کردی چه کاری باید انجام بدی در این شرایط به فکر راهکار افتاده ای من در این پست راهکار را گفته ام، گوش کن اگر شما هم راهکاری برای حل مشکل هموطنان دارین به ما بفرستین تا با هم به اشتراک بگذاریم لطفا این فیلم و پیج ما را به دوستان و اقوام معرفی کنید. #قطع_صدای_پمپ_آب #مرکز_فروش_پشم_سنگ_آسام #پشم_سنگ_آسام #پشم_سنگ_تخته_ای #عایق_پشم_سنگ_تخته_ای راه ارتباطی: 📲…
Showing the 12 most recent of 20 posts we hold for @Asamrockwool. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
@Asamrockwool 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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“مرکز فروش پشم سنگ آسام” (@Asamrockwool), 254 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/Asamrockwool.
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.