Telegram RegisterThe public register of Telegram
Telegram profile photo for DЫРКА | пирсинг Калининград

Channel

DЫРКА | пирсинг Калининград

@dyrkapiersing

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

563subscribers

+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-1002952623958
TypeChannel
Username@dyrkapiersing
CreatedBetween 1 August 2025 and 31 October 2025— 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/dyrkapiersing

Growth

556563559.56 August 2026 — 556 subscribers6 August 2026 — 556 subscribers7 August 2026 — 558 subscribers13 August 2026 — 563 subscribers6 August 202613 August 2026
4 measurements spanning 7 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 555–564 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 13:08563+5
7 Aug 2026, 01:21558+2
6 Aug 2026, 18:17556no change
6 Aug 2026, 13:08556first reading

Engagement

17 posts held, back to 4 June 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
121.9%
avg views ÷ 563 subscribers
Avg views / post
687
2 posts measured
Reaction rate
5.10%
reactions ÷ views · ER floor
Posts in window
2
of 17 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 27 July 2026
Posts held17 (4 June 202627 July 2026)
Views total1,373
Reactions total70
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 18:17 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

431 reactions across 17 posts, in 3 distinct kinds. The most used accounts for 49.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 544937690799068611721549.9%
18542.9%
custom 5346234281989517393317.19%

Custom emoji. 2 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 17 of the 17 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 431reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

27 Jul 2026, 11:37 UTC548 views42 reactionsread 6 August 2026
Photo

бридж 👶 тыкай для записи

custom 544937690799068611726custom 534623428198951739316

20 Jul 2026, 18:13 UTC825 views28 reactionsread 6 August 2026

🤩🤩🤩🤩 🤩🤩🤩🤩🤩🤩 08.08 16:00 17:00 10.08 13:00 14:00 15:00 12.08 14:00 15:00 17.08 13:30 20.08 14:00 15:00 16:00 22.08 17:00 18:00 24.08 13:00 14:00 15:00 25.08 14:00 15:00 29.08 15:00 🥴 записаться можно, написав нашему админу: @kogtyanka1 календарь добавлю чуть позже!

13custom 534623428198951739310custom 54493769079906861175

14 Jul 2026, 12:46 UTC879 views26 reactionsread 6 August 2026
Photo

дейс тыкай для записи

21custom 54493769079906861173custom 53462342819895173932

8 Jul 2026, 12:32 UTC971 views27 reactionsread 6 August 2026
Photo

язык 🤪 тыкай для записи

12custom 544937690799068611712custom 53462342819895173933

7 Jul 2026, 16:42 UTC776 views24 reactionsread 6 August 2026
Photo

бровь 🤩 тыкай для записи

15custom 54493769079906861179

3 Jul 2026, 15:01 UTC795 views23 reactionsread 6 August 2026
Photo

нострил 🤩 тыкай для записи

custom 54493769079906861171211

30 Jun 2026, 14:52 UTC892 views25 reactionsread 6 August 2026
Photo

лабрет 😉 тыкай для записи

13custom 544937690799068611712

29 Jun 2026, 18:09 UTC837 views25 reactionsread 6 August 2026
Photo

заменили украшение в трагусе, (моя работа) смотрите какая прелесть❤️

custom 54493769079906861171411

29 Jun 2026, 12:18 UTC732 views21 reactionsread 6 August 2026
Photo

язык 😏 тыкай для записи

11custom 544937690799068611710

26 Jun 2026, 17:38 UTC889 views29 reactionsread 6 August 2026
Photo

отпускаю с таким крутым сетом 😊 ранее делали бровь и вертикальный лабрет, сегодня прокололи вторую бровь и септум. в дальнейших планах - создать сет на ушках, но пока думаем о стиле. как думаете, что ей подойдет больше? тыкай для записи

custom 5449376907990686117209

20 Jun 2026, 15:58 UTC936 views23 reactionsread 6 August 2026
Photo

бровь ❤️ тыкай для записи

custom 54493769079906861171310

18 Jun 2026, 15:20 UTC836 views26 reactionsread 6 August 2026
Photo

дейс ❤️

custom 54493769079906861171610

Showing the 12 most recent of 17 posts we hold for @dyrkapiersing. 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 — 387,090 of 1,480,975entries 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 13 August 2026 — this entry's latest reading, not the date you are reading this.

“DЫРКА | пирсинг Калининград” (@dyrkapiersing), 563 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/dyrkapiersing.

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.