Telegram RegisterThe public register of Telegram
Telegram profile photo for ᴅᴇᴇᴘ ʟɪɴᴇs

Channel

ᴅᴇᴇᴘ ʟɪɴᴇs

@Ambarek89

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

194subscribers

-10 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002205824488
TypeChannel
Username@Ambarek89
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live17 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/Ambarek89

Growth

19420419910 August 2026 — 204 subscribers10 August 2026 — 204 subscribers18 August 2026 — 198 subscribers1 September 2026 — 199 subscribers10 September 2026 — 197 subscribers17 September 2026 — 194 subscribers10 August 202617 September 2026
6 measurements spanning 38 days, net -10. 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 193–206 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 01:39194-3
10 Sept 2026, 00:20197-2
1 Sept 2026, 07:35199+1
18 Aug 2026, 08:32198-6
10 Aug 2026, 08:30204no change
10 Aug 2026, 00:47204first reading

Engagement

20 posts held, back to 9 August 2026the 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 10 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

15 reactions across 2 posts, in 11 distinct kinds. The most used accounts for 13.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5215561710189947188213.3%
custom 5280569974404966639213.3%
custom 5838960132846784821213.3%
custom 5958755635544726672213.3%
custom 521326022619458382516.67%
custom 522005362321130578516.67%
custom 532330895774425472016.67%
custom 532361417100521091216.67%
custom 545399109443599759716.67%
custom 545417784820395121716.67%
custom 588871272047103733216.67%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 2 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 15 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 9 August 2026 to 10 August 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

10 Aug 2026, 00:03 UTC9 viewsread 10 August 2026
Forwarded from @sool0o

- ستبقى يتيمًا بعد رحيلها ولو عانقك العالم بأسره ! لا حضن يأخذك ولا قلب يحتويك ولا يدًا تُطبطب عليك ، فمن بعد رحيل أمك ستفقدُ نفسك تمامًا .

Signed نۭ

9 Aug 2026, 23:56 UTC8 viewsread 10 August 2026
Forwarded from @dontmove_87Sticker

Sticker, posted without a caption

Signed 𝗦𝗔𝗟𝗔𝟳

9 Aug 2026, 23:55 UTC7 viewsread 10 August 2026
Forwarded from @dontmove_87Photo

اللي درتوه من ورايا استغفال بيا حنديره قدامكم استهزاء بيكم ! 🔄🔄🔄🔄🔄🔄🔄🔄🔄🔄🔄

Signed 𝗦𝗔𝗟𝗔𝟳

9 Aug 2026, 22:21 UTC11 viewsread 10 August 2026

🌟🌟🌟🌟🌟🌟🌟🌟

Signed شقيرهه😮‍💨🔥.

9 Aug 2026, 22:21 UTC11 views12 reactionsread 10 August 2026
Photo

_الحاجه لي انت بتموت عليها فلواقع ملهاش ايي قيمه، قيمتها الوحيده بس انك انت تبيها جرب تقعد متبيهاش حتلقاها متسواش ولا حاجه في نظرك🚬.

custom 59587556355447266722custom 52132602261945838251custom 52155617101899471881custom 52200536232113057851custom 52805699744049666391custom 53233089577442547201custom 53236141710052109121custom 54539910944359975971

Signed شقيرهه😮‍💨🔥.

9 Aug 2026, 22:14 UTC8 viewsread 10 August 2026
Forwarded from @dontmove_87Sticker

Sticker, posted without a caption

Signed 𝗦𝗔𝗟𝗔𝟳

9 Aug 2026, 21:56 UTC11 viewsread 10 August 2026
Sticker

Sticker, posted without a caption

Signed ⵔⵜⴰⵊ‏

9 Aug 2026, 21:56 UTC10 viewsread 10 August 2026
Forwarded from @refr30Photo

. ᷂إحترامك ᷂لنفسك ᷂يبدأ ᷂من ᷂رفضك 🛸 ⚪️ ᷂أن ᷂تكون ᷂لإنسان ᷂سد ᷂إحتياج ❤️

Signed ⵔⵜⴰⵊ‏

9 Aug 2026, 17:49 UTC14 views3 reactionsread 10 August 2026

Posted without readable text

custom 52155617101899471881custom 52805699744049666391custom 58389601328467848211

Signed امبارك الزوي

9 Aug 2026, 13:27 UTC13 viewsread 10 August 2026
Forwarded from @dontmove_87Sticker

Sticker, posted without a caption

Signed 𝗦𝗔𝗟𝗔𝟳

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

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

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

“ᴅᴇᴇᴘ ʟɪɴᴇs” (@Ambarek89), 194 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Ambarek89.

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.