Telegram RegisterThe public register of Telegram
Telegram profile photo for не люблю звонить да что ты говоришь

Channel

не люблю звонить да что ты говоришь

@dawsfoushduiofsdf

2 usernames

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

694subscribers

-7 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003661748504
TypeChannel
Usernames@curved @dawsfoushduiofsdf
CreatedBetween 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/dawsfoushduiofsdf

Growth

694701697.56 August 2026 — 701 subscribers7 August 2026 — 701 subscribers14 August 2026 — 694 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net -7. 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 693–702 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 11:29694-7
7 Aug 2026, 01:55701no change
6 Aug 2026, 22:15701first reading

Engagement

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

ERR · 30 days
67.6%
avg views ÷ 694 subscribers
Avg views / post
469
15 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
15
of 15 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 5 August 2026
Posts held15 (30 July 20265 August 2026)
Views total7,039
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 22:15 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.

Recent posts

5 Aug 2026, 21:37 UTC394 viewsread 6 August 2026

дорогме друзья. сегодня 67 день лета

Signed ignorant

31 Jul 2026, 23:04 UTC543 viewsread 6 August 2026

за 5 часов до вылета переносят на 5 часов ПОЗЖЕ

Signed ignorant

31 Jul 2026, 23:04 UTC521 viewsread 6 August 2026

за месяц до полета переносят вылет на 1.5 часа РАНЬШЕ

Signed ignorant

31 Jul 2026, 23:03 UTC467 viewsread 6 August 2026

бля авиакомпания победа желаю вам успехов нахуй

Signed ignorant

31 Jul 2026, 02:42 UTC495 viewsread 6 August 2026

мне кажется это действительно стало невозможно он хуярит просто как демон какой то и ничего вообще не сьедает из лимитов ну вообще ничего

Signed ignorant

31 Jul 2026, 02:42 UTC482 viewsread 6 August 2026

чет я ваще нихуя не понимаю а как на opus 5 вообще сьедать недельные лимиты на max 20x

Signed ignorant

31 Jul 2026, 00:29 UTC479 viewsread 6 August 2026
Photo

в любом случае я щас с таким кайфом нарушал правила дорожного движения ох бляяя

Signed ignorant

31 Jul 2026, 00:28 UTC414 viewsread 6 August 2026

с одной стороны дохуя с другой — это всего 9 scared cat похуй

Signed ignorant

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

Citation-graph rank

Citation-graph rank — 1,298,163 of 1,480,944entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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

“не люблю звонить да что ты говоришь” (@dawsfoushduiofsdf), 694 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dawsfoushduiofsdf.

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.