Telegram RegisterThe public register of Telegram

Channel

Надя не придумала ник🐺

@pttdstr

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

1,074subscribers

+9 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001536590451
TypeChannel
Username@pttdstr
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/pttdstr

Growth

1,0651,0741,069.56 August 2026 — 1,065 subscribers6 August 2026 — 1,065 subscribers9 August 2026 — 1,070 subscribers13 August 2026 — 1,074 subscribers6 August 202613 August 2026
4 measurements spanning 7 days, net +9. 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 1,064–1,075 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 03:441,074+4
9 Aug 2026, 17:431,070+5
6 Aug 2026, 12:371,065no change
6 Aug 2026, 07:031,065first reading

Engagement

12 posts held, back to 19 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
62.6%
avg views ÷ 1,074 subscribers
Avg views / post
672
12 posts measured
Reaction rate
10.7%
reactions ÷ views · ER floor
Posts in window
12
of 12 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 4 August 2026
Posts held12 (19 July 20264 August 2026)
Views total8,068
Reactions total867
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 12:37 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.

Reaction mix

867 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 33.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 528080221187660925829033.4%
custom 591124533867656572222726.2%
custom 541587956040103526015818.2%
🍓9110.5%
custom 52808603829136644189010.4%
custom 5296389691870849433111.27%

Custom emoji. 5 of the rows above are 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 counts beside them areTelegram’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 12 of the 12 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 867reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

4 Aug 2026, 09:35 UTC270 views122 reactionsread 6 August 2026
Photo

Глупые картинкт одна была только в подборке к портфолио дей но захотелось и отдельно выложить

custom 541587956040103526068custom 528080221187660925826custom 591124533867656572220custom 52808603829136644185🍓3

2 Aug 2026, 18:03 UTC350 views70 reactionsread 6 August 2026

ВСЕМ СПАСИБО ЗА ЛУК щас голова ваще не соображает чтоб расписать больше. разваливаюсь как Лего человечк. Еду домой дальше рисовать картинки всем спасибо ещё раз было очень круто🍑

custom 591124533867656572237custom 528080221187660925816custom 528086038291366441811custom 54158795604010352606

2 Aug 2026, 08:40 UTC397 views92 reactionsread 6 August 2026
Photo

Qjeee xedfrbib cbrcctdty fvjyufc cdtu Стол б13. Пожалусто не забудьте про наличку спасибо за внимание 😡

custom 541587956040103526057custom 591124533867656572223custom 52808022118766092588custom 52808603829136644184

1 Aug 2026, 15:41 UTC457 views28 reactionsread 6 August 2026

Напоминаю про этот пост если кто-то кто идёт на лук ещё не видел⤴️

🍓28

31 Jul 2026, 11:50 UTC459 views36 reactionsread 6 August 2026
Forwarded from @maplepunPhoto

с любовью харви #lost_juno

🍓36

28 Jul 2026, 18:34 UTC801 views84 reactionsread 6 August 2026
Photo

🌷 Невероятно... карта мерча на лук лучок в это воскресенье!⭐️Буду за столом Б13🍑 🧡Не забывайте про наличку пожалуйста🌼 Карточки буду менять очень выборочно в приоритете все что указано на картинке Это всее УВИДИМСЯ НА МАРКЕТЕЕ!!УРАА🎉🎸🎤

custom 528080221187660925850custom 528086038291366441816custom 591124533867656572213custom 54158795604010352605

28 Jul 2026, 12:51 UTC≈1,840 views160 reactionsread 6 August 2026
Photo

Подборка картинков

custom 5280802211876609258104custom 528086038291366441828custom 541587956040103526022🍓6

21 Jul 2026, 09:43 UTC768 views56 reactionsread 6 August 2026
Forwarded from @kamazjajaPhoto

– 🎀🎀💜🥹 очень продуктивничаю , вторая атака для @pttdstr 🥹🥹 🦋🎀🥹🥹#арт #oc🥹

custom 528080221187660925836custom 529638969187084943310custom 591124533867656572210

20 Jul 2026, 12:32 UTC798 views45 reactionsread 6 August 2026
Forwarded from @KOSHHARA8k8Photo

Атаки 🥸

custom 591124533867656572236🍓7custom 52808022118766092582

19 Jul 2026, 12:02 UTC741 views51 reactionsread 6 August 2026
Forwarded from @NU61EGPhoto

девятая атака!

custom 591124533867656572233custom 52808603829136644189custom 52808022118766092587🍓1custom 52963896918708494331

19 Jul 2026, 08:22 UTC617 views59 reactionsread 6 August 2026
Forwarded from @dexfaberPhoto

атака для @pttdstr !!! 🪩🤩 пришло время вспомнить про аф

custom 591124533867656572244🍓8custom 52808603829136644185custom 52808022118766092582

19 Jul 2026, 07:20 UTC570 views64 reactionsread 6 August 2026
Forwarded from @HagHahgPhoto

🤩🎸 Атака на @pttdstr

custom 528080221187660925839custom 528086038291366441812custom 591124533867656572211🍓2

Showing the 12 most recent of 12 posts we hold for @pttdstr. 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 — 129,368 of 1,169,250entries 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.

Forward network

Republished by

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

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

Named by 7 registered channels — 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.

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

“Надя не придумала ник🐺” (@pttdstr), 1,074 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/pttdstr.

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.