Telegram RegisterThe public register of Telegram
Telegram profile photo for ITStockPro

Channel

ITStockPro

@itstockpro_com

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

658subscribers

+5 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001355324924
TypeChannel
Username@itstockpro_com
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/itstockpro_com

Topic

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

6526586557 August 2026 — 653 subscribers8 August 2026 — 653 subscribers23 August 2026 — 652 subscribers29 August 2026 — 654 subscribers9 September 2026 — 652 subscribers17 September 2026 — 654 subscribers1 October 2026 — 657 subscribers11 October 2026 — 658 subscribers7 August 202611 October 2026
8 measurements spanning 65 days, net +5. 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 651–659 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 14:02658+1
1 Oct 2026, 16:20657+3
17 Sept 2026, 21:37654+2
9 Sept 2026, 03:35652-2
29 Aug 2026, 23:07654+2
23 Aug 2026, 00:56652-1
8 Aug 2026, 02:46653no change
7 Aug 2026, 15:10653first reading

Engagement

20 posts held, back to 7 January 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.

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 2 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

6 reactions across 4 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍6100.0%

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 4 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 6 reactions 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 7 January 2026 to 2 August 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.

Recent posts

15 Jul 2026, 10:22 UTC588 viewsread 8 August 2026
Photo

🔥 سوئیچ Cisco Catalyst C9300-24S-A؛ انتخاب حرفه‌ای برای شبکه‌های Enterprise اگر به دنبال یک سوئیچ قدرتمند، پایدار و قابل توسعه برای زیرساخت شبکه سازمانی خود هستید، Cisco Catalyst 9300 یکی از بهترین گزینه‌های موجود است. ⚙️ مشخصات: 🔹 24× پورت +SFP گیگابیتی 🔹 Modular Uplinks 🔹 لایسنس Network Advantage 🔹 مناسب برای Core و Distribution شبکه 🔹 پشتیبانی از StackWise و قابلیت توسعه ✅ کالای اورجینال ✅ ریفر اورجینال با کیفی…

12 Jul 2026, 08:16 UTC217 views2 reactionsread 8 August 2026
Photo

🔥 فروش ویژه مینی‌کیس و تاینی استوک HP اگر دنبال یک سیستم جمع‌وجور، کم‌مصرف، اقتصادی و قابل اعتماد برای شرکت، فروشگاه، آموزشگاه، حسابداری، امور اداری یا استفاده روزمره هستید، مینی‌کیس‌ها و تاینی‌های استوک HP انتخابی حرفه‌ای و مقرون‌به‌صرفه‌اند. 💻 HP Mini / Tiny / Desktop مدل‌های موجود: G4 | G5 | G6 ⚙️ پردازنده‌های نسل 5 تا 10 🚀 Core i5 / Core i7 ⚡️ قابل ارائه با رم و حافظه دلخواه 💾 امکان کانفیگ با SSD / HDD مطابق ن…

👍2

12 Jul 2026, 08:02 UTC907 viewsread 8 August 2026
Photo

🚀 سرور بکاپ آماده کار با Veeam HPE DL380 Gen9 12LFF ⚙️ 2× Xeon E5-2680 v4 ⚡️ 32GB RAM 💾 12×1TB HPE SATA LFF New 🌐 2× SFP+ 10G مناسب برای Veeam Backup، آرشیو اطلاعات و ذخیره‌سازی سازمانی ✅ قابل ارائه با RAID 5 ✅ ظرفیت خام: 12TB ✅ ظرفیت مفید بعد از RAID 5: حدود 11TB ✅ سرعت حدودی Read: حدود 1.5 تا 2GB/s ✅ سرعت حدودی Write: حدود 700MB/s تا 1.2GB/s ✅ نرم‌افزار نصب‌شده و آماده کار 📌 جهت دریافت قیمت مطابق با کانفیگ مد …

12 Jul 2026, 08:01 UTC360 viewsread 8 August 2026
Photo

🚀 سرور مناسب VoIP و مرکز تماس HPE DL360 Gen9 ⚙️ 2× Xeon E5-2680 v4 ⚡️ 32GB RAM 💾 3×600GB HDD 10K SAS مناسب برای راه‌اندازی VoIP Server، Call Center، Issabel، FreePBX و IP-PBX با عملکرد پایدار و اقتصادی. 📌 جهت دریافت قیمت مطابق با کانفیگ مد نظر خود با ما در تماس باشید: 🌐 itstock.net 🆔 @ITStockPro ☎️ 021-91092796

8 Jul 2026, 14:39 UTC220 views2 reactionsread 8 August 2026
Photo

🚀 قدرت واقعی برای دیتابیس! HPE DL380 Gen10 💥 2× Xeon Gold 5222 با فرکانس 3.8GHz ⚡ 256GB RAM ⚡ 4×960GB Enterprise SSD (RAID10) 💾 4×1.2TB SAS 10K ساخته شده برای SQL Server، Oracle، نرم‌افزارهای مالی و پردازش‌های سنگین که سرعت پردازنده و دیسک، مهم‌ترین عامل عملکرد آن‌هاست. جهت دریافت قیمت مطابق با کانفیگ مد نظر خود با ما در تماس باشید 🌐 : @ITStockPro_com 🆔 : @ITStockPro ☎️ : 021-91092796 📳 : 09126962798 📳 : 09337796

👍2

2 Jul 2026, 11:07 UTC797 views1 reactionsread 8 August 2026
Photo

Ram HPE 16Gb 2133P 🔹 رم‌های HPE با کیفیت بالا، تست‌شده و تضمین 🔸 قیمت رقابتی ویژه همکاران و دیتاسنترها 📦 آماده ارسال فوری 💡 کاملاً سازگار 🛠 مناسب برای دیتاسنترها، پروژه‌های اقتصادی، و ارتقاء سیستم‌های سازمانی 💰 قیمت اقتصادی‌ : 9.500.000 راه‌های ارتباطی: 🌐 وب‌سایت: @ITStockPro_com 🆔 تلگرام: @ITStockPro ☎️ تلفن ثابت: 021-91092796 📱 همراه: 09126962798 | 0933779631

👍1

Showing the 12 most recent of 20 posts we hold for @itstockpro_com. 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 11 October 2026 — this entry's latest reading, not the date you are reading this.

“ITStockPro” (@itstockpro_com), 658 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/itstockpro_com.

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.