Telegram RegisterThe public register of Telegram

Channel

Писюар моль [18+]

@wasolix

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

172subscribers

-1 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003021218169
TypeChannel
Username@wasolix
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/wasolix

Growth

172173172.510 Aug 2026, 05:31 — 173 subscribers10 Aug 2026, 05:45 — 173 subscribers10 Aug 2026, 17:51 — 172 subscribers10 Aug 2026, 05:3110 Aug 2026, 17:51
3 measurements taken within a single day, net -1. 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 172–173 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 17:51172-1
10 Aug 2026, 05:45173no change
10 Aug 2026, 05:31173first reading

Engagement

18 posts held, back to 6 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
119.9%
avg views ÷ 172 subscribers
Avg views / post
206
9 posts measured
Reaction rate
13.4%
reactions ÷ views · ER floor
Posts in window
10
of 18 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 3 August 2026
Posts held18 (6 July 20263 August 2026)
Views total1,856
Reactions total249
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 05: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

412 reactions across 16 posts, in 22 distinct kinds. The most used accounts for 13.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52269612105235397965413.1%
custom 53777480032285220895312.9%
custom 53931373091367270515012.1%
custom 5386388326376812625419.95%
custom 5337187895453193967338.01%
custom 5307898615086200103286.80%
custom 5386572176746885706235.58%
custom 5877321689812963525235.58%
custom 5267106433048009704215.10%
custom 5217713325596514928153.64%
custom 5404696011023081910122.91%
custom 5463315133428170788112.67%
custom 5267289609108218217102.43%
custom 523359977826419520892.18%
custom 538684626437984628592.18%
custom 541158643135101008461.46%
custom 526741009153080741440.971%
30.728%
custom 521517569141428402520.485%
custom 521569958293511592320.485%
2 further kinds30.728%

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

Measured over the 18 most recent posts we hold, published 6 July 2026 to 3 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 16 we hold a reading for · 6%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @wasolix. 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 18 most recent posts we hold for this entry, published 6 July 2026 to 3 August 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

3 Aug 2026, 19:56 UTC79 views12 reactionsread 10 August 2026

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

custom 52671064330480097044custom 52672896091082182173custom 54046960110230819103custom 52674100915308074141custom 53032040311480830421

3 Aug 2026, 19:22 UTC91 views36 reactionsread 10 August 2026
Photo

бош оно что то высрало..

custom 526710643304800970417custom 54046960110230819107custom 53371878954531939676custom 52151756914142840252custom 52156995829351159231custom 52672896091082182171custom 52674100915308074141custom 53032040311480830421

23 Jul 2026, 13:17 UTC198 views22 reactionsread 10 August 2026

помню как планирвоала писать такую аушку по ним, но как то не сложилось. Дзено на вокале это просто превосходство

custom 533718789545319396714custom 52672896091082182173custom 52674100915308074142custom 54046960110230819102custom 52156995829351159231

23 Jul 2026, 13:16 UTC180 views16 reactionsread 10 August 2026
Forwarded from @sayochnostPhoto

Photo, posted without a caption

custom 533718789545319396713custom 52672896091082182173

20 Jul 2026, 12:52 UTC253 views31 reactionsread 10 August 2026
Photo

и ещё две остались потом возвращаюсь к ивенту

custom 538657217674688570618custom 53868462643798462855custom 541158643135101008453

17 Jul 2026, 21:21 UTC246 views21 reactionsread 10 August 2026

спасибо моей подружане за продленку🙏 ещеживем

custom 521771332559651492815custom 53868462643798462854custom 53865721767468857061custom 54115864313510100841

16 Jul 2026, 22:26 UTC276 views59 reactionsread 10 August 2026
Photo

наслаждаемся последними минутами прем реактов потом на бюджет переходим😪 #осторожнопорн

custom 522696121052353979626custom 537774800322852208914custom 53931373091367270518custom 52335997782641952085custom 53863883263768126252custom 54633151334281707882custom 53078986150862001031custom 58773216898129635251

16 Jul 2026, 13:09 UTC257 views18 reactionsread 10 August 2026
Forwarded from @avi0selz

Половину бюджета слили на то чтоб тэтте сказал два слова

custom 538638832637681262513custom 53931373091367270512custom 58773216898129635252custom 53865721767468857061

16 Jul 2026, 11:24 UTC276 views34 reactionsread 10 August 2026

меня оч радует, что в фд ищеек прибавляются столько новых людей, этаа круто

custom 537774800322852208918custom 52269612105235397966custom 53931373091367270516custom 53863883263768126252custom 53078986150862001031custom 53865721767468857061

15 Jul 2026, 15:31 UTC267 views15 reactionsread 10 August 2026

поправила немного первого, а то совсем кривым был.. 🥹🥹

custom 538638832637681262511custom 52269612105235397961custom 52335997782641952081custom 53078986150862001031custom 53865721767468857061

14 Jul 2026, 10:09 UTC261 views21 reactionsread 10 August 2026
Photo

👌

custom 530789861508620010310custom 53777480032285220894custom 53863883263768126253custom 52269612105235397962custom 53865721767468857061custom 53931373091367270511

Showing the 12 most recent of 18 posts we hold for @wasolix. 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,024,643 of 1,345,403entries 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

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 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.

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

“Писюар моль [18+]” (@wasolix), 172 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/wasolix.

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.