Telegram RegisterThe public register of Telegram
Telegram profile photo for C#.. visual studio

Channel

C#.. visual studio

@com_science_c_sharp

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

2,557subscribers

-74 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-1001128339073
TypeChannel
Username@com_science_c_sharp
Created7 September 2017 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live12 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/com_science_c_sharp

Topic

Technology — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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

2,5572,6312,5947 August 2026 — 2,631 subscribers7 August 2026 — 2,631 subscribers10 August 2026 — 2,624 subscribers13 August 2026 — 2,619 subscribers16 August 2026 — 2,615 subscribers19 August 2026 — 2,610 subscribers23 August 2026 — 2,607 subscribers26 August 2026 — 2,604 subscribers29 August 2026 — 2,605 subscribers31 August 2026 — 2,603 subscribers4 September 2026 — 2,602 subscribers10 September 2026 — 2,596 subscribers13 September 2026 — 2,593 subscribers17 September 2026 — 2,587 subscribers26 September 2026 — 2,582 subscribers5 October 2026 — 2,563 subscribers12 October 2026 — 2,557 subscribers7 August 202612 October 2026
17 measurements spanning 66 days, net -74. 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 2,546–2,642 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 02:362,557-6
5 Oct 2026, 04:562,563-19
26 Sept 2026, 11:362,582-5
17 Sept 2026, 12:212,587-6
13 Sept 2026, 21:192,593-3
10 Sept 2026, 10:592,596-6
4 Sept 2026, 19:412,602-1
31 Aug 2026, 23:182,603-2
29 Aug 2026, 09:072,605+1
26 Aug 2026, 04:292,604-3
23 Aug 2026, 00:292,607-3
19 Aug 2026, 19:582,610-5
16 Aug 2026, 19:372,615-4
13 Aug 2026, 06:472,619-5
10 Aug 2026, 04:482,624-7
7 Aug 2026, 04:152,631no change
7 Aug 2026, 04:062,631first reading

Engagement

19 posts held, back to 7 September 2017 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 2 pages 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 19 posts for this entry, the most recent from 21 September 2017. An engagement rate over an empty window would be a number about nothing.

Recent posts

21 Sept 2017, 10:42 UTC≈32,300 viewsread 7 August 2026

C# Program to Swap two Numbers using System; namespace Program { class Program { static void Main (string [ ] args) { int num1, num2, temp ; Console . WriteLine (" Enter the First Number : " ) ; num1 = int .Parse ( Console. ReadLine( )) ; Console . WriteLine (" Enter the Second Number : " ) ; num2 = int .Parse ( Console. ReadLine( )) ; temp = num1 ; num1 = num2 ; num2 = temp ; Console . WriteLine (" After…

21 Sept 2017, 10:42 UTC≈35,300 viewsread 7 August 2026

Here is the output of the C# Program: Enter the First Number : 23 Enter the Second Number : 25 After Swapping : First Number : 25 Second Number : 23

21 Sept 2017, 10:42 UTC≈38,800 viewsread 7 August 2026

static void SwapByRef(ref int x, ref int y) { int temp = x; x = y; y = temp; } When you call the SwapByRef method, use the ref keyword in the call, as shown in the following example. C# static void Main() { int i = 2, j = 3; System.Console.WriteLine("i = {0} j = {1}" , i, j); …

21 Sept 2017, 10:23 UTC≈31,200 viewsread 7 August 2026

If(a>0) { console. WriteLine("positive num"); } else { console. WriteLine("negative num"); } console. ReadKey();

21 Sept 2017, 10:23 UTC≈33,600 viewsread 7 August 2026

Int d=2; Switch(d) { Case 1: console. WriteLine("sunday"); break; Case 2: console. WriteLine("monday"); break; Case 3: console. WriteLine("tuesday"); break; Default: console. WriteLine("not a day"); }

21 Sept 2017, 10:23 UTC≈30,000 viewsread 7 August 2026

Control statements in c# Means branching and looping Branching includes If -else Switch-case ...... Looping includes For While Do while For each

20 Sept 2017, 15:48 UTC≈28,200 viewsread 7 August 2026

Explain the control statements in c# with suitable example.

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

“C#.. visual studio” (@com_science_c_sharp), 2,557 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/com_science_c_sharp.

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.