Telegram RegisterThe public register of Telegram

Channel

together in death info

@sta1lsk_inf

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

159subscribers

+0 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-1002567730383
TypeChannel
Username@sta1lsk_inf
Created23 August 2025measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/sta1lsk_inf

Growth

1597 Aug 2026, 19:14 — 159 subscribers8 Aug 2026, 17:31 — 159 subscribers7 Aug 2026, 19:148 Aug 2026, 17:31
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 158–160 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 17:31159no change
7 Aug 2026, 19:14159first reading

Engagement

16 posts held, back to 23 August 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 16 posts for this entry, the most recent from 5 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
5
Links
4

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

Recent posts

5 Apr 2026, 10:57 UTC≈1,910 viewsread 8 August 2026
Forwarded from @STA1LSK

всем здравия. мы не в первый раз сталкиваемся с проблемой воровства наших работ. хотелось бы поднять эту тему в надежде, что адекватных пользователей станет больше. неоднократно повторялось, что копирование наших паков запрещено. почему мы всё еще продолжаем это видеть? если вы думаете, что данная шалость останется незамеченной, вы очень заблуждаетесь. рано или поздно всё всплывет на поверхность, и никто из авторов

4 Jan 2026, 11:44 UTC≈4,130 viewsread 8 August 2026

🥡🔤еста для вп/рекламы! 3.08 — свободно 4.08 — свободно 5.08 — свободно 6.08 — свободно 7.08 — свободно 8.08 — свободно 9.08 — свободно 10.08 — свободно 11.08 — свободно 12.08 — свободно 13.08 — свободно 14.08 — свободно 15.08 — свободно

6 Oct 2025, 15:38 UTC≈6,620 viewsread 8 August 2026

ᅠᅠ🔤𝘙𝘐𝘊𝘌 @STA1LSK 🔗 на время; ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ 🥹 2/12 - 300₽ 🥹 3/24 - 400₽ 🥹 4/36 - 500₽ 🥹 5/48 - 600₽ 🥹 12/24 (ночной топ) - 1000₽ ᅠᅠᅠ 🔗в сторис канала; 🥹 6ч - 200₽ 🥹 12ч - 400₽ 🥹 24ч - 600₽ 🥹 48ч - 800₽ • в профиле канала - +100₽ к цене. • публикуется вне очереди бронов. ᅠᅠᅠ 🔗🔤ополнительно; 🥹 часы топа — 50₽ 🥹 подгоны — 50₽ 🥹 закреп — бесплатно  ᅠ 🔗НЕ рекламирую; рж, скам, хейт, 18+, каналы без четкой тема

24 Aug 2025, 11:05 UTC≈6,770 viewsread 8 August 2026
Photo

ᅠᅠ🥹 🔤равила для вступления: 🥹 относитесь к работе ответственно и оформляйте посты аккуратно, а не на скорую руку. 🥹 в названии обязательно сначала идет юз нашего канала, потом юз вашего. личные юзы не ставим. 🥹 желательно, чтобы колор в паках был более менее одинаковым, а фотографии в хорошем качестве. 🥹 норма: ᅠᅠᅠ— паки: 4 в месяц. ᅠᅠᅠ— аватарки: 8 в месяц. 🥹 для пиара нужно: ᅠᅠᅠ— 10+ паков. ᅠᅠᅠ— 15+ аватарок.

24 Aug 2025, 10:53 UTC≈6,280 viewsread 8 August 2026
Photo

ᅠᅠᅠ🔤заимный пиар; 🥡 на приход: ᅠᅠᅠ • 20-50 чел. ᅠᅠᅠ • только по тематике! 🥡 на время: ᅠᅠ • 1/12 & 2/24 ᅠᅠ• топ обязателен, насчет подгонов и закрепа договоримся лично 🥡 на просмотры: ᅠᅠᅠ• 1к - 5к ᅠᅠᅠ• беру как обычные посты, так и впешные. 🤍 писать: @sta1lsk_dr

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“together in death info” (@sta1lsk_inf), 159 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/sta1lsk_inf.

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.