Telegram RegisterThe public register of Telegram
Telegram profile photo for тот самый чел

Channel

тот самый чел

@adexxart

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

967subscribers

-13 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-1001778835042
TypeChannel
Username@adexxart
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/adexxart

Growth

967980973.57 August 2026 — 980 subscribers8 August 2026 — 980 subscribers15 August 2026 — 973 subscribers22 August 2026 — 967 subscribers7 August 202622 August 2026
4 measurements spanning 15 days, net -13. 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 965–982 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 07:17967-6
15 Aug 2026, 18:56973-7
8 Aug 2026, 00:45980no change
7 Aug 2026, 18:04980first reading

Engagement

17 posts held, back to 8 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
16.3%
avg views ÷ 967 subscribers
Avg views / post
158
2 posts measured
Reaction rate
10.8%
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 (8 June 202627 July 2026)
Views total316
Reactions total34
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 00:45 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

500 reactions across 16 posts, in 21 distinct kinds. The most used accounts for 16.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8216.4%
🔥5310.6%
💯408.00%
💋367.20%
❤‍🔥326.40%
custom 5213093310880557054316.20%
custom 5371012326277258638255.00%
😭255.00%
😁234.60%
224.40%
💔224.40%
😍214.20%
custom 5348300427546859519193.80%
custom 5345992170388070686142.80%
🤝132.60%
🤯132.60%
🖕112.20%
custom 527644871276626671871.40%
🤩61.20%
custom 544507615966869312330.6%
1 further kind20.4%

Custom emoji. 6 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 16 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 500reactions 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 8 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.

Telegram Stars

Stars received
42
across the posts below
Posts paid on
2
of 17 we hold a reading for · 12%
Most on one post
41
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @adexxart. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 17 most recent posts we hold for this entry, published 8 June 2026 to 27 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

27 Jul 2026, 09:11 UTC159 views23 reactions1 Starread 8 August 2026
Photo

смотрите какие анкеты красивые сделал

🔥14🤩531

10 Jul 2026, 07:03 UTC350 views49 reactions41 Starsread 8 August 2026
Photo

вот че сделяль

28❤‍🔥12💋81

7 Jul 2026, 17:55 UTC344 views8 reactionsread 8 August 2026

https://t.me/+Z5alsQq4MMoyYzUy давайте давайте к нам 💐

custom 5348300427546859519411🖕1😍1

2 Jul 2026, 05:11 UTC435 views29 reactionsread 8 August 2026

чета вы реакций пожалели. хотите чтобы я опять на пол года пропал? 💔

💔21😭4🤯21custom 53483004275468595191

1 Jul 2026, 07:30 UTC459 views64 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 521309331088055705431❤‍🔥16custom 534599217038807068614🔥21

26 Jun 2026, 20:24 UTC454 views29 reactionsread 8 August 2026
Photo

Photo, posted without a caption

😭20💋3🤯31❤‍🔥1💔1

26 Jun 2026, 18:20 UTC397 views19 reactionsread 8 August 2026

кажется мы входим в грув все стоят кроме двух

🖕8🤯6💯2🔥21

20 Jun 2026, 18:38 UTC552 views49 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 537101232627725863825💋13custom 5276448712766266718722

11 Jun 2026, 06:50 UTC621 views18 reactionsread 8 August 2026

ого вот это неформат

132🔥2🤩1

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

“тот самый чел” (@adexxart), 967 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/adexxart.

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.