4 measurements spanning 11 days, net +43. 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 880–935 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Sept 2026, 22:38
929
+1
7 Sept 2026, 07:55
928
+42
4 Sept 2026, 14:22
886
no change
4 Sept 2026, 13:47
886
first reading
Engagement
15 posts held, back to 31 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
ERR · 30 days
32.9%
avg views ÷ 929 subscribers
Avg views / post
306
15 posts measured
Reaction rate
3.40%
reactions ÷ views · ER floor
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. It is computed over the 14 of 15 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 4 September 2026
Posts held
15 (31 August 2026 – 4 September 2026)
Views total
4,585
Reactions total
144
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
4 Sept 2026, 14:22 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
Video runtime
1m 01s
Average length
20s
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
144 reactions across 14 posts, in 15 distinct kinds. The most used accounts for 15.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5260560413262621114
22
15.3%
custom 5407125098496809118
20
13.9%
custom 5300911966016010769
19
13.2%
custom 5420141555233071341
17
11.8%
custom 5235513242029139973
16
11.1%
custom 5246870183531790585
14
9.72%
custom 5195371378169108755
8
5.56%
custom 5427398207422346049
7
4.86%
custom 4967901363188009218
6
4.17%
custom 5260342465147185850
5
3.47%
custom 5264965984556450056
3
2.08%
custom 5307973403351751812
3
2.08%
custom 5264926591116413552
2
1.39%
custom 5262456422280493913
1
0.694%
custom 5264767222059924419
1
0.694%
Custom emoji. Every 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 counts beside them are Telegram’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 14 of the 15 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 144 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 31 August 2026 to 4 September 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.
друзья, я создала отдельный канал куда буду постить подборки аватарок, баннеров, обоев на телефон и тд.
какие то буду искать (в основном), какие то сама создавать через нейронки. я ежедневно нахожу очень много картинок, но не все удается вписать в профили, поэтому буду для вас их постить. свои запросы на картинки можете оставлять в канале просто в комментариях, постараюсь искать или делать.
не всегда удается часто п…
до 20 лет вообще не пила, потом немного начала
в этом году много выпивала какое то время потому что была не в себе, но я себя за это вообще не виню, планирую как и раньше вообще не пить, меня как не тянуло на алкоголь так и не тянет до сих пор, я все еще не понимаю как люди пьют эту отвратительную хуйню в течение всей жизни.
в этом году еще пыталась траить даже всякие коктейли в ресторанах, думала может мое мнение об…
ето роутер пришел, в субботу придут делать инет и я надеюсь наконец то смогу нормально поиграть!!!!
самое смешное что со дня заявки новому провайдеру мой интернет уже как дня 4 работает без перебоев
Showing the 12 most recent of 15 posts we hold for @tessuxluv. 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.
Mentions
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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 15 September 2026 — this
entry's latest reading, not the date you are reading this.
“tessuxluv” (@tessuxluv), 929 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/tessuxluv.
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.
