Telegram RegisterThe public register of Telegram
Telegram profile photo for سورس حماية سيجي - SeGE

Channel

سورس حماية سيجي - SeGE

@NNN0NN

Not marked by Telegram, checked 2 October 2026

On this record: Topic · Growth · Engagement · What this channel posts · View velocity · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

936,176subscribers

+72,405 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001825258931
TypeChannel
Username@NNN0NN
Description- بوت حجز التمويل @nnvbot . - قناة التمويل| @ninnnn. - لطلب التمويل | @NINNN .
CreatedBetween 1 October 2022 and 29 March 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live28 October 2026
Measurements held52
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/NNN0NN

Topic

Other / unclassifiable — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 65% 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.

Growth

862,7921,108,705985,748.56 August 2026 — 863,771 subscribers6 August 2026 — 863,771 subscribers7 August 2026 — 862,792 subscribers8 August 2026 — 913,042 subscribers9 August 2026 — 994,369 subscribers10 August 2026 — 1,059,914 subscribers11 August 2026 — 1,102,965 subscribers12 August 2026 — 1,108,705 subscribers13 August 2026 — 1,104,552 subscribers15 August 2026 — 1,100,192 subscribers16 August 2026 — 1,095,474 subscribers17 August 2026 — 1,090,938 subscribers18 August 2026 — 1,087,213 subscribers19 August 2026 — 1,084,386 subscribers20 August 2026 — 1,081,257 subscribers21 August 2026 — 1,077,043 subscribers23 August 2026 — 1,073,197 subscribers24 August 2026 — 1,068,725 subscribers25 August 2026 — 1,066,238 subscribers26 August 2026 — 1,063,708 subscribers27 August 2026 — 1,061,121 subscribers28 August 2026 — 1,058,184 subscribers29 August 2026 — 1,054,859 subscribers30 August 2026 — 1,051,668 subscribers31 August 2026 — 1,049,322 subscribers1 September 2026 — 1,045,934 subscribers2 September 2026 — 1,043,259 subscribers4 September 2026 — 1,039,375 subscribers7 September 2026 — 1,032,256 subscribers10 September 2026 — 1,024,224 subscribers12 September 2026 — 1,019,429 subscribers13 September 2026 — 1,015,469 subscribers15 September 2026 — 1,011,914 subscribers17 September 2026 — 1,007,247 subscribers29 September 2026 — 984,811 subscribers5 October 2026 — 974,218 subscribers9 October 2026 — 965,151 subscribers13 October 2026 — 957,417 subscribers14 October 2026 — 954,873 subscribers15 October 2026 — 953,579 subscribers16 October 2026 — 951,451 subscribers17 October 2026 — 949,273 subscribers18 October 2026 — 947,758 subscribers19 October 2026 — 946,552 subscribers21 October 2026 — 944,772 subscribers22 October 2026 — 942,980 subscribers23 October 2026 — 941,238 subscribers24 October 2026 — 939,910 subscribers25 October 2026 — 938,631 subscribers26 October 2026 — 938,381 subscribers27 October 2026 — 937,873 subscribers28 October 2026 — 936,176 subscribers936,1766 August 202628 October 2026
52 measurements spanning 83 days, net +72,405. 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 825,905–1,145,592 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 52
Measured (UTC)SubscribersChange
28 Oct 2026, 20:11936,176-1,697
27 Oct 2026, 16:36937,873-508
26 Oct 2026, 12:40938,381-250
25 Oct 2026, 13:30938,631-1,279
24 Oct 2026, 13:00939,910-1,328
23 Oct 2026, 15:08941,238-1,742
22 Oct 2026, 13:41942,980-1,792
21 Oct 2026, 05:06944,772-1,780
19 Oct 2026, 23:58946,552-1,206
18 Oct 2026, 23:39947,758-1,515
17 Oct 2026, 23:40949,273-2,178
16 Oct 2026, 21:15951,451-2,128
15 Oct 2026, 19:26953,579-1,294
14 Oct 2026, 22:10954,873-2,544
13 Oct 2026, 13:00957,417-7,734
9 Oct 2026, 16:41965,151-9,067
5 Oct 2026, 09:59974,218-10,593
29 Sept 2026, 08:19984,811-22,436
17 Sept 2026, 21:191,007,247-4,667
15 Sept 2026, 18:151,011,914first reading

Engagement

4,564 posts held, back to 29 March 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 170 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.124%
avg views ÷ 936,176 subscribers
Avg views / post
1,160
356 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
356
of 4,564 held

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. It is computed over the 2 of 356 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 October 2026
Posts held4,564 (29 March 2023 – 29 October 2026)
Views total412,570
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Oct 2026, 00:08 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.

What this channel posts

Photos
3
Videos
1
Links
12

Lifetime counters from Telegram’s own channel header, read 29 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 3,782 of this channel’s own posts over the last 30 days: across 6 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 2 days of being posted; a typical post has already reached 10.4% of its 24-hour view count within the first hour, and 45.3% within the first six; the median 24-hour reach across those posts is 12,000 views — 1.15% of this channel’s own subscriber count (90th percentile 43,150).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/1488707 Sept 2026, 00:55 UTC211 minutes – 47 minutes old294 viewsno reaction readingno checkpoint reading yetnot yet at 24h20 minutesprovisional — final view count still climbing
/1488687 Sept 2026, 00:50 UTC216 minutes – 51 minutes old4,100 views ~no reaction readingno checkpoint reading yetnot yet at 24h21 minutesprovisional — final view count still climbing
/1488677 Sept 2026, 00:45 UTC121 minutes – 21 minutes old176 viewsno reaction readingno checkpoint reading yetnot yet at 24hnot measurable yet
/1488657 Sept 2026, 00:40 UTC126 minutes – 26 minutes old2,410 views ~no reaction readingno checkpoint reading yetnot yet at 24hnot measurable yet
/1488647 Sept 2026, 00:35 UTC2under a minute – 31 minutes old214 viewsno reaction readingno checkpoint reading yetnot yet at 24h16 minutesprovisional — final view count still climbing
/1488627 Sept 2026, 00:30 UTC25 minutes – 35 minutes old174 viewsno reaction readingno checkpoint reading yetnot yet at 24h20 minutesprovisional — final view count still climbing
/1488617 Sept 2026, 00:25 UTC211 minutes – 41 minutes old245 viewsno reaction readingno checkpoint reading yetnot yet at 24h16 minutesprovisional — final view count still climbing
/1488597 Sept 2026, 00:20 UTC215 minutes – 46 minutes old203 viewsno reaction readingno checkpoint reading yetnot yet at 24h16 minutesprovisional — final view count still climbing

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 1,000 we hold a reading for · 0.2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @NNN0NN. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 2 September 2026 to 29 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

29 Oct 2026, 00:05 UTC18 viewsread 29 October 2026

عالمنا الخاص.. ملوك وملكات الشوارع 👑🥂 لمّة تجمع أفخم بنات وأفخم ولد بآجواء هادئة وضحكة من القلب.

28 Oct 2026, 23:55 UTC79 viewsread 29 October 2026

كروب اوتاكو سوالف مرتبة بدون عطلات 🎌

28 Oct 2026, 23:45 UTC145 viewsread 29 October 2026

أوروبا تجمع المختلفين… والفرص تبدأ من هنا. 🇪🇺✨

27 Oct 2026, 23:00 UTC229 viewsread 27 October 2026
Forwarded from @NlNNN

https://t.me/jojoowo11 تعالو نضحك ع طلاب المرحلة الاولى

27 Oct 2026, 22:52 UTC432 viewsread 27 October 2026

كـروب حـك سوالف وحتيت وونـسـه وسهر ، 🤍

Showing the 12 most recent of 4,564 posts we hold for @NNN0NN. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@NNN0NN edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
8 August 2026
Most recent edit
16 August 2026

Forward network

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.

Mentions

Named by 3 registered channels — 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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

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

“سورس حماية سيجي - SeGE” (@NNN0NN), 936,176 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/NNN0NN.

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.