Telegram RegisterThe public register of Telegram
Telegram profile photo for متاهة الأرواح.

Channel

متاهة الأرواح.

@sharedd

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

434subscribers

-17 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-1001305972987
TypeChannel
Username@sharedd
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 October 2026
Last confirmed live8 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/sharedd

Topic

Literature — 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 7 October 2026 and assigned it the closest of 31 fixed categories, at 71% 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

434451442.57 August 2026 — 451 subscribers14 August 2026 — 446 subscribers23 August 2026 — 448 subscribers7 September 2026 — 445 subscribers15 September 2026 — 443 subscribers28 September 2026 — 438 subscribers7 October 2026 — 438 subscribers8 October 2026 — 434 subscribers7 August 20268 October 2026
8 measurements spanning 62 days, net -17. 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 431–454 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 20:00434-4
7 Oct 2026, 17:23438no change
28 Sept 2026, 02:57438-5
15 Sept 2026, 15:41443-2
7 Sept 2026, 12:20445-3
23 Aug 2026, 08:58448+2
14 Aug 2026, 21:36446-5
7 Aug 2026, 15:20451first reading

Engagement

20 posts held, back to 20 March 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
26.3%
avg views ÷ 434 subscribers
Avg views / post
114
1 post measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
1
of 20 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 27 September 2026
Posts held20 (20 March 2026 – 27 September 2026)
Views total114
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Oct 2026, 17:23 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.

Reaction mix

102 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 64.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💔6664.7%
❤2625.5%
🔥32.94%
😢32.94%
😇21.96%
👍10.98%
🤣10.98%

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 19 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 102 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 20 March 2026 to 27 September 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

27 Sept 2026, 20:38 UTC114 viewsread 7 October 2026

أتساءلُ..؟ لو أنني منذُ البداية لم ألتقِ بكِ، هل كان قلبي سينجو من كل هذا الحنين..؟ هل كان الليل سيبدو أقل وحشة.. أقل وجعاً.. وأقل قسوة..؟ أتساءلُ..؟ كيف سيكون قلبي لو أنكِ لم تكوني في إحدى زواياه..؟ هل كنتُ سأعرف هذا الحنين..؟ هل كان الليل سيكون بهذا الإتساع..؟ وهل كانت الذكرى ستعرف طريقها إليَّ كلما أغلقتُ أبواب النسيان..؟ ربما.. كنتُ سأعيشُ أخفَّ قلباً، أقل إنتظاراً، وأكثر قدرةً على المرورِ من الأشياء دون أن ألتف…

Signed فكر شارد

11 Sept 2026, 17:56 UTC206 views4 reactionsread 7 October 2026

عُد... فقط عُد.. ولا تسألني لماذا.. فكل أسباب الحياة تختصرها عودتك.

💔3❤1

Signed فكر شارد

5 Sept 2026, 04:07 UTC275 views4 reactionsread 7 October 2026

إنه قلبي.. ما زالَ يُعلّق صورَكِ على جدرانِ الذاكرةِ كلَّ صباح.

💔3❤1

Signed فكر شارد

21 Aug 2026, 19:16 UTC400 views5 reactionsread 7 October 2026

في كل شيء هناك شيءٌ منكِ يطارِدني..

❤4💔1

Signed فكر شارد

11 Aug 2026, 05:08 UTC523 views2 reactionsread 7 October 2026

أفتح عينيّ في الصباح وكأنني أعتذر لنفسي لأنني ما زلتُ أتنفس. لا رغبة في شيء، لا شغف، لا دهشة... مجرد جسدٍ يتجول في العدم.

🔥2

Signed فكر شارد

6 Aug 2026, 17:31 UTC576 views4 reactionsread 7 October 2026

تعال… ابقى قليلاً، ثم ارحل إن شئت، لكن اترك شيئاً منك يكفيني لأعيش ليلة أخرى.

💔3❤1

Signed فكر شارد

14 Jul 2026, 00:09 UTC816 views6 reactionsread 7 October 2026

كل شيءٍ حولي يُذكرني بك، كل تفصيلٍ صغيرٍ يُحاكي ملامحك، كل سؤالٍ يواجهني أراكِ إجابةً له، وكل طريقٍ أسيرُ فيه يقودني إليكِ، رغم كل الحواجز التي تفرضُ نفسها بيننا.

💔4❤1😢1

Signed فكر شارد

3 Jul 2026, 23:42 UTC975 views4 reactionsread 7 October 2026

ما بين "مباركٌ لكِ"... و"رحمَ الله قلبي"... مسافةُ ثلاث سنوات...💔👨‍🦯

💔4

Signed فكر شارد

26 Jun 2026, 23:51 UTC≈1,120 views5 reactionsread 7 October 2026

وحيداً في عالمٍ خالٍ من البهجة...💔👨‍🦯

💔5

Signed فكر شارد

21 Jun 2026, 20:20 UTC≈1,280 views5 reactionsread 7 October 2026

مُستنزف... كحنجرةِ مغنٍّ في قاعةٍ فارغة.

💔4👍1

Signed فكر شارد

15 Jun 2026, 19:31 UTC≈1,510 views8 reactionsread 7 October 2026

لا أعرف أين أنا… ولا أعرف أين كُنت… ولا أعرف أين يجب أن أكون. كل ما أعرفه أنني في كل ليلة أعود إلى نفسي ولا أجدني.

💔7🤣1

Signed فكر شارد

8 Jun 2026, 17:45 UTC≈1,580 views7 reactionsread 7 October 2026

أخاف أن ألتقيكِ صدفةً أن تجمعنا الأقدارُ عند رصيفٍ مهجور أو محطةٍ نسيتُ أن أتفادى المرور بها. أن أراكِ واقفةً أمامي تحملين ذات الحضور الذي كنتُ أهرب منه، فتتساقط كل أقنعتي كأوراق خريفٍ استحال عليها الصمود. أخاف أن تُعيد اللحظةُ ترتيب المشهد، أن تنظرين إليّ بنظرةٍ تحملُ شيئاً من عتابٍ وشيئاً من شوق، فتسقط الكلمات مني كحجارةٍ تساقطت من جدارٍ ظننته منيعا. أأكون عندها قادراً على كبح انفعالاتي، أم أن قلبي سيخذلني كما خذل…

💔7

Signed فكر شارد

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

“متاهة الأرواح.” (@sharedd), 434 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/sharedd.

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.