Telegram RegisterThe public register of Telegram
Telegram profile photo for 🇹🇼台灣北中南叫小姐洛洛外送過茶

Channel

🇹🇼台灣北中南叫小姐洛洛外送過茶

@fb22385

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2,762subscribers

-13 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002054598399
TypeChannel
Username@fb22385
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live22 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/fb22385

Growth

2,7612,7752,7687 August 2026 — 2,775 subscribers7 August 2026 — 2,775 subscribers10 August 2026 — 2,769 subscribers13 August 2026 — 2,767 subscribers16 August 2026 — 2,762 subscribers19 August 2026 — 2,761 subscribers22 August 2026 — 2,762 subscribers2,7627 August 202622 August 2026
7 measurements spanning 15 days, net -13. 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 2,759–2,777 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 10:252,762+1
19 Aug 2026, 08:452,761-1
16 Aug 2026, 17:562,762-5
13 Aug 2026, 11:382,767-2
10 Aug 2026, 21:512,769-6
7 Aug 2026, 21:202,775no change
7 Aug 2026, 16:182,775first reading

Engagement

13 posts held, back to 6 August 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
3.39%
avg views ÷ 2,762 subscribers
Avg views / post
93.5
13 posts measured
Reaction rate
1.22%
reactions ÷ views · ER floor
Posts in window
13
of 13 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. It is computed over the 1 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held13 (6 August 20267 August 2026)
Views total1,216
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:18 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.

What this channel posts

Video runtime
1m 01s
Average length
20s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥1100.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 13 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 13 most recent posts we hold, published 6 August 2026 to 7 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.

Recent posts

7 Aug 2026, 09:45 UTC63 viewsread 7 August 2026
Video

#按摩師的 #第一視角

Signed 洛洛主動密我【送福利】

7 Aug 2026, 06:18 UTC88 viewsread 7 August 2026
Photo

午安呀 洛洛在等你喲

Signed 洛洛主動密我【送福利】

7 Aug 2026, 06:16 UTC82 views1 reactionsread 7 August 2026
Video

有哥哥一起來共浴的嗎?

❤‍🔥1

Signed 洛洛主動密我【送福利】

7 Aug 2026, 06:15 UTC74 viewsread 7 August 2026
Photo

木心 158cm.C奶.44kg.19歲 超幼齒小狗自帶輕微M,性經驗不多,技術不熟練想要被哥哥調教,喜歡溫柔會引導的哥哥,叫床很浪,粉嫩的小穴水超多 🎀洛洛Gleezy:nos9925 🎀洛洛TG: @fb22381 🎀洛洛LINE :nos9925 📲(Gleezy群組加入鏈接下載) https://c.gleezy.top/luo1 🌸全台外送 🌸北部專區 🌸特價專區 🌸中部專區 🌸大奶巨乳 🌸南部專區 🌸清純學生妹 🌸素人無碼A片 #外送茶 #找小姐 #約炮 #高中生 #清純學生 #爆乳 #正妹短兼 #人妻 #空姐 #台中東海校花 #模特 #貧乳妹

Signed 洛洛主動密我【送福利】

7 Aug 2026, 06:15 UTC68 viewsread 7 August 2026
Photo

糖心 157cm/Ccup/44kg/19歲 超可愛的妹妹.臉蛋可愛 個性可愛 很健談喔~ 聲音也超級可愛 身材嬌小 可親 喇舌看感覺 很有女友FU! 🎀洛洛Gleezy:nos9925 🎀洛洛TG: @fb22381 🎀洛洛LINE :nos9925 📲(Gleezy群組加入鏈接下載) https://c.gleezy.top/luo1 🌸全台外送 🌸北部專區 🌸特價專區 🌸中部專區 🌸大奶巨乳 🌸南部專區 🌸清純學生妹 🌸素人無碼A片 #外送茶 #找小姐 #約炮 #高中生 #清純學生 #爆乳 #正妹短兼 #人妻 #空姐 #台中東海校花 #模特 #貧乳妹

Signed 洛洛主動密我【送福利】

7 Aug 2026, 06:15 UTC66 viewsread 7 August 2026
Photo

小小 158cm.B奶.44kg.19歲 萌妹子來襲!好可愛的妹妹,身體小小隻 抱起來剛剛好,妹妹超體貼 滿足到尖叫 輕吻?可以有!配合度超高 🎀洛洛Gleezy:nos9925 🎀洛洛TG: @fb22381 🎀洛洛LINE :nos9925 📲(Gleezy群組加入鏈接下載) https://c.gleezy.top/luo1 🌸全台外送 🌸北部專區 🌸特價專區 🌸中部專區 🌸大奶巨乳 🌸南部專區 🌸清純學生妹 🌸素人無碼A片 #外送茶 #找小姐 #約炮 #高中生 #清純學生 #爆乳 #正妹短兼 #人妻 #空姐 #台中東海校花 #模特 #貧乳妹

Signed 洛洛主動密我【送福利】

6 Aug 2026, 08:26 UTC226 viewsread 7 August 2026
Photo

洛洛茶坊 月初福利推薦 約妹領取~ 1.升級vip(住家 3p 外約 一年7折優惠 免車資 vip小姐 送絲襪 ) 2.六折優惠卡一張(一年期限) 3.永久買二送一送 4.三次高檔尤物妹半價約 5.免費6K內妹試車一次【限名額】 6.低價處女一枚-有處女報班會通知 7.永久買二送二送 8.一年開房免費送 9.永久免費車資送

Signed 洛洛主動密我【送福利】

6 Aug 2026, 07:54 UTC113 viewsread 7 August 2026
Video

喜歡嗎 清新😍😍😍😍

Signed 洛洛主動密我【送福利】

6 Aug 2026, 07:48 UTC90 viewsread 7 August 2026
Video

#這樣的薯條 #我也想要有😊😊

Signed 洛洛主動密我【送福利】

6 Aug 2026, 05:36 UTC94 viewsread 7 August 2026
Photo

欣欣 150cm/38kg/Bcup/19歲 年輕幼齒可愛又活潑的個性 外表看起來清純 貧乳控 🎀洛洛Gleezy:nos9925 🎀洛洛TG: @fb22381 🎀洛洛LINE :nos9925 📲(Gleezy群組加入鏈接下載) https://c.gleezy.top/luo1 🌸全台外送 🌸北部專區 🌸特價專區 🌸中部專區 🌸大奶巨乳 🌸南部專區 🌸清純學生妹 🌸素人無碼A片 #外送茶 #找小姐 #約炮 #高中生 #清純學生 #爆乳 #正妹短兼 #人妻 #空姐 #台中東海校花 #模特 #貧乳妹

Signed 洛洛主動密我【送福利】

6 Aug 2026, 05:35 UTC79 viewsread 7 August 2026
Photo

詩詩 156cm.Ccup.44kg.22歲 自己偷偷下海兼職外快 清純鄰家小女孩 性格溫柔腼腆 長相甜美 聲音好聽 下面還是粉粉嫩嫩的水超多 胸部很好看 非常敏感 一不小心就濕透透 🎀洛洛Gleezy:nos9925 🎀洛洛TG: @fb22381 🎀洛洛LINE :nos9925 📲(Gleezy群組加入鏈接下載) https://c.gleezy.top/luo1 🌸全台外送 🌸北部專區 🌸特價專區 🌸中部專區 🌸大奶巨乳 🌸南部專區 🌸清純學生妹 🌸素人無碼A片 #外送茶 #找小姐 #約炮 #高中生 #清純學生 #爆乳 #正妹短兼 #人妻 #空姐 #台中東海校花 #模特 #貧乳妹

Signed 洛洛主動密我【送福利】

6 Aug 2026, 05:34 UTC76 viewsread 7 August 2026
Photo

琳琳 167cm.Ecup.50kg.29歲 #騷欠幹型 最愛深入抽插 頂到底的感覺 狗喝水是每次必玩的 #喜歡帶一點點劇情性的做 比如說在窗戶上 洗手台上 桌子上 🎀洛洛Gleezy:nos9925 🎀洛洛TG: @fb22381 🎀洛洛LINE :nos9925 📲(Gleezy群組加入鏈接下載) https://c.gleezy.top/luo1 🌸全台外送 🌸北部專區 🌸特價專區 🌸中部專區 🌸大奶巨乳 🌸南部專區 🌸清純學生妹 🌸素人無碼A片 #外送茶 #找小姐 #約炮 #高中生 #清純學生 #爆乳 #正妹短兼 #人妻 #空姐 #台中東海校花 #模特 #貧乳妹

Signed 洛洛主動密我【送福利】

Showing the 12 most recent of 13 posts we hold for @fb22385. 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 — 32,364 of 1,584,420entries 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 7 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.

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

“🇹🇼台灣北中南叫小姐洛洛外送過茶” (@fb22385), 2,762 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/fb22385.

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.