10 measurements spanning 22 days, net -499. 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 6,099โ6,924 and does not start at zero.
Measurement log โ every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
30 Aug 2026, 06:08
6,194
-107
27 Aug 2026, 02:02
6,301
-125
24 Aug 2026, 02:28
6,426
-122
20 Aug 2026, 02:03
6,548
-104
17 Aug 2026, 09:33
6,652
-18
13 Aug 2026, 15:26
6,670
-159
10 Aug 2026, 23:56
6,829
+184
8 Aug 2026, 10:18
6,645
-48
7 Aug 2026, 19:47
6,693
no change
7 Aug 2026, 19:38
6,693
first reading
Engagement
24 posts held, back to 15 April 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 8 pagesof Telegramโs post history, 20 posts per page.
ERR ยท 30 days
10.1%
avg views รท 6,194 subscribers
Avg views / post
623
13 posts measured
Reaction rate
2.50%
reactions รท views ยท ER floor
Posts in window
13
of 24 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
Window
Rolling 30 days ยท latest post in window 11 August 2026
Posts held
24 (15 April 2026 โ 11 August 2026)
Views total
8,096
Reactions total
202
Forwards / comments
not exposed by the public surface โ not measured, not estimated
Readings taken
12 Aug 2026, 02:44 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
291 reactions across 24 posts, in 13 distinct kinds. The most used accounts for 17.9% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
โค
52
17.9%
๐
49
16.8%
๐ฅฐ
37
12.7%
๐
33
11.3%
๐
26
8.93%
โคโ๐ฅ
16
5.50%
๐
16
5.50%
๐
14
4.81%
๐ฏ
14
4.81%
๐
12
4.12%
โก
11
3.78%
๐
10
3.44%
๐คทโโ
1
0.344%
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 24 of the 24 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 291reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 24 most recent posts we hold, published 15 April 2026 to 11 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.
Showing the 12 most recent of 24 posts we hold for @ENDUONLINEPROVEJOB. 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.
Posts edited after publishing
@ENDUONLINEPROVEJOB edited 1 post after it first published โ the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too โ this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
8 August 2026
Most recent edit
8 August 2026
Mentions
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channelโs posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@ENDUONLINEPROVEJOB named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleโs history โ see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today โ not that anything โdiedโ. How this is measured.
Never seen alive
References a handle that is not a live channel โ we have no record it ever was one.
@virtuix_iris named in 5 posts, 8 August 2026 โ 9 August 2026
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 30 August 2026 โ this
entry's latest reading, not the date you are reading this.
โETHIO ONLINE BUSINESS ๐ซต๐ซตโ (@ENDUONLINEPROVEJOB), 6,194 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/ENDUONLINEPROVEJOB.
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.
