Telegram RegisterThe public register of Telegram
Telegram profile photo for Fees share detail

Channel

Fees share detail

@fees_share

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

1,425subscribers

+7 since we began measuring on 8 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002882301844
TypeChannel
Username@fees_share
Created17 September 2025 — measured — dated from the channel’s first post
First recorded8 September 2026
Last confirmed live19 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/fees_share

Growth

1,4181,4271,422.58 September 2026 — 1,418 subscribers8 September 2026 — 1,418 subscribers10 September 2026 — 1,424 subscribers14 September 2026 — 1,427 subscribers19 September 2026 — 1,425 subscribers1,4258 September 202619 September 2026
5 measurements spanning 11 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 1,417–1,428 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 08:211,425-2
14 Sept 2026, 16:571,427+3
10 Sept 2026, 19:381,424+6
8 Sept 2026, 06:221,418no change
8 Sept 2026, 05:471,418first reading

Engagement

8 posts held, back to 17 September 2025 — 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
24.2%
avg views ÷ 1,425 subscribers
Avg views / post
345
7 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
7
of 8 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 2 September 2026
Posts held8 (17 September 2025 – 2 September 2026)
Views total2,416
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Sept 2026, 06: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.

Recent posts

2 Sept 2026, 10:39 UTC342 viewsread 8 September 2026

🇷🇺https://sciencesquad-iota.vercel.app 🔴Site එකේ register වන ආකාරය https://youtu.be/S5gb8fQr-kA?si=mKhBcQ4MzwRr9BA5 👀 🔴Payment සිදු කරන ආකාරය https://youtu.be/ntSr0sMLtsA?si=GxpfTm0vHVlygLAW 👀 🔴Classes recoding බලන ආකාරය https://youtu.be/l1o8Q_gS05k?si=10t_S473O-yFehDQ 👀

2 Sept 2026, 10:39 UTC340 viewsread 8 September 2026
Photo

🔴Classes live බලන ආකාරය (class එකක් live යන විට dashboard එකේ අදාල class එකට ගියාම උඩින්ම පේන join button එකෙන් live class එකට join විය හැක.

2 Sept 2026, 10:39 UTC362 viewsread 8 September 2026

✅Special package 🔔 ඉහත සඳහන් ඕනෑම class 03කට සම්බන්ද වීමට අවශ්‍ය අයට 1000/= කට class 03 සඳහාම සම්බන්ද විය හැක. 🔴Example👇 ✔️රුවන් දර්ශන Theory+Revision+paper 500/= ✔️නිලන්ත ජයසූරිය Theory+Revision+Paper 500/= ✔️උජිත් හේමචන්ද්‍ර Theory +Revision+paper 500/= මේ class 03ටම සම්බන්ද වීමට අවශ්‍ය අයට ඒ සඳහා 1500/= ක් නොව 1000/= කට ඒ සියල්ලටම add විය හැක. Fees share කරන් යන්න ඕනෙ අය 👉 @Sci_squad_owner කතා කරන්න.

2 Sept 2026, 10:39 UTC342 viewsread 8 September 2026

ඔයාලට සියලුම classes live,recoding සියල්ල බලන්න සහ අවශය classes වලට payment කරන්න පහත site එකෙන් පුලුවන්. 🇷🇺https://sciencesquad-iota.vercel.app සෑම විටම එක device එකක එකම browser එකෙන් පමනක් site එකට log වෙන්න. අවශ්‍යනම් පහත App ඔයා classes බලන device එකට install කරගෙන App එක හරහාද class බලන්න payment කරන්න පුලුවන්. 🔴මේ app එකෙන් ගිහින් video බැලුවත් Site එකෙන් ගිහින් video බැලුවත් ඔයාලට data කැපෙන්නෙ youtube pa…

2 Sept 2026, 10:39 UTC342 viewsread 8 September 2026

➖➖➖➖➖➖➖➖➖ 🅰️🅰️🅰️🅰️ 🅰️🅰️🅰️🅰️🅰️ ➖➖➖➖➖➖➖➖➖ 🔴🤣😉🤣🙃 A/L කරන ඔයාලට දැන් පහත සර්ලගෙ පන්ති ෆීස් බෙදාගෙන යන්න සම්බන්ද වෙන්න පුලුවන් ━━━━ Combine maths ━━━━━ 🔹මනෝජ් සෝලංගආරච්චි 🔹රුවන් දර්ශන 🔹මදුෂාන් නෙරන්ජන් ━━━━ Biology ━━━━━ 🔸සශංක ධනුජය 🔸දිනේශ් මුතුගල 🔸ධනංජය ආරියදාස 🔸පවර ජයසිංහ ━━━━ Physics ━━━━━ 🔹නිලන්ත ජයසූරිය 🔹සමිත රත්නායක 🔹දර්ශන උකුවෙල 🔹මහේන් ජේකබ් ━━━━ Chemistry ━━━━━ 🔶චරිත දිසානායක 🔶නිපුන් මද්දුමගේ 🔶උජිත් හේමචන්ද්…

Showing the 8 most recent of 8 posts we hold for @fees_share. 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.

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.

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

“Fees share detail” (@fees_share), 1,425 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/fees_share.

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.