Telegram RegisterThe public register of Telegram
Telegram profile photo for Omid Negar Software

Channel

Omid Negar Software

@omidnegarsoft

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

1,195subscribers

+33 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001005085265
TypeChannel
Username@omidnegarsoft
CreatedBetween 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/omidnegarsoft

Topic

Software piracy — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

1,1611,1961,178.57 August 2026 — 1,162 subscribers7 August 2026 — 1,162 subscribers12 August 2026 — 1,161 subscribers16 August 2026 — 1,186 subscribers19 August 2026 — 1,189 subscribers26 August 2026 — 1,193 subscribers1 September 2026 — 1,191 subscribers4 September 2026 — 1,193 subscribers9 September 2026 — 1,194 subscribers13 September 2026 — 1,196 subscribers17 September 2026 — 1,195 subscribers1,1957 August 202617 September 2026
11 measurements spanning 42 days, net +33. 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 1,156–1,201 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 17:011,195-1
13 Sept 2026, 19:151,196+2
9 Sept 2026, 23:591,194+1
4 Sept 2026, 19:181,193+2
1 Sept 2026, 03:381,191-2
26 Aug 2026, 04:281,193+4
19 Aug 2026, 11:551,189+3
16 Aug 2026, 04:251,186+25
12 Aug 2026, 18:551,161-1
7 Aug 2026, 03:511,162no change
7 Aug 2026, 00:461,162first reading

Engagement

20 posts held, back to 22 December 2025the 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 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

31 Jul 2026, 21:41 UTC≈2,300 viewsread 7 August 2026

https://www.csiamerica.com/software/ETABS/23/ETABSv2331Build4563Setup.exe برای دانلود از VPN استفاده کنید ( طریقه ی کرک کردن مطابق ETABS 23.3.0 می باشد )

20 Jun 2026, 14:36 UTC≈4,310 viewsread 7 August 2026
File

☀️اصلاحیه ی منتشر شده از سوی ACI اعمال شده است. ☀️پیوست E ( تبدیل واحدها ) اضافه شده است. 1405-03-30 ( 2026-06-20 )

22 Feb 2026, 00:24 UTC≈4,620 viewsread 7 August 2026
Video

⭐️ Tip ⭐️ Beam Design Information - Total Longitudinal Reinforcing in ETABS نکاتی در مورد نمایش نتایج طراحی تیرها - آرماتورهای طولی کل ☀️ از دقیقه ی 6:40 نسبت به کلیپ قبل اصلاح شده است.

15 Feb 2026, 05:23 UTC≈4,540 viewsread 7 August 2026
Photo

⭐️ از تغییرات ACI318-25 ⭐️ معیارهای پذیرش و موارد مجاز دانسته شده برای استفاده از وصله های مکانیکی و جوشی در ACI318-25 تغییرات اساسی داشته است که برای آگاهی از آن ها باید به فصل های 18 و 25 مراجعه کرد. ☀️وصله ی Type 2 در ACI318-19 معادل وصله ی Class L در ACI318-25 لحاظ شده است ، استفاده از وصله ی Class L در سازه های با شکل پذیری ویژه مجاز نمی باشد.

11 Feb 2026, 15:04 UTC≈1,190 viewsread 7 August 2026
Video

⭐️ Tip ⭐️ Draw Beam Sections Plan ترسیم پلان مقطع تیرها

29 Jan 2026, 00:14 UTC≈1,020 viewsread 7 August 2026
Video

Home - Import - Load Structure Data - Beam Settings - Additional Bars Tab

6 Jan 2026, 16:55 UTC≈1,190 viewsread 7 August 2026
Video

⭐️ Tip ⭐️ Alignment of Columns and Beams with Building Edges همباد کردن ستون و تیرها با لبه ی سازه

Showing the 12 most recent of 20 posts we hold for @omidnegarsoft. 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.

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.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Omid Negar Software” (@omidnegarsoft), 1,195 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/omidnegarsoft.

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.