Telegram RegisterThe public register of Telegram

Channel

[ПЕРЕЕЗД] данжер в деле

@Evaartes23

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

335subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002959864616
TypeChannel
Username@Evaartes23
DescriptionПЕРЕЕЗД: https://t.me/Evaartes232 здравствуйте, рисую скетчи + щп + жизнь 😧 занимаюсь фигней, оууу ес лор персов: https://t.me/+dXhPcjInyaxlYmU6 владелец > @quretymoon
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 August 2026
Measurements held2
On Telegramt.me/Evaartes23

Growth

3359 Aug 2026, 10:53 — 335 subscribers9 Aug 2026, 11:00 — 335 subscribers9 Aug 2026, 10:539 Aug 2026, 11:00
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 334–336 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 11:00335no change
9 Aug 2026, 10:53335first reading

Engagement

20 posts held, back to 20 February 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
14.0%
avg views ÷ 335 subscribers
Avg views / post
47.0
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 18 July 2026
Posts held20 (20 February 202618 July 2026)
Views total47
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 11:00 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.

What this channel posts

Photos
558
Videos
39
Links
26

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

Reaction mix

17 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 52.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
952.9%
😍317.6%
😱211.8%
custom 541589546466492930815.88%
💋15.88%
💔15.88%

Custom emoji. One 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 count beside it isTelegram’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 7 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 17reactions 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 February 2026 to 18 July 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

18 Jul 2026, 11:57 UTC47 viewsread 9 August 2026

все перешли на новый тгк?

Signed wordle1s | 03:03 | 🫪 [𝘞𝘌𝘙𝘠] #coilshot

16 Apr 2026, 16:29 UTC122 viewsread 9 August 2026

переходим

Signed 𝘞𝘖𝘙𝘋𝘓𝘌1𝘚 [𝘞𝘌𝘙𝘠] 🫪

16 Apr 2026, 16:29 UTC122 viewsread 9 August 2026
Forwarded from @Evaartes232Photo

🔤🔤🔤🔤🔤 🔤 🔤🔤🔤➖ 🔤🔤🔤 🤩: здравствуйте... это я с любимым 🌟🌟🌟🌟 🤩🤩 ребзи, я занимаюсь сейчас стикерами и в общем... эти ребята тоже в стикерах, ура ура смотрите какие милые 🤩🤩🤩🤩 ➿➿➿➿➿ #арт #стикеры #мэй #данжа 🤩 #ева@Evaartes232

Signed 𝘞𝘖𝘙𝘋𝘓𝘌1𝘚 [𝘞𝘌𝘙𝘠] 🫪

28 Mar 2026, 16:03 UTC94 viewsread 9 August 2026

переходим на этот тгк

Signed 𝘞𝘖𝘙𝘋𝘓𝘌1𝘚 [𝘞𝘌𝘙𝘠] 🫪

28 Mar 2026, 16:03 UTC134 viewsread 9 August 2026
Forwarded from @Evaartes232Photo

😊verything should be done mutually 🤩 да, я понимаю что выглядит лениво, я опять спешила.. хахаха, ради мэя только 🤩 🌟🌟🌟🌟 смотрите на это, у вас выбора не остаётся походу... ну почему бы и нет. кстати, поцелуи оставлены его яркой звездочкой 🤩 доп: я не знаю, можно ли сравнивать данжу и мэя как пару, время все покажет ➿➿➿➿ #арт #мэй 🤩 #ева@Evaartes232

Signed 𝘞𝘖𝘙𝘋𝘓𝘌1𝘚 [𝘞𝘌𝘙𝘠] 🫪

22 Mar 2026, 18:51 UTC103 views6 reactionsread 9 August 2026
Forwarded from @Evaartes232Photo

ну.. это вместо завтра, да и вообще, без негатива снова глаза данжи краснеют. хочу так же( 🌟🌟🌟🌟 как сказать человеку, что ну щас очень плохо, а он говорит тебе, что ты выдумываешь? помогите еще и тревожность эта достала, бе #скетч (?) #мем #данжа 🤩 #ева@Evaartes232

5custom 54158954646649293081

Signed wordle1s [WERY]

27 Feb 2026, 12:49 UTC111 viewsread 9 August 2026

переходим

Signed wordle1s #ваня #мэй🍇 𓆝 𓆟

27 Feb 2026, 12:49 UTC126 views3 reactionsread 9 August 2026
Forwarded from @Evaartes232Photo

не подумайте я исправляю ошибки своей молодости (добавляю мэю поцелуйчеке) 🌟🌟🌟🌟 да, я буду мусолить эту полноценку до остановки сердца ❓ #поцелуйчики #доработка #данжа 🤩 #мэймэй 🤩 #ева@Evaartes232

😍3

Signed wordle1s #ваня #мэй🍇 𓆝 𓆟

23 Feb 2026, 16:07 UTC129 viewsread 9 August 2026

это канал, в котором мы чиллим переходим

Signed wordle1s #ваня #черчи🇺🇸 𓆝 𓆟

23 Feb 2026, 16:07 UTC129 views1 reactionsread 9 August 2026
Forwarded from @Evaartes232

как мне добить ваще сотку на тгк, если кто то обязательно отпишется 😭😭😭 хелп ми пожалуйст #щп

💔1

Signed wordle1s #ваня #черчи🇺🇸 𓆝 𓆟

23 Feb 2026, 12:14 UTC122 viewsread 9 August 2026

переходим

Signed wordle1s #ваня #черчи🇺🇸 𓆝 𓆟

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

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

“[ПЕРЕЕЗД] данжер в деле” (@Evaartes23), 335 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/Evaartes23.

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.