Channel
@fu6698
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
147subscribers
+6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002594779440 |
|---|---|
| Type | Channel |
| Username | @fu6698 |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/fu6698 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 15:04 | 147 | +2 |
| 23 Aug 2026, 10:05 | 145 | +5 |
| 15 Aug 2026, 20:43 | 140 | -1 |
| 8 Aug 2026, 22:15 | 141 | no change |
| 7 Aug 2026, 22:47 | 141 | first reading |
9 posts held, back to 2 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 pageof 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. It is computed over the 1 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 9 (2 August 2026 – 8 August 2026) |
| Views total | 239 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 22:15 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 9 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 2 August 2026 to 8 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.
謝謝新客哥哥的信任❤️ 哥哥前一天下午才剛加入小芙， 沒想到聊完之後， 直接就確定今天下午要約， 而且完全相信小芙的推薦，直接安排 情心兩節🥰 第一次接觸就願意把選擇交給我， 這份信任真的很珍貴❤️ 希望今天妹妹的表現，也能讓哥哥覺得這次相信小芙沒有錯～ 📍台中｜清心 160／48／C／20歲 #12000 ✨ 亮麗型 ✨ 妹妹個性乖巧 ✨ 配合度很好 喜歡這種類型的哥哥可以安排喔❤️ 謝謝每一位願意相信小芙推薦的哥哥， 我會盡量按照大家的喜好去幫忙挑選適合的妹妹☺️ 還有別的潛水的哥哥 要來捧場一下嗎~
#新竹 熟客大大今天原本想約熟悉的老點妹妹❤️ 但剛好妹妹今天沒有出來～ 所以小芙就按照哥哥的喜好， 推薦了另一位奶量很有存在感的妹妹😏 沒想到哥哥也是超級相信小芙的眼光， 二話不說直接安排了兩節🔥 熟客就是這樣， 有時候不一定非得指定同一位， 相信我的推薦，反而會有意外的驚喜😉 小芙推薦的，哥哥放心交給我就對了！ 清清 6k 一節 166/53/ D/28歲 不介意有點肉的 大大可以試試看 服務真的很好 顔值也不錯 身上還香香的
熟客+1 #北部正妹~ #15k 有興趣的可以私密我~ https://t.me/tw77d38 身高：165 體重：53 罩杯：大E真奶！！！ 年齡：23 服務過程： 一進門就先來個甜甜的擁抱，抱抱時還不忘挑逗一下弟弟，繳了水錢後，就一起去洗澡，洗澡時就開始猛烈的吹奏樂器，不得不說這口技真的一流，到了床上一樣繼續吹奏，不過我也沒閒着，肯定是要讓妹妹知道什麽叫狗喝水，妹妹走一陣演奏後，主動騎了上來，沒想到妹妹騎術也是很頂，整個過程中，妹妹給人的情緒價值很高，高潮不像是裝的，服務真的超滿意，一定會回沖！！
有時候也會停下來想一想。 今天的我，真的有做到最好了嗎？ 或許還不夠完美， 但回頭看看一路走來的自己， 好像一直都在慢慢成長。 每天進步一點點， 比昨天更好一點點， 這樣就很好了。
❤1
感恩大大捧場 #涵涵 中間還加節了 很幸運妹妹後面沒有安排 身高：164 體重:48 罩杯：D 年紀：24 進門給了錢妹妹就拉着我去洗澡，中間妹妹很熱情主動，一直引導我，妹妹確實很敏感，我才碰到下面就流了好多水，其實我不太會寫，總之就是經驗還不錯。
被認可是一種幸福 被信任是一份責任 感謝新朋友捧場~ #喜歡這種類型的大大 真的可以把握一下 ✨
新客戶麻煩回答一下幾個問題喔 小芙比較瞭解你的喜好 按你需求合理安排 1.喜歡什麽類型的女孩 一定要詳細｛如身高 體重 年齡 大小奶 要求｝ 2.希望價位在什麽範圍內 3.想找什麽職業女孩 4.具體什麽時間需要 5.旅館希望那間哪區｛或請我推薦也可｝ 6.按照約定的時間準時 開好旅館 提供房號給我 7.在旅館房間等待女孩 並交代訪客XX朋友會來訪 8.見到小姐滿意後 付現金 付款後開始計時 {營造氣氛進入正題 ｝ 9.結束離開 提供心得客評 ｛整個流程結束｝ 我會你的需求 按照班表推薦符合你預期的妹妹 避免踩雷 小芙台灣外送兼職小姐區域 【台北】 大同、大安、士林、中山、中正、內湖、文山、北投、松山、信義、南港、萬華 【新北】 三重、土城、汐止、新莊、板橋、永和、蘆洲、中和、五股、泰山、新店、 {八里、林口、龜山、淡水+200車資） 【新竹】 新竹市區 ｛ 東區 北區 香山 竹北｝ 【台中】 西區、北…
這個哥哥找別人安排 開好房間 但是卻沒有妹妹可以 我可以理解這種的心情。 畢竟房間都開好了，結果最後沒有妹妹過去，換作誰都會覺得尷尬、不舒服。 但是也希望哥哥明白，這件事情並不是小芙叫你先去開房間，也不是小芙安排你做這個決定，所以希望不要把情緒發洩在我身上。 凌晨一點過後如果想約妹妹，建議哥哥最好提前預約。有讓我介紹的哥哥 都知道 我會特別說明 第一，可以先確認好妹妹的時間，避免臨時找不到合適的人選； 第二，也能確保當天真的有妹妹可以安排，不會發生房間開好了，卻沒有人過去的尷尬情況。 大家都希望過程順順利利，也希望哥哥可以理解一下安排上的限制。
哥哥今天超開心的 約到想約超久的嫩妹 小玥 ❤️ 其實有時候一節、兩節的時間真的不太夠，畢竟跟妹妹也是第一次見面，需要一點時間去熟悉彼此的節奏和感覺。 約長時間不只是相處更放鬆，也能有更多互動和交流，慢慢發現彼此適合的方式，體驗到不一樣的感覺。
Showing the 9 most recent of 9 posts we hold for @fu6698. 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 — 402,679 of 1,628,927entries 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.
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.
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.
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.
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.
“哥哥的真實體驗” (@fu6698), 147 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/fu6698.
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.