Channel
@MUTUALIN
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
16,364subscribers
+1,841 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003657438923 |
|---|---|
| Type | Channel |
| Username | @MUTUALIN |
| Description | For everyone to connect with each other. This base is using auto menfess system. Trigger: 👤 for every menfess. Autobot menfess: @MUTUMFBOT. Call center: @.MUTUCENTERBOT. Paid Promote: @ZonePaid. Rant all base: @txtdaribase. est. 06 February 2026 |
| Created | Between 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/MUTUALIN |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 08:54 | 16,364 | +59 |
| 27 Aug 2026, 05:22 | 16,305 | +50 |
| 26 Aug 2026, 04:13 | 16,255 | +79 |
| 25 Aug 2026, 05:13 | 16,176 | +49 |
| 24 Aug 2026, 00:56 | 16,127 | +109 |
| 22 Aug 2026, 08:57 | 16,018 | +85 |
| 20 Aug 2026, 22:43 | 15,933 | +57 |
| 20 Aug 2026, 01:32 | 15,876 | +78 |
| 18 Aug 2026, 22:24 | 15,798 | +60 |
| 17 Aug 2026, 19:56 | 15,738 | +67 |
| 16 Aug 2026, 19:17 | 15,671 | +139 |
| 15 Aug 2026, 07:02 | 15,532 | +100 |
| 14 Aug 2026, 01:28 | 15,432 | +62 |
| 12 Aug 2026, 19:13 | 15,370 | +83 |
| 11 Aug 2026, 18:48 | 15,287 | +142 |
| 10 Aug 2026, 16:15 | 15,145 | +117 |
| 9 Aug 2026, 18:42 | 15,028 | +231 |
| 8 Aug 2026, 21:38 | 14,797 | +200 |
| 7 Aug 2026, 23:32 | 14,597 | +74 |
| 7 Aug 2026, 01:59 | 14,523 | first reading |
880 posts held, back to 6 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 44 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 880 (6 August 2026 – 28 August 2026) |
| Views total | 69,458 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 14:29 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.
Lifetime counters from Telegram’s own channel header, read 28 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
👤 This Male (18) Kindly looking for lovers mole ingame/out game. Bisa sekalian FWA, sender user jung, lagi sering main push rank. Kita bisa sambil dc/call, bisa main roblox bareng juga atau nobar some movies, im into k drama lately. If you are talk active and clingy got free pass
👤 f16, be friend me please ;_____)
👤 mutualan ig yuk, main acc & pp rl only
👤 f17 (08L) looking for fwa, i love sending vns, calling, playing games together! we can also match pfp if u want :] any gender allowed btww!
👤 m21 chit-chat clingy, sayang-sayangan sini, open bxg aja ya
👤mutualan ba yuk? punya sender pf
👤 hi baru main X, ada yang mau mutual x sama sender? sender bakal like like postingan kalian
👤 Hi, This M (19) Kindly looking for FWA, im really craving for affection lately. So im looking for clingy girl who loves to teasing me :p, Anyway i play some games too, kind of roblox and mole, kita bisa main bareng sambil call. And i love watching movies and k drama, we can watch it tgt!
👤 let's exchange telegram contacts w this she/her? my account type is personal. r/kp acc & lgbt phobic, dnfi.
👤 f20 call until sleep? clingy but dom get a pass
👤 f18, looking for fwa slow-burn ada tah?.. sender baca manhwa, nonton anime, suka dengerin lagu. type of person yang bisa jadi the yapper sekaligus the listener. sender orangnya santai juga kok
👤 let's exchange telegram contacts w this she/her? my account type is personal. r/kp acc & lgbt phobic, dnfi.
Showing the 12 most recent of 880 posts we hold for @MUTUALIN. 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 — 682,616 of 1,623,166entries 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.
Named by 5 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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“MUTUALIN READ PIN 👤!” (@MUTUALIN), 16,364 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/MUTUALIN.
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.