Telegram RegisterThe public register of Telegram
Telegram profile photo for .

Channel

.

@signam0del

On this record: Previous handles · Growth · Engagement · Reactions · Posts · Cite this entry

2subscribers

-14 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003832098204
TypeChannel
Username@signam0del
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live10 September 2026
Measurements held4
Confirmed unchanged3 times, most recently 10 September 2026
On Telegramt.me/signam0del

Previous handles

@signam0del was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@signam0del
held 11 August 202611 August 2026

Growth

218108 August 2026 — 16 subscribers11 August 2026 — 16 subscribers15 August 2026 — 18 subscribers24 August 2026 — 2 subscribers8 August 202624 August 2026
4 measurements spanning 16 days, net -14. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 10:182-16
15 Aug 2026, 16:5218+2
11 Aug 2026, 22:0116no change
8 Aug 2026, 01:0116first reading

Engagement

8 posts held, back to 1 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 8 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

40 reactions across 5 posts, in 7 distinct kinds. The most used accounts for 35.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎1435.0%
🔥1127.5%
💋512.5%
💯410.0%
37.50%
💔25.00%
💘12.50%

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

Measured over the 8 most recent posts we hold, published 1 August 2026 to 6 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

6 Aug 2026, 09:59 UTC102 views6 reactionsread 11 August 2026
Photo

6 модель на ляжках в чёрных чулках - 30 ⭐ на ляжках в чулках с черепом - 40 ⭐ возле талии - 40 ⭐ на груди - 50 ⭐

👎2💔1💘1💯1🔥1

4 Aug 2026, 12:27 UTC137 views10 reactionsread 11 August 2026
Photo

5 модель на ляжках - 50 ⭐ на попе в колготках с сеточкой - 100 ⭐ на попе - 150 ⭐ видео с сигной на попе / со всем телом (до 10сек) - 200 ⭐

🔥7👎2💔1

3 Aug 2026, 16:42 UTC143 views10 reactionsread 11 August 2026
Photo

4 модель с языком - 40 ⭐ с флагом - 40 ⭐ с ножками - 75 ⭐ на груди - 100 ⭐

👎5💋2💯2🔥1

1 Aug 2026, 11:11 UTC173 viewsread 11 August 2026

первый отзыв уже есть ❣️❣️❣️

1 Aug 2026, 07:36 UTC185 views7 reactionsread 11 August 2026
Photo

3 модель на ляжках - 15 ⭐ в чулках - 25 ⭐

3👎3🔥1

1 Aug 2026, 06:50 UTC184 views7 reactionsread 11 August 2026
Photo

2 модель ໒꒰ྀི ˶• ༝ •˶ ྀི১ (остальных примеров пока что нет, но как видите вайб и качество есть) ✩ в туфельках 15 звездочек ✩ с лицом 40 звездочек ✩ на ляшках в милых чулочках 50 звездочек ✩ на груди в лифе 100 звёздочек ✩на бедре возле трусов 100 звездочек ✩ на внутреннией части бедра с раздвинутыми ногами 150 звёздочек ✩ на попе сидя 150 звёздочек ✩ на попе лежа 150 звездочек

💋3👎2💯1🔥1

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

“.” (@signam0del), 2 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/signam0del.

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.