Channel
@fulijibaobaoo
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
822subscribers
-13 since we began measuring on 9 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004474669566 |
|---|---|
| Type | Channel |
| Username | @fulijibaobaoo |
| Created | Between 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 30 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 30 September 2026 |
| On Telegram | t.me/fulijibaobaoo |
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 30 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Sept 2026, 06:37 | 822 | -14 |
| 12 Sept 2026, 04:18 | 836 | +1 |
| 10 Sept 2026, 00:22 | 835 | no change |
| 9 Sept 2026, 23:47 | 835 | first reading |
5 posts held, back to 9 September 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 page of 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 9 September 2026 |
|---|---|
| Posts held | 5 (9 September 2026 – 9 September 2026) |
| Views total | 50 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Sept 2026, 00: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.
Measured directly from 4 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.
🚀加入极搜互推一起赚钱🚀 车队：博彩专用2 2.42k 欧美|欧美剧情|欧美萝莉|欧美三级 136 အန်တီမမအကိတ်ကြီး 2.82k 微信号·抖音号·国内外账号·手机卡【老纪】 104 花呗白条公积金医保高炮 1.4k 能量闪兑+飞机号/会员+推特号 151 南宫集团 NG 非凡 星耀 君临 汇赢 C7 领航... 3.2k 微密圈写真合集 3.19k 异性SPA/富婆男技师推油😍😜😜 111 资源搬运家 505 106短信/短信代发/短信卡发/机房卡发通道/国际... 506 全球CVV 一手CVV cVV鱼料 美国cvv 螃...
DASS-093 娇嫩巨乳女友被父亲戴绿帽被种逼。 - #沙月芽衣 #美少女 #巨乳 #NTR #中出 与 Takeru 约会的女大学生 Mei 去迎接 Takeru 的父亲 Ichiro。虽然自以为是儿子的女朋友，却对小芽一见倾心，原来小芽父亲所在的公司是一郎的子公司。 “如果你要结婚，你们现在应该住在一起，我会告诉你父亲的，”他说，利用他的地位让梅和他住在一起。
MIDV-326 与讨厌的粘人社长的壮阳药 Kimeseku...浑身是脏汁，被做为 Ikuiku Nana Yagi 服务的可爱秘书 - #八木奈奈 #羞辱 #秘书 #接吻 #潮吹 #爆汗 【无辜小秘书吃鱿鱼汁！ 】 娜娜的秘书公司被一家无良的IT公司收购，娜娜决定服务于一个天生性骚扰和权力骚扰的丑陋老头的社长。最坏男人让我喝壮阳药，我舔一身汗水满身是口水！可耻的服从强烈的高潮性交！春药腌生肉玩具培训！变得过于敏感的身体吹潮，口水找公鸡！秘书的新工作是用性感的汁水为您服务。
START-588 一个天真平凡的妻子被一对有换妻癖的变态夫妇灌输了NTR（牛头人）的观念！她被借给一对富裕夫妇后，落入了不道德享乐的陷阱。 #青空光 - #美咲佳奈 #姐姐 #人妻 #NTR #伴侣交换 园丁裕太和妻子光收到一对在那里工作的富裕夫妇的“换妻”邀请。患有勃起功能障碍的裕太，在目睹心爱的妻子被另一个男人拥抱并肆意侵犯的那一刻，竟勃起了。在不道德的快感唤醒下，两人陷入了四人性爱的泥潭，在不平等和羞耻交织中挣扎。
SONE-111 为了您最好的自慰，Marin Mita 可爱地看著您，刺激您的鸡巴，并微笑著一次又一次地接受射精......大量面部射液微笑自慰支持 - #三田真铃 #美少女 #手淫 #颜射 #自慰辅助 Masuzu Mita 在支撑下露出巨大的脸部射液微笑。 “你今天想做什么样的自慰？”“看到你的感觉…是最幸福的事情。”“你想要温柔但坚定的自慰吗？还是…暴力自慰？” “如果你还没射精…那是行不通的。”“很多。…射精了（心）”“我希望你射精更多…更多”无论你射精多少次太可爱的女孩的脸…一个让你感到非常高兴的世界。小丸子似乎想被你的精液覆盖，所以请继续支持她的自慰。当她看到你的感受时，她脸上的笑容就会增加，她会尽全力为你服务，直到耗尽精子。 <角标题> 01. 甜蜜温柔的 JOI（自慰指导） 02. 与忠诚的女仆微笑招待性爱 03. 与超可爱的初级员工醉酒而激烈的 性爱 04. 与被宠坏的女朋友亲密而轻松的性爱
Showing the 5 most recent of 5 posts we hold for @fulijibaobaoo. 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.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“🔞🎉AV艺术影片💞—霓虹影🔞” (@fulijibaobaoo), 822 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/fulijibaobaoo.
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.