Telegram RegisterThe public register of Telegram
Telegram profile photo for Угрозы Дарьи Артемьевой

Channel

Угрозы Дарьи Артемьевой

@dashshart1

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

372subscribers

+25 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-1002251222244
TypeChannel
Username@dashshart1
CreatedBetween 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/dashshart1

Growth

347372359.57 August 2026 — 347 subscribers8 August 2026 — 347 subscribers16 August 2026 — 350 subscribers23 August 2026 — 362 subscribers29 August 2026 — 361 subscribers8 September 2026 — 370 subscribers15 September 2026 — 372 subscribers7 August 202615 September 2026
7 measurements spanning 39 days, net +25. 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 343–376 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 14:41372+2
8 Sept 2026, 03:01370+9
29 Aug 2026, 22:24361-1
23 Aug 2026, 01:05362+12
16 Aug 2026, 06:13350+3
8 Aug 2026, 06:49347no change
7 Aug 2026, 19:27347first reading

Engagement

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

What this channel posts

Video runtime
3m 13s
Average length
1m 04s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

126 reactions across 14 posts, in 13 distinct kinds. The most used accounts for 35.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁4535.7%
🤣3931.0%
🤮1411.1%
😭118.73%
😱53.97%
👍32.38%
💯21.59%
😐21.59%
10.794%
🍌10.794%
👏10.794%
🙏10.794%
🥴10.794%

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

Measured over the 16 most recent posts we hold, published 27 July 2026 to 7 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

7 Aug 2026, 05:24 UTC298 views12 reactionsread 8 August 2026

От энергосов плохо это не страшно… представь кому то приходится переживать отхода от мефедрона… или ебаться за деньги

😁9🤣2🍌1

2 Aug 2026, 18:41 UTC424 viewsread 8 August 2026

https://t.me/cattoophop там в чате можно найти высеры солевой

2 Aug 2026, 18:41 UTC420 viewsread 8 August 2026
Video

https://t.me/myakichfarforih Если нужен настоящее ФИО этой живодерки и данные, то пишите в лс

2 Aug 2026, 18:34 UTC299 views11 reactionsread 8 August 2026
Forwarded from @sigmacringekPhoto

#артемьева 😊

🤣7😁4

2 Aug 2026, 18:34 UTC320 views8 reactionsread 8 August 2026
Forwarded from @sigmacringekPhoto

#артемьева 📸

😁5🤮2😱1

2 Aug 2026, 18:34 UTC298 views6 reactionsread 8 August 2026
Forwarded from @sigmacringekVideo

#островский #фризов #артемьева легендарный админ кьют_инцелинизма (да, тот самый легенда, который рассказывал на стриме, что лизал хуй отца, чтобы он его ебал без жести) и николай островский (просто педик) ЖЕСТКО про шизанутую вебкам аристократку дарью артемьеву по мнению фимозова - это николай росов отправил артемьеву работать в вебкам кринжик|подписаться

😁6

2 Aug 2026, 18:29 UTC315 views5 reactionsread 8 August 2026

Тот что я не могу достать на Байконурской 26

🤣4😁1

2 Aug 2026, 18:29 UTC359 views4 reactionsread 8 August 2026
Voice message

Voice message, posted without a caption

🤣3😁1

2 Aug 2026, 18:29 UTC326 views4 reactionsread 8 August 2026

Про меф хорошая мысль

🤣3😁1

2 Aug 2026, 18:28 UTC377 views6 reactionsread 8 August 2026

Кому не лень, скиньте в этот чат сообщения Дарьи про убийства котов))) https://t.me/c/2375643544/23967 Нужно пролистать чат канала за сегодня, там Дарья сливает данные https://t.me/cattoophop

😁41👍1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Угрозы Дарьи Артемьевой” (@dashshart1), 372 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/dashshart1.

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.